0% found this document useful (0 votes)
138 views

Start-CMClientAction PowerShell Tool Help File

The Start-CMClientAction PowerShell function allows initiation of 49 different SCCM client actions on local and remote computers. Common actions include triggering hardware/software inventory cycles, policy retrieval and evaluation cycles, and software update scan/deployment cycles. The function can initiate a single action or a bundled set of three common actions with a delay between each.

Uploaded by

vamsi79
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
138 views

Start-CMClientAction PowerShell Tool Help File

The Start-CMClientAction PowerShell function allows initiation of 49 different SCCM client actions on local and remote computers. Common actions include triggering hardware/software inventory cycles, policy retrieval and evaluation cycles, and software update scan/deployment cycles. The function can initiate a single action or a bundled set of three common actions with a delay between each.

Uploaded by

vamsi79
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 10

Start SCCM Client Action PowerShell Tool Help File

The help information provided below can also be viewed by using the following syntax:

Get-Help Start-CMClientAction –Full

Help Info

NAME

Start-CMClientAction

SYNOPSIS

The "Start-CMClientAction" function initiates allows 49 different SCCM client actions to be initiated on
one, or more computers.

SYNTAX

Start-CMClientAction [-ComputerName <Object>] -SCCMClientAction <Int32>


[<CommonParameters>]

Start-CMClientAction [-ComputerName <Object>] [-SCCMActionsBundle] [<CommonParameters>]

DESCRIPTION

The "Start-CMClientAction" PowerShell function allows for the initiaion of 49 SCCM client actions that
can be ran on the

local computer, or remote computers. Only one client action can be ran at a time, so using an array to
include several

client actions is not allowed. The Configuration Manager applet in Control Panel on the Actions tab
lists 10 actions and

these are identified in the Notes section with a "ConfigMgr Control Panel Applet" in parenthesis.
SCCM Administrators

typically find themselves running the following 3 actions during their monthly software update
deployments (patching):
Machine Policy Retrieval & Evaluation Cycle, Software Updates Scan Cycle, and Software Updates
Deployment Evaluation

Cycle. Because these 3 actions are so common, I decided to offer a way to bundle them with a 5
minute wait time (300

seconds) between each action. The parameter to use to run these 3 bundled actions is the '-
SCCMActionsBundle' parameter.

The 'SCCMClientAction' and the 'SCCMActionsBundle' parameters are members of different


parameter sets, so they cannot be

used together.

PARAMETERS

-ComputerName <Object>

Enter the name of one or more computers that you wish to initiate an SCCM client action on.

Required? false

Position? named

Default value $env:COMPUTERNAME

Accept pipeline input? true (ByValue, ByPropertyName)

Accept wildcard characters? false

-SCCMClientAction <Int32>

Enter a numerical value from 1-49 that represents each SCCM client action listed in the Notes
section under ther "SCCM

Client Action Trigger Codes" heading.

Required? true

Position? named

Default value 0

Accept pipeline input? false


Accept wildcard characters? false

-SCCMActionsBundle [<SwitchParameter>]

A switch parameter that does not accept any values, but rather tells the function to run the
following 3 actions

listed in the Notes section under ther "SCCM Client Action Trigger Codes" heading:

* Option 7 - Request Machine Assignments - (ConfigMgr Control Panel Applet - Machine Policy
Retrieval & Evaluation

Cycle)

* Option 38 - Scan by Update Source - (ConfigMgr Control Panel Applet - Software Updates Scan
Cycle)

* Option 33 - Software Updates Assignments Evaluation Cycle - (ConfigMgr Control Panel Applet -
Software Updates

Deployment Evaluation Cycle)

Required? false

Position? named

Default value False

Accept pipeline input? false

Accept wildcard characters? false

<CommonParameters>

This cmdlet supports the common parameters: Verbose, Debug,

ErrorAction, ErrorVariable, WarningAction, WarningVariable,

OutBuffer, PipelineVariable, and OutVariable. For more information, see

about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216).

INPUTS
OUTPUTS

NOTES

SCCM Client Action Trigger Codes

