And yes, the blog postings written by Kevin Holman all about applying a certain UR come in handy here. But still, IMHO, the updates themselves should be far more friendly by showing the installation status/results.
Having said that, there is a quick way in order to see whether the related SCOM 2012 R2 components updated successfully or not. When a SCOM 2012 R2 component is updated by an UR, the application log on that same computer will contain multiple Event IDs 1022. One of those is the best however since it states that the UR is applied successfully against that certain SCOM 2012 R2 component.
Some examples:
- SCOM 2012 R2 Management Server:
Log Name: Application
Source: MsiInstaller
Date: M/DD/YYYY
Event ID: 1022
Task Category: None
Level: Information
Keywords: Classic
User: <DOMAIN>\<USER>
Computer: <SCOM 2012 MS SERVER>.<DOMAIN>.<DC>
Description:
Product: System Center Operations Manager 2012 Server - Update 'System Center 2012 R2 Operations Manager UR3 Update Patch' installed successfully. - SCOM 2012 R2 Web Console:
Log Name: Application
Source: MsiInstaller
Date: M/DD/YYYY
Event ID: 1022
Task Category: None
Level: Information
Keywords: Classic
User: <DOMAIN>\<USER>
Computer: <SCOM 2012 MS SERVER>.<DOMAIN>.<DC>
Description:
Product: System Center Operations Manager 2012 Web Console - Update 'System Center 2012 R2 Operations Manager UR3 Update Patch' installed successfully. - SCOM 2012 R2 Console:
Log Name: Application
Source: MsiInstaller
Date: M/DD/YYYY
Event ID: 1022
Task Category: None
Level: Information
Keywords: Classic
User: <DOMAIN>\<USER>
Computer: <SCOM 2012 MS SERVER>.<DOMAIN>.<DC>
Description:
Product: System Center Operations Manager 2012 Console - Update 'System Center 2012 R2 Operations Manager UR3 Update Patch' installed successfully.
I agree, it’s a workaround, but at least it helps you to see whether everything went fine. And YES, please do check the file versions as well .
No comments:
Post a Comment