Azure Runbooks are usually run in the cloud (on an automatically assigned ‘Microsoft’ host) or on a Hybrid Worker Group.<\/p>\n
Hybrid Worker Groups consist of 1 or more machines, but there are also ‘System hybrid workers’, which are machines monitored by OMS. If you want to execute a Powershell script directly on a specific System hybrid worker, or on a specific group member of a worker group, you can use Powershell and specify the host instead of the group:<\/p>\n
Start-AzureRmAutomationRunbook -Name “RunbookName” -RunOn hybridWorkerName\u00a0-AutomationAccountName “automationaccount” -ResourceGroupName “resourcegroup”<\/p>\n
If you try this on a System Hybrid Worker, you’ll get an error on the device itself and in the runbook results:<\/p>\n
\u201cInvalid Runbook xxx Authenticode signature status \u2013 NotSigned\u201d.<\/p>\n
This can be ‘fixed’ by setting the following registry key to ‘False’:<\/p>\n
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\HybridRunbookWorker\\GuidOfYourWorker\\EnableSignatureValidation<\/p>\n
Et voila, the runbook runs nicely. I do not recommend disabling this key in production, this article is purely to share knowledge, and if someone knows how to do this without disabling this key, I’d love to hear it!<\/p>\n","protected":false},"excerpt":{"rendered":"
Azure Runbooks are usually run in the cloud (on an automatically assigned ‘Microsoft’ host) or on a Hybrid Worker Group. Hybrid Worker Groups consist of 1 or more machines, but there are also ‘System hybrid workers’, which are machines monitored by OMS. If you want to execute a Powershell script directly on a specific System … Continue reading Running an Azure runbook on a System hybrid worker<\/span>