These are the steps that worked for me: reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Reliability" /v ShutdownReasonOn /t REG_DWORD /d 0 reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Reliability" /v ShutdownReasonUI /t REG_DWORD /d 0 I'm not sure if ShutdownReasonUI is actually valid but I saw it at a blog post. This can be tested by shutting down the host with IPMI (hard shutdown), starting it up and using VNC to look at it. This was deployed manually for all of our current machines (including recently re-imaged) in bug 895914..
Are we talking about the task sequence, Windows Server 2008 R2 Deploy, we currently use to redeploy 2008 machines that are not under Group Policy control?
Correct. That way when we re-image a w64-ix-slave## it does not require manual steps. What is the timeline to switch to PGO managed machines? If it is happening soon, I would not want to bother you with this.
I am not sure on the time line. The image is mostly built, and currently I am working with Jhopkins on finishing it up. However, this is a minor change. I can implement it and test it today.
Have add a task sequence step, Disable shutdown tracker, under Custom Tasks: cmd /c reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Reliability" /v ShutdownReasonOn /t REG_DWORD /d 0 Tested this by doing a hard reset through IPMI. Upon reboot there was no Shutdown tracker.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
This is great! Thanks Mark; I've removed it from our post-imaging steps: https://wiki.mozilla.org/ReferencePlatforms/Win64#Post-reimaging_steps
You need to log in before you can comment on or make changes to this bug.