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

  • WinRM (Windows Remote Management) Troubleshooting

    What is WinRM?

    New in Windows Vista, Windows Server 2003 R2, Windows Server 2008 (and Server 2008 Core) are WinRM & WinRS. Windows Remote Management (known as WinRM) is a handy new remote management service. WinRM is the “server” component of this remote management application and WinRS (Windows Remote Shell) is the “client” for WinRM, which runs on the remote computer attempting to remotely manage the WinRM server. However, I should note that BOTH computers must have WinRM installed and enabled on them for WinRS to work and retrieve information from the remote system.

    While WinRM listens on port 80 by default, it doesn't mean traffic is unencrypted. Traffic by default is only accepted by WinRM when it is encrypted using the Negotiate or Kerberos SSP. WinRM uses HTTP (TCP 80) or HTTPS (TCP 443). WinRM also includes helper code that lets the WinRM listener to share port 80 with IIS or any other application that may need to use that port.

    WinRM with SCVMM uses Kerberos for authentication, and does not support fall-back to NTLM. There will be an error instead. If no credentials are specified, then the logged-on credentials are used to authenticate against the remote machine. This allows for a single sign-on experience.

      

    What is WinRS?

    Remote Shell, (WinRS) is used to execute a program on a remote host. Similar in operation to the former Sysinternals tool PSExec, WinRS leverages Windows Remote Management to let you launch processes on remote machines. For example, if you want to perform a directory listing on the system drive on a remote machine, you can remotely launch ‘dir’ using this syntax:

    winrs -r:machinename dir

    Another handy use of WinRS can be when installing software on remote systems. If you want to quietly install an application using an MSI file onto a remote machine, use the following syntax. This syntax assumes the MSI file has already been deposited into the C:\ folder.

    winrs -r:machinename msiexec.exe /i c:\install.msi /quiet

    When specifying the remote machine, the following are valid:

    · Localhost

    · NetBIOS name

    · Fully Qualified Domain Name (FQDN)

    · IP address

    How to install WinRM

    The WinRM is not dependent on any other service except WinHttp. If the IIS Admin Service is installed on the same computer, you may see messages that indicate WinRM cannot be loaded before Interent Information Services (IIS). However, WinRM does not actually depend on IIS: these messages occur because the load order ensures that the IIS service starts before the HTTP service. WinRM does require that WinHTTP.dll be registered.

    (Stated simply: WinRM service should be set to Automatic (Delayed Start) on Windows Vista and Server 2008)

    · The WinRM service starts automatically on Windows Server 2008.

    · On Windows Vista, the service must be started manually.

    · UPDATE! Windows 2003 requires an update for WinRM

    936059 An update is available for the Windows Remote Management feature in Windows Server 2003 and in Windows XP

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;936059

    How to configure WinRM

    To set the default configuration type:

    winrm quickconfig (or the abbreviated version, winrm qc)

    ‘winrm qc’ performs the following operations:

    1. Starts the WinRM service and sets the service startup type to auto-start.

    2. Configures a listener for the ports that send and receive WS-Management protocol messages using either HTTP or HTTPS on any IP address.

    3. Defines ICF exceptions for the WinRM service and opens the ports for HTTP and HTTPS.

    (Note: Winrm quickconfig also configures Winrs default settings)

    If ‘winrm qc’ throws an error:

    If the firewall is disabled the quick config command will fail. The firewall can either be started in Services long enough to run ‘winrm qc’ or the commands below can be run:

    sc config "WinRM" start= auto

    net start WinRM

    winrm create winrm/config/listener?Address=*+Transport=HTTP

    netsh firewall add portopening TCP 80 "Windows Remote Management"

    Group Policy configuration:

    WinRM can be configured by group policies.

    1. Type gpedit at a command prompt. The Group Policy Object Editor window opens.

    2. Look for the Windows Remote Management and Windows Remote Shell Group Policy Objects (GPO) under Administrative Templates and Windows Components.

    Troubleshoot WinRM

    Common Issues:

    1. If the ISA2004 firewall client is installed on the computer, it can cause a Web Services for Management (WS-Management) client to stop responding. To avoid this issue, install ISA2004 Firewall SP1.

    2. Antivirus software can prevent proper WinRM communication. Disable antivirus software and reboot the machine if the Antivirus software is known to scan processes and protocols, or if there is any doubt about the software.

    Test WinRM communication on the local and remote machines

    This section addresses how to test whether WinRM is working on the local system, and whether it can communicate with the remote system. Test remote communication in both directions between machines.

    Local communication:

    Locate listeners and addresses: (No output means WinRM is not installed)

    winrm e winrm/config/listener

    Localhost Ping:

    (Successfully completing this step pretty much insure complete access to WSMan on the local system)

    Winrm id

    Further:

    Check state of configuration settings:

    winrm get winrm/config

    Check the state of WinRM service:

    winrm get wmicimv2/Win32_Service?Name=WinRM

    Remote communication:

    Locate listeners and addresses:

    winrm e winrm/config/listener

    Remote Ping:

    (Successfully completing this step pretty much insure complete access to WSMan on the remote system)

    Winrm id –r:machinename

    Further:

    Check state of configuration settings:

    winrm get winrm/config -r:machinename

    Check the state of WinRM service:

    winrm get wmicimv2/Win32_Service?Name=WinRM -r:machinename

    Sample Commands

    Here are some sample commands to play with. If you cannot get the ‘Test WS-Man...' step to work, none of the steps following will work either (you're probably not using the right credentials to access the remote machine). One more caveat, the remote commands work best on domain joined machines. For workgroup machines, the WinRM service needs additional configuration.

    Description

    Command

    Run from an Elevated Command prompt

    Quickly configure the WS-Man service

    winrm QuickConfig

    Quickly delete the WS-Man listener

    winrm invoke Restore winrm/Config @{}

    Run from an standard Command prompt

    Display your machine's basic hardware info

    winrm enumerate wmicimv2/Win32_ComputerSystem

    Display your operating system properties

    winrm get wmicimv2/Win32_OperatingSystem

    Output your OS info in XML

    winrm get wmicimv2/Win32_OperatingSystem -format:pretty

    Test WS-Man access to a remote machine**

    winrm id -remote:<some machine>

    Grab a remote machine's WS-Man config

    winrm get winrm/Config -r:<some machine>

    Grab a remote machine's CPU load

    winrm g wmicimv2/Win32_Processor?DeviceID=CPU0 -fragment:LoadPercentage -r:<some computer>

    Grab a remote machine's free memory

    winrm g wmicimv2/Win32_OperatingSystem -fragment:FreePhysicalMemory -r:<some computer>

    Stop a service on a remote machine

    winrm invoke stopservice wmicimv2/Win32_Service?name=w32time -r:<some computer>

    Start a service on a remote machine

    winrm invoke startservice wmicimv2/Win32_Service?name=w32time -r:<some computer>

    Reboot a remote machine

    winrm invoke reboot wmicimv2/Win32_OperatingSystem -r:<some computer>

    Run a command on a remote machine (this uses winrS, not winrM)

    winrs -r:<some computer> ipconfig /all

    Run from PowerShell

    Use PowerShell to grab the WS-Man Win32_OperatingSystem XML output

    [xml]$osInfo = winrm get wmicimv2/Win32_OperatingSystem /format:pretty

    Display the OS version property

    $osInfo.Win32_OperatingSystem.Version

    Display the last boot time

    $osInfo.Win32_OperatingSystem.LastBootupTime.DateTime

    Put free memory metric into an XML variable

    [xml]$freemem = cmd /c "winrm get wmicimv2/Win32_OperatingSystem -fragment:FreePhysicalMemory -f:pretty -r:<some computer>"

    Display the free memory value

    $freemem.XMLFragment.FreePhysicalMemory

    **Note: This step verifies that you have good connectivity to the remote machine, WS-Man is running and properly configured on the remote machine, AND you have the correct permissions to fully leverage WS-Man on the remote machine. If this step fails, it's probably a permissions issue.

    Advanced Concepts

    URI Aliases

    URI aliases can simplify the Winrm command line. The following URI aliases are supported:

    wmi = http://schemas.microsoft.com/wsman/2005/06/wmi

    wsman = wsman:microsoft.com/wsman/2005/06/

    cimv2.9 = http://schemas.dmtf.org/wsman/2005/06/cimv2.9

    cimv2 = http://schemas.microsoft.com/wsman/2005/06/wmi/root/cimv2

    For example, the following command:

    winrm get http://schemas.microsoft.com/wsman/2005/06/wmi/root/cimv2/Win32_Service?Name=WSMan

    Gets replaced with:

    winrm get wmi/root/cimv2/Win32_Service?Name=WinRM

    Performing an Invoke Operation

    ‘Invoke’ initiates commands

    winrm invoke StartService wmicimv2/Win32_Service?Name=WinRM -r:machinename @{}

    This will likely return ‘ReturnValue = 10’ on a remote system where WinRM is running

    WS-Man (WinRM) Architecture

    The following diagram shows a high-level overview of the WS-Man (WinRM) architecture. In the diagram the 'Client' is querying the 'Server' for WS-Man information. Note that HTTP.sys and WinHTTP support the HTTP(s) transport for WS-Man, not IIS. In addition, IIS (or another web publishing service) can co-exist with WS-Man and share port 80.

    Remember:

    WinHTTP = Client

    HTTP.SYS = Server

    clip_image002

    The Windows Remote Management architecture consists of components on the client and server computers. The following illustration shows the components on both computers, how the components interact with other components, and the protocol that is used to communicate between the computers.

    clip_image003

    Requesting Client

    The following WinRM components reside on the computer that is running the script that requests data.

    · WinRM application

    This is the script or Winrm command-line tool that uses the WinRM scripting API to make calls to request data or to execute methods. For more information, see the WinRM Scripting API [ http://msdn.microsoft.com/en-us/library/aa384469(VS.85).aspx ] .

    · WsmAuto.dll

    The OLE automation layer that provides scripting support.

    · WsmCL.dll

    C API layer within the operating system.

    · HTTP API

    WinRM requires support for HTTP and HTTPS transport.

    Responding Server

    The following WinRM components reside on the responding computer.

    · HTTP API

    WinRM requires support for HTTP and HTTPS transport.

    · WsmAuto.dll

    The OLE automation layer that provides scripting support.

    · WsmCL.dll

    C API layer within the operating system.

    · WsmSvc.dll

    WinRM listener [ http://msdn.microsoft.com/en-us/library/aa384465(VS.85).aspx ] service.

    · WsmProv.dll

    Provider subsystem.

    · WsmRes.dll

    Resource file.

    · WsmWmiPl.dll

    WMI plug-in [ http://msdn.microsoft.com/en-us/library/aa384465(VS.85).aspx ] . This allows you to obtain WMI data through WinRM.

    · Intelligent Platform Management Interface (IPMI) driver and WMI IPMI provider

    These components supply any hardware data that is requested using the IPMI classes. For more information, see Intelligent Platform Management Interface (IPMI) Classes [ http://msdn.microsoft.com/en-us/library/aa390891(VS.85).aspx ] . BMC hardware must have been detected by the SMBIOS or the device created manually by loading the driver. For more information, see Installation and Configuration for Windows Remote Management [ http://msdn.microsoft.com/en-us/library/aa384372(VS.85).aspx ] .

    References

    Installation and Configuration for Windows Remote Management

    http://msdn.microsoft.com/en-us/library/aa384372(VS.85).aspx

    Windows Remote Management Command-Line Tool (Winrm.cmd)

    http://technet.microsoft.com/en-us/library/cc781778.aspx

    How can Windows Server 2008 WinRM & WinRS help you

    http://windowsnetworking.com/articles_tutorials/How-Windows-Server-2008-WinRM-WinRS.html

    The things that are better left unspoken Remotely managing your Server Core using WinRM and WinRS

    http://blogs.dirteam.com/blogs/sanderberkouwer/archive/2008/02/23/remotely-managing-your-server-core-using-winrm-and-winrs.aspx

    Redmond Print First Look WinRM & WinRS

    http://redmondmag.com/columns/article.asp?EditorialsID=2262

    Otto Helweg - Management Matters A Few Good Vista WS-Man (WinRM) Commands

    http://blogs.technet.com/otto/archive/2007/02/09/sample-vista-ws-man-winrm-commands.aspx

    Windows Remote Management Architecture

    http://msdn.microsoft.com/en-us/library/aa384464(VS.85).aspx

  • VM does not Boot Following P2V or Disk2VHD

    So you perform a successful P2V using SCVMM. Or perhaps you use it’s cousin, ‘Disk2VHD’ from Sysinternals. All is well until you boot the new VM… FAILURE. For those situations where you simply get a black screen, maybe with a blinking cursor but definitely no Windows load, I have some solutions. (If you are experiencing a blue screen this article is not for you).

    First! Do not fear the black screen. It simply means the path to load Windows cannot be found by the boot loader. This may be due to the boot loader, or it may be due to the MBR or Boot Sector. Let’s just say we aren’t concerned with all of the technicalities and want to fix it. Here’s how.

     

     

    Windows 2008 R2 (Vista, Windows 7, Windows 2008)

    We’re going to fix the entire boot path, despite what part of it is broken. Go find an ISO or DVD of any of the operating systems just listed in the title. Prepare to boot your VM from this media. We’re going to use the recovery console. We’ll assume you are using Windows 7 media.

    1. Attach the Windows 7 installation disc to the virtual machine disc drive, and then start the computer.
    2. Press a key when you are prompted.
    3. Select a language, a time, a currency, a keyboard or an input method, and then click Next.
    4. Click Repair your computer.
    5. Click the operating system that you want to repair, and then click Next.
    6. In the System Recovery Options dialog box, click Command Prompt.
      1. If an operating system is not found simply continue anyway
    7. Type the following command in this order to set your system straight:
      1. bootrec /fixmbr    (Fixes MBR)
      2. bootrec /fixboot   (Fixes Boot Sector)
      3. bootrec /scanos    (Scans for Windows installations to add)
      4. Reboot! (Type Exit)
    8. If you still do not boot into Windows, or do not have a boot menu, or something is still wrong, follow steps 1 – 6 again. For step 7 type this instead
      1. bootrec /rebuildbcd    (Rebuilds entire BCD… not a really big deal)
      2. Reboot! (type Exit)

    You are now either booting into Windows, or you are not… Any blue screens I cannot help you with at this time. Search the internet for a solution, and in the meantime I intend to write an article on this as well. Comments welcome as always.

    Further Information:

    How to use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issues in Windows
    http://support.microsoft.com/kb/927392

    Windows 2003 R2 (Windows XP, Windows 2003)

    Again, we’re off to fix the boot path. Things are a bit different in Windows 2003. Same basic goal as with Windows 2008. Go find an ISO or DVD of any of the operating systems just listed in the title. Prepare to boot your VM from this media. We’re going to use the recovery console. We’ll assume you are using Windows 2003 media.

    1. Attach the Windows 2003 installation disc to the virtual machine disc drive, and then start the computer.
    2. When you receive the message that prompts you to press any key to start from the CD, press a key to start the computer from the Windows Server 2003 CD.
    3. When the Welcome to Setup screen appears, press the R key to start the Recovery Console.
    4. Select the Windows installation that you must access from the Recovery Console.
    5. Follow the instructions that appear on the screen, type the Administrator password, and then press ENTER.
    6. Type the following command in this order to set your system straight:
        1. fixmbr (Fixes MBR)
        2. fixboot (Fixes Boot Sector)
        3. bootcfg /rebuild  (Lists all Windows installations that you can add)
        4. Reboot! (type Exit)

    You are now either booting into Windows, or you are not… Any blue screens I cannot help you with at this time. Search the internet for a solution, and in the meantime I intend to write an article on this as well. Comments welcome as always.

    Further Information

    How To Use the Recovery Console on a Windows Server 2003-Based Computer That Does Not Start
    http://support.microsoft.com/kb/326215

    Description of the Windows XP Recovery Console for advanced users
    http://support.microsoft.com/kb/314058

     

     

    jonjor

  • What version of VMM am I running?!?

    A new KB has been released that makes it simple to know what build of VMM you are running. This is important as you should always be at the latest Update Rollup or Service Pack possible. By knowing your build number you can identify updates that need to be installed. Find your build number on the list, then look for a higher build number in the same release of VMM. Best of luck!

    Stay up to date on updates!

     

    How to determine the version of Virtual Machine Manager

    http://support.microsoft.com/kb/2627355

     

    an excerpt:

    System Center 2012 SP1 RTM  KB Date Released  3.1.6011.0  
    System Center 2012 SP1 Update Rollup 1 2785682
    11/20/2012
    3.1.6018.0 http://support.microsoft.com/kb/2785682
    System Center 2012 SP1 Update Rollup 2 2802159
    1/11/2013
    3.1.6020.0

    http://support.microsoft.com/kb/2802159

    System Center 2012 SP1 Update Rollup 3 2836751
    4/5/2013
    3.1.6027.0 http://support.microsoft.com/kb/2836751
    System Center 2012 SP1 Update Rollup 4 2879276
    8/12/2013
    3.1.6032.0 http://support.microsoft.com/kb/2879276
             
    System Center 2012 R2 RTM     3.2.7510.0

     

    Denis pointed out that there is a similar list here. Thanks!

    social.technet.microsoft.com/.../15361.list-of-build-numbers-for-system-center-virtual-machine-manager-vmm.aspx

     

     

      jonjor 

  • 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:

  • Orchestrator Web Console Fails after Upgrade to 2012 R2

    This is an issue we have been tracking for a while now. Please see the KB article on how to get around this error.

    Excerpt:

    After upgrading to System Center 2012 R2 Orchestrator, attempts to start the Orchestration Web Console fails and the following messages will pop up in the browser:
    Error Executing the current operation
    [httpwebrequest_webexception_remoteserver]
    Arguments: NotFound

    Error Executing the Current Operation

    Starting the Orchestration Web Console fails after upgrade to System Center 2012 R2
    http://support.microsoft.com/kb/2919041

     

     

    jonjor

  • Technical Documentation: Virtual Machine Manager 2012 R2

    This is the go to source for VMM. Can VMM do x? How do you make VMM do x? Both questions answered in this ~800 page document, with a multitude of links to related information. Keep this one in your VMM toolkit.

    … and to answer your first question, yes; SC2012_VMM does not reflect that there is updated R2 material. This is the right doc.

    Applies To

    System Center 2012 – Virtual Machine Manager

    System Center 2012 Service Pack 1 (SP1) – Virtual Machine Manager (VMM)

    System Center 2012 R2 Virtual Machine Manager – NICE!

    Word and PDF versions available.

    image

    Technical Documentation Download for System Center 2012 – Virtual Machine Manager

    http://www.microsoft.com/en-us/download/details.aspx?id=6346

    .

    .

    .

      jonjor

  • SCOtrace – Orchestrator Trace Tool

    What is SCOtrace?

    SCOtrace increases the Orchestrator log level, provides time for you to reproduce a problem, then sets all log levels back to their lowest (normal) level. Log files are then gathered for you in a central location.

    How does it work?

    Orchestrator activity is logged all the time, whether you know it or not. The log level is very low and does not impact your system. There are times, however, when it would be ideal to generate very detailed logs in order to better understand a problem. Following this article it is possible to increase the level of logging significantly (The article discuses Opalis, but it works the same for Orchestrator).

    Why would I need this?

    The idea of this tool is to automate the collection of verbose logs for you or a Microsoft Support Professional to review. You can perform these exact steps following the article mentioned above, but this way is simply quicker.

    Where should I use this?

    Run SCOtrace on the Management server, and if you think Runbook servers are involved run it there as well. Only the Orchestrator components you have installed on a system will be traced.

    How do I run SCOtrace?

    The latest version of SCOtrace can be downloaded here.

    Remove the .txt extension from the file and run from an elevated command prompt.

    Note: The latest file from each log directory is gathered. You may find some files that are old. Ignore these.

     

    image

     

     

     

     

      jonjor

  • Update Rollup 2 for System Center 2012 SP1

    imageThis blog focuses on VMM and Orchestrator, and for VMM alone there are 20 fixes in this update. Many of these corrections relate to networking. This update has helped a number of customers I have worked with resolve their issues entirely. Even in a controlled classroom environment (I’m out delivering training this week. Go OKC!) the update has made a strong positive impact. As for Orchestrator, there are a few fixes as well, both of which stemmed from customer cases I worked involving Oracle results and SNMP Traps.

     

    This is one update that should be installed immediately, or as soon as your outage window allows. There is one caveat: ‘In order to install Update Rollup 2 package for System Center 2012 SP1-  Virtual Machine Manager, you will need to uninstall Update Rollup 1 for System Center SP1 - Virtual Machine Manager package from your system.’ See this blog post for a great deal of information on the subject. Also, if you need to uninstall SC VMM for some unrelated reason, you will need to remove this update first to do so.

    Grab the update here. Description of Update Rollup 2 for System Center 2012 Service Pack 1

    A list of fixes in the update…

    Virtual Machine Manager Server (KB2826405) and Administration Console (KB2826392)

    Issue 1

    The SUSE Linux Enterprise Server 11 operating system is missing from the Linux OS list.

    Issue 2

    A virtual machine cannot start after migration from Windows 7 to Windows 8 when the DiscardSavedState method is used.

    Issue 3

    A connection to the VMware virtual machine remote console session cannot be established.

    Issue 4

    Externally published VMNDs are filtered incorrectly.

    Issue 5

    When you remove a virtual switch extension property or edit a virtual switch extension manager connection string, a user-interface generated script also removes the HostGroups that are associated with VSEM.

    Issue 6

    UPPSet is not set on a physical network adapter when you add the network adapter to a team and when the network adapter is the first in the list of network adapters.

    Issue 7

    The default gateway is missing on a host virtual network adapter after you add a second physical network adapter to the logical switch.

    Issue 8

    Static IP pool that has the first address in a subnet fails for external network type.

    Issue 9

    VMM crashes during host refresher when VMM is unable to create a CimSession with the remote host.

    Issue 10

    Standard (legacy) virtual switch creation on Windows 8 hosts with management virtual network adapter does not preserve the IP properties of the physical network adapter.

    Issue 11

    The administration user interface crashes with a NullReferenceException error when you click Remediate on a host instead of a virtual network adapter.

    Issue 12

    The Virtual Machine Manager user interface displays a network adapter in a "Not Connected" state.

    Issue 13

    The Virtual Machine Manager stops responding with high CPU usage for five to ten minutes when you configure a VMND that has 2,000 network segments.

    Issue 14

    The host virtual network adapter property for a management adapter does not show port classification.

    Issue 15

    Live Migration fails at 26 percent when the network adapter is attached to an isolated virtual machine network.

    Issue 16

    The Virtual Machine Manager Service crashes when a virtual machine that does not have a port profile is migrated to a cluster by using a logical switch that has a default port profile set.

    Issue 17

    Running Dynamic Optimizer on a cluster with incompatible host CPUs causes a Virtual Machine Manager Service crash.

    Issue 18

    The Host refresher crashes for any host that has the RemoteFX role enabled.

    Issue 19

    The minimum memory for dynamic memory greater than 32GB is a security risk.

    Issue 20

    The status of the network adapter is displayed as Not Connected in Virtual Machine Manager.

     

     

     

     

     

      jonjor

  • You may have problems with Virtual Machine Manager if some SPNs are missing

    As a support engineer at Microsoft, I see almost daily some issues with Service Principle Names (SPNs). SPNs are as important to VMM communication as DNS. They are attributes on DNS entries that allow other services to find VMM. This is not a new issue, and this article covers how SPNs should be set up on your system. If everything is working well, please do not make changes. To see if you have SPNs registered correctly, at an elevated command prompt type ‘setspn –L <computername>’. This will list what is registered. You DO  want to find SCVMM/Hostname and SCVMM/FQDN in the list. Below is only an example. Good luck with the article!

     

    You may have problems with Virtual Machine Manager if some SPNs are missing
    http://support.microsoft.com/kb/2123063

     

     

     

     

      jonjor

  • Update-Help: VMM PowerShell

    PowerShell iconIf you've opened the VMM 2012 SP1 PowerShell console and performed a command to get help on cmdlets, you may be in for a surprise. Examples are not included out of the box, and there were tons of great examples in VMM 2008 R2. The syntax below should, but does not, output all help including example use.

    get-help <cmdlet-name> -full

     

    There is a simple way of resolving this issue. Open the ‘Virtual Machine Manager Command Shell’ located in Start. Open this elevated as administrator. Now type the following and updated help will be available.

    update-help

    When this is done you can use a non-elevated VMM PowerShell and updated help will be available.

     

     

     

     

      jonjor

  • Free ebook: Microsoft System Center: Cloud Management with App Controller

    cover for System Center Cloud Management ebookA great free book has been released for App Controller 2012 R2. This is not a product generally covered in this blog, but can be an integral part of your System Center installation.

    Briefly… an excerpt from the post below.

    Introduction

    Microsoft System Center 2012 R2 App Controller is uniquely positioned as both an enabler and a self-service vehicle for connecting clouds and implementing the hybrid computing model. In Microsoft’s cloud computing solutions, both System Center and Windows Azure play critical roles. System Center can be used to transform enterprise IT from a device-based infrastructure and deployment strategy to a service-based user-centric consumption model based on private cloud computing. Windows Azure on the other hand is a subscription-based public cloud platform that enables the development, deployment, and management of cloud solutions. App Controller is the glue that unifies these two platforms by providing a single interface that enables administrators to perform complex operations without overwhelming them with the underlying technical complexities involved.

    Click here to read the post and grab the book!

    .

    .

    .

    .

      jonjor

  • Poster: Networking in Virtual Machine Manager

    There is a new post on the Download Center of networking in Virtual Machine Manager. It’s a bit intimidating posting this official poster right after my own attempts (see my previous post), but they all offer different ways of depicting the same abstract ideas. Pull down a copy of the post and use it for reference when you just can’t seem to put the pieces together. Enjoy!

     

    image

     

     

     

     

      jonjor

  • 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

  • System Center Update Rollups!

    warning

    Two new updates have been released for System Center 2012 and for System Center 2012 SP1. There are many fixes in these rollups, so treat them as mandatory, not optional. Links below. Happy troubleshooting!

     

     

    System Center 2012

    Description of Update Rollup 7 for System Center 2012

    http://support.microsoft.com/kb/2888943

     

    System Center 2012 SP1

    Description of Update Rollup 4 for System Center 2012 Service Pack 1

    http://support.microsoft.com/kb/2879276

     

     

     

     

     

      jonjor

  • Orchestrator Event Monitor fires multiple times for new events

    image

    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

    image

     

    Here are the details of the Event Monitor activity:

    image

     

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

    image

     

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

    image

     

     

    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.

    image

    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.

     

     

     

     

     

      jonjor

Jonathan's Virtual Blog

Jonathan's Virtual Blog