Qfyilyi

I have a couple of VMs OnPremises and I'd like to install Windows Updates via Log Analytics Update Management. At one of this VMs there is hybrid worker group configured what is supposed to communicate other VMs with Azure Automation.

I created a update schedule but jobs don't update VMs with this exception in logs:

cc964bc7-f63d-4432-ba9f-f2d009b61025:[localhost]:Failed to start Update jobs {



    "computername_6536f09e-b7d4-4945-a45b-0a341c4c915a":  "{"Message":"Failed to start the runbook. Check the parameters 



passed. RunbookName Patch-MicrosoftOMSComputer. Exception You have requested to create a runbook job on a hybrid worker 



group that does not exist.  Hybrid worker group: computername_6536f09e-b7d4-4945-a45b-0a341c4c915a.  Check that the machine 



is properly registered as a hybrid worker group."}",

My guess is that runbook is trying to execute directly on the machine "computername" instead of using hybrid worker. Is there any way to force scheduled patch runbook to update VMs using my hybrid worker group, not directly? Let's say that hybrid worker is running on "mastercomputer"

This is precisely what Hybrid Runbook Workers are for.

https://docs.microsoft.com/en-us/azure/automation/automation-hybrid-runbook-worker

We have no way of knowing what your configuration looks like, but the runbook should be run against the hybrid group.

Start-AzureRmAutomationRunbook –AutomationAccountName "MyAutomationAccount" –Name "Test-Runbook" -RunOn "MyHybridGroup"