SigmaSystemCenter 3.1 Update Module (SSC0301-0001.zip) Patch Name : SSC0301-0001 Patch Description : A module to improve functions and problems considered in SigmaSystemCenter 3.1. Release Date : 10/29/2012 File Name : SSC0301-0001.zip Target Product : SigmaSystemCenter 3.1 Target Versions of Components *1: SigmaSystemCenter Version: 3.1-20825, SystemProvisioning 6.1.0010 DeploymentManager Version: 6.10 System Monitor - Performance Monitoring Services Version: 5.1.1027.0 *2 Necessary Patch : SigmaSystemCenter: N/A DeploymentManager: N/A System Monitor - Performance Monitoring Services: N/A Reboot: N/A Patches Contained in This Patch: N/A *1) How to check target versions of components - SigmaSystemCenter and SystemProvisioning A version is displayed at the bottom of the Web Console. Target Version: "Version: 3.1-20825, SystemProvisioning 6.1.0010" - DPM Server 1) Start the DPM Web Console. 2) Check that "DeploymentManager 6.10" is displayed at the bottom of the DPM Web Console. 3) After checking, end the DPM Web Console. - System Monitor - Performance Monitoring Services 1) Click the [Start] button, select [All Programs]. From [All Programs], select [SigmaSystemCenter]. From [SigmaSystemCenter], select [System Monitor Management Console] to start the management console of System Monitor - Performance Monitoring Services. 2) The Logon window appears. Click [Cancel]. 3) Click the [Help] menu, select [Version Information] to display the Version Information window. 4) The version is displayed at the Version. Target Version: 5.1.1027.0 *2) The System Monitor - Performance Monitoring Services module is not need to be fixed, so this patch does not include its update. This update module incorporates the following fixes and improvements in SigmaSystemCenter 3.1. 1. Fixed Problems 1.1. Fixed Problems in DeploymentManager (1) DeploymentManager API Service ends abnormally. (#12784) Phenomenon: If you repeat the operation of obtaining the computer information, DeploymentManager API Service may end abnormally. Problem Explanation: If you operate such as obtaining the computer information (refreshing the screen, referring to/obtaining the computer information, etc.), a memory leak occurs when DPM obtains the applications/hotfixes information of the managed machine. As a result, if used memory exceeds the maximum limit of usable memory, the phenomenon that DeploymentManager API Service ends abnormally occurs. Solution: Fixed not to leak the memory. 2. Functional Enhancements 2.1. Functional Enhancements in SystemProvisioning (1) Support for VMware vSphere 5.1 Support Overview: VMware vSphere 5.1 is now supported. (#12281) The following describes limitations and notes in this update. Limitations: These limitations will be removed in the next SigmaSystemCenter update. (a) Guest operating system customization of Windows Server 2012 is not supported in VMware at the time of release of this update. (#12281) (b) Virtual machines cannot be created in the standalone ESXi environment if a virtual machine uses EFI firmware. (#12716) Use vSphere Client and select BIOS as firmware in Boot Options in virtual machine settings. (c) Virtual machines cannot be created with the HW Profile Clone method if a virtual machine uses EFI firmware. (#12994) Use vSphere Client and select BIOS as firmware in Boot Options in virtual machine settings. (2) Support for Windows Server 2012 Support Overview: Windows Server 2012 is now supported as managed machines. The following describes limitations in this update. Limitations: These limitations will be removed in the next SigmaSystemCenter update. (a) Distribution of applications and patches using DPM (b) Image deployment - Reflecting machine specific information using DPM is not available. - Reflecting machine specific information using VMware is not available because VMware vSphere 5.1 does not support guest operating system customization of Windows Server 2012. (3) Support for Windows Server 2012 Hyper-V Support Overview: Windows Server 2012 Hyper-V is now supported. (#12648) The following describes limitations and notes in this update. Limitations: These limitations will be removed in the next SigmaSystemCenter update. (a) Set the memory limit to 64 gigabytes or less in Edit Virtual Machine or Machine Profile. This also applies to the Maximum RAM setting of a source VM of VM Clone, a master VM and its snapshot. (#12904) (b) Port group creation by Change Configuration on a VM server is not supported. (#12905) Note: (a) Hyper-V in Windows Server 2012 can be managed with the Windows Server 2012 Hyper-V features as long as Windows Server 2008 R2 supports those features. The management of virtual machines or Hyper-V with new features of Windows Server 2012 Hyper-V, such as SMB 3.0, new live migration, and Hyper-V Replica, is not supported. This will be supported in post SigmaSystemCenter 3.1 update 1. (b) Accounts registered to the Hyper-V Administrators group which is introduced in Windows Server 2012 cannot be used as accounts for the Hyper-V management in SigmaSystemCenter. (#12909) 2.2. Functional Enhancements in DeploymentManager (1) vSphere 5.1 is supported. (#12641) Support Overview: vSphere 5.1 is supported. (2) The function of MAC Address Allocation in vSphere is supported. (#12763) Support Overview: In the early version, when the managed machine (virtual machine) was registered on DPM, the machine was not powered off after the registration. This is done by describing the MAC address in the following file. \Datafile\forceskip.ini However, in the function of MAC Address Allocation in vSphere 5.1, MAC address can be specified arbitrarily. Therefore from this version, the specification is changed not to power off the machine after the registration, regardless of whether the managed machine is physical or virtual. If you want to power off the machine after registering the machine, configure the above file by seeing Section 2.2.1.1, "Automatically Acquiring the Information of a Managed Machine and Registering the Machine on DPM" in DeploymentManager OperationGuide. (3) Windows Server 2012 is supported. (#12793) Support Overview: Windows Server 2012 is supported as a managed machine. Only the following functions are supported in this version. - Backup/restore/disk configuration check - Power on/shutdown - Status check of power on/off - Obtaining the information of OS/service packs/hotfixes/applications 2.3. Functional Enhancements in System Monitor - Performance Monitoring Services (1) vSphere 5.1 is supported. (#12691) Support Overview: - Performance monitoring for VMware ESXi 5.1 is supported. (2) Windows Server 2012 is supported. (#12689) Support Overview: - Performance monitoring for Windows Server 2012 is supported. - Performance monitoring for Hyper-V on Windows Server 2012 is supported. =============================================================================== Installation Procedures and Release Modules List =============================================================================== For the procedures to unzip and install this software, other information regarding installation, and release modules list, see Install.txt. In addition, if you set up SigmaSystemCenter components in a clustering environment, see Clustering.txt for the installation procedures in a clustering environment. =============================================================================== Notes on Unzipping a .zip File =============================================================================== [Notes 1] Before unzipping the zip file of this software, confirm and delete the ZoneID information with the following procedure. If you unzip the zip file and install the software with the ZoneID information, the module after installing the software will not work properly. The information called "ZoneID" has been added to a file downloaded from a site in a zone configured other than [Intranet] on Internet Explorer of Windows Vista, Windows XP Service Pack 2 or later, or Windows Server 2003 Service Pack 1 or later. If ZoneID is added to the zip file, the ZoneID information is succeeded to a deployed file and a warning of security is displayed when executing the file, consequently, services or processed may not start. (1) Checking and changing the policy setting (Hide mechanisms to remove zone information): 1) Click the [Start] button, and click [Run]. 2) Enter "gpedit.msc", and click [OK]. 3) The Group Policy Object Editor dialog box appears. Click [User Configuration], click [Administrative Templates], double-click [Windows Components], and double-click [Attachment Manager]. 4) Check the [State] of [Hide mechanisms to remove zone information]. If it is "Enabled," click [Disabled] on the Hide mechanisms to remove zone information Properties dialog box, and click [OK]. If it is "Disabled" or "Not Configured," you do not need to change the setting. (2) Deleting the ZoneID information of the zip file: 1) Open the properties dialog box of the zip file, and click the [General] tab. 2) If the following message is displayed, click [Unblock], and click [OK]. Security: This file came from another computer and might be blocked to help protect this computer. (3) Changing the policy setting (Hide mechanisms to remove zone information): If you changed the policy setting (Hide mechanisms to remove zone information) from "Enabled" to "Disabled," configure it to "Enabled" with the same procedure. [Notes 2] When unzipping the zip file of this software, specify a path whose length is not over 80 bytes as the path to extract. If you specify a path whose length is over 80 bytes, the zip file might not be extracted properly. -------------------------------------------------------------------------------- [Trademark and Copyright Information] All rights reserved. Copyright in this software is owned by NEC Corporation. * All other brands and products used in this document are the trademarks or registered trademarks of their respective trademark holders. -------------------------------------------------------------------------------- Copyright NEC Corporation 2012