P
pstoric
Trying to put together my timeline/methodology for upgrading our current 2003 level domain domain to 2016.
Currently I’ve moved the five FSMO roles and DNS role off the 2003 box and onto our 2008 R2 VM (hosted on ESXi) but the Domain Functional level is still 2003 as I had an issue migrating DHCP off it. I’ve successfully used the export command “c:\temp\dhcp.txt all” to export and then import the .txt file onto the new DHCP serve many times and its worked without a hitch however while the import did work this time, the workstations were not able to contact the new DHCP server as they were getting the 169.xxx.xxx.xxx address for some reason. Still working on figuring that out but it may have something to do with that server being hosted on ESXi so I had to re-enable it on the 2003 box temporarily.
The goal is to end up with our Domain upgraded to 2016 and we have built a Server 2016 Hyper-V host with a 2016 VM that will be the new Domain Controller. Currently waiting for the product key to activate it as it’s in trial mode as of now.
Once I get my DHCP issue figured out I can demote that 2003 DC and upgrade our Domain Functional level to 2008. That’s where I have a question. I see FRS was depreciated after 2003 in favor of DFS-R which I can do via the DFSRMIG command but are there any other major changes or “gotchas” I need to be aware of other then the FRS to DFS-R migration? Also any other tips will come in handy
FYI no local Exchange here and the 2003 server is not a fileserver.
Continue reading...
Currently I’ve moved the five FSMO roles and DNS role off the 2003 box and onto our 2008 R2 VM (hosted on ESXi) but the Domain Functional level is still 2003 as I had an issue migrating DHCP off it. I’ve successfully used the export command “c:\temp\dhcp.txt all” to export and then import the .txt file onto the new DHCP serve many times and its worked without a hitch however while the import did work this time, the workstations were not able to contact the new DHCP server as they were getting the 169.xxx.xxx.xxx address for some reason. Still working on figuring that out but it may have something to do with that server being hosted on ESXi so I had to re-enable it on the 2003 box temporarily.
The goal is to end up with our Domain upgraded to 2016 and we have built a Server 2016 Hyper-V host with a 2016 VM that will be the new Domain Controller. Currently waiting for the product key to activate it as it’s in trial mode as of now.
Once I get my DHCP issue figured out I can demote that 2003 DC and upgrade our Domain Functional level to 2008. That’s where I have a question. I see FRS was depreciated after 2003 in favor of DFS-R which I can do via the DFSRMIG command but are there any other major changes or “gotchas” I need to be aware of other then the FRS to DFS-R migration? Also any other tips will come in handy
FYI no local Exchange here and the 2003 server is not a fileserver.
Continue reading...