bobrossi56
asked on
Migrating from Windows Server 2003 Small Business to Windows 2012 Std
I have a Dell server that is 6.5 years old and is running Windows Server 2003 for Small Business Server. This is the only server in my office so it acts as a domain controller, file server, houses the free SQL database as well as Quickbooks. It also controls DHCP and DNS. It has been causing us problems lately so we decided to buy a new Dell server.
Now I am tasked with migrating all the things the Windows 2003 Server does over to the Windows 2012 Std Server. I have never done this so I am seeking advise on the best practices, steps to use, etc.
I will put the new server next to the old server so copying all the users files over will not be an issue, but all the user accounts, printers, making this a domain controller, etc is puzzling me. Do I need to unjoin all the client PCs from the current domain and rejoin them to the new server's domain, and on and on...My goal is to get this cut over across a weekend, so when the users arrive Monday we are good to go.
Any help, pointers, etc are most appreciated.
Thx Experts...BobR
Now I am tasked with migrating all the things the Windows 2003 Server does over to the Windows 2012 Std Server. I have never done this so I am seeking advise on the best practices, steps to use, etc.
I will put the new server next to the old server so copying all the users files over will not be an issue, but all the user accounts, printers, making this a domain controller, etc is puzzling me. Do I need to unjoin all the client PCs from the current domain and rejoin them to the new server's domain, and on and on...My goal is to get this cut over across a weekend, so when the users arrive Monday we are good to go.
Any help, pointers, etc are most appreciated.
Thx Experts...BobR
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK, I think I have a plan that will work. Let me know what you think:
I will install new server on LAN next to DC1 old server, I will name it DC2 I will join the existing domain.
1. Copy all files and printers to New server
2. Setup DHCP and copy configuration to new serve
3. Promote new server to DC (with different name - DC2), it will replicate old servers AD, etc.
4. "Open" the shares and printers, test them
5. Deactivate old server's DHCP
6. Test new server's DHCP, DNS, and AD
7. Demote old server and turn off
8. Verify new shares and printers are working from new server
I will install new server on LAN next to DC1 old server, I will name it DC2 I will join the existing domain.
1. Copy all files and printers to New server
2. Setup DHCP and copy configuration to new serve
3. Promote new server to DC (with different name - DC2), it will replicate old servers AD, etc.
4. "Open" the shares and printers, test them
5. Deactivate old server's DHCP
6. Test new server's DHCP, DNS, and AD
7. Demote old server and turn off
8. Verify new shares and printers are working from new server
With one license of Windows 2012 R2 std you have licensed Hyper-V host plus two virtual machines. So I would install all of them. One virtual machine I would dedicate as domain controller and file/print server, the other should be used as SQL server.