--------------------------------

1 - {00000000-0000-0000-0000-000000000001} Hardware Inventory - (ConfigMgr Control Panel


Applet - Hardware Inventory

Cycle)

2 - {00000000-0000-0000-0000-000000000002} Software Inventory - (ConfigMgr Control Panel


Applet - Software Inventory

Cycle)

3 - {00000000-0000-0000-0000-000000000003} Discovery Inventory - (ConfigMgr Control Panel


Applet - Discovery Data

Collection Cycle)

4 - {00000000-0000-0000-0000-000000000010} File Collection - (ConfigMgr Control Panel Applet -


File Collection Cycle)

5 - {00000000-0000-0000-0000-000000000011} IDMIF Collection

6 - {00000000-0000-0000-0000-000000000012} Client Machine Authentication

7 - {00000000-0000-0000-0000-000000000021} Request Machine Assignments - (ConfigMgr Control


Panel Applet - Machine

Policy Retrieval & Evaluation Cycle)

8 - {00000000-0000-0000-0000-000000000022} Evaluate Machine Policies

9 - {00000000-0000-0000-0000-000000000023} Refresh Default MP Task

10 - {00000000-0000-0000-0000-000000000024} LS (Location Service) Refresh Locations Task

11 - {00000000-0000-0000-0000-000000000025} LS (Location Service) Timeout Refresh Task

12 - {00000000-0000-0000-0000-000000000026} Policy Agent Request Assignment (User)

13 - {00000000-0000-0000-0000-000000000027} Policy Agent Evaluate Assignment (User) -


(ConfigMgr Control Panel Applet
- User Policy Retrieval & Evaluation Cycle)

14 - {00000000-0000-0000-0000-000000000031} Software Metering Generating Usage Report

15 - {00000000-0000-0000-0000-000000000032} Source Update Message - (ConfigMgr Control


Panel Applet - Windows

Installer Source List Update Cycle)

16 - {00000000-0000-0000-0000-000000000037} Clearing Proxy Settings Cache

17 - {00000000-0000-0000-0000-000000000040} Machine Policy Agent Cleanup

18 - {00000000-0000-0000-0000-000000000041} User Policy Agent Cleanup

19 - {00000000-0000-0000-0000-000000000042} Policy Agent Validate Machine Policy/Assignment

20 - {00000000-0000-0000-0000-000000000043} Policy Agent Validate User Policy/Assignment

21 - {00000000-0000-0000-0000-000000000051} Retrying/Refreshing Certificates in AD on MP

22 - {00000000-0000-0000-0000-000000000061} Peer DP Status Reporting

23 - {00000000-0000-0000-0000-000000000062} Peer DP Pending Package Check Schedule

24 - {00000000-0000-0000-0000-000000000063} SUM Updates Install Schedule

25 - {00000000-0000-0000-0000-000000000071} NAP action

26 - {00000000-0000-0000-0000-000000000101} Hardware Inventory Collection Cycle

27- {00000000-0000-0000-0000-000000000102} Software Inventory Collection Cycle

28 - {00000000-0000-0000-0000-000000000103} Discovery Data Collection Cycle

29 - {00000000-0000-0000-0000-000000000104} File Collection Cycle

30 - {00000000-0000-0000-0000-000000000105} IDMIF Collection Cycle

31 - {00000000-0000-0000-0000-000000000106} Software Metering Usage Report Cycle

32 - {00000000-0000-0000-0000-000000000107} Windows Installer Source List Update Cycle

33 - {00000000-0000-0000-0000-000000000108} Software Updates Assignments Evaluation Cycle -


(ConfigMgr Control Panel

Applet - Software Updates Deployment Evaluation Cycle)

34 - {00000000-0000-0000-0000-000000000109} Branch Distribution Point Maintenance Task

35 - {00000000-0000-0000-0000-000000000110} DCM Policy

36 - {00000000-0000-0000-0000-000000000111} Send Unsent State Message

37 - {00000000-0000-0000-0000-000000000112} State System Policy Cache Cleanout


