Description of Update Rollup 1 for System Center 2012

Issue 1

If a snapshot is merging into the parent virtual hard disk (VHD), and if the virtual machine is deleted, the VHD file is not deleted.

Issue 2

The Store-VM and Move-VM Windows PowerShell cmdlets ignore the -RunAsynchronously switch.

Issue 3

When an IP address is used from an IP pool, cluster creation is unsuccessful, and you receive the following error message:

Issue 4

If a highly available virtual machine is running on a cluster node that fails, the virtual machine status changes to "Update Failed." Additionally, the status is not updated until the cluster node is back online.

Issue 5

When you manually install the Virtual Machine Manager (VMM) Agent on a perimeter host, the user name and password are unexpectedly logged in the AgentSetup.log file on the host computer.

Issue 6

Successive virtual machine creations take longer if many virtual machines are created and deleted in a short time.

Issue 7

Agent upgrade fails during VMM upgrade if the Microsoft Virtual C++ 2008 Redistributable package is installed on the host computer. Additionally, you receive the following error message:

Issue 1

Powershell.exe memory usage may increase when the Set-SCGuestInfo and Read-SCGuestInfo Windows PowerShell cmdlets are used to obtain or to set the virtual machine Key Value Pair (KVP) values.

Note This is a VMM Client and Server issue. To resolve this issue, you must install the Virtual Machine Manager Console Update (KB2663960) package and the Virtual Machine Manager Server Update (KB2663959) package.

Issue 2

The Virtual Machine Manager console stops responding when many virtual machines are sorted.

Issue 3

If System Center App Controller and the VMM Server are installed on separate servers, single sign-on does not work when App Controller is used.

Issue 4

If a host network adapter property setting is changed, the SubNet VLAN settings are changed even if the settings were not changed by the administrator.

Issue 5

An Internal virtual network is created as a private network if the virtual network name contains any of the following special characters:

/ ? ! @ # % ^ & * ( ) _ + } { " : ] [ \Note This is a VMM Client and Server issue. To resolve this issue, you must install the Virtual Machine Manager Console Update (KB2663960) package and the Virtual Machine Manager Server Update (KB2663959) package. If the VMM Self-Service Portal is installed, the Virtual Machine Manager Self-Service Portal Update (KB2663961) package must also be installed.

Issue 6

Performance issues may occur if the console is open for several days and if many jobs were created.

Issue 7

Concurrent attach and detach operations may take a long time to complete on a cluster that hosts many virtual machines.

Note This is a VMM Client and Server issue. To resolve this issue, you must install the Virtual Machine Manager Console Update (KB2663960) package and the Virtual Machine Manager Server Update (KB2663959) package. If the VMM Self-Service Portal is installed, the Virtual Machine Manager Self-Service Portal Update (KB2663961) package must also be installed.

Issue 1

Users are prompted for credentials even though single sign-on functionality is enabled for App Controller. For more information about how to enable single sign-on for App Controller, go to the following Microsoft TechNet website:

Installing App Controller

Issue 2

When the Repair option is run by using the Programs and Features item in Control Panel, the SQL database configuration for App Controller is removed.

Note Installing this update package for App Controller will restore the SQL database configuration. The administrator can also restore the SQL database configuration by following the steps in the "Removal Instructions for App Controller" section.

Issue 1

Environment crashes in Operations Manager because of RoleInstanceStatusProbe module in AzureMP.

Issue 2

When multiple (two or three) consoles are running on the same computer under the same user account, the consoles may crash.

Issue 3

You cannot start or stop tracing for Reporting and Web Console if they were installed to a stand-alone server that is running IIS.

Issue 4

Connected Group alert viewing is not working, but no error is given in console.

Issue 5

Task result - CompletedWithInfo not supported with the SDK2007 assemblies.

Issue 6

SeriesFactory and Microsoft.SystemCenter.Visualization.DatatoSeriesController have to be public to give the controls extensibility and reuse.

Issue 7

