As most everyone knows in the OpsMgr community Kevin Holman has an excellent article on the various CU installations including the one on CU5: http://blogs.technet.com/b/kevinholman/archive/2011/08/03/opsmgr-2007-r2-cu5-rollup-hotfix-ships-and-my-experience-installing-it.aspx
We ran into an issue which I did not see discussed in his article however – or to be more clear – his article told us what we had to do to succeed in the installation but not how it would fail if we didn’t have the correct pre-requisites in place. What was happening for us is we downloaded CU5, extracted it, and ran it but it failed and rolled back almost immediately. In the applications log we had an error from MSInstaller of event # 1024 with the information below:
“Product: System Center Operations Manager 2007 R2 - Update 'System Center Operations Manager 2007 R2 Cumulative Update 5 (KB2495674)' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127”
Per Kevin’s article:
“****Requirement – as a required practice for a major update/hotfix, you should log on to your OpsMgr role servers using a domain user account that meets the following requirements:
- OpsMgr administrator role
- Member of the Local Administrators group on all OpsMgr role servers (RMS, MS, GW, Reporting)
- SA (SysAdmin) privileges on the SQL server instances hosting the Operations DB and the Warehouse DB.”
In our installation, the account we were attempting to install with was an OpsMgr administrator and was a member of the local administrators group on all OpsMgr role servers but it did NOT have SA permission on the OperationsManager or the OperationsManagerDW. Once we added these rights on the SQL server, it installed without issue.
Bonus CU installation tip: If you don’t know who has the Operations Manager console installed and you have SMS or Configuration Manager in your environment, you can use the following blog article to identify systems with the OpsMgr console installed on them:
Summary: Make sure that the account that you attempt to install your OpsMgr CU under matches the requirements (OpsMgr administrator, local administrators group, and SA permissions on the OperationsManager and OperatoinsManagerDW.