If you cannot or will not upgrade to OpsMgr 2007 R2 anytime soon – then this hotfix is for you!
Available at: http://support.microsoft.com/kb/971541
This updates OpsMgr 2007 SP1 to 6.0.6278.100. This is a rollup covering many new issues, plus most of the previously released critical hotfixes for OpsMgr. I recommend this rollup hotfix for anyone running OpsMgr 2007 SP1 that doesn't have very near term plans in place to upgrade to OpsMgr 2007 R2.
The Update Rollup for Operations Manager 2007 Service Pack 1 (SP1) combines previous hotfix releases for SP1 with additional fixes and support of SP1 roles on Windows 7 and Windows Server 2008 R2. This update also provides database role and SQL Server Reporting Services upgrade support from SQL Server 2005 to SQL Server 2008.
The Update Rollup includes updates for the following Operations Manager Roles:
- Root Management Server, Management Server, Gateway Server
- Operations Console
- Operations Management Web Console Server
- Audit Collection Server (ACS Server)
- Reporting Server
The following tools and updates are provided within this update which may be specific to a scenario:
- Support Tools folder – Contains SRSUpgradeTool.exe and SRSUpgradeHelper.msi (Enables upgrade of a SQL Server 2005 Reporting Server used by Operations Manager Reporting to SQL Server 2008 Reporting Server)
- Gateway folder – Contains a MSI transform and script to update MOMGateway.MSI for successful installation on Windows Server 2008 R2
- ManagementPacks folder – Contains an updated Microsoft.SystemCenter.DataWarehouse.mp which requires manual import
- Providing a rollup that supersedes nearly all SP1 binary hotfixes in a single package (~50 fixes) . See KB971541 for exceptions.
- Support for Windows 7 and Windows Server 2008 R2 - See KB974722 which will be updated to include data around the release of KB971541
- Operational and DataWarehouse database support for upgrade to SQL 2008.
- Additional stability hotfixes
- SCCM Monitoring via our 64-bit agent in the latest SCCM MP. See the latest SCCM MP guide for details.
- Exchange 2010 MP support
- Fix for Ops console crashes seen on Vista and Windows 7
The Supported Configurations Guide and Upgrade Guide have also been updated.
My experience upgrading a lab management group to the SP1 rollup:
First – I’d recommend making a plan…. like reading the KB article, known issues, and plan out the order of update operations. The KB article dont specifically state a specific order, so I will probably do something like this:
- Root Management Server (includes web console)
- all secondary Management Servers (includes any that are audit collectors)
- SCOM Reporting Server
- any stand alone OpsMgr consoles
- Agents (both from pending and manually installed)
Ok – getting started…..
- COPY the SystemCenterOperationsManager2007-SP1-KB971541-X86-X64-IA64-ENU.MSI file locally to the RMS.
- Run the update from the MSI – install to default locations
- If executing on Windows Server 2008 – run the MSI from an elevated command prompt.
- READ the release notes (you can copy these out to word to make them more readable
- Note the new splash screen for this hotfix:
- We will “Run Server Update”
- The hotfix installs with no further user interaction.
- The installer will finish – you can click “Finish”. However – another installer will kick off immediately afterward. This is by design – documented in the release notes, and is for installing localization updates. Then click “Finish” on the second update screen.
- At this point, you can click “Exit” on the Software Update splash screen.
- Continue applying the updates to the different roles – as documented in the release notes.
Some interesting things you might notice:
We actually clean up all the old hotfixes from the agent files – and move them to the root of \AgentManagement folder:
This is good – we wont try and re-apply them to subsequent agent installs/updates. Now – there will be two new hotfix files in the \x86, \AMD64, and \ia64 folders:
These include the agent hotfix update, plus a localization update which will vary based on your localization settings.
As for double-checking the update applied successfully – you can add “File Version” column to windows Explorer:
You will notice several management packs got updated in the console:
***Note – per the release notes and KB article
Import the following management pack from the ManagementPacks folder:
The location is a bit confusion – the full path would be: \Program Files\System Center 2007 Hotfix Utility\KB971541\ManagementPacks\
You can import this at any time… I’d recommend importing this after you are done updating all the server roles, including reporting.
In the console – you will also note that any agents that were not manually installed – will require an agent update. I would hold off updating any agents until your management group server roles are fully updated, and then only update around 200 agents at a time. This process will cause significant database and management server activity – so I’d advise doing the agent updates during off-peak use hours for large management groups:
- Next – I update my management servers, including any that run ACS (have a special ACS update for those too in the Hotfix installer splash screen)
- I kick this off on the SRS/SCOM Reporting server. Not prompted for anything… it completes in seconds.
- Next on the list – update agents. They all updated just fine via pending actions except for one…. this happens to be the same server that is hosting the OpsDB. Interesting. I got the following error:
The MOM Server failed to perform specified operation on computer DB.opsmgr.net.
Operation: Agent Install
Install account: OPSMGR\localadmin
Error Code: 8007064A
Error Description: The configuration data for this product is corrupt. Contact your support personnel.
This turned out to be due to some bad data in my HKEY_CLASSES_ROOT\Installer\Products\C9A0067E2876122489E4BA987C08CDD2\Patches\Patches REG_MULTI_SZ value. I am not sure how this got messed up – probably due to me testing a bunch of SP1 hotfixes previously and fat fingering a registry edit – so I would not assume this will be a common error. Once I fixed this registry entry – this agent updated just fine as well.
How can I be sure all my agents got updated?
One of the simplest ways – is to look at the “Patchlist” column on a Health Service State view. Create a new State View in “My Workspace”. Target “Health Service”:
On the Display Tab – select only Name, and Patch List: