Counter

Transferring FSMO roles using cmd.

From the domain controller run cmd as administrator.

Execute the following commands :

- netdom query fsmo

- ntdsutil

- roles

- connections

- connect to server DC02      [Here give ADC name instead of DC02]

- quit

- transfer PDC

- transfer rid master

- transfer infrastructure master

- transfer schema master

- transfer naming master


That's it!!! FSMO role has transferred to other domain controller.

From Additional Domain Controller where you want to transfer FSMO, start cmd as administrator.

- netdom query fsmo

To check transfered fsmo:

repadmin \syncall



Comments

Post a Comment

Total Viewer

Popular posts from this blog

Installing Distribution Point in SCCM using PowerShell

<# .SYNOPSIS Install Distribution Point role using PowerShell Script .DESCRIPTION This scripts lets you install the Distribution Point role on a server, Enable PXE, PXE password and Multicast options. .PARAMETER DistributionPoint This the server name where you would be installing Distribution Point role. .PARAMETER SiteCode This is the 3 letter site code. .PARAMETER PXEpass This is the PXE password. .NOTES Version: 1.0 Date: 8-Dec-2016 Author: Prajwal Desai Website: http://PrajwalDesai.com Script Download: https://gallery.technet.microsoft.com/Install-SCCM-Distribution-bc4e7d76/file/165501/1/Install_DP.ps1 #> #Load the Configuration Manager Module import-module ($Env:SMS_ADMIN_UI_PATH.Substring(0,$Env:SMS_ADMIN_UI_PATH.Length-5) + '\ConfigurationManager.psd1') $Drive = Get-PSDrive -PSProvider CMSite CD "$($Drive):" #Site Code and Distribution Point Server Information $SiteCode = 'AAA' $DistributionPoint = 'YOUR SERVER
Read more

How to fix NSLOOKUP Default Server: UnKnown?

Image
Issue :  "Default Server:  UnKnown"  error on NSLOOKUP from Windows Server 2008 DNS Server. This issue is not a critical one. Even under this error your DNS resolution can work smoothly. But it's embarrassing when there are issues like this. Right?. Yes I know! me too. :D The reason for this is your DNS server does not posses a record for the server itself. Or simply it does not know what is it's own name. By creating a PTR static entry we can fix this and let DNS server know it's own name. 1. Open the DNS management console in the Server 2008          Start > Administrative Tools > DNS 2. Go to the your Reverse Lookup Zone icon and right click on it and select " New Pointer(PTR) ". 3. In the New PTR window enter the   IP address  of DNS server and enter(or select) the  host name  of the server. 4. Now click OK and  restart  the DNS server service. Now check to see if it is working.
Read more