{"id":2635,"date":"2011-09-29T23:31:58","date_gmt":"2011-09-29T21:31:58","guid":{"rendered":"http:\/\/contoso.se\/blog\/?p=2635"},"modified":"2011-10-02T21:31:50","modified_gmt":"2011-10-02T19:31:50","slug":"maintenance-mode-report-part-ii","status":"publish","type":"post","link":"http:\/\/contoso.se\/blog\/?p=2635","title":{"rendered":"Maintenance Mode Report (part II)"},"content":{"rendered":"

In the\u00c2\u00a0Notification and reporting for maintenance mode<\/a> post we created a report for every object that is in maintenance mode. I did a update to that script today, instead of showing all objects that are in maintenance mode the report now only show computer objects. You can download the script MMReport.txt<\/a> (rename to .ps1). As you can see on the last two lines in the script, the script is stopping it self.\u00c2\u00a0These lines are\u00c2\u00a0needed it you want to run the script from Orchestrator and the “Run Program” activity, else the activity will not finish and move on in the runbook.<\/p>\n

$objCurrentPSProcess = [System.Diagnostics.Process]::GetCurrentProcess();
\nStop-Process -Id $objCurrentPSProcess.ID;<\/p><\/blockquote>\n

If you want to run this in Orchestrator, for example\u00c2\u00a0every 15 minutes to generate a update maintenance mode report, you can use a “Monitor Date\/Time” activity and then a “Run Program” activity. You can configure the “Run Program” activity with the following settings<\/p>\n