This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(124.80000000000001, 11%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMG%3C/text%3E%3C/svg%3E)
Hello. I have inherited the following situation :
Azure Automation account with Hybrid Worker Group and a single Hybrid Worker inside. The machine on which this worker was installed has been decommissioned and doesn't exist anymore. The problem is that it's name is still present in the Hybrid Worker group in Azure. The GUI doesn't provide me with a way to delete just the worker. I can only delete the whole group. Is there a way to delete only that stale worker machine and preserve the group?
Maybe this helps:
----------
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Andreas Baumgarten
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(102.4, 72%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMG%3C/text%3E%3C/svg%3E)
Remove-HybridRunbookWorker cmdlet is part of the HybridRegistration.psd1 module. This module is being installed with the script New-OnPremiseHybridWorker.ps1 during registration of a new machine as a Hybrid worker. When I imported it in a standard powershell console on a non-registered as a worker machine, and tried to run this command, I got this error:
Remove-HybridRunbookWorker : Machine not registered
So the first problem is that in order to be able to delete a worker machine from Azure, we have to have another worker machine.
Since I intended to create a new worker machine anyway, I did just that and tried to delete the stale machine in Azure from the new one. This time Remove-HybridRunbookWorker command with -Verbose switch said that deletion was completed. Yes but no. The old worker machine stays in Azure in it's Hybrid workers group. It's been about fifteen hours so I doubt it's a "waiting" issue.
Next I intend to put a worker into the group of the stale machine and see if that helps. But I doubt it. Probably this cmdlet Remove-HybridRunbookWorker tries to start the necessary process on the worker machine that is to be deleted and it is this process that tells Azure to delete the machine as well. Since I don't have that machine anymore I'm afraid the only "solution" would be to delete the whole Hybrid worker group.
Well as surprisingly as it sounds, putting the new worker machine into the same hybrid worker group as the stale machine did the trick. Verbose logs in the powershell console were exactly the same, but this time the ghost machine disappeared from the worker group. So to answer my question in the first post: