HKLM>Software>Microsoft>Windows Server>SetupĪs soon as i did that, the Wizard failed, and i was presented with the choice to hit ‘retry’.Īfter doing that the wizard went through and completed successfully. This fit in with what i was expecting in that the server was not registering the fact that it had been rebooted. I noticed that the Essentials registry Setup Key had a value for ‘ RebootExpected’. We did a manual DCPromo on the server and installed AD, but again the Essentials wizard was stuck on 17%.
What should happen is a reboot should occur, the wizard should push on to 25%, then by 39% DCPromo has completed and the CA is installed.ĭaniels server was stuck at 17% even after a manual reboot. SharedServiceHost-NotificationServiceConfigĪt 17% the SharedServiceHost-ManagementServiceConfig log shows us that IIS has been installed, and that the AD Binaries are being installed.At this point we had the following logs created in c:\programData\Microsoft\Windows Server\Logs He was also using a Portuguese language edition of the TP but reported the same issue with the English one, I got him to start over with the English one so I could read it!! His Lab was running on a Windows 10 workstation with Hyper-V. I volunteered to login to his server and check it out. He also reported that the environment had not changed and that previous TPs had installed correctly. He reported an issue he was having installing the Essentials 2016 TP4 OS which was stalling at 17% during the Essentials configuration Wizard.
This week I had a Skype conversation with a fellow MVP and friend from Brazil, Daniel Santos.
0 kommentar(er)
