AD

 Commands to transfer fsmo roles

The primary command for transferring FSMO roles is Move-ADDirectoryServerOperationMasterRole in PowerShell, used with the -Identity parameter for the target server and -OperationMasterRole for the roles to move. Alternatively, you can use the older ntdsutil command-line utility by first navigating through roles and connections to select the server before using the transfer <role_name command. 

Using PowerShell (Recommended)

This method is more modern and straightforward.

1. Open PowerShell as an administrator. 
Run the command with the target server name and the role(s) you want to transfer. 
To transfer a single role (e.g., PDC Emulator):

Move-ADDirectoryServerOperationMasterRole -Identity <TargetDC> -OperationMasterRole pdcemulator 

To transfer all roles at once, specify them comma-separated:

Move-ADDirectoryServerOperationMasterRole -Identity <TargetDC> -OperationMasterRole pdcemulator, ridmaster, infrastructuremaster, schemamaster, domainnamingmaster 

You can also use numeric shortcuts for roles (0-4).

Using ntdsutil

This method is useful if you need to use the command-line utility for a specific reason. 

Open the Command Prompt as an administrator.
Type ntdsutil and press Enter.
Type roles and press Enter.
Type connections and press Enter.
To connect to the new server, type connect to server <server_name> (where <server_name> is the new server) and press Enter.
Type quit and press Enter to return to the FSMO maintenance prompt.
Type the command to transfer a specific role (e.g., transfer rid master) and press Enter.
Repeat for each role you want to transfer.
Type quit again to exit ntdsutil.

Important considerations

Role Seizure: 
If a domain controller is not online, you must seize the role instead of transferring it. For PowerShell, use the -Force switch. For ntdsutil, use the seize command. 
Permissions: 
The account performing the transfer must have the necessary permissions, such as being a member of the Schema Admins group for the Schema Master role. 
Replication: 
After a role transfer or seizure, the new role holder must wait for a successful replication cycle to become fully operational. 
Verification: 
After the transfer, use netdom query fsmo to verify that the roles have been moved to the correct domain controller. 

DHCP Lease Duration:

Minimum : 1 Minute

Default : 8 Days

Maximum : 999 Days 23 Hours 59 Minutes