Huy Nguyen

23 Aug 2011 9:55 PM

Thanks again Kevin! I have successfully upgraded my SCOM R2 environment to CU5 by following your steps. Question: I have a server that I am unable to monitor with SCOM. I can manually install the agent and it shows up in SCOM and once I approve the agent, it just sits in the "Not monitored" state. This server name was once a print server cluster resource and was agentless managed but we have moved it to a VM. I think there must still be a residual entry in the OpsMgr DB somewhere. Tried running this against the OpsMgr DB "exec p_AgentPendingActionDeleteByAgentName 'agentname.domain.com" but it didn't help. Any suggestions?

Thanks,

Huy

Kevin Holman

23 Aug 2011 10:05 PM

@Huy -

How long was the old agentless cluster machine removed before you added the agent on the machine with the same name as the old cluster resource?

This is uncommon.... it is very possible that what happened is that since it was deleted, we only mark the object as deleted in the database - but it still exists for 2-3 days until it gets groomed. If you deployed the SCOM agent, it is very possible that we dont re-create the relationship correctly - and in the DB the machine is still managed by the old cluster node, and not by the management server it is now managed by. You can try some things: 1. Uninstall the agent and ensure it is deleted in the Agent Managed, and ensure that it is not showing up under Agentless at all, and wait 3 days. This is a good approach if you cant make any headway any other way. 2. Rename the server and install agent (unlikely possible) 3. There is a method via powershell to set the primary relationship with a management server for a healthservice - get-managementserver and set-managementserver. Check on the powershell commands for Gateway managed devices on technet for the commands.

SEB

24 Aug 2011 11:06 AM

Hi! We have upgraded from CU4 to CU5 and also upgraded client. Even after reboot and reapir the patchlist looks like this:

System Center Operations Manager 2007 R2 Cumulative Update 4 (KB2449679); System Center Operations Manager 2007 R2 Cumulative Update 5 (KB2495674); System Center Operations Manager 2007 R2 Cumulative Update 5 (KB2495674) - ENU Components;

Why is the CU4 entry still showing? Is it an error or can we ignore this and consider it successful? The file versions on the client all seems to be of version 6.1.7221.81.

Thanks,

Sven-Erik

hans de jongh

24 Aug 2011 11:33 AM

hi, i followed the steps but within the console everything still shows with version number 6.1.7221.0 is that correct?

Huy Nguyen

24 Aug 2011 3:01 PM

@Kevin-

>>How long was the old agentless cluster machine removed before you added the agent on the machine with the same name as the old cluster resource?

That cluster resource was removed about a year ago. The two physical cluster nodes are still being monitored by SCOM and they are providing agentless monitoring for the other cluster resources withing that cluster. I was going to try removing the rest of the agentless monitored cluster resources and then uninstall/reinstall the SCOM agent on the physical nodes to see if that will clear up the phantom cluster machine entry. Do you think this is a reasonable

approach?

Thanks,

Huy

Mike

26 Aug 2011 11:02 AM

Hi all,

Well I've done the upgrade and it's almost completely perfect, I have one issue that hopefully someone can help me with?

When approving the agents a handful (around 10) fail and do not update, as a test on one server I tried several ways to get the agent running, (reinstall, uninstall, repair etc and got no joy it just would not work. at this point I manually uninstalled the agent and tried to rediscover and could not, I have installed the agent manually and updated it but it does not appear in SCOM despite setting the management group.

Does anybody have any ideas on this, the server I tried this on isn't critical so we can do without monitoring on it but the other are extremley critical.

Many thanks in advance

Michael

5 Sep 2011 11:05 AM

Hi Kevin,

I have successfully updated all agetns in my environtment, but only one agent in the Agent Version list displays CU5. I have restarted the servers and made a repair, but they are still appearing as CU4. I have checked the file version of the files on the servers, they are all 6.1.7221.81, so they have been updated. Whats up? Thanks.

RHC

8 Sep 2011 1:42 PM

Hi Kevin

I have the same problem as SEB, our patch list shows "System Center Operations Manager 2007 R2 Cumulative Update 4 (KB2449679); System Center Operations Manager 2007 R2 Cumulative Update 5 (KB2495674); System Center Operations Manager 2007 R2 Cumulative Update 5 (KB2495674) - ENU Components;"

Is this a known problem? and can I fix it?

- RHC

VSN

15 Sep 2011 3:08 AM

I have upgrade scom cu4 to cu5 but scom agents are not reflecting in pending management. I have followed guideline given by Kelvin in Step2:-Apply the hotfix to the RMS. Issue is still persisting.

Kevin Holman

15 Sep 2011 3:23 PM

@Michael and RHC -

If your patchlist is not showing up correctly - most likely the agent monitored server needs a reboot for one of the components to apply correctly. This would be VERY common if you havent rebooted the server in a long time. One of the MSI's could not install due to a pedning reboot. I would recommend testing this by rebooting the server, then running a repair - and see if it shows up correctly then.

Kevin Holman

15 Sep 2011 3:25 PM

@VSN -

Agents are placed into pending actions based on the following criteria:

1. Agents are only placed into pending at the time the CU is applied – placing agents into pending is a post-install action of the CU itself.

2. Agents will only be placed into pending that are directly assigned to the RMS/MS that is being updated.

3. Agents will only be placed into pending if their “Remotely Manageable” flag is set to true/yes.

If an agent(s) is not placed into pending upon patching a RMS/MS with a CU, one of the following is true:

1. The agent(s) did not meet the criteria above.

2. The CU failed, or was not applied correctly, in order to allow the pending agent insert action to occur. The most common causes of this are not following instructions, not running from an elevated CMD (UAC), the management server needs a reboot from a previous MSI installation, not running from the splash screen, etc….

If you feel neither 1 or 2 apply, then the steps in the CU are failing for some external reason (DNS resolution, lack of resources, etc..) and only troubleshooting via the CU log will offer a solution.

Jarrad

20 Sep 2011 2:18 AM

Hi Kevin,

Awesome blog once again. Used it already 3 times. I have a question for you though regarding CU's in general. When deploying Ops Mgr for the first time is there any recommendations as to when to apply the current CU? i.e after all roles have been deployed or update as roles are installed? i've never been quite sure and can't find any supporting articles.

Many thanks,

Jarrad

Peter

29 Sep 2011 4:07 PM

Hello Kevin!

What about updating SCOM Reporting Services? Is there any doing?

Peter

PS: Great Job - great Article - thanks for your input !!!

Kevin Holman

29 Sep 2011 4:35 PM

@Jarrad -

Great question. I recommend installing ALL of the infrastructure (RMS, MS, DB roles, reporting, etc...) and THEN applying the CU to all of this, THEN deploy agents. You dont want to deploy agents, then apply and update with a CU, because that is double the work.

Kevin Holman

29 Sep 2011 4:36 PM

@ Peter -

All steps are covered in the KB article and my blog. There is no reporting server role update in this CU.