CIM/WMI cmdlets in PowerShell - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to get all running processes using CIM cmdlet.

PowerShell

Get-[1] -ClassName Win32_Process

Drag options to blanks, or click blank then click option'

AGet-WmiObject

BGet-Process

CGet-Service

DGet-CimInstance

Attempts:

3 left

💡 Hint

Common Mistakes

Using Get-Process which does not use CIM/WMI.

Using Get-Service which lists services, not processes.

The Get-CimInstance cmdlet retrieves instances of CIM classes, such as Win32_Process, which lists running processes.

2fill in blank

medium

Complete the code to filter processes with the name 'notepad' using WMI cmdlet.

PowerShell

Get-[1] -Class Win32_Process -Filter "Name = 'notepad.exe'"

Drag options to blanks, or click blank then click option'

AGet-WmiObject

BGet-Process

CGet-Service

DGet-CimInstance

Attempts:

3 left

💡 Hint

Common Mistakes

Using Get-CimInstance which uses -Query instead of -Filter.

Using Get-Process which does not support -Filter.

Get-WmiObject is the older cmdlet to query WMI classes and supports the -Filter parameter for filtering.

3fill in blank

hard

Fix the error in the code to get the operating system info using CIM cmdlet.

PowerShell

Get-CimInstance -ClassName [1]

Drag options to blanks, or click blank then click option'

AWin32_Service

BWin32_Process

CWin32_OperatingSystem

DWin32_ComputerSystem

Attempts:

3 left

💡 Hint

Common Mistakes

Using Win32_Process which lists processes, not OS info.

Using Win32_Service which lists services.

The class Win32_OperatingSystem contains information about the OS, so it must be used here.

4fill in blank

hard

Fill both blanks to get the total visible memory size from the operating system using CIM cmdlet.

PowerShell

$os = Get-CimInstance -ClassName [1]
$totalMemory = $os.[2]

Drag options to blanks, or click blank then click option'

AWin32_OperatingSystem

BWin32_ComputerSystem

CTotalVisibleMemorySize

DFreePhysicalMemory

Attempts:

3 left

💡 Hint

Common Mistakes

Using Win32_ComputerSystem which does not have this property.

Using FreePhysicalMemory which shows free memory, not total.

The Win32_OperatingSystem class has the property TotalVisibleMemorySize which shows total memory in kilobytes.

5fill in blank

hard

Fill all three blanks to query services that are running using WMI cmdlet.

PowerShell

Get-[1] -Class [2] -Filter "State = '[3]'"

Drag options to blanks, or click blank then click option'

AGet-WmiObject

BWin32_Service

CRunning

DGet-CimInstance

Attempts:

3 left

💡 Hint

Common Mistakes

Using Get-CimInstance which uses -Query instead of -Filter.

Using incorrect class or state value.

Get-WmiObject queries WMI classes like Win32_Service. Filtering by State = 'Running' gets running services.

Practice

1. What does the PowerShell cmdlet Get-CimInstance do?

easy

A. Starts a new PowerShell session.

B. Retrieves management information from local or remote computers using CIM.

C. Deletes files from the system.

D. Installs software packages.

Solution

1. Step 1: Understand the purpose of Get-CimInstance

   Get-CimInstance is used to get management data from computers, like hardware or software info.

2. Step 2: Compare options with cmdlet purpose

   Only Retrieves management information from local or remote computers using CIM. describes retrieving management info, matching the cmdlet's function.

3. Final Answer:

   Retrieves management information from local or remote computers using CIM. -> Option B

4. Quick Check:

   Get-CimInstance = Retrieves info [OK]

Hint: Get-CimInstance fetches system info, not file or session tasks [OK]

Common Mistakes:

• Confusing Get-CimInstance with file or session commands
• Thinking it installs software
• Assuming it deletes files

2. Which of the following is the correct syntax to get the list of running processes using CIM cmdlets?

easy

A. Get-CimInstance -ClassName Win32_Process

B. Get-CimInstance Win32_Process

C. Get-WmiObject -Class Win32_Process

D. Get-Process -ClassName Win32_Process

Solution

