Sccm Action Trigger via CMD

Hi, Again Folks

Today we will check sccm action trigger on remote computer via cmd. As you know, all sccm jobs have been trigger with these actions to get related data's about the client. Most common actions is on the below ;

For Application Deployment Evaluation Cycle ;

WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000121}" /NOINTERACTIVE

For Hardware Inventory Cycle ;

WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000001}" /NOINTERACTIVE

For Machine Policy Retrieval Cycle ;

WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000021}" /NOINTERACTIVE

For Machine Policy Evaluation Cycle ;

WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000022}" /NOINTERACTIVE

For Software Inventory Cycle ;

WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000002}" /NOINTERACTIVE

For Software Update Scan Cycle ;

WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000113}" /NOINTERACTIVE

For User Policy Evaluation Cycle ;

WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000027}" /NOINTERACTIVE

After Run these command, output will be like on below screenshot;

If you want to used for remote client, you can make a files such as trigger.cmd then used it to deploy triggers on remote client via psexec such as ;

psexec -s \\Computername "\\SharedFolder\Trigger.cmd"

Note: Clients that will be implement these trigger, must be access to SharedFolder.