Packaging OpsMgr 2012 R2 Agent WITH Update Rollup in ConfigMgr 2012

Background About 6 months ago, I wrote a 2-part blog series on deploying OpsMgr 2012 R2 agents using ConfigMgr  (Part 1, Part 2). Since then, Update Rollup 1 and Update Rollup 2 has been released. Because UR1 did not include agent updates, I didn’t have to patch any agents. The most recent release of Update Rollup 2 does include agent updates, I’ll have to get the agents patched. For me, and the project that I’m working on, this is a perfect timing, UR2 was release right before we production transitioning our newly built OpsMgr 2012 R2 management groups and we

Applying OpsMgr 2012 SP1 UR3 Console Update via ConfigMgr Software Update

OpsMgr 2012 Sp1 Update Rollup 3 has been released for about a month now. Today I had some time after dinner so I thought it’s time for me to get my lab environment updated. In the past, I’ve been updating the OpsMgr server roles manually and using ConfigMgr Software Update (SUP) to apply the agent and console updates. While I was downloading the updates manually from WSUS (so I can manually update server roles), I noticed the console update is pretty big (621.5MB): This is because it contains updates for different languages. If I manually download it, I’ll see a

%d bloggers like this: