Error between Management pack versions and SCVMM after upgrade SCVMM 2012 R2 to CU4

Hi friends!

After upgrade SCVMM 2012 R2 CU3 to CU4 I have seen in the VMM console on the connector between SCVMM and OpsMgr 2012 R2 CU4 an incompatibility with the Management Pack version and the SCVMM version.

vmmops01

Management pack Microsoft.SystemCenter.VirtualMachineManager.PRO.Library version 3.2.7672.0 is incompatible with this version of Virtual Machine Manager
Management pack Microsoft.SystemCenter.VirtualMachineManager.PRO.V2.Library version 3.2.7672.0 is incompatible with this version of Virtual Machine Manager
Management pack Microsoft.SystemCenter.VirtualMachineManager.Pro.2008.Library version 3.2.7672.0 is incompatible with this version of Virtual Machine Manager
Management pack Microsoft.SystemCenter.VirtualMachineManager.Library version 3.2.7672.0 is incompatible with this version of Virtual Machine Manager
Management pack Microsoft.SystemCenter.VirtualMachineManager.2012.Discovery version 3.2.7672.0 is incompatible with this version of Virtual Machine Manager
Management pack Microsoft.SystemCenter.VirtualMachineManager.2012.Monitoring version 3.2.7672.0 is incompatible with this version of Virtual Machine Manager
Management pack Microsoft.SystemCenter.VirtualMachineManager.2012.Reports version 3.2.7672.0 is incompatible with this version of Virtual Machine Manager
Management pack Microsoft.SystemCenter.VirtualMachineManager.PRO.V2.HyperV.HostPerformance version 3.2.7672.0 is incompatible with this version of Virtual Machine Manager
Management pack Microsoft.SystemCenter.VirtualMachineManager.Pro.2012.Diagnostics version 3.2.7672.0 is incompatible with this version of Virtual Machine Manager
Management pack Microsoft.SystemCenter.VirtualMachineManager.2012.Discovery version 3.2.7672.0 is incompatible with this version of Virtual Machine Manager

Seeking on internet I saw entries talking to change a key in the registry of the SCVMM server. In my case this key was correct and I didn´t it.

https://social.technet.microsoft.com/Forums/projectserver/en-US/1392e940-c8b6-4004-bbc5-9173b19ae59e/management-pack-microsoftsystemcentervirtualmachinemanagerprolibrary-version-3160320-is?forum=virtualmachinemgrproscintegration

http://technet.microsoft.com/en-us/library/hh882396.aspx#BKMK_registry

And also Kevin Holman talk about it:

http://blogs.technet.com/b/kevinholman/archive/2012/08/21/integrating-vmm-2012-and-opsmgr-2012.aspx

But I´m lucky, the registry key issue it´s ok in my SCVMM 2012 R2 CU4 version and I only need to rebuild the connection between SCVMM and OpsMgr and the problem is gone.

vmmops03

Here we remove and rebuild the connection:

vmmops02

Appear the wizard

vmmops04

Add OMS that is RMS and Service Account (In my case Service Account comes configured)

vmmops05

Add connection user name (I used the same user than on the past window)vmmops06

Finish the wizard.

vmmops07

Now the problem is gone!

vmmops08

Regards!

How to find a RunAsAccount from their SSID

Hi!

Today installing and configuring various MP in a SCOM 2012 R2 I needed to find the RunAsAccount from their SSID.

Seeking on internet I found this article http://michielw.blogspot.co.uk/2011/02/scom-account-specified-in-run-as.html that say how to do.

I did the following:

Log in the SCOM OMS Server

Create a ps1 file with the following lines (Look that I changed Get-RunAsAccount for Get-ScomRunAsAccount):

Get-ScomRunAsAccount | Sort Name | % {$string = $null;$_.SecureStorageId | % {
$string = $string + “{0:X2}” -f $_}

$RunAsAccountName = $_.Name
[string]$RunAsAccountSSID = $string
if ($SSID -match $RunAsAccountSSID) {write-host “The Run As Account is .. $RunAsAccountName”}
}

Execute from powershell console and insert the SSID.

SSID

Open OpsMgr console and go to Administration Pane\ Run As Configuration \ Accounts and seek the Run As Account name that you saw on the powershell. Double click and on credentials tab you can see the account name.

Regards!

SCOM 2012 R2: Unable to connect to the Data Access service for this management server

Hi folks,

These days I´m implementing a SCOM 2012 R2 on a environement where I have one OMS, one Reporting server and a two node sql 2012 SP1 failover cluster.

The problem that I have been experiencing is when I was installing reporting services (SSRS) in the dedicated server for that porpouse. The error showed in installation log OpsMgrSetupWizard.log was:

Info: :Could not connect to Management Server: OperationsManagerServer with exception: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[15:43:35]: Info: :StackTrace: at System.Version.TryParseVersion(String version, VersionResult& result)
at System.Version..ctor(String version)
at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupHelpers.IsManagementServerCurrentVersion(String managementServer)

In the wizard I saw the message: Unable to connect to the Data Access service for this management server. Ensure the Data Access service is running and that the service, the management group, and setup are all the same version.

Imagen

I solved it adding data writter account, data access account and sdk account to a gpo that allow for these accounts log on locally in the Operations Manager servers.

Regards!

 

 

 

Register sdk service account for SCOM 2012 R2

Hi,

Like others SC products, you need to register the sdk service account that run OM services in your OMS with setspn to work correctly.

The syntax to execute are below:

setspn -S MSOMSdkSvc/OMS.domain.fqdn.com domainnetbiosname\SVC-SCOMsdk-PRE
setspn -S MSOMSdkSvc/OMS domainnetbiosname\SVC-SCOMsdk-PRE

To see if you did ok, use setspn -L SVC-SCOMsdk-PRE

If you want to know more about SPN for SCOM I put here a good article from Kevin Holman.

http://blogs.technet.com/b/kevinholman/archive/2011/08/08/opsmgr-2012-what-should-the-spn-s-look-like.aspx

Regards!