Issues that are fixed in this update rollup
App Controller (KB2887822)
Issue 1You cannot view or restart Microsoft Azure virtual machines that are in a Stopped (deallocated) state.
Issue 2A6 and A7 Microsoft Azure Virtual machine sizes are displayed with a size of "Unknown."
Issue 3Images for Microsoft Azure virtual machines are listed when the image is not available in the selected region.
Issue 4You cannot specify an administrative user when a Microsoft Azure virtual machine is deployed.
Operations Manager (KB2880799)
Issue 1When you try to run a Windows PowerShell script or module in an AllSigned environment, you receive the following error message:
System.Management.Automation.CmdletInvocationException: AuthorizationManager check failed.
Issue 2Location points are not displayed on the GSM Map dashboard because of an SQL time-out error. When this problem occurs, the following events are logged in the Operations Manager log.
Event ID 33333
Task Category: None
Data Access Layer rejected retry on SqlError:
Message: Query processor could not produce a query plan because of the hints defined in this query. Resubmit the query without specifying any hints and without using SET FORCEPLAN.
Event ID 26319
Task Category: None
Source: OpsMgr SDK Service
An exception was thrown while processing GetProjectionsByCriteria for session ID uuid:e3999b5c-870f-42cb-9e78-f7a0850a7c29;id=1175.Exception message: Query processor could not produce a query plan because of the hints defined in this query. Resubmit the query without specifying any hints and without using SET FORCEPLAN.Full Exception: Query processor could not produce a query plan because of the hints defined in this query. Resubmit the query without specifying any hints and without using SET FORCEPLAN.
Issue 3An incorrect message description is generated when security event 5140 is monitored. For example, the message contains incorrect information for Source Address, Source Port, and Share Name.
Issue 4An empty target group is created when endpoints are enumerated. Additionally, a message that resembles the following is logged in the event trace log (.etl):
Issue 5By default, when a generic performance report is exported, the object information (such as server name, disk label, and so on) is collapsed, and the information is missing.
Issue 6When you start the network node dashboard on a computer that's running a 32-bit edition of Windows 7 Service Pack 1, CPU usage is near 99 percent, and the console may stop responding.
Issue 7A user role that is created by using Windows PowerShell on a non-United States locale-based system does not show the Display name and Description fields in the console.
Issue 8When you create an override on a group or when you use a cmdletadd to a group, you receive the following message:
Issue 9When you select objects on the dashboard, you receive the following error message:
Issue 10When network discovery is run, duplicate entries for the same device may be added to the database. This problem occurs when a different device key is found for the same device.
Issue 11Availability Reports may be displayed as blank because the vStateDailyFull aggregate is returned empty. This problem occurs when the time zone on the data warehouse server is set to UTC+0X:30.
Issue 12The monitored health state of the System Center Advisor agent is always in a "Warning" state on the Advisor Health State dashboard.
Issue 13Application Performance Monitoring (APM) is not functional when you upgrade to later versions of Operations Manager.
Issue 14A website cannot be discovered or monitored on a system that's running Internet Information Services 8 (IIS8) or Internet Information Services 7 (IIS7)if the HTTP binding is missing from the website configuration.
Operations Manager - UNIX and Linux Monitoring (part of KB2880799)
Issue 1In rare cases, the Monitoringhost.exe process on the Management Server may crash with an access violation 0xc0000005 when log files are monitored on UNIX and Linux computers. When this crash occurs, it causes the managed UNIX or Linux computers to become unmonitored and in a "Critical" state.
Issue 2When discovering a Linux computer, discovery fails during secure shell (SSH) discovery, or the operating system name and version are determined incorrectly. This issue can occur when multiple *-release files exist in the /etc directory, and one of the files is named os-release. Additionally, you receive an error message that resembles the following:
Standard Error: line 1: syntax error near unexpected token `('
Operations Manager - UNIX and Linux Monitoring (Management Pack update)
Issue 1A Solaris computer that uses lots of monitored resources such as file systems, physical disks, or network adapters, may run out of file descriptors and cannot monitor the resources. This is the result of the default user limit on Solaris being too low to allocate sufficient file descriptors. The updated agent now overrides the default user limit with a user limit for the agent process of 1,024.
Additionally, the Operations Manager agent's log file (/var/opt/microsoft/scx/log/scx.log) contains errors or warnings that resemble the following:
Issue 2A monitored Solaris Zone configured for dynamic CPU allocation with Dynamic Resource Pools may log errors in the agent logs and return incorrect values for Processor performance counters.
This issue applies to any monitored Solaris Zones configured to use Dynamic Resource Pools and a "dedicated-cpu" configuration that involves a range of CPUs.
Issue 3If Linux Container (cgroup) entries are in /etc/mtab directory, errors are logged when physical disk discovery is enabled, and some physical disks may not be discovered.
Additionally, errors that resemble the following may be logged in the Operations Manager agent's log file (/var/opt/microsoft/scx/log/scx.log):
Issue 4Physical disk configurations that cannot be monitored or failures in physical disk monitoring for UNIX and Linux computers, may cause failures in Logical Disk instances (File Systems) monitoring.
New support included in this update
- Debian GNU/Linux 7
- Java Enterprise Edition (JEE) Application servers:
- IBM WebSphere 8.0
- IBM Websphere 8.5
- Oracle Weblogic 12c
Note The JEE application server additions are a separate Management Pack release. However, they depend on updates to the UNIX/Linux agent.
Service Manager (KB2887775)
Issue 1You receive many 33610 events on various rules and subscriptions. Additionally, the size of the EntityChangeLog table grows because of stalled grooming.
Issue 2When you accidentally double-click a parent link of an extended Incident class object instead of single-clicking it, the console crashes. If the Incident class object has not been extended, the console does not crash if you double-click the parent link.
Issue 3Service requests may complete unexpectedly leaving any included activities in a Pending state.
Issue 4When you have many manual activities assigned to you, the "My Activities" view in the Self-Service Portal may not display the whole list of activities. In some cases, depending on the number of activities that are assigned to you, the "My Activities" view may be displayed without information.
Issue 5The Exchange Management Pack may always be in a state of "Pending Association" in the management pack sync Job in the console. Additionally, the status of the "Management Pack" node in the Data Warehouse space is "Failed" and may display an Event ID 33410 from the source deployment.
Issue 6Service requests that are manually canceled during execution are marked incorrectly as "Completed" when they should be marked as "Canceled."
Issue 7When a new SqlNotificationRequest instance is created, new rows are created in the sys.conversation_endpoints catalog view that has state="CO." Because the SqlNotificationRequest class does not provide any method to close the conversation accordingly, the sys.conversation_endpoints catalog view grows quickly to a very large number.
Issue 8Service requests that are put on hold are marked incorrectly as "Completed."
Issue 9Intermittently, file attachments are saved with zero (0) bytes in the database. The File Attachment record shows the correct data size together with file names and so on. But there is no actual data saved to the database.
Issue 10Service Manager cannot capture the failed status on invoked runbooks. Runbook activities therefore remain "In Progress" even though the invoked runbooks have finished with a "Failed" status.
Issue 11After Service Manager 2012 is upgraded to Service Pack 1, the Service Dependents view under Business Services is not displayed correctly. Additionally, creating or editing a new Business Service by adding one or more configuration items as "Service Dependents," the Business Service information is not saved.
Issue 12Other activities in a Service Request may start to run even though the current activity has not finished.
Issue 13When a reviewer is added to a Review Activity, workflow notifications may not always run. Additionally, you receive an Event ID 33880.
Issue 14After a self-service portal is upgraded to Service Pack 1, simple lists do not function correctly. For example, a drop-down option that was selected in a simple list is not unselected when another option is selected.
Issue 15This update enables "Run As" accounts for use with Exchange Connector.
Issue 16When Service Manager runs a task that was created by using the PowerShell authoring tool, the workflow does not run and you receive the following error message:
Virtual Machine Manager (KB2887779, KB2888944, and KB2888946)
Issue 1For scale-out file servers, if one of the file server nodes is offline, Virtual Machine Manager cannot discover or register the scale-out file shares.
Issue 2Virtual Machine Manager cannot deploy port profiles if one of the port profile's maximum size is reached.
Issue 3The Virtual Machine Manager Service crashes when there is an empty value for the vNICperf counter.
Issue 4A "RunAs" account cannot be defined by using a service setting and cannot support the validation for network load balancing.
Issue 5New virtual machines cannot be created from a library virtual machine if that library virtual machine has a snapshot on it.
Issue 6In some cases, if a user imports a user interface add-in, the user might be unable to access the Virtual Machine Manager Server connection because the PowerShellContext property is null.
Issue 7System Center 2012 Service Pack 1 Virtual Machine Manager cannot be uninstalled if any previous Update Rollup is applied to the system.
Issue 8Virtual machine creation fails because the VMNetworkServiceSetting property cannot be set.
Issue 9A new virtual machine deployment together with multiple pass-through disks may fail because Virtual Machine Manager cannot locate the boot or system volume during the installation of virtual guest services.
Issue 10The Virtual Machine Manager Service may crash when it tries to discover a virtual machine on specific Storage Area Networks (SAN) storage.
Issue 11In some cases, Virtual Machine Manager cannot update the VMWare host, the virtual machine or networking information.
Issue 12Virtual Machine Manager tries to reset a virtual local area network (VLAN) ID when there is no change in the virtual machine network (VM network) or virtual machine subnet (VM subnet) of the network adapter.
Issue 13When you migrate the storage of an online highly available virtual machine (HAVM), the cluster resource for the storage is not updated.
Issue 14Virtual Machine Manager may report 0-percent CPU usage or 0 kilobytes (KB) available memory on the Hyper-V host.
Issue 15Failed or canceled cross cluster migration does not clean the highly available virtual machine (HAVM) resource that is left in the target cluster.
Issue 16The Virtual Machine Manager Service may crash because of Foreign Key violations in the tbl_ADHC_FibrePort table. This can be caused by a port that is deleted by Virtual Machine Manager before mapping is added.
Issue 17Forecasting reports do not work if you use Microsoft SQL Server Analysis Services (SSAS) 2012.
Issue 18A Server Message Block (SMB) protocol dialect shows 30,000 network-attached storage devices when Virtual Machine Manager is run on a German locale.
Issue 19You try to create a virtual machine by using a virtual machine template. When you use some specific virtual hard disks (VHDs), the virtual machine creation may fail at the "Install VM component" step.
Issue 20VMware templates imported from the Virtual Machine Manager 2012 Service Pack 1 console that are deleted from the Virtual Machine Manager console are put in the "Missing" state.
Issue 21When a Windows Communication Foundation (WCF) channel is used after having aborted, the Virtual Machine Manager Service may ultimately crash.
Issue 22You migrate a virtual machine with live migration. If you then migrate the virtual machine with stopped migration (for example, the source location does not exist in the target host), the migration fails. Additionally, you receive the following error message:
Issue 23You change the Preferred Owners and the Possible Owners settings of a highly available virtual machine (HAVM). When you migrate the HAVM from a cluster to a stand-alone host, the Virtual Machine Manager Service may crash.
Issue 24When you run a physical-to-virtual (P2V) conversion or a virtual to virtual conversion (V2V), the conversion wizard should use the virtual machine network (VM network) parameter in the network adapter cmdlet instead of the logical network parameter.
Issue 25When unmasking a logical unit number (LUN) to the host, you may receive the following error message:
Issue 26You receive an error when you add a storage pool to Virtual Machine Manager. This problem occurs if the logical unit number (LUN) of the storage pool is part of multiple storage pools.
Issue 27After you install the Microsoft .NET Framework security update 2840632, some of user interface (UI) controls may not work.
Issue 28Servicing services that were deployed before Update Rollup 3 for System Center 2012 Service Pack 1 was applied might fail after Update Rollup 3 is applied.
How to obtain and install Update Rollup 4 for System Center 2012 Service Pack 1
Download informationThe update packages are available from Microsoft.
- To obtain and install the updates from Microsoft Update, follow these steps on a system that has a App Controller, Operations Manager, Service Manager, or Virtual Machine Manager component installed:
- Click Start and then click Control Panel.
- In Control Panel, double-click Windows Update.
- In the Windows Update window, click Check Online for updates from Microsoft Update.
- Click Important updates are available.
- Select the Update Rollup 4 package and then click OK.
- Click Install updates to install the update package.
- To manually download the update packages from Microsoft Update Catalog, go to the following Microsoft websites:
App Controller (KB2887822)Operations Manager (KB2880799)Operations Manager - UNIX and Linux Monitoring (Management Pack update)Service Manager (KB2887775)Virtual Machine Manager Server (KB2887779)Virtual Machine Manager Guest Agent (KB2888944)Virtual Machine Manager Administrator Console (KB2888946)
- To manually install the update packages, run the following command from an elevated command prompt:msiexec.exe /update packagenameFor example, to install the Virtual Machine Manager update (KB2887779), run the following command:msiexec.exe /update KB2887779_vmmServer.msp
Files updated in Update Rollup 4 packagesThe following files are updated in Update Rollup 4 for System Center 2012 Service Pack 1.
App Controller (KB2887822)
Operations Manager Update (KB2880799)
Operations Manager - UNIX and Linux Monitoring
Service Manager (KB2887775)
Virtual Machine Manager (KB2887779, KB2888944, and KB2888946)
ID do Artigo: 2879276 - Última Revisão: 20/06/2014 - Revisão: 1