If you want to view those machines that are not in compliance you can click on Non-Compliant and it take you to another report that provide you with a list of those machines. In this dashboard, you find general information about the reboot pending check baseline and how your environment is reporting against it. The first report is call Dashboard - Reboot Pending Check PFE V1 Reporting of those clients pending reboot, here is one of the interesting information.Ĭreate reports that will show how those machines that have a reboot pending.įor this we have created a series of reports to help you get this information. We will use this collection later on to perform a manual remediation of those clients. For this case, create a Non-Complaint collection. One of the options is to create a new collection based on the compliance status, you just need to right click on it and create the collection that you need. Once the configuration item is completed, lets create a configuration baseline to deploy it to all the configuration manager desktop clients.ĭuring the deployment of the baseline you will specify how often you want it to check against the system, here you can set it to everyday or once a week it depends on your environment. The CI will identify if the reboot is needed from the machines or not and if it’s required will be listed as non-compliant. Note: The GetPendingReboot PowerShell script was modified to fit the needs of this configuration item, its suggested to use the provided CI instead of creating a new one. We created a new Configuration Item that will use a PowerShell script for the compliance check. To be able to implement this challenge we try to use a Configuration Item to run it against each machine. To know more about this PowerShell script you can read it on the Scripting Guy:įind the best way to implement the script with ConfigMgr. Use a PowerShell script that was already wrote to accomplish this.Ĭopy of the PowerShell script created by Brian Wilhite Getting a report that will display the reboot pending status of machines. Let's see how I was able to accomplish it. For my benefit the article was writing by one of my peers, so I reach out to him and ask him a few questions about the script and how I could use it inside ConfigMgr. So during my research I found one article that talk about getting this information using PowerShell, I found this very interesting and start thinking on the best way for me to accomplish this using ConfigMgr.
I told him this was not an easy task to be performed in ConfigMgr 2012 due to the many parameters that makes a machine in need of a reboot. First published on TECHNET on Jun 27, 2014Ī few days ago one of my peers ask me a very interesting question, how can I get a report that show reboot pending machines.
0 kommentar(er)
