Shutdownertron v1.2

[z4ydi]

I checked the application log on the server it says:

Event Type: Information
Event Source: Shutdownertron
Event Category: None
Event ID: 0
Date: 24/11/2008
Time: 11:26:18
User: N/A
Computer: FBSADMPDC01
Description:
Current settings:
Enabled: False
Hour: 0
Minute: 0
Delay: 60
Message: ''
AllowAbort: True
ShutdownMode: Shutdown

For more information, see Help and Support Center at Events and Errors Message Center: Basic Search.

[powdarrmonkey]

Ok those are the default settings if it can't get anything from GP... take a look in the registry at HLKM\Software\Policy\Shutdownertron, what have you got?

If you haven't tried it I would upgrade to 1.3, I changed the policy template a bit to make it more flexible later on.

[z4ydi]

I have reinstalled the new version and applied the policy to my test PC again and when I go to the registry of the test PC all the settings are applied, yet the machine wont shut down

[powdarrmonkey]

Can you paste your event log entry again please if it's any different now.

[z4ydi]

I dont get any event log error related to shutdownertron

[powdarrmonkey]

Not even logging its settings as the service starts? in which case the service hasn't started properly, check that it is running as the local system and try starting it manually. If it fails to start check the event log for related Service Control Manager entries, if it does start check for an entry from Shutdownertron to say what it's current settings are.

Edit: looking at your screenshot, there's a shutdownertron error logged at 11:53. This is a guess, but the service hasn't been upgraded and then restarted since you updated the policy template. Going between 1.2 and 1.3 the policy format changes slightly, and if you don't use the 1.3 agent it will crash nastily.

[z4ydi]

the version installed is 1.3. You can see from the image that there is no entry for Shutdownertron in the registry. but yet my test meachine has the right registry settings applied, posted in my previous post.

[powdarrmonkey]

Well where your previous screenshot of the registry looked correct, it now isn't - the policy isn't being applied to that machine properly. Fix that (try gpupdating it) and then post some event viewer events.