Version 3.0 of Damian’s and My Script to Download All SCOM Management Packs with PowerShell

So my good friend Damian Flynn and fellow MVP has decided to bring this script to another level by making more like PowerShell module than only script. The result is cleaner code and some parts can be reused. You can find the new version here. Some of the changes include:

  • Refactored the script to a powershell module, and split the code into functions to ease support and prepare for some automation ;)
  • added Write-CMTraceLog – to enabled it execute   Get-SCOMManagementPacks –CMTrace
  • removed two download links that are incorrectly gathered at the beginning

I hope you will like these improvements. Leave any feedback on the TechNet Gallery page. This is why community rocks. Expect more from Damian on this topic.

SCVMM and Windows Azure Pack Surveys

I would like to bring you two survey that you should fill in:

PSWB – Script to run a search for required updates data in System Center Advisor

I’ve just released a PowerShell script similar to the ones released by Advisor team. The search in Advisor is focused on Required Updates for servers. You will need System Update Assessment Intelligence Pack enabled in Advisor. You can find the script here.

System Center Advisor Limited Preview is Still Open for Registration

I’ve just received a message from Daniele Muscetta – one of the PMs for System Center Advisor that there are still slots available for the preview. So if you want to try it yourself head here for instructions.

Tips From the Field: Applying Update Rollup 3 to System Center 2012 R2 and Windows Azure Pack

SCSMWhile I was on vacation UR3 for System Center 2012 R2 and Windows Azure Pack was released. In this release the following components were up for update:

As always there are some important fixes and feature in this updated so I recommend to apply it. Of course first in your Test/Dev environment.

Here are some tips that you might find useful during deployment:

  • VMM update contains a SQL script that you will need to execute against the VMM DB. That script you can find in the KB for the update;
  • VMM Management Packs are also updated so you will need to import the new versions in SCOM. If one of the MPs fail during import try importing them again.
  • VMM contains a DHCP extension plugin that is installed on Hyper-V hosts. There is updated for that extensions that you will need to apply manually. More here.
  • When you update VMM management packs you might receive Report deployment error for ‘Microsoft.Virtualization.Reports.ForecastMachineGroupNetworkIO’. I would guess that this is some kind of a bug that will be fixed. Not a fatal one.
  • When you apply VMM server update you may need to stop SCOM health service and Virtual Machine Manager agent service.
  • SCSM update contains some special instructions of executing PowerShell script after update. You will find the information in the KB.
  • When you apply SCSMA update for Runbook worker you will need to stop the Runbook Service.
  • Updating SCOM will require executing scripts against OperationsManagerDB and OperationsManagerDW. Those scripts will be available in your SCOM installation folder after applying the update. It is better to stop your SCOM services on your Management servers while applying them.
  • To update SCOM agents to UR3 you will need to reject them trough Pending Management and do repair trough Agent Managed.
  • After update of SCOM Gateway server you will need to copy the new version of SCOM agent manually.
  • After updating DPM agents on Hyper-V hosts you will need to restart the Hyper-V hosts in order backup to work.
  • When DPM agents are updated on Hyper-V hosts and hosts are restarted you will need to do consistency check on backups of VMs.
  • Remember to update consoles for SCSM, SCOM and VMM on places you have them installed.

Hope this was helpful for you.

Kemp LoadMaster Monitoring Management Pack (Community MP)

Recently I was looking how to monitor Kemp LoadMaster devices with SCOM. I was able to discover them trough SCOM as Network Devices but that was the only thing and it was not enough. Fortunately fellow MVP Daniele Grandini decided to help me and develop Kemp LoadMaster Management Pack. He was the main driver for this MP to exists as he was the main developer and I’ve took the task of testing it and fixing some small bugs that we’ve encountered. This is initial version of the MP and contains some know issues some of them are due to kemp loadmaster others are internal for the MP. Consider this version somehow as beta as we have some plans to re-write the MP in the future if we can. You will find the MP here along with some documentation. You can log any feedback you have on the Codeplex page.

Using VMM Cmdlets locally on SMA Worker Server in SMA Runbooks

If you are working with SMA and VMM you are probably familiar with the following sample Runbook for connecting to VMM:

workflow Sample-Managing-VirtualMachineManager  {      # Connection to access VMM server.      $VmmConnection = Get-AutomationConnection -Name 'VmmConnection'      $VmmServerName = $VmmConnection.ComputerName        # Create a PSCredential from the 'Username' and 'Password' fields within       # 'VmmConnection' because this is the form of authentication that an       # inlinescript accepts.       $SecurePassword = ConvertTo-SecureString -AsPlainText -String $VmmConnection.Password -Force      $VmmCredential = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $VmmConnection.Username, $SecurePassword            inlinescript {          # Import VMM module.          Import-Module virtualmachinemanager                    # Connect to VMM server.          Get-SCVMMServer -ComputerName $Using:VmmServerName            # Obtain VMM server license information.          Get-SCVMMAccessLicense -VMMServer $Using:VmmServerName -License      } -PSComputerName $VmmServerName -PSCredential $VmmCredential  }
Trough this way basically you are making remote connection to the VMM server and you are executing everything there. For most cases this is not the best way and there is another one. The other way is to install the VMM console on the SMA worker server/s thus making available the VMM cmdlets there. Keep in min that this also requires updating the console upon new Update rollup.
Now that we have the cmdlets on the SMA worker you can use a simple example like this to make the connection to VMM:

workflow Get-VM
$VmmConnection = Get-AutomationConnection -Name ‘VmmConnection’
$VmmServerName = $VmmConnection.ComputerName 
$SecurePassword = ConvertTo-SecureString -AsPlainText -String $VmmConnection.Password -Force 
$VmmCredential = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $VmmConnection.Username, $SecurePassword 
$VMMobject=Get-SCVMMServer -ComputerName $VmmServerName -Credential $VmmCredential

$VMS=Get-SCVirtualMachine -VMMServer $VmmServerName | select -Property Name

Hope this helps you when you integrate SMA and VMM.

Begin Your Journey to the Cloud with the Cloud Administrator


Get every new post delivered to your Inbox.

Join 838 other followers