Understanding Restartable AD DS
In most cases, where the AD DS need to be managed, you must restart in the directory service domain controller Recovery mode.
Windows Server 2012 is enabled Administrators can stop and start the AD DS Like any other service, and do not restart Domain controllers, do some Administrative tasks quickly. this feature The so-called restart Active Directory Domain Service.
Restartable AD DS to reduce the execution time required for their operations. You can stop AD DS This update can be applied to a domain controller. In addition, administrators can stop AD DS to perform Tasks, such as offline defragmentation of the Active Directory database, without restarting the domain Controller. Running on the server, and does not depend on AD DS to play a role in other services, Such as Dynamic Host Configuration Protocol (DHCP), remain available to satisfy client requests AD DS is stopped.
Restart AD DS by default in Windows Server running on all domain controllers 2012 there are no functional-level requirements or any other requirements for using this feature.
Note: You can not do the system state and stop AD DS domain controller recovery. To complete a domain controller system state recovery, we need to start the recovery directory service Mode (DSRM). However, you can do, and authoritative restore AD Active Directory objects DS is stopped by using Ntdsutil.exe.
Restart AD DS adds minor changes to existing Microsoft Management Console (MMC) Management unit. Display domain controller in the domain controller running Windows Server 2012 for AD DS Component Services snap-in and snap-in Computer Services (Local) node. Application The unit, the administrator can easily stop and restart AD DS the same way as any other service, running locally on the server.
Although stopping AD DS is similar to the Directory Services Restore Mode login, Restart AD DS provides a unique state, known as AD DS is stopped; it is a domain controller Running Windows Server 201
Understanding Restartable AD DS
Reviewed by Unknown
on
6:54 PM
Rating:
No comments: