Closed Bug 893888 Opened 11 years ago Closed 11 years ago

Please disable the "shutdown event tracker" on the gpo-managed Win64 build machines

Categories

(Infrastructure & Operations :: RelOps: General, task)

x86
Windows Server 2008
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: armenzg, Assigned: markco)

References

Details

''' The shutdown event tracker was disabled to avoid manual intervention after power outages and other improper shutdowns. This was done with this OPSI package, which sets the following registry key as follows: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Reliability\ShutdownReasonOn\REG_DWORD:0x0 ''' OR http://mxr.mozilla.org/build/source/mozharness/external_tools/count_and_reboot.py#25 os.system("shutdown -f -r -t 0") jhopkins, where do we reboot Win64 machines inside of briarpatch? I found these: https://github.com/mozilla/briar-patch/search?q=shutdown%28%29&ref=cmdform
Flags: needinfo?(jhopkins)
A clean shutdown won't trigger the dialog. It's when the computer crashes or the power is removed that we see this dialog. Kittenherder (or a human) can PDU-reboot a Windows build slave which results in an "unclean" shutdown. The kittenherder code is here: https://github.com/mozilla/briar-patch/blob/master/releng/remote.py#L357 (in rebootPDU()) Some instructions on how to disable the shutdown event tracker: http://blogs.technet.com/b/chenley/archive/2011/03/05/how-to-disable-the-shutdown-tracker-in-windows-server-2008-r2.aspx http://www.askvg.com/how-to-disable-remove-annoying-shutdown-event-tracker-in-windows-server-2003-2008/ We need to disable it on the existing win64 build slaves and the new win64 build slaves.
Flags: needinfo?(jhopkins)
Assignee: nobody → relops
Blocks: 781277
Component: Release Engineering: Platform Support → RelOps
Product: mozilla.org → Infrastructure & Operations
QA Contact: coop → arich
Summary: Please disable the "shutdown event tracker" on the Win64 build machines and/or use /c to give a comment to every reboot we do → Please disable the "shutdown event tracker" on the gpo-managed Win64 build machines
Mark can work on automating this for the new version of the builders that will be joined to the domain.
Assignee: relops → mcornmesser
This is now handled by the 2008_shutdown_tracker GPO, and the GPO has been linked to the builder OU. Computer Configuration-> Policies-> Administrative Templates-> System-> Policy-> Display Shutdown Event Tracker Disabled.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
I'm using the following sequence of commands to deploy (via ssh) and verify the fix on the win64 builders: reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Reliability reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Reliability /v ShutdownReasonOn /t REG_DWORD /d 0 reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Reliability /v ShutdownReasonUI /t REG_DWORD /d 0 reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Reliability
Blocks: 906660
No longer blocks: 906660
Q, markco: I've determined that I can run this to disable the shutdown event tracker: reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Reliability" /v ShutdownReasonOn /t REG_DWORD /d 0 Nevertheless, I cannot see gpedit.msc change and show the setting as "not configured" rather than "disabled". Is that expected?
I think that would be expected. Though the registry value has been changed, it was changed outside of the local group policy and there is no mechanism for that registry change to be communicated to gpedit.msc. I think there would be no impact by this either. Unless someone goes into gpedit.msc and enables the tracker. Then the registry value would be changed.
You need to log in before you can comment on or make changes to this bug.