Archive for the ‘SCVMM & SCOM’ Category

System Center–Version

March 31, 2017

Below you can find a quick summary to identify the version by the build number, added also latest download links

Operations Manager

SCOM 2012 UR1 7.0.8560.1021
SCOM 2012 UR2 7.0.8560.1027
SCOM 2012 UR3 7.0.8560.1036
SCOM 2012 UR7 7.4.4337.0
SCOM 2012 SP1 UR1 7.0.9538.1005
SCOM 2012 SP1 UR2 7.0.9538.1047
SCOM 2012 SP1 UR3 7.0.9538.1069
SCOM 2012 SP1 UR4 7.0.9538.1084
SCOM 2012 SP1 UR5 7.0.9538.1106
SCOM 2012 SP1 UR6 7.0.9538.1109
SCOM 2012 SP1 UR7 7.0.9538.1117
SCOM 2012 SP1 UR8 7.0.9538.1123
SCOM 2012 SP1 UR9 7.0.9538.1126
SCOM 2012 R2 UR1 7.1.102626.1009
SCOM 2012 R2 UR2 7.1.10226.1015
SCOM 2012 R2 UR3 7.1.10226.1037
SCOM 2012 R2 UR4 7.1.10226.1046
SCOM 2012 R2 UR5 7.1.10226.1052

Virtual Machine Manager

SCVMM 2012 UR1 3.0.6019.0
SCVMM 2012 UR2 3.0.6040.0
SCVMM 2012 UR4 3.0.6055.0
SCVMM 2012 UR5 3.0.6057.0
SCVMM 2012 UR6 3.0.6060.0
SCVMM 2012 UR7 3.0.6062.0
SCVMM 2012 SP1 3.1.6011.0
SCVMM 2012 SP1 UR1 3.1.6018.0
SCVMM 2012 SP1 UR2 3.1.6020.0
SCVMM 2012 SP1 UR3 3.1.6027.0
SCVMM 2012 SP1 UR4 3.1.6032.0
SCVMM 2012 SP1 UR5 3.1.6038.0
SCVMM 2012 SP1 UR6 3.1.6046.0
SCVMM 2012 SP1 UR7 3.1.6084.0
SCVMM 2012 SP1 UR9 3.1.6099.0
SCVMM 2012 SP1 U10

3.1.6108.0

SCVMM 2012 SP1 U11

3.1.6109.0

SCVMM 2012 R2 3.2.7510.0 
SCVMM 2012 R2 UR1 3.2.7620.0
SCVMM 2012 R2 UR2 3.2.7634.0
SCVMM 2012 R2 UR3 3.2.7672.0
SCVMM 2012 R2 UR4 3.2.7768.0
SCVMM 2012 R2 UR5 3.2.7895.0
SCVMM 2012 R2 UR6 3.2.8002.0
SCVMM 2012 R2 UR7 3.2.8071.0
SCVMM 2012 R2 UR8 3.2.8117.0
SCVMM 2012 R2 UR9 3.2.8145.0
SCVMM 2012 R2 UR10 3.2.8169.0
SCVMM 2012 R2 UR11 3.2.8224.0
SCVMM 2012 R2 UR12 3.2.8292.0
SCVMM 2016 RTM 4.0.1660.0
SCVMM 2016 RTM UR1 4.0.1968.0
SCVMM 2016 RTM UR1 (Hotfix1) 4.0.1968.10
SCVMM 2016 RTM UR2

4.0.2043.0

SCVMM 2016 RTM UR2.1

4.0.2051.0

 
Checkout also below links for KB articles related to System Center family:
List of Public Microsoft Support Knowledge Base (KB) Articles for System Center 2012 Virtual Machine Manager (VMM 2012)
List of Public Microsoft Support Knowledge Base Articles for System Center 2012 Virtual Machine Manager Service Pack 1
List of Public Microsoft Support Knowledge Base Articles for System Center 2012 R2 Virtual Machine Manager
 

SCOM-Agent Failover

March 29, 2017

Operations Manager is the monitoring component from the System Center suite. Honestly one of the best and broadest monitoring solutions I saw so far. There is a ton of product knowledge inside the management packs. I’m using SCOM now for a while and based on my experience the most important rule when it comes to monitoring be sure you read the management pack guides Smile Next is to tune and tweak the management packs to your specifics.

Agents do have by nature ability to failover if you have SCOM large deployment where more than 1 management / gateway server exists. in case you have regional requirements you can configure the failover based on your needs

How to configure Gateway Failover?

#Set all Gateway Servers to use PRI_MS and Primary and FAILOVER_MS as Failover
$primaryMS = Get-SCOMManagementServer | where {$_.Name –match "SCOMMS1"}
$failoverMS = Get-SCOMManagementServer | where {$_.Name –match "SCOMMS1"}
$gatewayMS = Get-SCOMManagementServer | where {$_.IsGateway -eq $true}
Set-SCOMParentManagementServer -GatewayServer: $gatewayMS -PrimaryServer: $primaryMS
Set-SCOMParentManagementServer -GatewayServer: $gatewayMS -FailoverServer: $failoverMS

How to configure Agent Failover?

