Win32_NamedJobObject

The Win32_NamedJobObject WMI class represents a kernel object that is used to group processes for controlling the life cycle and resources of the processes within the job object. Only the job objec...

The Win32_NamedJobObject WMI class represents a kernel object that is used to group processes for controlling the life cycle and resources of the processes within the job object. Only the job objects that are named are instrumented.

Methods

Win32_NamedJobObject has no methods.

Properties

Win32_NamedJobObject returns 4 properties:

'BasicUIRestrictions','Caption','CollectionID','Description'

Unless explicitly marked as writeable, all properties are read-only. Read all properties for all instances:

Get-CimInstance -ClassName Win32_NamedJobObject -Property *

Most WMI classes return one or more instances.

When Get-CimInstance returns no result, then apparently no instances of class Win32_NamedJobObject exist. This is normal behavior.

Either the class is not implemented on your system (may be deprecated or due to missing drivers, i.e. CIM_VideoControllerResolution), or there are simply no physical representations of this class currently available (i.e. Win32_TapeDrive).

BasicUIRestrictions

UINT32

Restrictions on a job regarding the user interface.

1 (0x1)

Desktop

2 (0x2)

Display Settings

4 (0x4)

Exit Windows

8 (0x8)

Global Atoms

16 (0x10)

Handles

32 (0x20)

Read Clipboard

64 (0x40)

System Parameters

128 (0x80)

Write Clipboard

Get-CimInstance -ClassName Win32_NamedJobObject | Select-Object -Property CollectionID, BasicUIRestrictions

Caption

STRING

Short textual description of the object.

Get-CimInstance -ClassName Win32_NamedJobObject | Select-Object -Property CollectionID, Caption

CollectionID

KEY PROPERTY STRING

Number that identifies a job object. Because they are kernel objects, job object names are case sensitive. However, Windows Management Instrumentation (WMI) keys are case insensitive and must be decorated to distinguish case. To indicate a capital letter, precede the letter by using a backslash. For example, “A” and “a” are lowercase and “\A” and “\a” are uppercase. This property overrides the CollectionID property in CIM_CollectionOfMSEs.

Get-CimInstance -ClassName Win32_NamedJobObject | Select-Object -Property CollectionID

Description

STRING

Textual description of the object.

Get-CimInstance -ClassName Win32_NamedJobObject | Select-Object -Property CollectionID, Description

Examples

List all instances of Win32_NamedJobObject
Get-CimInstance -ClassName Win32_NamedJobObject

Learn more about Get-CimInstance and the deprecated Get-WmiObject.

View all properties
Get-CimInstance -ClassName Win32_NamedJobObject -Property *
View key properties only
Get-CimInstance -ClassName Win32_NamedJobObject -KeyOnly

Selecting Properties

To select only some properties, pipe the results to Select-Object -Property a,b,c with a comma-separated list of the properties you require. Wildcards are permitted.

Get-CimInstance always returns all properties but only retrieves the ones that you specify. All other properties are empty but still present. That’s why you need to pipe the results into Select-Object if you want to limit the visible properties, i.e. for reporting.

Selecting Properties

The code below lists all available properties. Remove the ones you do not need:

$properties = 'BasicUIRestrictions',
              'Caption',
              'CollectionID',
              'Description'
Get-CimInstance -ClassName Win32_NamedJobObject | Select-Object -Property $properties
Limiting Network Bandwidth

If you work remotely, it makes sense to limit network bandwidth by filtering the properties on the server side, too:

Get-CimInstance -Class Win32_NamedJobObject -Property $property | 
Select-Object -Property $property

Selecting Instances

To select some instances, use Get-CimInstance and a WMI Query. The wildcard character in WMI Queries is % (and not “*”).

The parameter -Filter runs a simple query.

Listing all instances where the property Caption starts with “A”
Get-CimInstance -Class Win32_NamedJobObject -Filter 'Caption LIKE "a%"' 
Using a WQL Query

The parameter -Query uses a query similar to SQL and combines the parameters -Filter and -Property. This returns all instances where the property Caption starts with “A”, and returns the properties specified:

Get-CimInstance -Query "SELECT BasicUIRestrictions, Description, Caption, CollectionID FROM Win32_NamedJobObject WHERE Caption LIKE 'a%'"

Any property you did not specify is still present but empty. You might need to use Select-Object to remove all unwanted properties:

Get-CimInstance -Query "SELECT BasicUIRestrictions, Description, Caption, CollectionID FROM Win32_NamedJobObject WHERE Caption LIKE 'a%'" | Select-Object -Property BasicUIRestrictions, Description, Caption, CollectionID

Accessing Remote Computers

To access remote systems, you need to have proper permissions. User the parameter -ComputerName to access one or more remote systems.

Authenticating as Current User
# one or more computer names or IP addresses:
$list = 'server1', 'server2'

# authenticate with your current identity:
$result = Get-CimInstance -ClassName Win32_NamedJobObject -ComputerName $list 
$result
Authenticating as Different User

Use a CIMSession object to authenticate with a new identity:

# one or more computer names or IP addresses:
$list = 'server1', 'server2'

# authenticate with a different identity:
$cred = Get-Credential -Message 'Authenticate to retrieve WMI information:'
$session = New-CimSession -ComputerName $list -Credential $cred

$result = Get-CimInstance Win32_NamedJobObject -CimSession $session

# remove the session after use (if you do not plan to re-use it later)
Remove-CimSession -CimSession $session

$result

Learn more about accessing remote computers.

Requirements

To use Win32_NamedJobObject, the following requirements apply:

PowerShell

Get-CimInstance was introduced with PowerShell Version 3.0, which in turn was introduced on clients with Windows 8 and on servers with Windows Server 2012.

If necessary, update Windows PowerShell to Windows PowerShell 5.1, or install PowerShell 7 side-by-side.

Operating System

Win32_NamedJobObject was introduced on clients with Windows Vista and on servers with Windows Server 2008.

Namespace

Win32_NamedJobObject lives in the Namespace Root/CIMV2. This is the default namespace. There is no need to use the -Namespace parameter in Get-CimInstance.

Implementation

Win32_NamedJobObject is implemented in Wmipjobj.dll and defined in Wmipjobj.mof. Both files are located in the folder C:\Windows\system32\wbem:

explorer $env:windir\system32\wbem
notepad $env:windir\system32\wbem\Wmipjobj.mof