Book Image

Instant Migration from Windows Server 2008 and 2008 R2 to 2012 How-to

By : Santhosh Sivarajan
Book Image

Instant Migration from Windows Server 2008 and 2008 R2 to 2012 How-to

By: Santhosh Sivarajan

Overview of this book

Migrating to a new server involves a lot of decision making and planning. Windows Server 2012 comes with exciting new features and ease of use. This book will help you migrate to your new server in no time. "Instant Migration from Windows Server 2008 and 2008 R2 to 2012 How-to" provides you with many practical and real world scenarios in a step-by-step guide. It is designed to lead you through the entire process of migration.Beginning with an introduction to Windows Server 2012, the author then takes you through the installation and configuration of the server, before continuing on to migrate the existing services to Windows Server and how to decommission old servers. The ‚Äúhow-to‚Äù migration scenarios described are based on the author's own field experiences, guaranteeing real-world solutions. The scenarios include Active Directory, enabling a Remote Desktop, Print Server, and Hyper-V migration details. From the planning to  theimplementation phase, "Instant Migration from Windows Server 2008 and 2008 R2 to 2012 How-to" is your comprehensive guide for completing migration solutions.
Table of Contents (7 chapters)

FSMO role transfer/migration (Must know)


Transferring or migrating a Flexible Single Master Operations (FSMO) role is not a requirement at this point. However, some of the new features in Windows Server 2012 such as cloning of virtual domain controllers, and so on, won′t be available until the PDC emulator (PDCe) role is transferred to a Windows Server 2012 Domain Controller. To take advantage of improvements in RID Master, this role must be running on Windows Server 2012 Domain Controller. The placement and optimization of FMSO roles is beyond the scope of this book. For this scenario, we will be moving all FMSO roles (Schema, Domain Naming Master, PDCe, Infrastructure Master, and RID) to a new Windows Server 2012 Domain Controller.

How to do it...

Using PowerShell:

  1. Log on to Windows Server 2012 and open the PowerShell window.

  2. In the PowerShell window enter the following cmdlet:

    Move-ADDirectoryServerOperationMasterRole -Identity "DCName″ -OperationMasterRole SchemaMaster,DomainNamingMaster,PDCEmulator,RIDMaster,InfrastructureMaster
    
  3. To confirm the FSMO transfer, press Y.

Using MMC:

  1. Log on to the Windows Server 2012 Server or Windows 8 machine and open the Active Directory User and Computers (ADUC) MMC.

  2. Right-click on the domain name and select Operations Masters….

  3. In the Operations Masters tab, click on the Change button to transfer the FMSO role to the new Windows Server 2012 Domain Controller. Repeat these steps for transferring the PDC emulator and Infrastructure Master roles.

The forest-specific role—Domain Naming Master—can be transferred using Active Directory Domains and Trust MMC.

  1. Log on to the Windows Server 2012 or Windows 8 machine and open the Active Directory Domains and Trust console.

  2. Right-click on the Active Directory Domains and Trust node and select Operations Master….

  3. In the Operations Master tab click on the Change button to transfer the Domain Naming Master FMSO role.

The forest-specific role—Schema Master FMSO—can be transferred using the Active Directory Schema MMC. You may need to register schmmgmt.dll using the regsvr32 schmmgmt.dll command in order to view the Active Directory Schema MMC.

  1. Log on to the Windows Server 2012 or Windows 8 machine and open the Active Directory Schema console.

  2. Right-click on the Active Directory Schema node and select Operations Master….

  3. In the Operations Masters tab, click on the Change button to transfer the Schema Master FMSO role.

How it works...

The Move-ADDirectoryServerOperationMasterRole PowerShell cmdlet is part of the Active Directory PowerShell module. Instead of using FSMO roles, you could use numeric values. For example, 0 for PDC emulator, 1 for RID Master, 2 for Infrastructure Master, 3 for Schema Master, and 4 for Domain Naming Maser.

There′s more...

Alternatively, the NTDSUTIL tool can be used to transfer the FSMO roles. The domain-specific roles—RID, PDC, and Infrastructure Master—can be transferred using the Active Directory User and Computer (ADUC) tool.

The FSMO roles can be verified using the Netdom Query FSMO command as shown in the following screenshot:

The following PowerShell cmdlet can also be used to verify the FMSO roles:

Get-ADDomain domain.com | Format-List PDCEmulator,RIDMaster,InfrastructureMaster
Get-ADForest domain.com | Format-List SchemaMaster,DomainNamingMaster

Note

The Get-ADDomain PowerShell cmdlet is part of Active Directory PowerShell module.