Need to read blogs
This blog post provides a playbook that demonstrates how to install Update Rollup 3 for System Center 2012 R2 Operations Manager.
First, please download the UR3 update package from the Microsoft Update catalog: http://support.microsoft.com/kb/2965445/en-us
Issue #1: After you install this update rollup package on all roles on the server that is running System Center Operations Manager 2012 R2 (except on the Gateway role), the updates do not appear in the Add or Remove Programs item in Control Panel.Issue #2: After you install this update rollup package, the version number of the console is not changed.No Workaround available yet.
Issue #3: After you install this update rollup package on a web console, you receive the following error message in Internet Explorer:Server Error in '/OperationsManager' Application.To resolve this issue, close and then restart Internet Explorer.
Issue #4: Agent is not updated when you use Pending Patch view in the Operations Manager console. To work around this issue, deploy the update to agents by using the Repair option. To do this, expand Device Management in the Administration hierarchy, right-click Agent Managed, and then click Repair to repair the agents.
Issue #5: Agent is not updated when you install from the gateway computer.
To work around this issue, copy the agent update from the SCOM server to the gateway computer. For example, copy KB2929891-amd64-Agent.msp from the following: \\SCOM Server\Program Files\System Center Operations Manager\Gateway\AgentManagement\amd64 Then, copy KB2929891-amd64-Agent.msp to the following: \\SCOM Gateway\Program Files\System Center Operations Manager\Gateway\AgentManagement\amd64Deploy the update to agents by using the Repair option. To do this, expand Device Management in the Administration hierarchy, right-click Agent Managed, and then click Repair to repair the agents.
Issue #6: When you try to import Microsoft.SystemCenter.Visualization.Component.Library, the import fails because of missing dependencies.To resolve this issue, import Microsoft.SystemCenter.Visualization.Component.Library again.
Please note: For XPLAT related issue please refer to the KB avbove.
Once the update was applied please check the application Event log for the following message:
If you are getting the following error which has the note that Microsoft.SystemCenter.TFSWISynchronization.mpb has the following dependency: Microsoft.SystemCenter.AlertAttachment.mpb, which should be installed from the SCOM 2012 R2 RTM media
The Microsoft.SystemCenter.TFSWISynchronization.mpb is located on the Installation media under Management Packs.
Once all dependencies are met, the Management Packs can be imported without dependency errors:
Please be aware of the following issues:
What's not clear through all SC URs now is if other URs such as 1 and 2 are required prior to applying 3. The documentation leads you to believe they aren't however when discussing this with the SCSM product team, they indicated prior URs are required.
Update Rollups are considered to be cummulative - can you direct me to the documentation that states somethng different?
The documentation isn't clear on the subject. In a lyncup call with the SCSM product team, someone mentioned URs had to be installed in order
during installation of our agents, I noticed an error event about MsiInstaller:
Product: Microsoft Monitoring Agent -- Error 1923.Service '@C:\Windows\system32\AdtAgent.exe,-500' (AdtAgent) could not be installed. Verify that you have sufficient privileges to install system services.
My account is Domain Admin and machine administrator, also the UR3 update is correctly installed:
Product: Microsoft Monitoring Agent - Update 'System Center 2012 R2 Operations Manager UR3 Update Patch' installed successfully.
Can I safely ignore this event?