Reboot pending status messages

[Count430]

Hello SMS community..

I keep seeing the "Reboot pending" when I run my report labled "Advertisements for a specific package"

I pushed out security updates to 1500 machines where 100 of these machines ran the updates successfully accordding to my Execmgr.log and the eventvrw logs.

The Mif file is also located and passes the status for the client.

But my reports continue to generate the "Reboot Pending: status for these machines... Heeelllppp!

Any assistance with this would make my Xmas this year...

Thanks and Happy Holidays to all...

 

[tbrennans]

SMS will only reboot if there are certain situations, for instance if the machine is locked it wont reboot,

if say Outlook is open sms wont reboot, so to fix that you have to use manually reboot or have the patch do it.

so perhaps these machines really didnt reboot, have a user manually reboot one and see if it updates it.

personally I never let the sms reboot.

 

[tbrennans]

switches on a patch like this::

PatchInstall.exe /g:0 /f /s /q /c:0 /t:30 /m:

 

[Count430]

Thanks tbrennans...

This switch info is very useful, I have the correct command line parameters, I guess what Im asking is how to determin what's causing the machines to hang. Instead of rebooting once the updates are complete.

Out of the 1500 machines, the 100 will not generate the correct status until the end user manually restarts the PC.

It's the lack of knowledge pertaining to how to troubleshoot application installs on a system and read the corresponding logs.....

Here's the message I get in SMS below...

"The program for advertisement "USA20ABD" ("APC003C5" - "Install - Security Patches December 2005 - America") returned an exit code of "0"(" "), which indicates the operation was successful but a restart of the system is required for the operation to be complete.

 

[Count430]

Okay, I here's what I discovered, the systems with the "reboot pending" status have lot's of files in the winnt\temp folder.

In addition to the "PendingFileRenameOperations" key created in the registry.

This looks like it's leaning towards applications running on the desktop with key files open.

Thanks again...

 

[Count430]

False alarm! I mis diagnosed this one and still can't find why these systems won't reboot after running my updates via Vbscript. As for the commandline the proper switches are in place...

If anyone has seen this before I would be greatful for any information with this problem.

We re-ran the advertisments but received the same results.

 

[psionics1]

I am also seeing this exact error on about 17% of the machine I deploy to. I can't figure out what it is right now but I'm starting to examine the possibility of it being a rights issue.

 

[Count430]

Thanks tbrennans

Be careful, if these machines are in the right groups and have the base policies and security your company uses it could in fact be a locked machine, or other service preventing the reboot.

We've seen mixed results accross the network, however we started using the Win32Shutdown call from WMI to reboot the stubborn machines.

Thanks again...