When bm-vmware12 died today we had to restart several windows slaves after an unclean shutdown. This broke the auto-login process because Windows required a reason for the unexpected shutdown in the Shutdown Event Tracker. We should disable this functionality, so that we don't have to touch every windows slave in the aftermath of an unexpected ESX outage. Something like this probably http://support.microsoft.com/kb/555541
I'm writing a few other OPSI packages this week, I may as well grab this.
Assignee: nobody → bhearsum
Created attachment 415664 [details] [diff] [review] disable the shutdown event tracker Just ran this through testing on win32-slave21. Turns out it's controlled by a different registry key on Windows 2003, but still easy enough to control. Also, we have to delete the entire "Reliability" key to turn it off.
Attachment #415664 - Flags: review?(nrthomas)
Comment on attachment 415664 [details] [diff] [review] disable the shutdown event tracker (In reply to comment #2) > Also, we have to delete the entire "Reliability" key to turn it off. Looks like we're creating that key when we "install" so that's fine by me.
Attachment #415664 - Flags: review?(nrthomas) → review+
Comment on attachment 415664 [details] [diff] [review] disable the shutdown event tracker changeset: 26:adf0da4acda2
Attachment #415664 - Flags: checked-in+
I've set this package to install on all of the Build slaves and the ref platform. Should be picked up by everything in the next 24h or so.
All the slaves and the ref platform have this now. I didn't deploy on the Talos machines because it's not enabled on XP or Vista by default.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.