1. Step 1: Identify correct syntax for Get-CimInstance

   The correct parameter to specify the class is -ClassName, so Get-CimInstance -ClassName Win32_Process is valid.

2. Step 2: Check other options for syntax errors

   Get-CimInstance Win32_Process misses the parameter name, Get-WmiObject -Class Win32_Process uses Get-WmiObject (older cmdlet), and Get-Process -ClassName Win32_Process uses Get-Process incorrectly with a class parameter.

3. Final Answer:

   Get-CimInstance -ClassName Win32_Process -> Option A

4. Quick Check:

   Correct syntax uses -ClassName parameter [OK]

Hint: Use -ClassName to specify CIM class in Get-CimInstance [OK]

Common Mistakes:

• Omitting -ClassName parameter
• Mixing Get-CimInstance with Get-WmiObject syntax
• Using Get-Process with CIM class names

3. What will be the output of this command?

Get-CimInstance -ClassName Win32_OperatingSystem | Select-Object -Property Caption

medium

A. A list of running processes.

B. The computer's network adapter details.

C. An error about invalid property.

D. The name of the operating system installed on the computer.

Solution

1. Step 1: Understand the CIM class and property

   The class Win32_OperatingSystem contains OS info; the property Caption holds the OS name.

2. Step 2: Analyze the command output

   Selecting Caption will output the OS name, not processes or network info, and no error occurs.

3. Final Answer:

   The name of the operating system installed on the computer. -> Option D

4. Quick Check:

   Win32_OperatingSystem Caption = OS name [OK]

Hint: Win32_OperatingSystem class holds OS info; Caption is OS name [OK]

Common Mistakes:

• Confusing OS info with process or network info
• Expecting full object instead of selected property
• Assuming property Caption does not exist

4. You run this command but get an error:

Get-CimInstance -Class Win32_Processor

What is the likely cause?

medium

A. The parameter name should be -ClassName, not -Class.

B. Win32_Processor is not a valid CIM class.

C. Get-CimInstance cannot query processor info.

D. You need administrator rights to run this command.

Solution

1. Step 1: Check the parameter name used

   The correct parameter for specifying the class in Get-CimInstance is -ClassName, not -Class.

2. Step 2: Verify class validity and permissions

   Win32_Processor is a valid class and Get-CimInstance can query it; admin rights are usually not required for this query.

3. Final Answer:

   The parameter name should be -ClassName, not -Class. -> Option A

4. Quick Check:

   Use -ClassName parameter with Get-CimInstance [OK]

Hint: Use -ClassName, not -Class, with Get-CimInstance [OK]

Common Mistakes:

• Using -Class instead of -ClassName
• Assuming class is invalid
• Thinking admin rights are needed

5. You want to list all services that are currently running on a remote computer named 'Server01' using CIM cmdlets. Which command is correct?

hard

A. Get-CimInstance -ClassName Win32_Service -ComputerName Server01 | Where-Object { $_.Status -eq 'Running' }

B. Get-WmiObject -Class Win32_Service -ComputerName Server01 | Where-Object { $_.Status -eq 'Running' }

C. Get-CimInstance -ClassName Win32_Service -ComputerName Server01 | Where-Object { $_.State -eq 'Running' }

D. Get-CimInstance -ClassName Win32_Service -ComputerName Server01 | Where-Object { $_.State -eq 'Stopped' }

Solution

1. Step 1: Identify the correct property for running services

   The property State with value 'Running' correctly filters running services in Win32_Service.

2. Step 2: Choose the correct cmdlet and filter

   Using Get-CimInstance with -ComputerName is modern and correct. Filtering with Where-Object { $_.State -eq 'Running' } matches running services.

3. Final Answer:

   Get-CimInstance -ClassName Win32_Service -ComputerName Server01 | Where-Object { $_.State -eq 'Running' } -> Option C

4. Quick Check:

   Filter by State='Running' with Get-CimInstance [OK]

Hint: Filter services by State='Running' using Get-CimInstance [OK]

Common Mistakes:

• Using Status instead of State property
• Filtering for 'Stopped' instead of 'Running'
• Mixing Get-WmiObject with CIM cmdlets