You’re setting up your server, ready to roll out Active Directory Domain Services (AD DS), and bam! You hit a snag with error 0x800f031. Frustrating, right? We’ll guide you through the troubleshooting process to get your server up and running smoothly.
Table of Contents
Problem
You’re seeing “Error: 0x800f031” when trying to add AD DS on a Windows Server 2016 Standard. Despite running DISM and SFC commands, and ensuring no updates are pending, the error persists. The server’s been shifted from a domain to a workgroup and is now on a fresh network.
The detail error message as below:
The request to add or remove features on the specified server failed. Installation of one or more roles, role services, or features failed. Error: 0x800f031.
Add-WindowsFeature : The request to add or remove features on the specified server failed.
Installation of one or more roles, role services, or features failed. Error: 0x800f0831
At line:1 char:1
+ Add-WindowsFeature AD-Domain-Services
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (@{Vhd=; Credent…Name=localhost}:PSObject) [Install-WindowsFeature],
Exception
+ FullyQualifiedErrorId : DISMAPI_Error__Failed_To_Enable_Updates,Microsoft.Windows.ServerManager.Commands.AddWind
owsFeatureCommand
Solution 1: Verify server not connected to any AD domain
Verify that the server is not connected to any existing Active Directory domain. If it was previously joined to a domain, make sure it has been properly removed and restarted.
Solution 2: Check for residue
If the server was part of a domain, ensure no old domain settings linger. Clear any DNS settings that might point to a previous domain controller.
Solution 3: Review the DISM log
The path you’ve given, C:\Windows\Logs\DISM\dism.log, will have clues. Look for specific error messages that could point to the root cause.
Solution 4: Set static IP on server
Ensure that the server has a static IP address configured correctly and that the DNS server points to itself (10.1.10.123 in your case).
Solution 5: Metadata cleanup
If the server was a domain controller, perform a metadata cleanup. This removes remnants of the old domain controller from Active Directory.
Solution 6: Manual updates
Sometimes, manual installation of updates can resolve these issues. Check for the latest Service Stack Update (SSU) and Cumulative Update (CU) for your server version.
Solution 7: Re-attempt installation
Use PowerShell or Server Manager to try adding the AD DS role again. Try running the AD DS installation from the Server Manager GUI instead of PowerShell. Sometimes, the GUI can provide more informative error messages. If using PowerShell, run as administrator.
Solution 8: Clean installation
If the above steps don’t resolve the issue, consider performing a clean installation of Windows Server 2016 and attempt the AD DS installation again on the fresh system.
Remember, setting up Active Directory Domain Services can be complex, but with patience and systematic troubleshooting, you’ll have your server running smoothly in no time. Don’t hesitate to reach out for additional support if needed.