Anonymous

My feedback

  1. 17 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Update Management » Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous commented  · 

    I think I have figured a way around this. I am not an Azure expert by any means but quickly becoming good at cleaning up when things change overnight. I think I've found a way to repair the situation, let me know if I'm off on anything. The following steps took a VM out of its stuck on stupid state and reconnected it with the chosen workspace:

    1. Download the Microsoft Monitoring Agent from the new Workspace to the problem VM desktop
    2. Run the installer and remove the agent. REBOOT
    3. Remove the MMA Extension-
    Remove-AzureRmVMExtension -ResourceGroupName "YourRG" -Name "MMAExtension" -VMName "YOUR-VMName"
    4. Reset the MMA Extension-
    $PublicSettings = @{"workspaceId" = "myWorkspaceId"}
    $ProtectedSettings = @{"workspaceKey" = "myWorkspaceKey"}

    Set-AzureRmVMExtension -ExtensionName "MMAExtension" `
    -ResourceGroupName "myResourceGroup" `
    -VMName "myVM" `
    -Publisher "Microsoft.EnterpriseCloud.Monitoring" `
    -ExtensionType "MicrosoftMonitoringAgent" `
    -TypeHandlerVersion 1.0 `
    -Settings $PublicSettings `
    -ProtectedSettings $ProtectedSettings `
    -Location WestUS `

    REBOOT

    Anonymous supported this idea  · 

Feedback and Knowledge Base