How to use the WIN32_MassDeploy WMI Class to target devices

The Win32_MassDeploy WMI class can be used to target devices in specific departments or pilot systems. This is especially useful for Group Policy targeting.

Properties

Name: ReleaseChannel
Type: string
Registry path (32-bit): HKEY_LOCAL_MACHINE\SOFTWARE\MassDeploy|ReleaseChannel
This value is often set to “Pilot” while setting up a computer with an “IT” build, but it can also be set manually, or automatically with Group Policy.

Name: TargetConfig
Type: string
Registry path (32-bit): HKEY_LOCAL_MACHINE\SOFTWARE\MassDeploy|TargetConfig
By default, this value will match the build option chosen while setting up a device. e.g. If a PC was set up with an “Accounting” build, the TargetConfig value will be “Accounting” without the quotes.

Installation

The Win32_MassDeploy WMI class is automatically installed by the MassDeploy System Builder, but you can install it manually by running your “MassDeploy Windows Config” package.

Example Group Policy WMI Filters

In the Group Policy Management console, under WMI Filters, create a new filter called “IT Systems“. Add the following query:

In the Group Policy Management console, under WMI Filters, create a new filter called “Pilot Systems“. Add the following query:

Automatically Define Pilot Systems in Group Policy

You can use Group Policy Preferences to automatically define pilot systems, based on where your pilot users log on.

1. Open the Group Policy Management console
2. Create a new GPO called “Pilot system Targeting”
3. Edit the GPO and browse to: User Configuration\Preferences\Windows Settings\Registry
4. Create a New Registry Item with the following values:
   1. Action: Update
   2. Hive: HKEY_LOCAL_MACHINE
   3. Key Path: SOFTWARE\WOW6432Node\MassDeploy
   4. Value name: ReleaseChannel
   5. Value type: REG_SZ
   6. Value data: Pilot
5. Under the Common tab, enable “Item-level targeting”
6. Press the “Targeting…” button
7. Create a new “WMI Query” item:
   1. Query: SELECT OSArchitecture FROM Win32_OperatingSystem WHERE OSArchitecture = “64-bit”
   2. Namespace: Root\cimv2
8. Create a new “Security Group” item:
   1. Press the “…” button to find your “pilot users” group
   2. Select the “User in group” radio button
9. Press OK, and OK again
10. If you have any 32-bit systems, create another identical Registry Item with the Key Path:
    SOFTWARE\MassDeploy, and
    target OSArchitecture = “32-bit”

Automatically Define Pilot Systems in WSUS

You can use Group Policy to automatically sort computers into a WSUS “Pilot Systems” computer group, instead of manually updating the group each time a pilot user changes or rebuilds their computer.

1. Open the Group Policy Management console
2. Create a new GPO called “WSUS Pilot Systems”
3. In the Scope tab, under WMI Filtering, select “Pilot Systems”
4. Edit the GPO and browse to: Computer Configuration\Policies\Administrative Templates\Windows Components\Windows Update
5. Set the following values:
   1. Enable client-side targeting=Enabled
   2. Target group name for this computer=”Pilot Systems”
6. Open the WSUS admin console
7. Under <ServerName>\Computers\All Computers, add a computer group called “Pilot Systems”
8. Under Options\Computers, where “you can specify how to assign computers to groups”, select “Use Group Policy or registry settings on computers”