Microsoft stopped all its support for Windows Server 2008 R2 on the 14th of January 2020. So, those still using this version of the server will receive no additional patches for security after this date. Most Businesses initiate Server upgrades and Migration and contact their server Support companies for this upgrade. But, if you have not already scheduled the Migration of the FSMO roles or upgraded your system to a new version of the Server Operating System, this article will help you transfer your Windows server from 2008 R2 FSMO to 2019.
FSMO is an acronym for Flexible Single Master Operations. These are the type of particular tasks that the domain controllers of the Active Directories operate. Thus if the Microsoft Active Directories need to be migrated to a single server, then there can be an in-place update or a new installation of the 2019 version. Moving to a new Server requires Migration of the FSMO roles.
In place up-gradation of 2008 R2 FSMO role to 2019 Version
No step can directly upgrade Windows server 2008 R2 to 2019. The procedure will need three steps for the up-gradation of the servers, which are:
- Update from Windows server 2008 to 2012 or R2 2012
- Update from Windows Server 2012 to 2016 and
- Ultimately update from Windows Server 2016 to 2019
Another Option of Azure
Another alternative from Microsoft called Azure expands the support for Windows Server 2008 with security updates and patches. But the servers should be migrated to Microsoft Azure for three years. This might be a problem for users unwilling to invest money in new hardware. Migration of the FSMO roles is no longer required if you migrate to Azure, and Microsoft provides three years of support.
Installation of Active Directory in a Windows Server 2019
To install Windows 2019, log into the account with enterprise and domain admin rights on the member servers. The permissions are vital to add a domain controller to expand the schema and add to the active directory. Now let us check the procedures for the installation.
- Start a PowerShell prompt, and the command of Install-WindowsFeature AD-Domain-Services should be typed. The binaries will be added to the server through this command.
- The next module for ADDSDeployment is added by putting the Import-Module ADDSDeployment command to continue the operation of the Active Directory configuration from PowerShell.
- After adding the tools, input Test-ADDSDomainControllerInstallation -DomainName to examine the prerequisites.
- Next, the member server is promoted into the domain controller by implementing the command Install-ADDSDomainController -CreateDnsDelegation:$false -InstallDns:$true -DatabasePath ‘C:\Windows\NTDS’ –DomainName.
- The ADSafeMode password must be entered, and a reboot will begin an installation procedure.
- There will be several messages that will pop up on the PowerShell Prompt screen about the installation, the extension of the schema and the progress for replication will take place.
- At last, a restart will initiate once all the above steps are completed.
Migration of the FSMO roles to Windows Server 2019
The steps for Migration of the FSMO roles or the FSMO roles to the windows server 2019 are below.
- First, the replication errors need to be checked in the PowerShell prompt by running the command Get-ADReplicationFailure -scope SITE -target default-first-site | FT Server, FirstFailureTime, FailureCount, LastError, Partner –AUTO.
- Next, we must determine which roles are present in domain controllers using the following commands.
- To list off the two Active Directory’s comprehensive roles and check out which domain controller includes them, the command Get-ADForest Domain Name | Format-List SchemaMaster, DomainNamingMaster needs to be initiated.
- To list off the broad roles of the three Active Directory and to check out which domain controller includes them, the command Get-ADDomain Domain Name | Format-List PDCEmulator, RIDMaster, and InfrastructureMaster needs to be implemented.
- You can also transfer the five roles of FSMO from the existing location to the new domain controller by running Move-ADDirectoryServerOperationMasterRole -identity DC03- OperationMasterRole PDCEmulator, RIDMaster, InfrastructureMaster, SchemaMaster, DomainNamingMaster command.
- It will ask for confirmation before migrating the roles. After confirmation, the process is finished.
Checklists to tick before the Migration of the FSMO roles to the Windows 2019 server
Let us see the checklist to tick before beginning the process of up-gradation from 2008 R2 FSMO to 2019.
The active directory is working.
Make sure that the Active Directory is operating and nothing is broken. Microsoft offers many GUI tools and command lines to check this before beginning the up-gradation process.
Backup before Migration of the FSMO roles
Always create a backup of the 2008 RS FSMO roles. Stop all the enterprise applications running in the background for the consistent backup of the applications. Ensure that the system’s state and the Active Directory should also back up.
Upgradation of the AD Schema
The schema of the Active Directory needs to be updated to allow new features and functionality. This is one of the essential parts of the Migration of the FSMO roles.
Migration of the resources
If any shares are left in the old server, those need to be migrated to the Windows server 2019. Storage Migration service is the most suitable tool to transfer all the files and resources in one go.
Conclusion
This is a small effort to guide you on the Migration of the FSMO roles migrating Windows Server R2 FSMO to Windows Server 2019 from our side. The user can go for in-place or side-by-side up-gradation of the servers. Check the configuration of the systems. If something is not working, you can always change back to the previous version of the servers.
Server Consultancy is one of London’s best Server support companies, offering server upgrade and Azure migrations services for years. Get in touch if you need help with your server upgrade or request a callback by filling out the callback request form to discuss your upgrade.
Related Links