FAQShop.com : Creating a Collection for Laptops

Creating a Collection for Laptops

My client base is composed of a mix of Laptop and Desktop users. Many of our laptop users are based in remote/home offices as well as in our head office. I am looking for the easiest way to group all the mobile users into a collection and then further create sub collections based on their location. SMS 2.0 is set up as only one primary site.

I can do this based on the machine model being used or by directly adding them to a collection but I am looking for a more automated way if possible (since we have quite a mixture of machine currently).

Contributed By: Sangeetha Visweswaran [MSFT]
These are all the possible ways of finding out Laptops using hardware inventory.

Win32_SystemEnclosure, ChassisTypes(1)=10. This property when set to the value of 10 is equivalent to "notebook." However, not all computers provide this property. This class is defined in the SMS_def.mof but reporting is not enabled by default.

Win32_Battery or Win32_PortableBattery. If any instances exist, then the computer is probably a laptop. However, uninterruptible power supplies (UPSs) sometimes are reported as batteries, so this might not be reliable if some of your computers have UPSs. This class is defined in the SMS_def.mof but reporting is not enabled by default.

Win32_PCMCIAController. If any instances exist, the computer is probably a laptop. This class is defined in the SMS_def.mof but reporting is not enabled by default.

Win32_DriverVXD.Name = "pccard". If any instances exist, the computer is probably a laptop. However, this option only works on Windows 98 computers. This class and property are enabled for reporting by default.

Win32_ComputerSystem.Manufacturer. If you purchase your laptops from a different vendor than your desktop computer and server vendor, this value might reliably identify your laptops. This class and property are enabled for reporting by default.

Win32_ComputerSystem.Model. You might have to check for a variety of different models to cover all your laptops. This class and property are enabled for reporting by default.

Static record. You could define your own property in a MIF or MOF and set it when the computer is set up.

Power scheme. Laptops usually use the "Portable/Laptop" power scheme (number 1). This is a registry entry, so you have to use the following MOF:

#pragma namespace("\\\\.\\root\\cimv2")

// Registry property provider

instance of __Win32Provider as $PropProv

{

Name ="RegPropProv" ;

ClsID = "{72967901-68EC-11d0-B729-00AA0062CBB7}";

ImpersonationLevel = 1;

PerUserInitialization = "FALSE";

};

instance of __PropertyProviderRegistration

{

Provider =$PropProv;

SupportsPut =TRUE;

SupportsGet =TRUE;

};

#pragma namespace ("\\\\.\\root\\cimv2\\sms")

[ SMS_Report (TRUE),

SMS_Group_Name ("Power Management"),

SMS_Class_ID ("MICROSOFT|POWER_MGMT|1.0") ]

class Power_Mgmt : SMS_Class_Template

{

[SMS_Report(TRUE),key]

string index;

[SMS_Report(TRUE)]

sint32 CurrentPowerPolicy;

};

#pragma namespace ("\\\\.\\root\\cimv2")

[DYNPROPS]

class Power_Mgmt

{

[key]

string index = "current";

sint32 CurrentPowerPolicy;

};

[DYNPROPS]

instance of Power_Mgmt

{

[PropertyContext("local|HKEY_CURRENT_USER\\Control

Panel\\PowerCfg|CurrentPowerPolicy"),

Dynamic, Provider("RegPropProv")]

CurrentPowerPolicy;