This does not occur because of the Security Configuration Wizard ( scw.exe). A common configuration is to disable the service: This error occurs because a policy or an administrator prevents the DS Role Server service ( DsRoleSvc) from starting. The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.Īdditionally, you see that C:\Windows\Debug\dcpromoui.log contains the following line of text: When you try and perform the actions above through PowerShell, you receive the following error: The configuration change fails, and you receive an error, stating that the service cannot be started, either because it is disabled or because it has no enabled devices associated with it: Clone a virtualized Domain Controller by using dccloneconfig.xml.Remove Active Directory Domain Services from an existing Domain Controller by using the Uninstall-ADDSDomainController PowerShell Cmdlet from the AddsDeployment Windows PowerShell module.Remove Active Directory Domain Services from an existing Domain Controller by using Server Manager and the Active Directory Domain Services Configuration Wizard.Configure a new Domain Controller using the Install-ADDSForest, Install-ADDSDomain, or Install-ADDSDomainController PowerShell Cmdlets from the AddsDeployment Windows PowerShell module.Configure a new Domain Controller by using Server Manager and the Active Directory Domain Services Configuration Wizard.
It is not present by default on Windows Server 2012, but gets installed when the Active Directory Domain Services Server Role is installed, either through Server Manager or the Install-WindowsFeature PowerShell Cmdlet. The DS Role Server service ( DsRoleSvc) is new to Active Directory Domain Services in Windows Server 2012 and is used to install or remove Active Directory or to clone Domain Controllers. Its root cause is a policy or an administrator that prevents the DS Role Server service ( DsRoleSvc) from starting. Microsoft KnowledgeBase article 2737880, titled "The service cannot be started" error during AD DS configuration describes an issue where promotion of a Windows Server 2012-based server to a Domain Controller and demotion of a Windows Server 2012-based Domain Controller is unable to finish.
0 kommentar(er)
