Creating a list of Machines capable of power management for SCCM 2007 R3

Over on Technet there is an article stating that to create collection of machines capable of power management you should use the following query

select SMS_R_System.Name, SMS_R_System.OperatingSystemNameandVersion
from  SMS_R_System
inner join SMS_G_System_POWER_MANAGEMENT_CAPABILITIES
on SMS_G_System_POWER_MANAGEMENT_CAPABILITIES.ResourceID = SMS_R_System.ResourceId
where (SMS_G_System_POWER_MANAGEMENT_CAPABILITIES.RtcWake = "PowerSystemHibernate"
or SMS_G_System_POWER_MANAGEMENT_CAPABILITIES.RtcWake = "PowerSystemSleeping3"
or SMS_G_System_POWER_MANAGEMENT_CAPABILITIES.RtcWake = "PowerSystemShutdown")
and SMS_G_System_POWER_MANAGEMENT_CAPABILITIES.SystemS3 = 1
and SMS_G_System_POWER_MANAGEMENT_CAPABILITIES.PreferredPMProfile != 2
order by SMS_R_System.Name DESC

I believe there might be a problem in that query..

 SMS_G_System_POWER_MANAGEMENT_CAPABILITIES.PreferredPMProfile != 2

I think refers to the 'preferred power management profile' that is set by the OEM when creating the machine. See here for more info. By using the above query you are actually excluding all mobile type devices (laptops)

The proper query should be

select SMS_R_System.Name, SMS_R_System.OperatingSystemNameandVersion
from  SMS_R_System
inner join SMS_G_System_POWER_MANAGEMENT_CAPABILITIES
on SMS_G_System_POWER_MANAGEMENT_CAPABILITIES.ResourceID = SMS_R_System.ResourceId
where (SMS_G_System_POWER_MANAGEMENT_CAPABILITIES.RtcWake = "PowerSystemHibernate"
or SMS_G_System_POWER_MANAGEMENT_CAPABILITIES.RtcWake = "PowerSystemSleeping3"
or SMS_G_System_POWER_MANAGEMENT_CAPABILITIES.RtcWake = "PowerSystemShutdown")
and SMS_G_System_POWER_MANAGEMENT_CAPABILITIES.SystemS3 = 1
order by SMS_R_System.Name DESC

Bonus query for today.. All computer not capable of power management

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_POWER_MANAGEMENT_CAPABILITIES on SMS_G_System_POWER_MANAGEMENT_CAPABILITIES.ResourceID = SMS_R_System.ResourceId   where SMS_R_System.OperatingSystemNameandVersion like "Microsoft Windows NT Workstation %" and SMS_G_System_POWER_MANAGEMENT_CAPABILITIES. SystemS3 <> 1 

If you find this article useful please leave me a comment or click on an ad to show your support.

SCCM Distribution error "SMS distribution manager failed to process package" Message ID 2302

I was trying to update a package on a DP (Distribution Point) but the package kept failing with "SMS distribution manager failed to process package" Message ID 2302.  This error was only occurring one distribution point the rest were fine.

Taking a look into the distmgr.log on your SCCM sever showed me where the error was.

This particular package was failing to package up a Thumbs.db file (which it shouldn't be doing anyway) so I went to the source  files and deleted the file Thumbs.db and tried sending out the package again. This time it worked.

More Information:

List of Log Files in Configuration Manager 2007

What is Thumbs.db (windows thumbnail cache)

Other Users have also come across this issue:
MyItForum

I'm thinking about disabling the thumbs.db on the SCCM servers to prevent this from occurring again
Tweaks.com or Social Technet discussion 

If you find this article useful please leave me a comment or click on an ad to show your support.

SCCM DP's and Riverbed.

I've tested SCCM and riverbed's together. River bed makes a huge impact to how we consider deploying software to remote sites.

Somewhere along the lines of 90% descrease in WAN traffic when deploying a large app over several PC's.

WMI Query for Microsoft Word 2010 or greater

Select * from Win32_Product where name  like "%Microsoft Office Word%" and version >= 14

If you find this article useful please leave me a comment or click on an ad to show your support.

IBM please fix your Notes installer

During an upgrade you call MSI Custom Action  ibmUpdateRegForMultiUser
It tries to run in the User Context. The CA calls a UpgradeUtils.dll which must contain some code that when runs gets error 2

BUT!

Most installs of Notes are done under the system context hence the following error and the upgrade fails.

MSI ERROR: "UpgradeUtils/UpdateRegForMultiUser (Line 6743): Error - 'GetPropertyFromRegistry' for 'REGDATAPATHPROPERTY' failed with return code '2' - The system cannot find the file specified. 

If you find this article useful please leave me a comment or click on an ad to show your support.

Citrix Access Gateway and Vmware Workstation

I found that if you try to access CAG while the Vmware Network adapters are still live it will misconfigure your CAG connection and you will not able to access all resources.

Disable any VMware network adapters before connecting to CAG and this should workaround your issue.

If you find this article useful please leave me a comment or click on an ad to show your support.

Office 2010 installs Sharepoint components even when not enabled

I found that when you installed Office 2010 with the SP1 update it would install the Sharepoint component even when the component was disabled using a .MSP configuration file.

Microsoft acknowledges this as an issue but the fix isn't very clear.

What you need to do to resolve the issue at the package level is

• Download this update.
• Then unpack the EXE files into temp directory (use the /? to find out how to unpack the files)
• Next you need to copy the .MSP and .XML file in the office updates folder.
• Now copy the .DLL file in to the admin folder of your office install. 

Notes:

• This is only applicable for new Office 2010 SP1 installs not for existing installs
• This exact issue was mentioned in deployment jeopardy in Tech ED North America this year. 

If you find this article useful please leave me a comment or click on an ad to show your support.