Cloning print server Virtual Machine
Posted on 2014-01-01
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.