Install New AD Server & Move Active Directory Operations Master Role

Prerequisites List (Active Directory Server):

  • Install Server 2012 R2 Operating System.
  • Join server to the domain.
  • Install AD Services Roles
  • Promote the Server to a Domain Controller.

 Installing the Roles:

Open up Server Manager on your New 2012 R2 Server.


  • Once the server has initialized all its roles then click on Manage as shown above and then click on “Add Roles and Features”


  • Read through the information (if you knew to this), to continue click Next.


  • Select “Role-Based or feature-based installation” and click Next.


  • In my case I had multiple DC’s, I selected one, after that click Next.


  • Click on Active Directory Domain Services


  • Click “Add Features” and then click Next.


  • Review the summary and then click the Install Button.


  • Installation Starting.


  • Installation completed.
  • Click on “Promote this server to a domain controller”, you can either use the hyper-link above or click on the yellow exclamation in Server Manager next to the refresh button.


  • I chose option 1 “Add a domain controller to an existing domain”, then click on the select button to select your domain. After this click on change and enter the details of a Domain Admin. Once done click the Next button.


  • Select if this is a DNS server. Type in the DRSM password and store this password. Click the Next button.


  • Verify the information and click Next.
  • Review the options and then click Next.


  • The prerequisite check will run, you can view the warnings and click the Install Button.


  • Progress screen. This will replicate all information.


  • The above screen will appear when the installation is complete and your server will automatically restart after a min.
  • After the restart you will have a new domain controller in your environment.

Moving all Roles to the new DC:

To find which servers hosts what roles you can open up and elevated prompt and run the following:

  • netdom query FSMO

It will return the following information:

  • Schema Master                   DC Name
  • Domain Naming Master       DC Name
  • PDC                                    DC Name
  • RID Pool Manager               DC Name
  • Infrastructure Master           DC Name

After this we can run one command to move the roles to a new Domain Controller. Open up an elevated PowerShell Window and run the following:

  • Move-ADDirectoryServerOperationMasterRole -identity “DC Name” -OperationMasterRole 0,1,2,3,4

After that you can go back to your elevated prompt and query FSMO and it should show the name of the DC you moved the roles to.

Upgrade Exchange 2013 CU3 to SP1 (CU4)

Microsoft released the much awaited Service Pack 1 for Exchange 2013. The upgrade is similar to the previous CU’s. I hope the diagnostic error that has bugged exchange 2013 since release has been fixed. I have one server upgraded so we will see.

Lets start. First I will put one of my Exchange Servers in Maintenance Mode. Best practice as I have seen if you don’t do this DAG copies give problems. Here are the 4 commands I will be running. You can make this a PS1 script but I like making sure each command has successfully completed. Start Maintenance Mode:

  • Set-MailboxServer <Server Name> -DatabaseCopyActivationDisabledAndMoveNow $True
  • Set-ServerComponentState –Identity <Server Name> –Component HubTransport –State Draining –Requester Maintenance
  • Suspend-ClusterNode –Name <Server Name>
  • Set-MailboxServer –Identity <Server Name>–DatabaseCopyAutoActivationPolicy Blocked

(**You need to open up the Exchange Management Shell as Administrator or point 3 will give you a permission error**)

Now we need to first prepare the Schema and AD before we can proceed with the installation.

From an elevated prompt you can run the following commands:

  • Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
  • Setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

(**Note you need to have RSAT tools installed to prepare AD etc. You can do so by running the following command from the Exchange Management Shell: Add-WindowsFeature RSAT-ADDS)

Once both commands have run and finished you can now run the Exchange 2013 CU4 (SP1) setup. It will check for any updates which you can skip and the proceed to the upgrade screen.

Now that the setup has completed we need to take the server out of maintenance mode to resume normal operation. We need to run 4 commands again to Stop Maintenance Mode:

(**Remember you need to run these commands as an administrator from an elevated Exchange Management Shell)

  • Set-MailboxServer –Identity <Server Name> –DatabaseCopyAutoActivationPolicy Unrestricted
  • Resume-ClusterNode –Name <Server Name>
  • Set-ServerComponentState –Identity <Server Name> –Component HubTransport –State Active –Requester Maintenance
  • Set-MailboxServer –Identity <Server Name> –DatabaseCopyActivationDisabledAndMoveNow $False

Now that everything is online you can check the DAG Status etc.

Hope it helps

Export Exchange 2010 Database into PST format with default utility

export pst

Importing data from or exporting data to .pst file format is extremely easy using   MailboxImportRequest and MailboxExportRequest cmdlet. These both sets are part of Exchange Management Shell, after user has submitted the request of Import or export, the process is carried out by Mailbox Replication Service (MRS). The Exchange Mailbox Replication Service is available in Exchange 2010 Client Access servers. The MRS is the sole application or service that is responsible for transferring mailboxes and importing and exporting .pst files. Let us focus upon the possible causes that prompt user to go for Importing or Exporting mailbox data: Continue reading