Comments for System Management Compendium

Comment on System Center Inventory Tool (SCIT) 0.4 released! by Muppie

Muppie — Fri, 03 Sep 2010 14:19:43 +0000

This is really nice, its like a consolidated view of my site all from one location. Thanks for taking time to script this Jeroen.

Comment on Trigger SCCM client actions by Nash

Nash — Thu, 19 Aug 2010 16:29:28 +0000

Thanks for posting the full list.

While I like sendsched.exe, WMIC is included on all XP/Vista/W7 machines already.

I had been using TriggerSchedule like this:
WMIC /node:”accounting1″ /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000021}” /NOINTERACTIVE

I didn’t realize you could just use ‘call requestmachienpolicy’ like Gary mentioned. I’ll have to look into that as it may simplify using WMIC so you don’t need to look at a table of UIDs to know what action is being done.

Comment on SCCM AD-based permission structure by Arnulfo Wahr

Arnulfo Wahr — Sun, 18 Jul 2010 21:11:16 +0000

I recently came across your blog and have been reading along. I thought I would leave my first comment. I don¡¯t know what to say except that I have enjoyed reading.

Comment on An honorable attempt to revive a SCCM server by Christoph Voigt

Christoph Voigt — Wed, 30 Jun 2010 09:08:53 +0000

Broken SCCM servers are always a great timesink. It’s a shame such vital systems are even allowed to become broken due to missing maintenance and monitoring.

For the last years our servers also had a few hickups, nothing that serious though. However – as you stated – sometimes you will reach a point with SCCM at which it is neither logical nor efficient to continue resolving a problem of which you dont even know why it came to be nor how to solve it. Let’s hope v.Next will solve a few problems with the design of SCCM (like SQL Replication instead of filebased)

Thanks for the hints

Comment on Windows updates monthly update cycle by Jeroen Erkelens

Jeroen Erkelens — Mon, 28 Jun 2010 04:31:47 +0000

PS: You should have (at least) 1 collection to define maintenance windows and (at least 1) collection to link the deployment to. It’s best not to use 1 collection for this. By following this, you can have 1 collection to deploy updates to (i.e. all computers) and divide them into multiple maintenance windows for flexibility

Comment on Windows updates monthly update cycle by Jeroen Erkelens

Jeroen Erkelens — Mon, 28 Jun 2010 04:27:21 +0000

Are you using one and the same deployment? If not, make sure the setting are appropriate.
Also, check http://www.sylvari.org/blog/2009/12/21/machines-affected-by-prompted-maintenance-window/ to see whether all machines are listed here (are in the same collection with the maintenance window)

Comment on Windows updates monthly update cycle by bravonomi

bravonomi — Sun, 27 Jun 2010 06:03:13 +0000

Hi ,
After Updates deployment my some server did restarted but few didn’t restart in maintenance windows … do you have any idea about this what could be the issue ?

Best Regards,

Comment on Windows updates monthly update cycle by bravonomi

bravonomi — Sun, 27 Jun 2010 05:59:57 +0000

Thanks Jeroen

Comment on Windows updates monthly update cycle by Jeroen Erkelens

Jeroen Erkelens — Sat, 26 Jun 2010 11:29:04 +0000

Hi, you most certainly can!

Comment on Windows updates monthly update cycle by bravonomi

bravonomi — Sat, 26 Jun 2010 11:01:12 +0000

Hi ,
can we deploy Windows Security and Critical update together in one deployment template?

Regards,