On Jun 18, 6:30=A0am, Scott <Sc...@discussions.microsoft.com> wrote:
> I'm trying to use IIS Cert Wizard to temporarily copy the wildcard
> certificate from a production web server to a dev web server and then ins=
tall
> and apply the cert to the dev web server. When I specify the production w=
eb
> server's name and with userid and password having domain admin and enterp=
rise
> admin credentials, I am getting 'Access is denied' error. I tried giving =
that
> same user id NTFS full control on the inetpub\wwwroot directory and to th=
e
> actual certificate file with no luck. What do I have to do to enable the =
cert
> copy or, alternatively, perform some workaround to get the other server's
> wildcard working on the dev server?

"David Wang" wrote:

> On Jun 18, 6:30 am, Scott <Sc...@discussions.microsoft.com> wrote:
> > I'm trying to use IIS Cert Wizard to temporarily copy the wildcard
> > certificate from a production web server to a dev web server and then install
> > and apply the cert to the dev web server. When I specify the production web
> > server's name and with userid and password having domain admin and enterprise
> > admin credentials, I am getting 'Access is denied' error. I tried giving that
> > same user id NTFS full control on the inetpub\wwwroot directory and to the
> > actual certificate file with no luck. What do I have to do to enable the cert
> > copy or, alternatively, perform some workaround to get the other server's
> > wildcard working on the dev server?
>
>
>
> You need to be able to connect to the production web server's
> Certificate store, export (with private key) the desired certificate
> from the Local System's Personal store, and then re-import that key
> into your dev web server's Local System Personal Store.
>
> I don't know what you mean by "giving that same user id NTFS full
> control to the actual certificate file"
>
> What certificate file is that? If you have the PFX private key used on
> the Production Web Server, just import it into the same place I
> mentioned earlier.
>
> FYI: I don't have problems doing what you are trying to do remotely,
> even with just a normal user in the machine's Administrators group, so
> it seems like something specific to your environment is breaking your
> desired remoting functionality. And discovering how your general
> environment is broken (probably because someone else was a little
> overzealous in security lockdown) is a little beyond the scope of IIS
> or this newsgroup.
>
> It'd be easier for you to ask your support staff "what have people
> changed" on the server than to reverse engineer from the system what
> has changed/broken. And if people cannot tell you what has changed on
> the server from default -- that's a procedure problem that must be
> resolved within your organization. If people can make changes without
> anyone knowing, you are liable for much more damage than just failure
> to access a server remotely.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //