Just a quick one on our recent opsmgr R2 CU1 update.
Kevin Holman has a good post about his experiences. Start here. I would add the below
1. The gateway update does not copy the update msp to the agentmanagement folder. Due to this, when I approved updates for agents on the other side of a gateway, they did not get the update. You could fix this by copying the files from your gateway server before you approve your pending agent updates. Copy the files at c:\Program Files\System Center 2007 R2 Hotfix Utility\KB974144\agent to the appropriate directory under c:\Program Files\System Center Operations Manager 2007\AgentManagement. Make sure you copy the x86 update to the x86 folder. x64 goes in AMD64 and ia64 goes in ia64.
2. Only remotely managed agents will offer an update. In my case, my only agents that were manually installed were due to troubleshooting or other issues. Another solution from Kevin Holman shows how to reset your agents to be remotely managed. Pay attention to the whole post to make sure it is right for you.
3. If you didn’t realize your gateways were not updated (like me) or put in the wrong password for one of your domains, you may need to update manually. You can go on each server and run the installer and then choose install agent but that seemed annoying. You can do it from the server over the network w/:
"\\GATEWAYSERVER\c$\Program Files\System Center 2007 R2 Hotfix Utility\KB974144\SetupUpdateOM.exe" /silent /x86msp:KB974144-x86.msp /amd64msp:KB974144-x64.msp /UpdateAgent
4. or you can do what I did and psexec it w/:
psexec -u DOMAIN\user "\\comp1,comp2,compN" cmd /c "\\GATEWAYSERVER\c$\Program Files\System Center 2007 R2 Hotfix Utility\KB974144\SetupUpdateOM.exe" /silent /x86msp:KB974144-x86.msp /amd64msp:KB974144-x64.msp /UpdateAgent
Note that you need to pass the user to psexec (which will query for a password) so you can access network resources. Also note that I needed to enclose my computer list in “ to get it to pass correctly. YMMV.
Also note that this will not work w/ 2k8+ clients as UAC gets in the way. You could add –s to the the psexec line but then you would need a file share that the machine accounts could get at. You could also probably do a small script that did a net use and then accessed the files. I cheesed out and logged on directly as I only had a few that needed to be done manually.