sysprep on a new VM
Greetings,
I performed a PtoV and have my new VM created. I'd like to add this new VM to my existing domain, however from my understanding I will need to perform a sysprep. Before I did the PtoV within VMWARE Converter, the physical box was part of the domain. I'd like to change the hostname and rejoin, but I'd like to know how to do a sysprep. I appreciate your help!
Thanks,
nimdatx
I performed a PtoV and have my new VM created. I'd like to add this new VM to my existing domain, however from my understanding I will need to perform a sysprep. Before I did the PtoV within VMWARE Converter, the physical box was part of the domain. I'd like to change the hostname and rejoin, but I'd like to know how to do a sysprep. I appreciate your help!
Thanks,
nimdatx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Just to be safe, I'd remove it from the domain and place it in a workgroup before running sysprep.
No. Applications would be left alone. It just basically strips out the GUID, password, etc.
Of course, make a backup of your VM before just to be safe.
Of course, make a backup of your VM before just to be safe.
ASKER
cool. I'll put into workgroup, good idea.
No need to Sysprep really! either!
when you join the VM to the Domain, it get's a new Domain SID!
when you join the VM to the Domain, it get's a new Domain SID!
sysprep'ing a machine that has been in production is unsupported. Sysprep is intended for use with image creation - not "eventual" machine duplication.
if you are P2V'ing a system and will DESTROY the physical machine's install, then there is no need to worry about this - the machine remains unique on the network
If you are trying to duplicate a production system and the physical machine will remain online afterwards, basically, you can't and still be in a supported state.
If you created a base image using a volume license media and you want to make this a master copy, it SHOULD have been done in Audit mode, then sysprep is required.
Taking shortcuts can get you into trouble. Microsoft tests patches and updates by using SUPPORTED configurations. When you do things in ways Microsoft doesn't support, patches could one day BREAK your systems and you'd have no idea why and Microsoft may not be able to help. DO IT RIGHT!!
Finally SYSPREP is not JUST a SID Changer. It does a lot of things to ensure your Windows install is seen as unique on the network. Building deployable images REQUIRES sysprep, regardless of which tools you may want to use to image and deploy.
if you are P2V'ing a system and will DESTROY the physical machine's install, then there is no need to worry about this - the machine remains unique on the network
If you are trying to duplicate a production system and the physical machine will remain online afterwards, basically, you can't and still be in a supported state.
If you created a base image using a volume license media and you want to make this a master copy, it SHOULD have been done in Audit mode, then sysprep is required.
Taking shortcuts can get you into trouble. Microsoft tests patches and updates by using SUPPORTED configurations. When you do things in ways Microsoft doesn't support, patches could one day BREAK your systems and you'd have no idea why and Microsoft may not be able to help. DO IT RIGHT!!
Finally SYSPREP is not JUST a SID Changer. It does a lot of things to ensure your Windows install is seen as unique on the network. Building deployable images REQUIRES sysprep, regardless of which tools you may want to use to image and deploy.
ASKER