asked on Cloning print server Virtual Machine
I have cloned an existing Print server and used the customization wizard so that the new Cloned VM will have its own SID. after the clone was created, then users were not able to connect to the Print server. I am not sure what would have caused the issue.
So I had to delete the cloned VM, then run Ipconfig/flushDNS on end users workstations, I believe I also ran Ipconfig/flushdns on the print server, I am not sure it is necessary.
when users brought up the issue, I was able to ping the print server by IP but not by name.
Users are now able to connect to the Print server, so I am not sure why the cloning would create the connection issue.
Any idea?
Thanks
So I had to delete the cloned VM, then run Ipconfig/flushDNS on end users workstations, I believe I also ran Ipconfig/flushdns on the print server, I am not sure it is necessary.
when users brought up the issue, I was able to ping the print server by IP but not by name.
Users are now able to connect to the Print server, so I am not sure why the cloning would create the connection issue.
Any idea?
Thanks
VMwareWindows Server 2008
Last Comment
jskfan
I'm assuming you cloned the print server, lets call it printserver1 to printserver2.
again assuming it's a member server in the active directory!
You then ran the customiation wizard (you could have just used sysprep).
printserver1 is still running??
printserver2 has now had sysprep run on it.. It's a member of the AD..
If my assumptions are correct..
You should have disconnected the NIC on printserver2, remove it from the AD, sysprep it, name it, enable it's NIC (in virtual hardware), give it an IP, add it to the domain.
Check both both your printservers are in the AD (active directory) and are registered correctly in DNS..
again assuming it's a member server in the active directory!
You then ran the customiation wizard (you could have just used sysprep).
printserver1 is still running??
printserver2 has now had sysprep run on it.. It's a member of the AD..
If my assumptions are correct..
You should have disconnected the NIC on printserver2, remove it from the AD, sysprep it, name it, enable it's NIC (in virtual hardware), give it an IP, add it to the domain.
Check both both your printservers are in the AD (active directory) and are registered correctly in DNS..
ASKER
the Ip address of the cloned VM has changed(different than the existing print server's IP).
I thought the customization wizard of vmware cloning is the Sysprep. through the wizard there is an option to create a new SID, I selected that.
I did not have time to check AD or do other things, because everyone was screaming , the print server is offline…..So I had to delete the cloned VM, and go around users workstation and flush their DNS resolver.
I thought the customization wizard of vmware cloning is the Sysprep. through the wizard there is an option to create a new SID, I selected that.
I did not have time to check AD or do other things, because everyone was screaming , the print server is offline…..So I had to delete the cloned VM, and go around users workstation and flush their DNS resolver.
Customisation with create new SID is Sysprep.
I'm not clear what were you trying to achieve? With this cloning project?
If you could explain, what you were trying to achieve in steps, we can probably work out what went wrong.
Were you trying to have two print servers on the network, or was this a replacement, e.g. a single print server?
why clone a good working print server, and then add another to the network?
If you could explain, what you were trying to achieve in steps, we can probably work out what went wrong.
Were you trying to have two print servers on the network, or was this a replacement, e.g. a single print server?
why clone a good working print server, and then add another to the network?
ASKER
in our network we do not have windows 2008 OS server without any applications installed on it. so to save time installing OS from scratch , I thought I could just clone a VM then remove the applications or services installed on it.
I picked print server so that I do not have to delete many roles just Print services Roles.
I bumped against the issue I described.
I picked print server so that I do not have to delete many roles just Print services Roles.
I bumped against the issue I described.
Okay, so you took an existing VM, which happens to be a Print Server, and you cloned it, and used Customization Specification, generated a new SID.
How did you do the above? What process did you do?
Once you had completed the CLONE, what did you do next with it?
How did you do the above? What process did you do?
Once you had completed the CLONE, what did you do next with it?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
markzz…that's the orthodox way to do it…create a pristine VM with OS installed and save it as a template
Thanks
however sometimes we try shortcuts that turn out are not really shortcuts.
regarding the licenses, it was not my goal for cloning.
Thanks
however sometimes we try shortcuts that turn out are not really shortcuts.
regarding the licenses, it was not my goal for cloning.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thank you Guys!
Was the correct IP Address and DNS registered?