For some odd reason, the CU1 isn't being automatically sent to newly console-deployed agents. Is it supposed to be? I've tried with 3 new deployments in the past couple of days and none are getting it.
andyinsdca
21 Jan 2010 5:34 PM
21 Jan 2010 5:46 PM
andyinsdca
If an agent isnt getting the hotfix - two things to check:
1. Look at the MS or GW you deployed the agent from - in the \AgentManagement folder. If it is missing on a MS - you didnt install the hotfix correctly. If it is missing on a GW - you must manually copy it there.
2. Look int he application event log of the agent - for the msiinstaller events - and see if the patch is failing.
andyinsdca
21 Jan 2010 5:47 PM
I got it, it just took a few min for the patch to pop into the list. I'm stupid :)
Larry
21 Jan 2010 5:50 PM
Re: Kevin
The goal is to successfully complete the CU1 and validate that it has been done.
Server (RMS and MS) and desktops that are running the Console seem to update fine, but running the same process for individual servers to update the agents isn't.
21 Jan 2010 6:07 PM
Larry - have you tried using the UI for the hotfix installer - and choosing "Run Agent Update" ?
That is what I would do - or simply run the correct MSP file on the agent:
KB974144-x86-Agent.msp
KB974144-x64-Agent.msp
KB974144-ia64-Agent.msp
SetupUpdateOM.exe is meant only for the larger MSP files - not these extracted files. If you need to run this as a command line - the correct syntax should be:
SetupUpdateOM.exe /x86msp:KB974144-x86.msp /amd64msp:KB974144-x64.msp /UpdateAgent
You use both MSP's in the command line - SetupUpdateOM.exe will detect the OS version and apply the correct one.
You CANNOT simply copy the MSP files and SetupUpdateom.exe over to a new system to patch it - there are other files which are necessary which get extracted to the default location of C:\Program Files\System Center 2007 R2 Hotfix Utility\KB974144
The absolute minimum would be a "package" with the two MSP files and SetupUpdateOM.exe in the root, with the \Agent and \Image folders also copied from the hotfix installer path listed above.
Drew Van Order
21 Jan 2010 8:43 PM
Hi Kevin,
As always, superb stuff.
We too had unpredictable results (.msp's not copying to(AgentManagement) with a number of our R2 environments. We even found a number of GW's and MS that still had old SP1 hotfixes, not to mention outdated asp, msxml, and oom files). Opened a call with support and just heard acknowledgement that this has been reported by other customers, and is being looked into. Nice to know MSFT's remediation steps were what we already did to correct ;-)
Larry
21 Jan 2010 10:04 PM
Kevin
Last set of instructions was perfect. Then followed up with steps 6-8 to confirm; all is well. NOW, as you pointed out, how to roll the agent update installer to the rest of the manually installed agents of mixed architecture...or I could spend all night here getting it done. =-( I suppose I would miss an opportunity to learn some more Powershell code!!
Brian
22 Jan 2010 1:17 AM
Perfect - the patchlist shoes the CU1 patch. I swore in pre R2 it only showed patches that were deployed via the console.
One other quetion. While I can filter to show agents with CU1 I cannot filter and show Agents without CU1. Anyone know how to do this?
Tom
22 Jan 2010 1:43 AM
Just wanted to confirm that this hotfix will update the agent version from 6.1.7221.0 to 6.1.7221.13
Thanks,
Tom
Brian
22 Jan 2010 1:47 AM
No it does not update the agent version. Agent version will stay .0
22 Jan 2010 1:51 AM
Patchlist has always showed all patches for all agents - it gets this from a discovery that runs on the agents.
Patchlist was changed to collect less data in a post-SP1 MP update, and this was included in R2.
For filtering and reporting on which agents are missing, or have a hotfix:
You can even run a custom configuration report - add the HealthService objects, and then tick the Patchlist box. :-)
22 Jan 2010 1:57 AM
Agent version WILL NOT change.
We do not increment the agent version number in hotfixes - only in major releases (RTM, SP1, R2)
Incrementing agent version with hotfixes was a major ordeal in MOM 2005 - because not all customers applied all hotfixes, and not all hotfixes were cumulative... so a customer implementing the ".55" version of a DLL hotfix, would not necessarily implement older hotfixes... which update other DLL's. The only way you could logically increment the agent version with a hotfix, is if you ONLY have cumulative hotfixes that apply to agents and management servers.
I would like to see that path taken as well, because agent version is such a simple, sortable field to see who needs a hotfix - and available in the "agent managed" section of the console - but since cumulative hotfixes just started in OpsMgr - I would not expect that anytime soon.
If you desire this capability - you should file a bug under feedback on connect.microsoft.com for OpsMgr.
Brian
22 Jan 2010 5:06 PM
Are there any known issues with upgrading the backend, then taking a couple of weeks to upgrade agents? Or does it need to be done as soon as possible?
Craig Pero
25 Jan 2010 10:22 PM
did anyone find that the MOMBidLdr.dll file did not match the documentation? the first one in the documentation for x64 was 5.2.3790.1289 but the file installed was version 5.2.3.3790.1290. I'm happy to see it a higher number than a lower number but didn't know if this was an issue or not. I assume if it was breaking something all grief would be on the table at this point.
AlanZ
26 Jan 2010 9:32 PM
Thanks Kevin, I had a similar experience and I'm now running CU1. My agents are showing that CU1 is installed in the patch list but not the MS and RMS, do you see the same thing ?