Fredric Robinson
asked on
Server 2008 R2 migration to Server 2019 Standard
I have a client that wants us to migrate their existing Server 2008 R2 Enterprise to Server 2019 Standard. We will be provisioning the new server from scratch so I want to make sure that we have the new server properly configured before we start the process. Can anyone direct me to a resource where I can find the exact steps required to move the AD and all of the data on the old server to the new server. I am hoping that when everything is finished all the users have to do is to log off and then log back in and all of their settings, desktops and files etc. are available to them. I am contemplating getting our NOC help desk involved to do this or if the instructions are starightforward then we will do it on our own. We are efficient at provisioning servers but we have never attempted a migration.
Your new server should be a VM. That is standard for deployment.
There are guides provided by MS (a quick search of "2008 AD to 2019 migration guide" will give you those)
That said the basic steps for any AD move is to AS said above check health of AD.
Load the OS on the new server (I don't agree that VM is standard as it doesn't fit all scenarios but is more common place now days)
Once your Server is online and joined to the domain add the AD role to the server.
Once AD and DNS etc are on the server you will then need to move the FSMO roles to the new server.
As said above the roles / functions the server provides directly effects the order / steps so start there as kevinhsieh indicated.
That said the basic steps for any AD move is to AS said above check health of AD.
Load the OS on the new server (I don't agree that VM is standard as it doesn't fit all scenarios but is more common place now days)
Once your Server is online and joined to the domain add the AD role to the server.
Once AD and DNS etc are on the server you will then need to move the FSMO roles to the new server.
As said above the roles / functions the server provides directly effects the order / steps so start there as kevinhsieh indicated.
ASKER
this has been very helpful. I read the documentation, view several video demos and now I have a few other questions. What about \user, homes$, profiles$ folders etc.? How are they moved over to the new DC? I would assume the data would be moved over manually. When everything is said and done I would expect that the workstationsn on the network would restart their computers and upon restart they would be connected to the new DC and their environment would be as it was prior to the new DC being put into place? I may have to recreate the shares to company data.
ASKER
another question, are their any roles that shouldn't be configured in the new server in addition to leaving out AD roles until the migration process begins?
ASKER
have any of your heard about server-essentials.com migration guides?
Lots of roles should not be on a DC, including Exchange, RDS Session Host, public IIS, and others that I would be wary of including SQL and SharePoint.
File server migration can be its own book. It depends on how is it being used? Are there just drive mappings? What about home folders specified by user? Redirected folders? IIS mappings? How about drives that users map? How are drives mapped? What about linked documents in Microsoft Office? Did someone already exercise excellent forethought and use DFS Namespace? Any copiers or scanners scanning to file server?
I would certainly want to implement DFS Namespace if it doesn't already exist. If makes future migrations very easy. Just copy data and modify the DFS Namespace. Windows clients don't need to be touched or even rebooted.
File server migration can be its own book. It depends on how is it being used? Are there just drive mappings? What about home folders specified by user? Redirected folders? IIS mappings? How about drives that users map? How are drives mapped? What about linked documents in Microsoft Office? Did someone already exercise excellent forethought and use DFS Namespace? Any copiers or scanners scanning to file server?
I would certainly want to implement DFS Namespace if it doesn't already exist. If makes future migrations very easy. Just copy data and modify the DFS Namespace. Windows clients don't need to be touched or even rebooted.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks guys, I fully understand now what has to be done. It makes since about dfs namespace, however in this situation they only have one folder shared so recreating the share on the new server will be very easy. Thank you both.
If you're in luck, everything is already using a DFS Namespace for pile path mapping.
Exchange, WSUS, SQL, all have their own migration paths.
AD is relatively straightforward. Be sure AD is healthy and using DFSR for SYSVOL replication.
https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405