Thursday, July 05, 2012 2:55 PM
Environment: All servers are 2008 R2, 64 Bit
On VSHOST2, RDS1 is a working VM. It functions as a Remote Desktop (Terminal) Server. RDS1 is a production server, in use (but I can shut it down off-hours if needed). I do not want to sysprep it!
Plan: "Clone" RDS1 to become RDS2, which will run on VSHOST3. I know Hyper-v does not have a cloning function, so after doing a bunch of reading, I have a process I want other geeky eyes to look at.
VHD "Cloning" Procedure- is this going to work?
- On VSHOST2: Shut down RDS1 (to avoid domain conflicts).
- Copy RDS1 VHD file
- Rename copy to RDS2
- On VSHOST3: In Hyper-v, create new VM
- Attach copied now-named RDS2 VHD to VM
- Start RDS2
- Run sysprep on RDS2 giving new computer name of RDS2 and new IP
- On VSHOST2 Restart RDS1
In the past, I have run into "General access denied" errors when attaching and importing and have had to run icacls commands - I am prepared for that.
I cannot afford to purchase the Hyper-V management software, so please do not suggest that.
Thanks everyone -
Thursday, July 05, 2012 3:27 PM
Yes, as long as you do not connect the copy (RDS2) to the network before running sysprep, it should work. If a conflict should occur (such as RDS2 attempting to contact the domain as RDS1), just unjoin and then rejoin the VM's to the domain under different names.
"I cannot afford to purchase the Hyper-V management software, so please do not suggest that." --- You don't have to. SCVMM 2008 R2 currently also use sysprep when deploying virtual machine templates into production, so the end results would pretty much be the same.
- Marked As Answer by Vincent HuModerator Thursday, August 09, 2012 7:49 AM
Thursday, July 05, 2012 3:53 PM
Thank you so much for your prompt reply! Guess what I'm doing after hours tonight??