#Agents reporting to "SCOMGATEWAY1.DOMAIN.COM" – Failover to "SCOMGATEWAY2.DOMAIN.COM"
$primaryMS = Get-SCOMManagementServer | where {$_.Name –eq "SCOMGATEWAY1.DOMAIN.COM"}
$failoverMS = Get-SCOMManagementServer | where {$_.Name –eq "SCOMGATEWAY2.DOMAIN.COM"}
$agent = Get-SCOMAgent | where {$_.PrimaryManagementServerName -eq "SCOMGATEWAY1.DOMAIN.COM"}
Set-SCOMParentManagementServer -Agent: $agent -PrimaryServer: $primaryMS
Set-SCOMParentManagementServer -Agent: $agent -FailoverServer: $failoverMS

How to verify?

#Verify Failover for Agents reporting to "SCOMGATEWAY1.DOMAIN.COM"
$Agents = Get-SCOMAgent | where {$_.PrimaryManagementServerName -eq "SCOMGATEWAY1.DOMAIN.COM"}
$Agents | sort | foreach {
Write-Host "";
"Agent :: " + $_.Name;
"–Primary MS :: " + ($_.GetPrimaryManagementServer()).ComputerName;
$failoverServers = $_.getFailoverManagementServers();
foreach ($managementServer in $failoverServers) {
"–Failover MS :: " + ($managementServer.ComputerName);
}
}
Write-Host "";

SCOM Datawarehouse-Event31551 Failed to store data in the Data Warehouse

March 15, 2017

After I updated the SQL management pack to latest release we did saw below error related to SCOM DW system

Failed to store data in the Data Warehouse. The operation will be retried. Exception ‘SqlException’: Login failed for user ‘SCOMAccount’

image

since the latest SQL management pack update there are now new SQL RunAs profiles and one which is called “Data Warehouse SQL Server Authentification Account”. In my case the SCOM Action account was entered here and this is no permission on SQL to login so above error is correct. adding the right account fixed the issue and DW was back healthy state and data now gets pushed out of the OperationalDB to DW

image

image

again and again but reading the SQL management pack is a must for having a healthy SQL monitoring which is usually business critical databases

Microsoft System Center Management Pack for SQL Server
https://www.microsoft.com/en-US/download/details.aspx?id=10631

…Stay tuned and happy SCOM’ing!

SCOM Reporting Services-rslogon failed

March 15, 2017

After you change password for your service accounts for SCOM you can hit below issue if you have custom reports

image

There are few areas where passwords has to be updated in SCOM. beside the RunAs accounts you also have to update SQL reporting services credentials stored on your SQL server. Run the SQL reporting services configuration manager to update the credentials for RS (see below article to get more detailed steps)

image

If you still hit report error like below, highly like you have stored separate credentials credentials to accessing data sources. so I verified the new RunAsProfiles for SQL and make sure password is correct. Still I couldn’t get my reports. In this environment we also have lots of own custom reports which have do store own credentials for accessing databases.

so lets verify this Smile 

Open http://SCOMRS/Reports and select the report which failed above with “rsLogonFailed” –> Data Sources –> Test Connection

image

Gotcha! this report is using separate credentials to access databases. if possible, you should avoid this and use the shared datasource option for your reports

image

as a key in SCOM, review the management guide for SQL to get better understanding around security. sometimes the permissions to monitor SQL instances have to be granular and restricted to the minimum to monitor health of an SQL server (a.e. highly secure networks like DMZ). I do highly recommend to checkout the SQL server management pack guide especially since the latest release there are new RunAs profiles which allow better and granular control

Microsoft System Center Management Pack for SQL Server
https://www.microsoft.com/en-US/download/details.aspx?id=10631

Below are some useful resources related to this topic

How to Change the Windows Service Account Password for the SQL Server Reporting Service
https://technet.microsoft.com/en-us/library/hh456426(v=sc.12).aspx

How to Change the Credentials for the Action Account
https://technet.microsoft.com/en-us/library/hh456432(v=sc.12).aspx

How to Change Credentials for the System Center Management Configuration service and System Center Data Access service
https://technet.microsoft.com/en-us/library/hh456438(v=sc.12).aspx

How to Change the Reporting Server Execution Account Password
https://technet.microsoft.com/en-us/library/hh456428(v=sc.12).aspx

VMMUpdate – How to (automatically) check for available updates for SCVMM, Hyper-V and Failover Cluster?

April 11, 2011

Jonathan Jordan (Support Escalation Engineer) has released an really helpful tool to check the patch status for your SCVMM, Hyper-V and Failover Cluster environments. 

The solution here is called VMMUpdate!

VMMUpdate creates a report of required updates for technologies used by the SCVMM server and all Hosts.

– Windows
– Hyper-V
– Failover Cluster

As well as components SCVMM and other technologies leverage…

– WinRM
– BITS
– WMI
– VDS
– VSS

After extract you can start the script with “VMMUpdatev2.4.cmd” and when scan is completed you receive an textfile with all relevant information’s:

image

image

These logfiles are saved in C:\Windows\SCVMM\vmmupdate\logs

more details around VMMUpdate can be found at Jonathan’s Blog here:

http://blogs.technet.com/b/jonjor/archive/2010/10/14/vmmupdate.aspx

Download VMMUpdate is here

Kudos to Jonathan!

Stay tuned…. 😉

Regards

Ramazan