Trevor Sullivan's Tech Room

Minding the gap between administration and development

Posts Tagged ‘microsoft system center configuration manager 2007’

ConfigMgr: Cleanup Software Updates Objects

Posted by Trevor Sullivan on 2011/11/29


Introduction

A common complaint I hear about Microsoft System Center Configuration Manager (SCCM / ConfigMgr) 2007 is the ability to clean up expired and superseded software updates from the objects related to software updates. As software updates are marked as expired or are superseded by newer software updates, Microsoft marks the old updates accordingly. Once an update has been retired, it is desirable for ConfigMgr administrators to remove the updates from deployments and reporting objects. This cleanup effort saves disk space for deployment packages, and can reduce unnecessary information from showing up in reports.

Read the rest of this entry »

Posted in configmgr, powershell, scripting, tools, wmi | Tagged: , , , , , , , , , , , , | Leave a Comment »

Failing software updates in SCCM / WSUS

Posted by Trevor Sullivan on 2009/10/09


I recently was troubleshooting an issue with some failing software update installations being deployed via SCCM / WSUS, and finally found out what was affecting them. All of the failed updates were related to Microsoft Office, so that kind of tells you something right there. It turns out, the root cause of the installation failure was that the “Office Source Engine” (short name ‘ose’) was disabled.

A quick, easy way to re-enable the service remotely is to use Windows PowerShell. Here is a command you can issue to set the start mode to manual:

(Get-WmiObject -Query “select * from win32_service where name = ‘ose'” -ComputerName RemoteMachine).ChangeStartMode(“Manual”)

The error messages I was getting in the UpdatesHandler.log are below:

WSUS update (32cd1fb9-5401-4025-b8dc-22a3b41060cc) installation result = 0x80070652, Reboot State = NoReboot
Update execution failed.
WSUS update (880f4592-a57e-4af6-ae6c-c2988519df4e) installation result = 0x80070652, Reboot State = NoReboot
Update execution failed.
WSUS update (8fe60694-94c6-4568-8094-17e2e92045ea) installation result = 0x80070652, Reboot State = NoReboot
Update execution failed.
WSUS update (938d8bbf-f928-4dac-baef-b66005583409) installation result = 0x80070652, Reboot State = NoReboot
Update execution failed.
WSUS update (ae97d343-7c0d-4c06-9a62-67eff01890a9) installation result = 0x80070652, Reboot State = NoReboot
Update execution failed.
WSUS update (bf20a84c-6662-4755-b60d-7fe3a090eb01) installation result = 0x80070652, Reboot State = NoReboot
Update execution failed.
WSUS update (e33db88f-49ab-4cce-aa24-16d952526b6b) installation result = 0x80070643, Reboot State = NoReboot
Update execution failed.
WSUS update (f6e3e036-eaf1-4423-9eab-9359a23fcb9e) installation result = 0x80070643, Reboot State = NoReboot
Update execution failed.
WSUS update (f75401a0-0419-48fc-8011-bb0b30c061f8) installation result = 0x80070643, Reboot State = NoReboot
Update execution failed.

Update (2009-10-29): I thought I had posted this somewhere, but I guess not. While the suggested PowerShell code above would work for a one-off fix, a better way to manage this configuration would probably be to use the Microsoft Group Policy Preferences Client Side Extensions (CSE). You can use these GPO extensions to enforce service configurations for systems with the CSE installed, thus reducing helpdesk tickets resulting from improper configurations (whether done maliciously or non-maliciously).

Posted in Uncategorized | Tagged: , , , , , , , , , , , , , , , | Leave a Comment »

SCCM Inventory – Group Policy Preferences

Posted by Trevor Sullivan on 2009/09/10


Update (2009-10-14): I’ve included a WQL query to use in creating a collection to identify systems without the GPP CSE installed.

If you want to discover which systems have the group policy preferences client-side extensions installed, you can add gpprefcl.dll to your software inventory policy on your ConfigMgr site server. This file resides in the System32 folder on a 32-bit OS, and in the SysWow64 folder on a 64-bit OS. The file description is “Group Policy Preference Client“.

Here is the WQL collection query I am using to identify Windows XP systems that do not have the GPP CSE installed:

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_R_System.ResourceId not in (select SMS_R_System.ResourceID  from  SMS_R_System inner join SMS_G_System_SoftwareFile on SMS_G_System_SoftwareFile.ResourceId = SMS_R_System.ResourceId where SMS_G_System_SoftwareFile.FileName = “gpprefcl.dll”) and SMS_G_System_OPERATING_SYSTEM.Caption = “Microsoft Windows XP Professional” and SMS_R_System.Obsolete = 0

Posted in configmgr | Tagged: , , , , , , , , | 3 Comments »

Running ccmsetup synchronously

Posted by Trevor Sullivan on 2009/09/04


I recently ran into a situation where my MDT task sequence was failing due to a couple failed application installs. The symptom was a return value of 1 coming from our Office 2007 and Office Communicator 2005 app installs.

I finally checked out the setup log file for Office 2007, and discovered that the MSIexec service was “busy.” I opened up the task sequence log and looked at what was running just prior to the Office 2007 install, and it turned out to be the SCCM client. Knowing that ccmsetup runs asynchronously, I started looking for a method of running it synchronously, so that the task sequence would not proceed before it completed.

As it turns out, the /NoService parameter to ccmsetup causes the SCCM client to install synchronously. This makes the installation of the client much more predictable, and reduces or prevents the conflict of SCCM and other software installations during a task sequence.

Posted in configmgr | Tagged: , , , , , | Leave a Comment »