locked
cumulative update 4 RRS feed

  • Question

  • how can i tell if scom has the cumulative update 4 installed?

    Tuesday, July 19, 2011 5:59 PM

Answers

  • that version number doesnt change for some reason.

    look at the view under "operations manager\agent\agent by version" and check out the "patchlist column"


    Rob Korving
    http://jama00.wordpress.com/
    • Marked as answer by Vivian Xing Friday, July 29, 2011 8:19 AM
    Thursday, July 21, 2011 1:21 PM

All replies

  • Hi

    For Management Servers and Gateways, check out the file versions:

    http://support.microsoft.com/kb/2449679

    For agents, there is an agent version state view under Operations Manager, agents -> the patch list field will tell you if CU4 has been applied.

    Cheers

    Graham

     


    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    Tuesday, July 19, 2011 7:12 PM
  • i am getting an error when running the install on my rms

     

    The setup wizard was intterupted before system center operations manager 2007 R2 could be installed. You system has not been modified. to complete installation at another time, please run setup again.

     

    the program failed to apply the software Update. Please check the patch file is present in the patch folder and proper version of MOM is instaled on the machine

    Tuesday, July 19, 2011 8:37 PM
  • Check the operations manager event log on the RMS .. although the following relates to CU3, it might still be an issue with CU4 and Kevin may provide the fix there:

    http://social.technet.microsoft.com/Forums/en/operationsmanagerdeployment/thread/b84e0fb2-7afb-4935-a538-0e931bbf7d26

    There is a great walkthrough here:

    http://blogs.technet.com/b/kevinholman/archive/2011/02/01/opsmgr-2007-r2-cu4-rollup-hotfix-ships-and-my-experience-installing-it.aspx?PageIndex=2

    And be aware of this:

    http://support.microsoft.com/kb/2526113

    Cheers

    Graham

     


    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
    Tuesday, July 19, 2011 9:02 PM
  • where is the log? still getting that error when I change the registry

    Tuesday, July 19, 2011 10:07 PM
  • still does not work. changed registry to 180000
    Tuesday, July 19, 2011 10:30 PM
  • sam problem with cu3
    Tuesday, July 19, 2011 10:45 PM
  • same problem with cu1, 2, 3, 4. any ideas??
    Tuesday, July 19, 2011 10:54 PM
  • Have you tried to run the update with a command line msiexec?  You can use that and specify a log file to view.
    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/
    Tuesday, July 19, 2011 10:55 PM
  • doesnt work either. tried it from command line with elevated prompt. 
    Wednesday, July 20, 2011 12:06 AM
  • here is the install log

     

     

    === Logging stopped: 7/19/2011  21:39:53 ===

    MSI (c) (B4:24) [21:39:53:542]: Product: System Center Operations Manager 2007 R2 - Update 'System Center Operations Manager 2007 R2 Cumulative Update 4 (KB2449679)' could not be installed. Error code 1603. Additional information is available in the log file C:\Users\ADMINI~1.WSG\AppData\Local\Temp\KB2449679-x64_0.log.

     

    MSI (c) (B4:24) [21:39:53:542]: Windows Installer installed an update. Product Name: System Center Operations Manager 2007 R2. Product Version: 6.1.7221.0. Product Language: 1033. Update Name: System Center Operations Manager 2007 R2 Cumulative Update 4 (KB2449679). Installation success or error status: 1603.

     

    MSI (c) (B4:24) [21:39:53:542]: Note: 1: 1729 

    MSI (c) (B4:24) [21:39:53:542]: Product: System Center Operations Manager 2007 R2 -- Configuration failed.

     

    MSI (c) (B4:24) [21:39:53:542]: Windows Installer reconfigured the product. Product Name: System Center Operations Manager 2007 R2. Product Version: 6.1.7221.0. Product Language: 1033. Reconfiguration success or error status: 1603.

     

    MSI (c) (B4:24) [21:39:53:542]: Attempting to delete file C:\Users\ADMINI~1.WSG\AppData\Local\Temp\fe8af6.msp

    MSI (c) (B4:24) [21:39:53:542]: Unable to delete the file. LastError = 32

    MSI (c) (B4:24) [21:39:53:542]: Grabbed execution mutex.

    MSI (c) (B4:24) [21:39:53:542]: Cleaning up uninstalled install packages, if any exist

    MSI (c) (B4:24) [21:39:53:542]: Attempting to delete file C:\Users\ADMINI~1.WSG\AppData\Local\Temp\fe8af6.msp

    MSI (c) (B4:24) [21:39:53:542]: MainEngineThread is returning 1603

    === Verbose logging stopped: 7/19/2011  21:39:53 ===

     

    Property(C): OutOfSpaceDlg_DlgDesc = Disk space required for the installation exceeds available disk space.
    Property(C): OutOfSpaceDlg_DlgTitle = Out of Disk Space
    Property(C): OutOfSpaceDlg_DlgText = The highlighted volumes do not have enough disk space available for the currently selected components. You can remove files from the highlighted volumes, choose to install less components onto local drives, or select different destination drives.
    Property(C): DiskSpaceDlg_DlgDesc = The disk space required for the installation of the selected components.
    Property(C): DiskSpaceDlg_DlgTitle = Disk Space Requirements
    Property(C): PreReqNotMetDlg_PreReq_Recommended_Not_Met = The recommended prerequisites for installation have not been met. You may continue to install Operations Manager, but you might not achieve optimum performance. For more information, click View Log.
    Property(C): PreReqNotMetDlg_PreReq_Not_Met = The mimimum prerequisites for installation have not been met. For more information, click View Log.
    Property(C): PreReqNotMetDlg_PreReq_No_Component_Selected = No components have been selected for installation. To select components for installation, click Back.
    Property(C): PreReqNotMetDlg_Title_PreReq_Recommended_Not_Met = Prerequisite Check Passed with Warnings
    Property(C): PreReqNotMetDlg_Title_PreReq_Not_Met = Prerequisite Check Did Not Pass
    Property(C): ReadyToInstallDlg_Desc = The wizard is ready to install Operations Manager 2007 R2.
    Property(C): ReadyToInstall_DlgTitle = Ready to Modify the Program
    Property(C): ReadyToInstall_DlgTitle2 = Ready to Repair the Program
    Property(C): ReadyToInstall_DlgTitle3 = Ready to Install the Program
    Property(C): ReadyToInstall_DlgText1 = If you want to review or change any of your installation settings, click Back. Click Cancel to exit the setup wizard.
    Property(C): FilesInUse_DlgDesc = Some files that need to be updated are currently in use.
    Property(C): FilesInUse_DlgTitle = Files in Use
    Property(C): FilesInUse_DlgText = The following applications are using files that need to be updated by this setup. Close these applications and click Retry to continue.
    Property(C): ReadyToRemove_DlgDesc = You have chosen to remove the program from your system.
    Property(C): ReadyToRemove_DlgTitle = Remove the Program
    Property(C): ReadyToRemove_DlgText1 = If you want to review or change any settings, click Back.
    Property(C): DestFolder_Text = Destination Folder
    Property(C): AgreeToLicenseDlg_Desc = Please read the following license agreement. Press the PAGE DOWN key to see the rest of the agreement.
    Property(C): AgreeToLicenseDlg_Title = End-User License Agreement
    Property(C): AgreeToLicenseDlg_No = I &do not accept the terms in the license agreement
    Property(C): AgreeToLicenseDlg_Yes = I &accept the terms in the license agreement
    Property(C): MaintenanceDlg_Remove = Remove this product from your computer. Use this option to remove all Operations Manager components.
    Property(C): MaintenanceDlg_Repair = Repair Operations Manager components that are already installed. Use this option to fix missing or corrupt files, shortcuts, and registry entries.
    Property(C): MaintenanceDlg_Modify = Change which Operations Manager components are installed. Use this option to add or remove components.
    Property(C): RootManagementServerDlg_Title = Connect to the Root Management Server
    Property(C): RootManagementServerDlg_MGServer = &Root Management Server:
    Property(C): RootManagementServerDlg_PageDesc = The Root Management Server is the first management server installed in a management group unless modified otherwise.
    Property(C): RootManagementServerDlg_Note = Note: To connect to the Root Management Server you must be a member of the Operations Manager Administrators user role.
    Property(C): RootManagementServerErrDlg_Desc1 = Unable to verify the Server.
    Property(C): RootManagementServerErrDlg_Desc2 = We were unable to connect to the given server. Please check the server name and it's DNS name resolution. Also make sure the user running setup is Operations Manager Administrator and try again.
    Property(C): RMS_Connect_Wait_Text = Setup may take a moment to conenct to the Root Management Server. Please wait...
    Property(C): CustomSetupTipsDlg_Title = Custom Setup Tips
    Property(C): CustomSetupTipsDlg_Desc = Custom setup allows you to select which components to install.
    Property(C): CustomSetupTipsDlg_Menu = The icon next to the component name indicates the install state of the component. Click the icon to drop down the install state menu for each component.
    Property(C): CustomSetupTipsDlg_FirstInstall = Will be installed on first use. (Available only if the component supports this option.)
    Property(C): CustomSetupTipsDlg_NetworkInstall = Will be installed to run from the network. (Available only if the component supports this option.)
    Property(C): CustomSetupTipsDlg_InstallState = This install state means the component...
    Property(C): CustomSetupTipsDlg_DontInstall = Will not be installed.
    Property(C): CustomSetupTipsDlg_Partial = Will have some subcomponents installed to the local hard drive.
    Property(C): CustomSetupTipsDlg_Install = Will be completely installed to the local hard drive.
    Property(C): CustomSetupDlg_Title = Custom Setup
    Property(C): CustomSetupDlg_Desc = Select the components that you want to install.
    Property(C): CustomSetupDlg_FeatureGroup = Component description
    Property(C): CustomSetupDlg_Location = <selected component path>
    Property(C): CustomSetupDlg_Install = Location:
    Property(C): CustomSetupDlg_ItemDescription = Multiline description of the currently selected item
    Property(C): CustomSetupDlg_Size = Component size
    Property(C): CustomSetupDlg_Text = Click an icon in the list below to change how that component will be installed.
    Property(C): ACSAgentFeature_Description = This component installs the Microsoft Operations Manager Audit Collection Agent.
    Property(C): DatabaseOptionsErrDlg_Title1 = Database Size Error
    Property(C): DatabaseOptionsErrDlg_Title2 = Out of disk space
    Property(C): DatabaseOptionsErrDlg_Title3 = Database or Database Files Already Exists
    Property(C): DatabaseOptionsErrDlg_Title4 = Database name error
    Property(C): DatabaseOptionsErrDlg_Text11 = The Operations Manager 2007 database requires a minimum of 500MB size. To continue setup click Back, change the database size to be greater or equal to 500MB.
    Property(C): DatabaseOptionsErrDlg_Text12 = Setup found that the selected database file locations do not contain sufficent disk space. To continue setup, go back and either choose a different drive or reduce the database size.
    Property(C): DatabaseOptionsErrDlg_Text131 = Setup has found that either the database server you specified contains a MOM database or that the database file location you specified contains the [Database Name].mdf or [Database Name].ldf database files.
    Property(C): DatabaseOptionsErrDlg_Text132 = To continue setup, either remove the existing database or database files, or click Back to select a different database instance or database file location.
    Property(C): DatabaseOptionsErrDlg_Text14 = The database name can contain only alphabets, numbers, '-',  '_' characters, should start with alphabet and cannot exceed 100 characters. To continue setup click Back, change the database name.
    Property(C): DatabaseOptionsDlg_Title = Database and Log File Options
    Property(C): DatabaseOptionsDlg_Desc = Enter the size for the database and the location for the database files. To change database file locations, click Advanced.
    Property(C): DatabaseOptionsDlg_ReferDocs = For more information about determining the disk space required, refer to the product documentation.
    Property(C): DatabaseOptionsDlg_Size = Database si&ze:
    Property(C): DatabaseOptionsDlg_DBName = Database Name:
    Property(C): DatabaseOptionsDlg_MB = MB
    Property(C): DatabaseOptionsDlg_DataLocation = Data file location:
    Property(C): DatabaseOptionsDlg_LogLocation = Log file location:
    Property(C): DatabaseOptionsDlg_FilesGroup = Database files:
    Property(C): AdvancedDBOptionsDlg_Title = Database Files Location
    Property(C): AdvancedDBOptionsDlg_Desc = Select the location for the database and log files.
    Property(C): AdvancedDBOptionsDlg_DataLoc = Database data file location:
    Property(C): AdvancedDBOptionsDlg_LogLoc = Database log file location:
    Property(C): RegisterUserDlg_Name = &User Name:
    Property(C): RegisterUserDlg_Company = &Organization:
    Wednesday, July 20, 2011 4:43 AM
  • Hi,

    According to the log, it says that "Setup found that the selected database file locations do not contain sufficent disk space. To continue setup, go back and either choose a different drive or reduce the database size."

    It seems that the disk space is not enough.

    Please refer to the following article, make larger disk space and then install the update again:

    http://blogs.technet.com/b/kevinholman/archive/2011/02/01/opsmgr-2007-r2-cu4-rollup-hotfix-ships-and-my-experience-installing-it.aspx


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, July 20, 2011 8:23 AM
  • i logged in as another user and looks like it worked but when i try to update the agent on the rms server itself it says

     

    upgrade patch cannot be installed because the program to be upgraded may be missing or the upgrade patch may update a different version of the program.

     

    how do I upgrade the agent manually?

    Wednesday, July 20, 2011 5:58 PM
  • When you run the CU updates on your management group infrastructure (RMS/Management Servers), you will not then have to run agent update, as this will take place when the CU bits get updated on them.  Now your backend and SRS will have to have agents updated, but the management servers and RMS do not require this (from what I remember).  In regards to Gateway servers, I am not sure, but Kevin Holman has several blog posts about the steps to take to apply a CU to a SCOM infra.

     

    http://blogs.technet.com/b/kevinholman/archive/2011/02/01/opsmgr-2007-r2-cu4-rollup-hotfix-ships-and-my-experience-installing-it.aspx

     

    Apparently it was so simple, his cat did it (verified by the cat raising it's arms in a victorious fashion).


    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/
    Wednesday, July 20, 2011 6:19 PM
  • all my servers were pending an upgrade of the agent but when i upgraded it, they still show as version

     

    6.1.7221.0

     

    this is not cu4

    Wednesday, July 20, 2011 7:31 PM
  • In the admin part of the console it will show this.  There is a view in the opsmanager views of the monitoring pane that shows something called agent patch list.  You have to look in that view.  

    Agents should appear in the pending upgrade, but your RMS or management servers should not appear in this list.


    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/
    Wednesday, July 20, 2011 7:37 PM
  • so how do I update the agent to cu4? I approved the pending update and it still shows as 6.1.7221.0
    Wednesday, July 20, 2011 9:18 PM
  • Where are you seeing that version number?
    Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/
    Wednesday, July 20, 2011 10:57 PM
  • that version number doesnt change for some reason.

    look at the view under "operations manager\agent\agent by version" and check out the "patchlist column"


    Rob Korving
    http://jama00.wordpress.com/
    • Marked as answer by Vivian Xing Friday, July 29, 2011 8:19 AM
    Thursday, July 21, 2011 1:21 PM