Virtualize SBS 2003 - P2V vs migrating to new VM
Posted
by
jlehtinen
on Server Fault
See other posts from Server Fault
or by jlehtinen
Published on 2013-11-05T20:10:08Z
Indexed on
2013/11/05
21:56 UTC
Read the original article
Hit count: 259
windows-sbs-2003
|p2v
I need to virtualize a SBS 2003 server in my work environment. I need some tips on what people think is the best way to proceed.
Background: The SBS 2003 server is the primary DC for the domain and also hosts FTP, RRAS(VPN), DNS, and file shares. Exchange is NOT used, neither is SQL server. DHCP is done via a firewall appliance.
I have added a Server 2003 VM to the domain and promoted it to the DC role. AD/DNS is replicating here correctly. This was mainly done to provide fault-tolerance to the domain, I was not intending to make this VM the primary DC.
I've already asked about buying upgraded licensing for Server 2008/2012 but was refused due to cost.
Options: I see (at least) two routes I could take to complete this. From what I've read option 2 is the "preferred" method, but there's a few steps where I'm not clear on what to expect.
Option 1.) P2V the primary DC
- Power off primary DC
- Power off secondary DC (to prevent USN rollback in case P2V has issue)
- P2V (cold clone) primary DC
- Boot new PDC VM
- Allow new hardware to detect
- Remove old NIC hardware from device manager
- Assign old IPs to new virtual NICs
- Reboot PDC VM, confirm connectivity and no major issues
- Power on secondary DC, confirm replication
Option 2.) Create new VM, transfer roles, remove original DC from domain
- Create new VM, install SBS 2003
- Do I need the original SBS install discs for this? MS migration doc mentions this.
- Add VM to domain, promote to DC role
- Does this start 7 day timer where two SBS servers can be in same domain?
- Set up RRAS on new VM
- Set up IIS/FTP on new VM
- Move file shares to new VM
- Transfer FSMO roles to new VM DC
- dcpromo original primary DC out of domain
© Server Fault or respective owner