Client Actions Command line rights
the client actions (on the client) that can be performed via the UI (control panel applet) should be allowed to be performed by a normal user via powershell.
if you try to triggerschedule as normal user, you get access denied
$SMSCli = [wmiclass] "root\ccm:SMS_Client"
marking declined, per Adam’s comment
Jack Rudlin commented
Hi Adam, did you end up writing a blob post on this? I would love to see how this message is generated. Is it the CcmEvaluatePolicyAssignmentsMessage class from the SDK that's used?
AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) commented
Hi, Raphael. This behavior is By Design as the SMS_Client class is restricted to high rights users.
The control panel works around this by getting details from the CCM_Scheduler_ScheduledMessage="scheduleid" instance from root\ccm\policy\machine and then sends a message to the client through the client framework.
This should be pretty straightfoward to automate using the messaging SDK along with a simple PowerShell script.
I have written down a note to write a blog entry on how to do this when I get an opportunity.