Moving Licensing & Certificate Server



Hi all.
I need to change the hardware that is hosting my Licensing & Certificate
Server (Win2K Server in a Win2K AD). I had this machine die suddenly once
and it was a bit of a hassle to get things setup again. As I am "Planning"
the shift this time I am hoping to avoid some of the hassles.

I have checked Article ID 306578 for deactivating and reactivating the
License server, but there is no info about saving and restoring the current
info. Do I just start from the beginning again and need to authorize the
clients again?

Same question about the certificate server, do I end up with a clean slate
and have to certify the WSs again?

Like I said trying to make this as painless as possible and any suggestions
are welcomed.


--
Thanks for your Time.
Remove the kNOT to reply.
But it is best to share it with the group.




.



Relevant Pages

  • Terminal Services confusion...
    ... Terminal Services and if we are over-loaded on licensing. ... The 2nd licensing server is on our old, Citrix Metaframe box (win2k server) ... we have about 20 various Windows servers ...
    (microsoft.public.windows.terminal_services)
  • SSL problem on IIS5 - Win2K Server
    ... I am trying to install a secured site on a Win2K Server ... the server certificate. ...
    (microsoft.public.inetserver.iis.security)
  • Re: SSL problem on IIS5 - Win2K Server
    ... > I am trying to install a secured site on a Win2K Server ... It also works fine with HTTP on the Server ... > the server certificate. ...
    (microsoft.public.inetserver.iis.security)
  • RPC over HTTP, Microsoft solution
    ... Exchange Server 2003 RPC over HTTP Deployment Scenarios ... Place a check in the box next to 'Certificate Services' and click 'Yes' ...
    (microsoft.public.exchange.setup)
  • Re: OWA 2003 w/ Smart Card Authentication.
    ... Exchange 2003 server via ActivSync. ... the IIS certificate. ... Whether or not authentication will succeed is completely dictated by ... Server's SSL certificate must be configured on root of v-server via ...
    (microsoft.public.exchange.connectivity)

Loading