Rebooting/Patching SCOM Environment Procedure

Hello,
I have heard mixed opinions with respect to patching and rebooting a SCOM infrastructure. I have heard you can go ahead and patch the SQL server and not have to worry about the Management Servers and the gateways. I have also heard you should shutdown the
gateways, then shutdown the management servers, then shutdown the RMS server, then finally patch the SQL server. Likewise, when bringing the environment back online, the exact opposite procedure, SQL online first, then RMS, then Management Servers, followed
by gateways.
Does anyone have any official notes from Microsoft with regards to patching a SCOM environment?
Thanks.

If the patch you want to install is a OS system update, you can just install it. If you do not want the alert raised, put the server into Maintenance Mode.
If the patch is SCOM update, you need to follow the steps below.
1.Backup the operations Manager Databases and unsealed Management Pack’s
2.Install Update to the Management server
3.Install Update to the Web Console
4.Install Update to the Operations Manager Console
5.Install update to the secondary Management Servers
6.Install update to the gateway servers
7.Run the SQL scripts
8.Import Management Pack’s
9.Deploy the update to the agents
Juke Chou
TechNet Community Support

Similar Messages

Moving SCOM environment to new servers

We need to upgrade our SCOM servers from Windows Server 2008 to 2012.   In our current environment we have all of our servers in the same environment -- both Prod and Test servers. When we make the move to new servers, we want to fix that,
so that we have a proper Test environment with only the Test agents in it, and a Prod environment as well.    So, because we don't want to carry forward all of the old data that no longer applies to that environment, we were thinking that we'd
just no migrate over the SCOM databases, and start fresh.   I have an idea of how I plan to tackle this migration, but I am looking for some confirmation that what I have in mind make sense and would work.   So here's how I foresee the
migration going...
1. We install SCOM onto all the new Test environment servers, with a fresh database, everything brand new.
2. We export the management packs from the current SCOM environment and then import them into the new SCOM environment.
3. We update the Test SCOM agents and tell them to report to the new Test SCOM environment.
4. Repeat the same steps for Prod.
Is it really as simple as that?   Seems like if we have the management packs there, that all the overrides we've configured should still be there as well as the groups, monitors, rules, etc that we've created in our current environment.
So if we simply import those onto the new environment and tell the agent to go there, then everything should still apply correctly, right?
   Does that make sense?   Am I missing something and it's not really this easy?

Yes, it really is that simple. It's even easier if you have to upgrade the agents. I've already done this to migrate from SCOM 2007R2 to 2012R2. I stood up the new environment, imported the MPs and then ran discovery for the systems I wanted in that environment.
The new SCOM 2012R2 MG deployed/upgraded the agents and they were "dual-homed" reporting to the old 07 and the new 12 instance. After I was happy with the new 12 instance, I just removed the configs from the 07 agents and shut down the 07 management
group.
"Fear disturbs your concentration"

ODI Patch Testing Environment

Hi,
I am working on setting up the ODI environment. I am planning on having one master repository which holds three work repositories one for development and two exeuction ones for the quality assurance and production environments.
My question is:
For my patch testing environment, do I need to set it up the same way as my production environment, i.e. one master repository and three work ones. Or is it enough to have one master and work repository only?
The whole puprose of this environment is to try Oracle patches before implementing those patches on my actual environment.

Agents:
We are thinking of spinning a different agent for each developer. This should allow developers to work simultanously without affecting each other.
For production, we will probably have one agent and one scheduler agent as a starting point. As we see the need for more agents, we may create more.
Topology:
I didn't follow you on this point. Shouldn't both Dev and Production share the same topology since they share one master repository? If you mean having the same number of data servers, physical and logical schemas, then we do plan to have them consistent across the environment. So if we work with one physical schema in Dev, we will also be using one physical schema in production. (Most likely will not be the same physical schema.)

Patching through Deployment Procedures

Hi
I try to patch my databases 10.2.0.4 (CPU Oct release) through Deployment Procedures in Grid Control but its failing on Step: stagePatchStageApply without any warnings or comments. (Everything was working until GC crashed because of lack of space on filesystem. I have deleted the old files from softwareLibrary and restarted GC. OS reboot do not help as well.). Besides patching all is working well.
OS: Enterprise Linux 4.

Paste the emoms.trc meanwhile Can you try by setting up another software lib

Solaris 10 Sparc not rebooting in graphical environment

I've installed Solaris 10 on Sparc. When I reboot the system it only boots into character login prompt. I then logged in and cd /usr/dt and executed dtlogin which enabled me to bring up the graphical environment. This is a brand new install on some old hard drives.
When I installed 9 last week on this same machive, but different harddrive, the graphical login always came up.
What have I done or doing wrong. I installed solaris 10 for sparc and chose automatic reboot after installation so there weren't any other questions that I may have missed during the install.
Any help appreciated. Thanks.

It is working now - I ran sysid-unconfig, rebooted, re-entered all the info and it rebooted and came up to the login screen.

Best Practices for Patching RDS Environment Computers

Our manager has tasked us with creating a process for patching our RDS environment computers with no disruption to users if possible. This is our environment:
2 Brokers configured in HA Active/Active Broker mode
2 Web Access servers load balanced with a virtual IP
2 Gateway servers load balanced with a virtual IP
3 session collections, each with 2 hosts each
Patching handled through Configuration Manager
Our biggest concern is the gateway/hosts. We do not want to terminate existing off campus connections when patching. Are there any ways to ensure users are not using a particular host or gateway when the patch is applied?
Any real world ideas or experience to share would be appreciated.
Thanks,
Bryan

Hi,
Thank you for posting in Windows Server Forum.
As per my research, we can create some script for patching the server and you have 2 servers for each role. If this is primary and backup server respectively then you can manage to update each server separately and bypass the traffic to other server. After
completing once for 1 server you can just perform the same step for other server. Because as I know we need to restart the server once for successful patching update to the server.
Hope it helps!
Thanks.
Dharmesh Solanki

OMS patch post-install procedures fail

Hello,
It might be a long shot, but I have to ask for suggestions:
Doing PSU7 upgrade on the OMS server (11.1 EMGControl) , the last step (after OPatch apply) is to have "apply.sql" run:
$ORACLE_HOME/bin/rcuJDBCEngine [email protected]:1521:GRIDREPO JDBC_SCRIPT apply.sql $PWD $ORACLE_HOME
Please enter database password:
A SQL Error occurred!Unable to connect to the database using the provided details.
Please enter a valid hostname and port or check if the listener is up and running.[oracle@mn17 13711705]$ export ORACLE_HOME=/opt/oracle/11g/product/11.2.0/db_1
I attempted dozen times setting the environment - ORACLE_HOME to OMS_HOME and all PATHs, server name , db name, etc - to no avail.
Found a note on MOS that specifies a culprit such a cursor_ parameter, but related to 10.x ...
So far no progress-> even uninstall is not possible as same story repeats - the rollback script fails the same way...
THx,

Hello,
It might be a long shot, but I have to ask for suggestions:
Doing PSU7 upgrade on the OMS server (11.1 EMGControl) , the last step (after OPatch apply) is to have "apply.sql" run:
$ORACLE_HOME/bin/rcuJDBCEngine [email protected]:1521:GRIDREPO JDBC_SCRIPT apply.sql $PWD $ORACLE_HOME
Please enter database password:
A SQL Error occurred!Unable to connect to the database using the provided details.
Please enter a valid hostname and port or check if the listener is up and running.[oracle@mn17 13711705]$ export ORACLE_HOME=/opt/oracle/11g/product/11.2.0/db_1
I attempted dozen times setting the environment - ORACLE_HOME to OMS_HOME and all PATHs, server name , db name, etc - to no avail.
Found a note on MOS that specifies a culprit such a cursor_ parameter, but related to 10.x ...
So far no progress-> even uninstall is not possible as same story repeats - the rollback script fails the same way...
THx,

Handling of pending reboot, exclusive updates for patch management with SCCM 2012

Hello,
Planning to use SCCM 2012, I would like to understand how smart is SCCM 2012 when dealing with specific patch management situation.
Assuming I have the following:
- A given server to be patched is missing a lot of updates, several being mutually exclusive. This typical case will require several reboot / patching to properly obtain a server fully up to date.
- A given server to be patched is in pending reboot state because the local admin installed new software and has not restarted the server yet as requested
- Those servers have configured maintenance windows of 2 hours during each night. I scheduled a deployment of missing patches authorizing restart.
--> when the maintenance window will be reached:
- will the server first be restarted to clean the pending reboot ?
- will the the server be patched / restarted several times as required to fully meet the updates to be deployed.
Another scenario on workstation side:
- can I enforce deployment of updates at a given time, do not automatically restart the workstation during patch deployment, but after deployment schedule a mandatory restart with a countdown if there is a pending reboot... From end-user perspective, it
would have the following behavior. For instance:
- patches are automatically installed on Monday at 10 AM
- as soon as deployment is done, warning message is displayed to ask users to reboot
- then user has up to 48h to restart his computer by himself. If he does not do it, it will be automatically done after countdown expires.
--> Can such a scenario be managed by SCCM 2012 ?
Regards.

Hi,
I have a related question about deploying Microsoft Security Updates to workstations via SCCM 2012. Is there a way to deploy the MS updates to workstations and only suppress reboots for machines with users logged on or locked? There seems to
be only 2 different options for reboots, Suppress them all or don't suppress them at all. We would like SCCM to reboot the machines that are logged off, but suppress the reboot for those that are logged on, while at the same time, provide the user with
a notification that their machine needs to be rebooted (at their convenience).
We've tried applying the Domain GPO "No auto-restart with logged on users for scheduled automatic updates installations" (Enabled) and "Configure Automatic Updates" (Disabled), but the logged on/locked machines still receive the restart countdown with no
option to postpone or delay.
This is a show stopper for us since we have an environment where we are absolutely not allowed to reboot a logged on machine.
For a little background, we are coming from SMS 2003 and the Distribute Software Updates (ITMU) way of deploying MS Updates, where we could always set the program to run "Only when no user is logged on".
Please tell me there is a way to achieve our desired result.
Thanks,
Dan

SCOM 2012 R2 Post upgrade issues

Hey all,
yesterday we upgraded our SCOM environment from 2012 SP1 to R2. All of the installers ran fine without any issues. After a couple reboots it was back up however we have run into some issues.
Issue 1: The ACS seems to be broken. I can usually run a query on the ACS database manually and get back audit entries. However, now I am getting nothing back at all. Here are the errors that are repeated every few minutes on both
management servers. I did run the ACS upgrade on them both yesterday.
Error occured on database connection:
Status: 0x00040000
ODBC Error: 14
ODBC State: 01000
Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (ParseConnectParams()).
Database: Register
Connection: ComplianceTest
Statement: -
Error occured on database connection:
Status: 0x00200001
ODBC Error: 14
ODBC State: 08001
Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid connection.
Database: Register
Connection: ComplianceTest
Statement: -
Issue 2: Our UNIX agents are all greyed out now and when I try to upgrade them I get the following error.
EDIT: and here is something else I just found on our other management server
Any info would be great
Thanks
Warm Fuzzies!

I am going to update this post. The service is still crashing nightly. The views dvAll, dvAll5 and dvHeader are not being created. I tried the fix provided by the Microsoft rep and it did nothing. I have uninstalled and reinstalled
the ACS server multiple times and the views are never created. When I start the ACS services I get the same errors.
AdtServer encountered the following problem during startup:
Task: Load Certificate
Failure: Certificate for SSL based authentication could not be found. SSL authentication will be disabled
Error: 0x00000002
Error Message:
The system cannot find the file specified.
Error occured on database connection:
Status: 0x00040000
ODBC Error: 4624
ODBC State: 01000
Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot grant, deny, or revoke permissions to sa, dbo, entity owner, information_schema, sys, or yourself.
Database: SqlWriter
Connection: Maintenance
Statement:
I see where the forwarders are connecting. No other errors or messages. The service is set to start up as the Network Services account. The DOMAIN\SERVER$ has a logon and is mapped to the SQL user AdtServer on the OperationsManagerAC database.
We have almost a terabyte of data that we cannot get to after the R2 upgrade.
Very frustrating!!!!
Warm Fuzzies!

ZOnes not coming up after patching

Hi
I patched a T5240 Solaris 10 server having root and zone filesystems in zfs using Live Upgrade . patching and luactivate went on successfully .After reboot the server booted from the new BE but some of the zones did not boot while others started The error for the non booting zones while trying to boot manually is
zoneadm -z dgpb003z boot
zoneadm: zone 'dgpb003z': zone root /zones/dgpb003z/root is reachable through /zones/dgpb003z-sol10_u7_be3/lu/b
zoneadm: zone 'dgpb003z': call to zoneadmd failed
dgpb003z-sol10_u7_be3 is the old BE.
How can the zone be made to point to the new BE
Any help is appreciated

AS I used luupgrade the patching was done on the inactive boot environment created through lucreate . After luactivate activated the newly patched boot environment , the server booted but some zones did not come up THey were showing in installed state
The clone is made in the same root pool and zone pool as the original environment
Looks like after luactivate and rebooting the server with the newly created environment the zone paths seem to still point to the old environment On top of that the server would not boot from the original environment also . Looks to using lucreate on zfs is not reliable and has issues
Has someone come across this i problem Now How can it be made sure that the zone paths are pointing to the patched zone root

SCOM only monitoring disk space of a group of servers

I have been looking for a way to setup SCOM to ONLY monitor the disk space on a specific group of servers.
We have a sandbox environment that consists of approximately 100 servers. The only responsibility we have is to make sure these machines are patched. Everything else related to the OS and Software is handled by the developers who own the sandbox,
so no other monitors are needed. Microsoft patches are failing because some of the C drives do not have enough disk space. Is there a way to discover these servers and only have the disk monitored? All other monitors in SCOM can be ignored on these
servers.
Thanks for any assistance that can be provided.

Without knowing what else you have in your SCOM environment, it could be a lot of work to start excluding this group of servers from all the other monitoring you have.
Other options you could consider are to allow the servers to be monitored, but somehow exclude those alerts from being sent in any subscriptions, or putting the components of those servers into Maintenance Mode other than the C: drives, but both of these
options will still collect information on these 100 servers and take space in your SCOM DBs.
You can refer to this page for how to use the free space monitor and override it for a group that will target your 100 servers. http://blogs.technet.com/b/jonathanalmquist/archive/2009/04/04/logical-disk-free-space-monitor.aspx

SCOM 2007 R2 Removal

Hi Guys,
Looking for an advice, if there is any procedure to do SCOM 2007 R2 decommissioning, it is updated with Cu5
Thanks,
- Thanks, Varshinie

If you are looking to decommission the whole SCOM 2007 R2 environment (ie remove everything) then there is no need to remove the CU .. below assumes that there is only one SCOM environment and you want to purge it from your organisation:
1) Uninstall all agents.
2) Uninstall all core components (MS, RMS, Reporting). Potentially decommission the servers if they were dedicated to SCOM
3) If you are looking to reinstall at some time or want to use the SQL Servers for something else then delete the databases and logins for the SCOM service accounts
4) Disable the SCOM service accounts. You can delete them but I'd prefer to disable them in the first instance in case they have been reused elsewhere. If something breaks then you can just re-enable the account
5) If you have deployed the AD Management Pack then delete the OpsMgrLatencyMonitors container
6) If you used AD Integration then remove the container that this creates from AD
7) If you have configured excchange to relay messages from the Management Server then you can remove this configuration in Exchange
8) Network devices that have been configured to use SCOM can be reconfigured (security removed) to clean up the ACLs
9) Ideally, if you have created Run As Accounts for specific applications e.g. SQL then you might need to remove these from the applications themselves e.g. remove the SQL logins used for SQL monitoring
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/

Automatic create Software Update Group and assign patches

Does someone has a e.g. powershell/vbs script which does the following:
- step 1: verify which patches are added to Windows 7 image using SCCM 2012 Offline Servicing
- step 2: verify all downloaded and deployed patches in the SCCM 2012 environment
- step 3: get the multi-reboot patches
Then creates a Software Update Group and add all patches obtained in step 2 and exclude all patches obtained in step 1 and step 3..
Then I can assign that software update group to my Reference Image task sequence and I will not ran in the currently available problems where lists are to big and software updates during the task sequence are failing :-)
Does some likes this and want to help me with it ?
I think it is a nice solution for the patch deployment problem during the reference image task sequence phase.

1. I've not written a script for that but to be plain: why? There's no reason you shouldnt have those patches downloaded and deployed anyway in case someone makes a computer "the old fashioned way" then joins it to the domain.
2. This is what ADR is for. I've got a few runbooks to help with things like cleaning up expired patches, but you shouldn't need any script for this step specifically.
3. Getting multi-reboot patches someone already did for you :) http://blogs.technet.com/b/deploymentguys/archive/2015/03/11/excluding-known-multi-reboot-updates-during-a-zti-deployment.aspx
Basically for #3, you just replace the update task with the MDT version and put this script right in front. Bam, done :) As for the extra scripting to exclude downloading patches you injected with DISM (#1)... I honestly don't see a point ...
but I could probably write something if you wanted.

SCOM 2012 SP1 UR4 management servers grey state

Hi,
My SCOM environment is made up of the below :-
SCOM 2012 SP1 UR4.
3 SCOM Management Servers all on Windows 2008 R2 SP1.
Shared SQL 2008 cluster with 2 Windows nodes also on same OS.
Just recently all our SCOM management servers have been flipping in and out from grey to green state. Gateways/agents all look ok as showing green. Alerting from agents appears normal as can see lots of them in console.
Have flushed the health state cache folder on all 3 SCOM MS's and still the same issue.
Appreciate any help on this one.

Event id: 7011 - Was your server recently patched (Installed by any automatic updates) ?
IS SCCM Configured in your MS? If Yes disable and check?
Is Windows update service running ? Stop if for one or two days and check if this issue still appears
Reference threads:
http://social.technet.microsoft.com/Forums/en-US/b86e5a3d-0c2e-4d5e-9d3d-905da91fc982/scom-2012-event-id-7011-service-control-manager-error-when-fep-definition-updates-apply?forum=configmanagersecurity
http://stefanroth.net/2012/09/26/scom-2012-event-id-7011-service-control-manager-error/
Solution also available in: http://technet.microsoft.com/en-us/library/cc756319(v=ws.10).aspx
===========================================
For Event id 20026 -
1. Does your Operationsmanager database have enough space ? Check that first.
What is you DB size ?
How much is the free space left ?
2. Was there any resent change in the SCOM Action accoutn password ? Or has the password expired. Try re entering the SCOM Action password by re directing your self to Administration tab --> Run as Config -- > Accounts --> SCOM Action account.
The description would be - This is the user account under which all rules run by default on the agent.
Right click and go to properties and re enter the account name and password there and check.
Refer the below screen shot
Check this article as well:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/102d443c-db0e-4bf2-b0d6-31d7f9328537/all-agents-greyed-out-multiple-event-errors-with-ids-20026-20028?forum=operationsmanagergeneral
============================================
Event id : 11904 - As per my knowledge appears due to incorrect Alrting string display name selected in any Rule or monitor.
Also the description what you pasted in Event id : 11904 says Microsoft.SystemCenter.HealthService.ActionAccountConfigured.Error as highlighted below.
Suggest to re enter the action account password and tell the results.
Also is the Healthservice on the MS running using System account or Domain account ?
=================================================================
Description : The Microsoft Operations Manager Expression filter Module failed to query the delivered item, item was dropped.
Property Expression: Reachability/State
Error : 0XC00EE22
One or more workflows were affected by this. Workflow
name: Microsoft.SystemCenter.HealthService.ActionAccountConfigured.Error
Gautam.75801

SCOM. Event ID 29181. SnapshotSynchronization error

Hi!
The Management servers is constantly throwing following event id:
Error: 29181:
===========================================================================================
OpsMgr Management Configuration Service failed to execute 'SnapshotSynchronization' engine work item due to the following exception
Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessException: Snapshot data transfer operation failed batch write
   at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.SnapshotSynchronizationWorkItem.CheckBatchWriteErrors()
   at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.SnapshotSynchronizationWorkItem.TransferData(SnapshotProcessWatermark initialWatermark)
   at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.SnapshotSynchronizationWorkItem.ExecuteSharedWorkItem()
   at Microsoft.EnterpriseManagement.ManagementConfiguration.Interop.SharedWorkItem.ExecuteWorkItem()
   at Microsoft.EnterpriseManagement.ManagementConfiguration.Interop.ConfigServiceEngineWorkItem.Execute()
Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessException: Data access operation failed
Server stack trace:
   at Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessOperation.ExecuteSynchronously(Int32 timeoutSeconds, WaitHandle stopWaitHandle)
   at Microsoft.EnterpriseManagement.ManagementConfiguration.SqlConfigurationStore.ConfigurationStore.ExecuteOperationSynchronously(IDataAccessConnectedOperation operation, String operationName)
   at Microsoft.EnterpriseManagement.ManagementConfiguration.SqlConfigurationStore.ConfigurationStore.WriteConfigurationSnapshot(IConfigurationSnapshotDataSet dataSet)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
   at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
   at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.WriteConfigurationSnapshotDelegate.EndInvoke(IAsyncResult result)
   at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.SnapshotSynchronizationWorkItem.SnapshotBatchWritten(IAsyncResult asyncResult)
System.Data.SqlClient.SqlException (0x80131904): The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION.
Sql execution failed. Error 1750, Level 16, State 0, Procedure ManagedEntitySnapshotSyncIndexBuild, Line 25, Message: Could not create constraint. See previous errors.
0
1750
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.CompleteAsyncExecuteReader()
   at System.Data.SqlClient.SqlCommand.EndExecuteNonQueryInternal(IAsyncResult asyncResult)
   at System.Data.SqlClient.SqlCommand.EndExecuteNonQuery(IAsyncResult asyncResult)
   at Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.NonQuerySqlCommandOperation.SqlCommandCompleted(IAsyncResult asyncResult)
ClientConnectionId:daed4452-3c75-4350-9c97-52b3f4e44b87
===========================================================================================
When I try to debug this procedure (ManagedEntitySnapshotSyncIndexBuild) with SQL Management Studio, each step in the transaction (SELECT, ALTER or CREATE Index) completed successfully
separately. But, if I run procedure, all changes is rollback.
Configuration:
3 x SCOM Management Server 2012 R2 (Update Rollup 2 installed)
1 x SQL Server 2012 (all SP's and hotfixes)
Any idea how to resolve this ?
Regards
Timofey

Hi,
I would like to know that when did this issue happen, what changes in your SCOM environment before that? I have seen a similar issue, and the resolution for it is to change another switch as it seems like an network issue.
Here is the similar thread:
http://social.technet.microsoft.com/Forums/en-US/38a31daf-2c57-4376-b302-c8fc30bf9837/29181-opsmgr-management-configuration-service-failed-to-execute-snapshotsynchronization?forum=operationsmanagergeneral
In addition,we can increase the timeout using the following method on
all management servers:
Make a backup of "x:\Program Files\System Center 2012\Operations Manager\Server\ConfigService.Config"
Increase the timeout values in ConfigService.config for the following:
<OperationTimeout DefaultTimeoutSeconds="30"> to 300 seconds
<Operation Name="GetEntityChangeDeltaList" TimeoutSeconds="180" /> to 300 seconds.
Restart the configuration service
Hope this helps.
Regards,
Yan Li
Regards, Yan Li

Rebooting/Patching SCOM Environment Procedure

Similar Messages

Maybe you are looking for