question

BryceI-1452 avatar image
0 Votes"
BryceI-1452 asked DSPatrick commented

Physical Server 2016 Reboot Loop

Hello-
I have a Window Server 2016 installation running on a Dell PowerEdge T320 server. The server clears POST fine. When I get into the Window boot process, I get the Windows logo then Please wait for the Trusted Installer, followed by Getting Windows Ready....Don't turn off your computer. After several minutes, the server just reboots. Here is what I have tried:

  1. Startup Repair - Failed, but srttrail.txt says OS booted successfully.

  2. Enable boot logging. Nothing particularly revealing in the bootlog.

  3. Safe Mode / Safe Mode Network / Safe Mode Command Prompt - same reboot issue.

  4. Last Known Good Configuration - same reboot issue.

  5. DISM /scanhealth and /checkhealth - reported OK.

  6. DISM /cleanup-image /restorehealth. Had issues locating the source files though I mounted the downloaded Windows Server 2016 install.wim to c:\temp. Think this could be related to WSUS - which is running in this environment.

I do have backups of my files, which are on a separate D: spindle. This machine is a domain controller, though it does not hold the FSMO roles. My last System State backup is unfortunately from 6 months ago and questionable.


Suggestions? Thanks

windows-serverwindows-server-2016
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DSPatrick avatar image
0 Votes"
DSPatrick answered

machine is a domain controller, though it does not hold the FSMO roles

The simplest and recommended solution is to perform clean up to remove failed one, then stand up a new one for replacement.
https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup
https://techcommunity.microsoft.com/t5/itops-talk-blog/step-by-step-manually-removing-a-domain-controller-server/ba-p/280564

After cleanup I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2016, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.


--please don't forget to Accept as answer if the reply is helpful--






5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

BryceI-1452 avatar image
0 Votes"
BryceI-1452 answered DSPatrick commented

Thanks for the prompt reply!

Do you think the remove crashed DC from AD followed by metadeta cleanup via ntdsutil is simpler than:

Dcpromo / AllowDomainControllerReinstall:yes.

I have never used that switch and am hopeful but leery.

· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I'd do the cleanup following the links I provided. It is a very simple process, then you can rebuild failed one with same name (if desired) following steps above.

--please don't forget to Accept as answer if the reply is helpful--





0 Votes 0 ·

Agreed. I think that is the safer, more reliable route. /AllowDomainControllerReinstall is too big of an unknown.
Thanks

0 Votes 0 ·

Sounds good.

--please don't forget to Accept as answer and vote up if the reply is helpful--


0 Votes 0 ·
Show more comments