WebConsole is not FIPS compliant out of the box.

Issue 8

Network Dashboard should overlay Availability when displaying health state.

Issue 9

Dashboards: Group picker does not show all groups in large environment.

Issue 10

IIS Discovery: Prevent GetAdminSection from failing when framework version was detected incorrectly by IIS API.

Issue 11

Performance Counters are not displayed in the Application list view of AppDiagnostics.

Issue 12

Console crashes when state view with self-contained object class is opened.

Issue 13

PerformanceWidget displays stale "last value" in the legend because of core data access DataModel.

Issue 14

Availability Report and "Computer Not Reachable" Monitor display incorrect data.

Issue 15

Agent install fails on Win8 Core because of dependency on the .NET Framework 2.0.

Issue 16

Web Services Availability Monitoring Wizard - Console crashes if the wizard finishes before a test has finished.

Issue 17

Several Windows PowerShell changes are needed:

• Changed License parameter in Get-SCOMAccessLicense to ShowLicense

• Changed SCOMConnectorForTier cmdlets to SCOMTierConnector

• Some formatting changes

Issue 1

Schannel error events are logged to the System log on Operations Manager Management servers and on gateways that manage UNIX/Linux agents.

Issue 2

On HP-UX, Operations Manager cannot discover and monitor a logical volume composed of more than 127 physical volumes.

Issue 3

Upgrade of UNIX and Linux agents fails when using Run As credentials in the Agent Upgrade Wizard or Update-SCXAgent Windows PowerShell cmdlet.

Known issues for this update

• No updates items appeared in Control Panel ARP after installing Update Rollup 1 (UR1). After installing UR1 on server and all roles (except Agent and Gateway), no update item appears in Control Panel ARP list.

• The version number of the console does not change after installing Update Rollup 1 in the UI. After installing Update Rollup 1 ,the version number of the console is still 7.0.8560.0 in the UI.

• After installing UR1 on web console, a Server Error in "/OperationsManager" Application appears in Internet Explorer. Closing and restarting Internet Explorer resolves this problem.

Notes on installation

• Operations Manager Update Rollup 1 will at first be available only in English and cannot be applied to non-English products. Fixes included in this UR will be localized in a future release.

• User must run updates as administrator.

• If UAC is enabled, MSPs must be run from an elevated command prompt window.

• System Administrator rights on the database instances for the Operational Database and Data warehouse are required in order to run updates on these databases.

• User has to close console before applying console update to avoid having to restart.

• Restart and clear cache of the browser to obtain new Silverlight instance.

• This UR should not be installed immediately after installing server. Otherwise, user could encounter an issue in which Health Service state remains uninitialized.

• Web console fixes will work after adding the following line to the %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\web.config file:
  
  <machineKey validationKey="AutoGenerate,IsolateApps"
  decryptionKey="AutoGenerate,IsolateApps" validation="3DES" decryption="3DES"/>
  
  The line should be added under <system.web>, as described in the following article in the Microsoft Knowledge Base:

  911722 You may receive an error message when you access ASP.NET Web pages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0

Supported installation order

We recommend that you install this update rollup in the following order.

Note This update rollup can be installed on agents either before or after server infrastructure.

1. Server infrastructure:

   1. Management server or servers

   2. Gateway servers

   3. Reporting servers

   4. Web console server role computer

   5. Operations console role computers

   6. Manually imported management packs

2. Apply the agent update to manually installed agents, or push installation from the Pending view in the Operations console.

Note If Connected MG/Tiering is enabled, the top tier should be patched first.

Installation Information

To extract the files that are contained in this update, follow these steps:

1. Copy the following file to either a local folder or an available network share, and then execute the file to extract it:

   SystemCenter2012OperationsManager-CU1-KB2674695-X86-X64-IA64-ENU.exe

2. Apply the appropriate MSPs to each computer. All MSPs that apply to a given computer must be applied. For example, if a Management Server also has Web Console and Console roles installed, three MSP packages should be applied to the Management Server. The following MSPs are included in the update:

3. • KB2674695-AMD64-Agent.msp

   • KB2674695-AMD64-Console.msp

   • KB2674695-AMD64-Gateway.msp

   • KB2674695-AMD64-Reporting.msp

   • KB2674695-AMD64-Server.msp

   • KB2674695-AMD64-WebConsole.msp

   • KB2674695-i386-Agent.msp

   • KB2674695-i386-Console.msp

   • KB2674695-ia64-Agent.msp

4. Import the following management packs:

   1. Microsoft.SystemCenter.DataWarehouse.Library.mpb

   2. Microsoft.SystemCenter.Visualization.Library.mpb

   3. Microsoft.SystemCenter.WebApplicationSolutions.Library.mpb
      
      For information about how to import a management pack from disk, go to the following Microsoft TechNet website:

      How to Import an Operations Manager Management Pack

Install Linux/UNIX management packs and update Linux/UNIX agents

Update Rollup 1 for System Center 2012 Operations Manager contains new agents and management packs for all supported Linux and UNIX operating systems. Therefore, to fully install Update Rollup 1, follow these steps to make sure that your monitoring of UNIX and Linux computers is up to date.

1. Download and then install the updated management packs from the following Microsoft website:

   http://www.microsoft.com/download/details.aspx?FamilyID=9f947878-6bf6-48a1-adb1-3cc4c2e5d4af

2. Import the updated management pack for each version of Linux or UNIX that you are monitoring in your environment.

3. Use the Update-SCXAgent Windows PowerShell cmdlet or the UNIX/Linux Agent Upgrade Wizard in the Administration pane of the Operations Console to upgrade each agent to the latest version.
   
   Note The Management Pack Bundle files for each UNIX and Linux operating system version contain the management pack and agent files. It may take several minutes after importing the Management Pack Bundle for the agent files to become available for agent upgrades.

For each UNIX or Linux Management Pack Bundle that is imported, the update installs new UNIX and Linux agents to the following folder:

Program Files\System Center 2012\Operations Manager\Server\AgentManagement\UnixAgents\DownloadedKits The updated agents have file names that use the following format and a version number of 214:

Scx-1.3.0-214-server type.server version.architecture.package type

Notes

• The placeholder server type represents the name of the UNIX or Linux server product.

• The placeholder server version represents the version number of the server type.

• The placeholder architecture represents the processor architecture of the destination computer.

• The placeholder package type represents the kind of installation file.
  

For example, the following is the file name format for the agent for SUSE Linux Enterprise Server 10 (x86):

Scx-1.3.0-214-sles.10.x86.rpm The agents that are included with the original release of System Center 2012 Operations Manager have a version number of 204. These files are not removed during installation. These files are as follows:

• Scx-1.3.0-206.aix.5.ppc.lpp.gz

• Scx-1.3.0-206.aix.6.ppc.lpp.gz

• Scx-1.3.0-206.aix.7.ppc.lpp.gz

• Scx-1.3.0-206.hpux.11iv2.ia64.depot.Z

• Scx-1.3.0-206.hpux.11iv2.parisc.depot.Z

• Scx-1.3.0-206.hpux.11iv3.ia64.depot.Z

• Scx-1.3.0-206.hpux.11iv3.parisc.depot.Z

• Scx-1.3.0-206.rhel.4.x64.rpm

• Scx-1.3.0-206.rhel.4.x86.rpm

• Scx-1.3.0-206.rhel.5.x64.rpm

• Scx-1.3.0-206.rhel.5.x86.rpm

• Scx-1.3.0-206.sles.10.x64.rpm

• Scx-1.3.0-206.sles.10.x86.rpm

• Scx-1.3.0-206.sles.9.x86.rpm

• Scx-1.3.0-206.solaris.10.sparc.pkg.Z

• Scx-1.3.0-206.solaris.10.x86.pkg.Z

• Scx-1.3.0-206.solaris.9.sparc.pkg.Z