Jonathan's Manage and Automate

VMM SCO SMA WAP - Solutions and Guidance


 Manage and Automate

                                           VMM SCO SMA WAP - Solutions and Guidance

  • Orchestrator Event Monitor fires multiple times for new events


    What is Microsoft Orchestrator?! This blog now covers SC VMM as well as Orchestrator System Center components. To learn more about Orchestrator follow this link. Now on to troubleshooting…

    The Runbook shown below is set up to monitor and send an alert for any new Application log events that have an Event ID of 808. This is a simple Runbook and is an ideal use of Orchestrator. There is a problem in that each time a new event such as the 808 event is logged to the event log, the Orchestrator Event Monitor executes a few times. It should fire only once per new event.

    So how do we get around this? Simple. We use the Link following the Event Monitor activity as an additional filter. This of course is not an ideal setup, but it does get around an issue currently in Orchestrator 2012 SP1.

    Here is the Runbook



    Here are the details of the Event Monitor activity:



    Here is the command we use to kick off the monitor.



    Here we see that the event caused multiple firings of the Event Monitor.




    Here, in the details of the link we set an Include filter for the same event. This will prevent the Event Monitor from firing more than once per new event log event.


    With the additional Link setting in place we now have an Event Monitor that performs as we would expect. This issue should be corrected in a future release. No ETA at this time.







  • Adding a Host and Enabling Connectivity in VMM 2012 SP1

    Sometimes a Host cannot be added to VMM, especially when there is a cluster involved. The steps below should resolve basic connectivity issues when adding a new host. For information about Hosts If this does not work, see the article just prior to this ‘Managing Hyper-V hosts using Virtual Machine Manager fails with Error: 0x8033803b. Extra remediation steps.

    Adding a Host and Enabling Connectivity

    Step 1: Advanced Firewall settings

    Open Advanced Firewall settings. Choose ‘Inbound Rules.’ Scroll to the bottom and make sure the five items below are enabled. Below only Windows Remote Management is enabled.


    The image below shows all items enabled.


    Step 2: Enable File Sharing Role

    In ‘Roles and Features’ place a check in ‘File Server’. Reboot is optional but recommended.







  • VMM Admin Console 2012 SP1 takes a few minutes to open

    Here’s one that might stump you occasionally. You open the Admin Console and instead of popping open you have to wait a few minutes before it opens. Once open all is fine. What happened?! It may have been looking for the SCOM server. If VMM and SCOM are integrated and the SCOM server is down, this can happen. Has this happened to you before? Check the Application event log on the VMM server for the event below. If you see it, this scenario was probably the case. The workaround is to have the SCOM server up when you open the VMM Admin Console.


    Log Name:      Application
    Source:        Microsoft.SystemCenter.VirtualMachineManager.2012.Monitor.FabricCloudMonitor
    Date:          2/15/2013 12:21:49 PM
    Event ID:      25935
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    AllChildHosts property is null. Can't compute capacity, so monitor wouldn't work





  • Managing Hyper-V hosts using Virtual Machine Manager fails with Error: 0x8033803b. Extra remediation steps.

    I just resolved a case where remediation as listed in the article below alone did not work, but there are a few things we commonly do that correct the problem. Just put these below what is already there as alternative additional steps. The manual removal and re-addition of the VMM agent is key. Thanks Thomas and Vlad!


    KB2795043    Managing Hyper-V hosts using Virtual Machine Manager fails with Error: 0x8033803b after installing WMF 3.0

    Re-install the VMM Agent

    1. Remove the VMM agent from the Host using Programs and Features in the Control Panel

    2. Re-install the agent using the latest ‘vmmAgent.exe’ in: C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\agents\amd64\3.x. Copy this file locally to the Host before installation.

    Re-associate the Host with VMM

    1. Follow this article to re-associate the Host with VMM. If this does not work or there are errors, follow step 2.

    How to Reassociate a Host or Library Server

    2. Open the VMM Admin Console. Open a PowerShell session by clicking the PowerShell button in the top ribbon. Type the following, replacing <HostName> with the system being re-associated:

    Reassociate-VMMManagedComputer –VMMManagedComputer <HostName>

    - or -

    Replace the server in the first line with the name of the VMM server. You will not need to specify the name of the Host to be added.

    C:\> Get-VMMServer -ComputerName ""

    C:\> $Credential = Get-Credential

    C:\> Get-VMMManagedComputer | where {$_.State -eq "AccessDenied"} | Reassociate-VMMManagedComputer -Credential $Credential






February, 2013

February, 2013