locked
"The Update Management solution cannot be enabled." message on "Update management" blade for VM RRS feed

  • Question

  • Detailed error message:

    The solution cannot be enabled on this VM because the VM already has the management agent but the workspace associated with the agent cannot be found within the subscription: XXXX-XXXX-XXXX-XXX

    SubscriptionId: XXXX-XXXX-XXXX-XXX

    VM: vstsbuild01

    I have tried aka.ms/f_fKXaNRW9 and aka.ms/d_fKXaNRW9 but could not find a solution



    Friday, May 25, 2018 8:41 AM

Answers

  • Hi

    On Azure VM you can install the OMS agent (used by Update Management solution) by either installing the agent manually or by applying Azure VM OMS extension. In your case the VM you are trying to onboard already has such agent. Because of that you are blocked to onboarding because this could result in other issues. In order to onboard you will have to remove the agent manually. If it is installed via Azure VM OMS Extension you have to go to the blade for that VM and remove the extension from Extensions section. If there is no such extension there you will have to logon to the VM via RDP/PowerShell/SSH (depending on the VM type and the access you have) and uninstall the agent manually either from control panel -> programs and features in Windows or via command line (https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/OMS-Agent-for-Linux.md#uninstalling-the-oms-agent-for-linux) on linux. After the agent is removed you should be able to onboard the VM to Update Management solution.

    Mark this reply as answer if it has helped you.

    Friday, June 8, 2018 11:59 AM

All replies

  • It seems you are trying to redeploy the VM management solution. You may upvote the similar UserVoice. Also, you may refer the solutions provided over the same link.

    --------------------------------------------------------------------------------------

    If this answer was helpful, click “Mark as Answer” or Up-Vote. To provide additional feedback on your forum experience, click here


    • Proposed as answer by Ajay Kadam Friday, May 25, 2018 9:50 AM
    • Edited by Ajay Kadam Friday, May 25, 2018 9:50 AM
    Friday, May 25, 2018 9:50 AM
  • I am trying to enable "Update management" for specified VM via Azure portal.

    "The solution cannot be enabled on this VM because the VM already has the management agent but the workspace associated with the agent cannot be found within the subscription" error message is displayed in Azure portal on Update management blade for specified VM. 

    When trying to add same VM to an existing Update magement by using "Manage multiple machines" and "Add Azure VMs", Azure portal displays "VM reports to a workspace that is not available in this subscription."

    Wednesday, May 30, 2018 1:34 PM
  • Hi

    On Azure VM you can install the OMS agent (used by Update Management solution) by either installing the agent manually or by applying Azure VM OMS extension. In your case the VM you are trying to onboard already has such agent. Because of that you are blocked to onboarding because this could result in other issues. In order to onboard you will have to remove the agent manually. If it is installed via Azure VM OMS Extension you have to go to the blade for that VM and remove the extension from Extensions section. If there is no such extension there you will have to logon to the VM via RDP/PowerShell/SSH (depending on the VM type and the access you have) and uninstall the agent manually either from control panel -> programs and features in Windows or via command line (https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/OMS-Agent-for-Linux.md#uninstalling-the-oms-agent-for-linux) on linux. After the agent is removed you should be able to onboard the VM to Update Management solution.

    Mark this reply as answer if it has helped you.

    Friday, June 8, 2018 11:59 AM
  • Hi Stanislav, this issue got solved by Microsoft Support Engineer through a support request, so I cannot tell if your answer works or not. The issue was that the agent was pointing to a workspace that was notavailable and could not be found in Microsoft backend. The solution was to remote to the VM, uninstall the Microsoft Monitoring agent manually, restart the VM, connect the machine from Azure portal to the workspace, and then enabled the Update Management (as documeneted in support case).
    Friday, June 22, 2018 4:34 AM
  • Great. Sounds like slightly different issue but seems the same steps were applicable. 
    Friday, June 22, 2018 5:38 AM
  • Hi,

    i cannot found to uninstall the agent on linux "https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/OMS-Agent-for-Linux.md#uninstalling-the-oms-agent-for-linux"

    TY

    kenny

    Wednesday, March 25, 2020 3:56 PM