38 - {00000000-0000-0000-0000-000000000113} Scan by Update Source - (ConfigMgr Control Panel
Applet - Software Updates

Scan Cycle)

39 - {00000000-0000-0000-0000-000000000114} Update Store Policy

40 - {00000000-0000-0000-0000-000000000115} State System Policy Bulk Send High

41 - {00000000-0000-0000-0000-000000000116} State System Policy Bulk Send Low

42 - {00000000-0000-0000-0000-000000000120} AMT Status Check Policy

43 - {00000000-0000-0000-0000-000000000121} Application Manager Policy Action - (ConfigMgr


Control Panel Applet -

Application Deployment Evaluation Cycle)

44 - {00000000-0000-0000-0000-000000000122} Application Manager User Policy Action

45 - {00000000-0000-0000-0000-000000000123} Application Manager Global Evaluation Action

46 - {00000000-0000-0000-0000-000000000131} Power Management Start Summarizer

47 - {00000000-0000-0000-0000-000000000221} Endpoint Deployment Reevaluate

48 - {00000000-0000-0000-0000-000000000222} Endpoint AM Policy Reevaluate

49 - {00000000-0000-0000-0000-000000000223} External Event Detection

-------------------------- EXAMPLE 1 --------------------------

C:\PS>Initiate an SCCM Client Action on the Local Computer

Start-CMClientAction -SCCMClientAction 1

-------------------------- EXAMPLE 2 --------------------------


C:\PS>Initiate an SCCM Client Action on a Remote Computer

Start-CMClientAction -ComputerName 'RemoteComputer1' -SCCMClientAction 1

-------------------------- EXAMPLE 3 --------------------------

C:\PS>Initiate an SCCM Client Action on Multiple Remote Computers

Start-CMClientAction -ComputerName 'RemoteComputer1', 'RemoteComputer2', 'RemoteComputer3'


-SCCMClientAction 1

-------------------------- EXAMPLE 4 --------------------------

C:\PS>Initiate an SCCM Client Action on Multiple Remote Computers Using a List of Computers in a
Text File

Start-CMClientAction -ComputerName (Get-Content -Path


"$env:userprofile\desktop\RemoteComputerList.txt") -SCCMClientAction
1

-------------------------- EXAMPLE 5 --------------------------

C:\PS>Initiate an SCCM Client Action Bundle on the Local Computer that Runs Options 7, 38, and 33
(Machine Policy

Retrievale & Evaluation Cycle, Software Updates Scan Cycle, and Software Updates Deployment
Evaluation Cycle)

Start-CMClientAction -SCCMActionsBundle

-------------------------- EXAMPLE 6 --------------------------

C:\PS>Initiate an SCCM Client Action Bundle on a Remote Computer that Runs Options 7, 38, and 33
(Machine Policy

Retrievale & Evaluation Cycle, Software Updates Scan Cycle, and Software Updates Deployment
Evaluation Cycle)

Start-CMClientAction -ComputerName 'RemoteComputer1' -SCCMActionsBundle


-------------------------- EXAMPLE 7 --------------------------

C:\PS>Initiate an SCCM Client Action Bundle on Multiple Remote Computers that Runs Options 7, 38,
and 33 (Machine Policy

Retrievale & Evaluation Cycle, Software Updates Scan Cycle, and Software Updates Deployment
Evaluation Cycle)

Start-CMClientAction -ComputerName 'RemoteComputer1', 'RemoteComputer2', 'RemoteComputer3'


-SCCMActionsBundle

-------------------------- EXAMPLE 8 --------------------------

C:\PS>Initiate an SCCM Client Action Bundle on Multiple Remote Computers Using a List of Computers
in a Text File that

Runs Options 7, 38, and 33 (Machine Policy Retrievale & Evaluation Cycle, Software Updates Scan
Cycle, and Software

Updates Deployment Evaluation Cycle)

Start-CMClientAction -ComputerName (Get-Content -Path


"$env:userprofile\desktop\RemoteComputerList.txt") -SCCMActionsBundle
RELATED LINKS

You might also like