How to setup a Compliance Baseline for computers that are in Reboot Pending state

want to make sure I am doing it right. Getting lots of "Failure Count" when I run the baseline for Pending Reboots.

below is what I have created for the configuration Item

created a "Configuration Item" with settings to run the following powershell script - "Invoke-WmiMethod -Namespace "ROOT\ccm\ClientSDK" -Class CCM_ClientUtilities -Name DetermineIfRebootPending  | select-object -ExpandProperty "RebootPending""

Set the compliance rule for Reboot Pending\Reboot State to Equal "False"

On some Collections (based on location/site), I am getting some results. but on some collections are am not getting any results.

Clients Settings - Computer Agent - Powershell execution policy = Bypass

Now, if I run this command (Invoke-WmiMethod -Namespace "ROOT\ccm\ClientSDK" -Class CCM_ClientUtilities -Name DetermineIfRebootPending) from my test computer that actually needs a reboot, it states as False in the "Reboot Pending" attribute.  I also changed the ExecutionPolicy on my test computer to "Unrestricted" to see if it was a powershell issue. 

Could it be GPO related?

thanks

June 17th, 2015 11:38am

anything at all in the logs?

http://blogs.msdn.com/b/scom_2012_upgrade_process__lessons_learned_during_my_upgrade_process/archive/2012/09/21/compliance-settings-sccm-2012.aspx

You could try and deploy a powershell script to a problematic device, something simple like

New-Item c:\windows\temp\mytest -type directory

Are general deployments working to those devices?

Free Windows Admin Tool Kit Click here and download it now
June 17th, 2015 12:07pm

I have deployed powershell scripts before in SCCM, as long as I add the -executionpolicy bypass in my command line.

not sure why I am not getting the right results when I run this command (Invoke-WmiMethod -Namespace "ROOT\ccm\ClientSDK" -Class CCM_ClientUtilities -Name DetermineIfRebootPending) from powershell

June 17th, 2015 12:17pm

here is the latest.  I am now getting results within my Compliance Baseline and the Collections base on this compliance baseline rule.  I re-applied the sccmclient policy with setting stated above. 

I manually ran windows updates and applied a security update that requires a reboot.  I left the computer running all night to see if it shows up in my collection that requires a reboot. It does not.  In the Configuration Manager Properties > Configuration tab, I noticed that the Assigned configuration baseline for my "Reboot Pending", it shows as compliant.  Question - could this means that it will only show non-compliant if security updates were pushed via sccm?

thanks

Free Windows Admin Tool Kit Click here and download it now
June 17th, 2015 1:23pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics