Hello, I recently deployed System Center Operations Manager Cumulative Update 3. I installed the update using this command line on our RMS: SetupUpdateOM.exe /x86msp:KB2251525-x86.msp /amd64msp:KB2251525-x64.msp /ia64msp:KB2251525-ia64.msp /x86locmsp:KB2251525-x86-ENU.msp /amd64locmsp:KB2251525-x64-ENU.msp /ia64locmsp:KB2251525-ia64-ENU.msp /Agent /noreboot Source: http://blogs.technet.com/b/kevinholman/archive/2010/10/12/command-line-and-software-distribution-patching-scenarios-for-applying-an-opsmgr-cumulative-update.aspx After that I approved the Agent Update Of course I also followed these before executing the command stated above: Backup the Operations and Warehouse databases, and all unsealed MP’s. Apply the hotfix to the RMS Run the SQL script(s) update against the OpsDB AND Warehouse DB. Import the updated management packs provided. Now when I look at the Agent Version view, I only see System Center Operations Manager CU2, instead of CU3. This is very strange, because when I do an repair of an Agent the correct version of CU3 is shown. I checked the MSI error logs for some of the agents where the update failed, the MSI logs of CU3, but I'am not able to found an error in these MSI error logs, if these help. The MSI error logs of installing CU3 are generated in C :\Program Files \System Center Operations Manager 2007\AgentManagement \AgentLogs\servernameMOMAgentMgmt.log. The update of the Agents seems to be executed, because an MSI error log is there. So I guess it seems to be failed. I'm willing to post these MSI error logs, if they are helpful in troubleshooting. Also no errors in the Operations Manager log. Now I'm really stuck and I have no clue, can someone help me diagnose and resolve this issue? Certifications: MCSA 2003|MCSE 2003|MCTS(4*)| MCTIP:SA

how many agents are reporting directly to your RMS? It might be better to ensure all the clients are updated to run a repair on the agents, (max of 200 at a time). hope this helps!Scott Moss MVP (Operations Manager) | President - System Center Virtual Users Group | Vice President - Atlanta Southeast Management Users Group (ATL SMUG) Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi there. Did you check the fileversions on the servers with a SCOM Agent installed? Approx. 14 files should be of fileversion 6.1.7221.49, among them files like these: HealthService.dll HealthServiceRuntime.dll Microsoft.EnterpriseManagement.HealthService.Modules.WorkflowFoundation.dll MOMConnector.dll MOMModules.dll MOMNetworkModules.dll And a new file shoud also be present: Microsoft.EnterpriseManagement.Modules.Azure.dllBest regards, Marnix Wolf (Thoughts on OpsMgr)

Marnix, The fileversion is 6.1.7221.49 on the servers where the Agents in Agent Version View show Cumulative Update 2. But why shows the view then CU2, when they are effectively CU3?Certifications: MCSA 2003|MCSE 2003|MCTS(4*)| MCTIP:SA

Hi there. So the Agents have been updated correctly. Looks like the SCOM R2 Console is not updated accordingly. Could be a Discovery issue as well. What you could try to do is to lower the Agent Patch Level discovery for a single server to lets say 5 minutes. And check out the Console in order to see what comes in for that server.Best regards, Marnix Wolf (Thoughts on OpsMgr)

See this posting of mine: http://thoughtsonopsmgr.blogspot.com/2009/04/patchlevel-discovery-of-scom-agents.htmlBest regards, Marnix Wolf (Thoughts on OpsMgr)

Hello, Thanks for your answer. What is the impact of doing this?Certifications: MCSA 2003|MCSE 2003|MCTS(4*)| MCTIP:SA

Hi Small as long as you target a single server of which you are sure the Agent is at CU#3 level.Best regards, Marnix Wolf (Thoughts on OpsMgr)