Issues that this update fixes
Issues that are fixed in this update rollup
- Assume that users have both SMTP and Session Initiation Protocol (SIP) endpoints. When you send email messages to these users from the Service Manager console, Service Manager uses the Lync SIP endpoint as the email address.
- After you select the Service Requests with Service Level Warning feature, an error occurs about one hour later.
- After you select the Assigned to me view, a FullAdapter exception occurs about one hour later.
- When the Service Manager console runs in maximized mode, you encounter one or more of the following issues:
- You experience slow performance in the console, and the console consumes excessive CPU resources.
- Context menus in the console are not displayed as expected, and instead it is displayed at the upper-right hand corner of the main window.
- Scroll bars for the work items preview pane do not display when you run in full-screen mode. Even if the scroll bars display, they are still inactive and you cannot move the slider.
- Certain forms or wizards do not display appropriately. Specifically, only the left navigation pane displays and the right area is blank.
- When you create or edit on a User Prompts page in a request offering, the page is not displayed appropriately.
- When you scroll on an open work item or a configuration item form, the scrolling does not work. In this case, you can have the mouse held over the scroll bar for scrolling.
- When you run PowerShell workflows at the same time, the results are displayed as successful. Actually, the workflows fail.
- When a user tries to open an already opened attachment from a work item form, an exception is thrown.
- After you mark a release record as Closed, the attachment and associated details cannot be retrieved.
- When you create service requests from Request Offerings, it takes a long time to display the request offerings form.
- When you try to use a service request template, the console crashes.
- When you try to create a service request, a NullReferenceException exception is thrown and the console crashes.
- The Service Manager console shows a generic Microsoft SQL exception instead of the detailed Data Collision exception when you run in a non-English environment.
Additionally, this update rollup resolves the following issues for Service Manager:
- The p_DataPurging stored procedure is not completed during database grooming. Additionally, event ID 8623 is logged in SQL log that indicates the query processor runs out of internal resources and cannot produce a query plan.
- Assume that you add multiple RegEx expressions to a group definition. When you add or execute the group, a SQL exception is thrown.
- The Configuration Manager connector does not handle updates to the DeviceHasSoftwareItemInstalled property correctly. A divergence occurs in the data synchronization between the Service Manager and Configuration Manager databases.
- When Service Manager has any Management Packs from an earlier version present, MPImporter cannot import Management Packs from Operations Manager.
Issues that are fixed in this update rollup
This update rollup makes the stored procedure performance aggregate more robust against out-of-range values.
Adding multiple regular expressions (RegEx) to a group definition causes an SQL exception when the group is added or run.
Web applications fail when they are monitored by the System Center Operations Manager 2012 R2 APM agent.
Service Level Objectives (SLO) dashboards sometimes load in several seconds and sometimes take minutes to load. Additionally, the dashboard is empty after it loads in some cases.
Operations Manager Console crashes when you try to override the scope in the Authoring pane.
The System Center Operations Manager console is slow to load views if you are a member of a custom Operator role.
This update rollup includes a fix for the dashboard issue that was introduced in Update Rollup 1.
SQL Time Out Exceptions for State data (31552 events) occur when you create Data Warehouse workflows.
New features in this update rollup
1- Support for Windows Server 2003 workloads
2- Protection of SQL AlwaysOn with Clustering
3- Issues that are fixed in this update rollup
When you install DPM 2010, right after the prerequisites verification you receive an error “Verify that Windows Management Instrumentation (WMI) Service is running. if…
in order to fix this issue, you need to reinstall WMI , this is how to do it
From an elevated Command Prompt
1. Disable and stop the WMI service.
sc config winmgmt start= disabled
net stop winmgmt
2. Rename the Repository folder under C:\Windows\System32\wbem to Repository.old
3. Run the following commands.
Winmgmt /salvagerepository %windir%\System32\wbem
4. Re-enable the WMI service and then reboot the server to see how it goes.
sc config winmgmt start= auto