Forum Discussion
Server 2008 unresponsive after WIndows Update
Better option is if it eventually starts up then I stand up a new one ASAP
I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting. Then stand up a new one (no newer that 2016 in case FRS is still used) , 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, transfer pdc emulator role, use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.
Other options are to verify system and servicing health by running;
sfc /scannow
also system update readiness tool
https://support.microsoft.com/en-us/kb/947821
Then check for errors in;
%SYSTEMROOT%\Logs\CBS\CheckSUR.log
Dave PatrickI was thinking dcdiag now that it might be up partially. The plan was to migrate to 2019, but that's 3 steps from 2008. I was also thinking Azure. We'll see. I just need to get this into a good state to move forward.
When I finally got into services, I saw that some services seem to be stuck at "Starting."
I've already done an SFC /scannow and it showed that it fixed errors. Maybe doing it again will help. I'll also look at the Readiness Tool and see if that helps.
Thanks for the suggestions.
Was able to run the dcdiag an the only errors it's showing is some services not started. Everything else looks okay from that perspective. Trying to run the System Update Readiness Tool.
Oh... and here's the kicker now that I can see services..... they've got Exchange on this box too. (The dcdiag's only errors were about Exchange services, so I'm looking through those.) Most of the services have started, but the rest are just slowly getting going. I guess they didn't know that everything was on the same server. :(
Then I'd stand up a new domain controller (following above) ASAP. In order to introduce the first 2019 domain controller the domain functional level needs to be 2008 R2 or higher and sysvol replication needs to be migrated from older FRS technology to DFSR
https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405For the exchange migration I'd reach out to experts in dedicated forums over here.
https://social.technet.microsoft.com/Forums/office/en-us/home?category=exchangeserver
Dave PatrickSlowly, but surely, everything seems to be coming up. It just takes a couple hours to do something that should take 10 seconds. The odd thing is, resource monitor doesn't show anything out of the normal as everyone is gone and I'm the only one on the box.
I can't stand up a new domain until the new hardware and OS arrive. But I'm giving them options. Since they're having problems, I figure that they just might go for a hybrid cloud solution so they don't have to worry as much about the technical stuff.
Sounds good, you're welcome.