Pages

Thursday 12 June 2014

Set Failover for MS/Gateway Servers



1.      First list all Agents with Primary and Secondary MS/Gateway Server
#list all agents with Primary and Secondary servers
get-agent|ft -a ComputerName,primarymanagementservername,@{l=”secondary”;e={$_.getfailovermanagementservers()|foreach{$_.name}}}

2.      Second, isolate all agents which report to Primary MS/Gateway Server
 #Verify Failover for Agents reporting to FQDN_of_primaryMS
$Agents = Get-Agent | where {$_.PrimaryManagementServerName -eq ‘FQDN_of_primaryMS‘}
$Agents | sort | foreach {
Write-Host “”;
“Agent :: ” + $_.Name;
“–Primary MS :: ” + ($_.GetPrimaryManagementServer()).ComputerName;
$failoverServers = $_.getFailoverManagementServers();
foreach ($managementServer in $failoverServers) {
“–Failover MS :: ” + ($managementServer.ComputerName);
}
}
Write-Host “”;

3.      Third, set Failover MS/Gateway failoverMS for all agents which report to  Primary FQDN_of_primaryMS
#Agents reporting to FQDN_of_primaryMS – Failover to FQDN_of_failoverMS
$primaryMS = Get-ManagementServer | where {$_.Name –eq ‘FQDN_of_primaryMS‘}
$failoverMS = Get-ManagementServer | where {$_.Name –eq ‘FQDN_of_failoverMS‘}
$agent = Get-Agent | where {$_.PrimaryManagementServerName -eq ‘FQDN_of_primaryMS‘}
Set-ManagementServer -AgentManagedComputer: $agent -PrimaryManagementServer: $primaryMS -FailoverServer: $failoverMS
 

Monday 30 September 2013

System Center 2012 Operations Manager: Recommended Agent OS Fixes and Updates

This article discusses fixes and updates recommended for Microsoft System Center 2012 Operations Manager (OpsMgr) Agent computers.

http://support.microsoft.com/kb/2843219/en-us

Microsoft Monitoring Agent 2013 is available for download

Microsoft Monitoring Agent monitors computer infrastructure and application health. It collects diagnostic data, such as performance metrics, event logs, and traces. Microsoft Monitoring Agent can be used as a standalone tool or together with System Center Operations Manager. When monitoring .NET applications, you can direct the agent to save application traces in an IntelliTrace log format.

http://www.microsoft.com/en-us/download/details.aspx?id=40316&WT.mc_id=rss_alldownloads_all

Wednesday 18 September 2013

My Experience Handling Event ID: 31551 and 31552 issue



I have observed new flavors of Event ID 31551 and 31552 in our environment.

Event Type:      Error
Event Source:   Health Service Modules
Event Category:            Data Warehouse
Event ID:          31551
Date:                9/13/2013
Time:                11:06:52 AM
User:                N/A
Computer:         IND-MS1
Description:
Failed to store data in the Data Warehouse. The operation will be retried.
Exception 'InvalidOperationException': This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
One or more workflows were affected by this. 
Workflow name: Microsoft.SystemCenter.DataWarehouse.CollectEventData
Instance name: IND-MS1
Instance ID: {98AA3CF1-B05A-0B45-1417-3D532A1D5D79}
Management group: MG_LAB
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Error
Event Source:   Health Service Modules
Event Category:            Data Warehouse
Event ID:          31552
Date:                9/18/2013
Time:                9:46:00 AM
User:                N/A
Computer:         IND-MS1
Description:
Failed to store data in the Data Warehouse.
Exception 'InvalidOperationException': This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
One or more workflows were affected by this. 
Workflow name: Microsoft.SystemCenter.DataWarehouse.CollectEventData
Instance name: IND-MS1
Instance ID: {98AA3CF1-B05A-0B45-1417-3D532A1D5D79}
Management group: MG_LAB
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

To fix this issue please edit the below registry entry to 0

HKLM\SYSTEM\CurrentControlSet\Control\LSA\FipsAlgorithm 0