Link to home
Get AccessLog in
Avatar of jpletcher1
jpletcher1Flag for United States of America

asked on

Cloning 2008 R2 VMs, SIDS, and WSUS

I have a group of production RDS servers running as VMs in VMWare.  I wanted to take one and clone it, then remove and readd it to the domain and use as a test RDS server.  I did this, and all appears to have worked well, but I think my new test server is now running with the same SID as the production server that I cloned it from because WSUS is goofy between the two.  I've read another article on here with someone that had the same issue, but I'm unclear what they did to resolve it.  My question is:

When you just "clone" a VM in VMware, it does not create a new SID.  What methods of copying/cloning a machine in VMware can I use that will give a new SID?  Do I need to create a template and then deploy from that?  Or will that not give a new SID either?  I don't want to lose all my RDS settings and customizations, and I need the server to stay as it is other than renaming it.
ASKER CERTIFIED SOLUTION
Avatar of Don
Don
Flag of United States of America image

Link to home
membership
This content is only available to members.
To access this content, you must be a member of Experts Exchange.
Get Access
SOLUTION
Link to home
membership
This content is only available to members.
To access this content, you must be a member of Experts Exchange.
Get Access
Avatar of jpletcher1

ASKER

Thank you for the responses.  Can someone please answer the specific questions I had asked about VMWare and which method of copying actually creates a new SID?

Also, if I do run sysprep will that blow away my current server configuration?
I'd try following dstewartjr's recommendation for generating a new SID on this VM, but moving forward, I would use sysprep for clones/templates.  All of the links I provided will help you get a clone/template/custom spec setup, which will create a new SID each time it's used.

The new SID's are created with sysprep.
dstewartjr - does this process you posted actually create a new SID or does it just get the server around the issue with WSUS?
Run Sysprep and generate a new SID, if you believe it is causing you issues.
hanccocka - since my server was cloned from a working RDS setup, if I run sysprep will that affect the functionality of the server?

Also, what methods of deploying copied/cloned virtual machines in VMWare will change the SID for me?
It generates a new SID, also a system SID and WSUS SID are 2 entirely different items.
If that bat file creates a new SID, will that affect things currently running on the server?

Also, does anyone know which methods of copying/cloning within VMWare will create a new SID?
"If that bat file creates a new SID, will that affect things currently running on the server?"


Not at all
I should have asked, does it create a new MACHINE SID or just a new WSUS SID?  Looking at the bat file, it looks like it creates a new WSUS SID only.  Just wanted to distinguish between the two.
WSUS