Jonathan's Virtual Blog

System Center Virtual Machine Manager and Orchestrator - Solutions and Guidance


 Jonathan's Virtual Blog

   Virtual Machine Manager - Orchestrator - Solutions and Guidance

  • VMM Repro: Simple tracing for VMM

    imageSupports:

    VMM 2012 SP1
    VMM 2012 R2

    VMM Repro captures detailed information on systems involved in a reproducible VMM problem. This is a verbose data capture and should be run for a short period of time while the problem is reproduced.

    Features

    • It will test to see that the right version of VMM is installed, and will point you to my other tool for older systems as needed.
    • Displays explanation of what the tool is going to do.
    • Log files are renamed after the PC, plus the date and time.
    • Log files are automatically zipped up.
    • The folder that contains the zip file opens in Explorer for you.

    When to use?

    When you’ve made it through the items below and are still are no closer to resolution you should consider capturing a trace.

    • Review Application and System Event logs on the SCVMM server and Hosts involved in the problem
    • Install all update and verify using Windows Update
    • Verify required basics again:
      • DNS resolution in all directions
      • Account running VMMService is located in ‘Administrators’ and ‘Virtual Machine Manager Servers’ groups on SCVMM server and Hosts
      • Hyper-V, Cluster and so on are healthy

    How to use?

    Elevated PowerShell prompt required.

    • Change to the directory of the script.
    • Unblock the script as it was downloaded from the internet: unblock-file .\VMMReprov1.ps1
    • Kick off with ‘.\VMMReprov4.ps1’.
    • If you get an error about not being digitally signed:
      • Set-ExecutionPolicy Unrestricted
      • (When done with the script you can run ‘Set-ExecutionPolicy Restricted’ if you like)

    Troubleshooting – If ‘How to use?’ does not work

    If the script does not kick off it is for one of three reasons:

    1. PowerShell console is not being run as Administrator.
    2. Scripts are not allowed to run on your system in PowerShell. Type ‘set-executionpolicy unrestricted’.
    3. The script has been blocked by the OS as it was downloaded from the internet. See illustration below for instructions.

    If you get this error it means that the script has been blocked. To unblock scripts (especially ones you pull from the internet) see the next picture.

    clip_image002

    Go to properties of the script and unblock it.

    clip_image004

     

     

      jonjor

    Download here:

  • Free ebook: Designing Orchestrator Runbooks

    5025_image_thumb_23B34BDBA great new book has been released from Microsoft Press that covers Orchestrator and the creation of Runbooks very well. As a support professional I found the book to be informative from an architectural perspective, and full of great examples to get started.

    From the posting on the Orchestrator TechNet blog site:

    We’re very excited to announce a free ebook offering from Microsoft Press: Microsoft System Center: Designing Orchestrator Runbooks (ISBN 9780735682986) by David Ziembicki, Aaron Cushner, Andreas Rynes and the System Center series editor, Mitch Tulloch. This is the first in a series of unique (and free) ebooks that bring System Center experts together to discuss designing, deploying, and troubleshooting some of the most complex and mission critical aspects of key System Center capabilities.”

    … and

    “Our objective with this book is to provide a framework for runbook design and IT process automation to help you get the most out of System Center Orchestrator 2012 and to help you utilize Orchestrator in concert with the rest of the System Center for an enterprise-wide and systematic approach to process automation.”

    Click here to get the book!

    .

    .

    .

      jonjor

October, 2013

October, 2013