SigmaSystemCenter 3.5 Update Module (SSC0305-0001.zip) Patch Name : SSC0305-0001 Patch Description : A module to improve functions and problems considered in SigmaSystemCenter 3.5. Release Date : May/31/2017 File Name : SSC0305-0001.zip Target Product : SigmaSystemCenter 3.5 Target Versions of Components *1: SigmaSystemCenter Version: 3.5-29023, SystemProvisioning 6.5.0010 System Monitor - Performance Monitoring Services Version: 5.7.1034.0 Necessary Patch : SigmaSystemCenter: N/A System Monitor - Performance Monitoring Services: N/A Reboot : 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.5-29023, SystemProvisioning 6.5.0010" (SigmaSystemCenter 3.5) - 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.7.1034.0 This update module incorporates the following fixes and improvements in SigmaSystemCenter 3.5. 1. Fixed Problems 1.1. Fixed Problems in SystemProvisioning (1) Fixed the problem that cannot move a virtual machine, which is configured as a dependent machine in the dependency setting, to another virtual machine sever by using the ssc command (#18580). Phenomenon: When you move a virtual machine, which is configured as a dependent machine in the dependency setting, by using the ssc command, the command ends abnormally with the following error: Not supported "Move With Shutdown" operation for VM (xxx) which is depended by other machines. Move VM (xxx) after execution of "Shutdown" operation for the VM and its dependent machines. Problem Explanation: This problem occurs in the following ssc commands: - The ssc migrate machine command - The ssc evacuate machine command with specifying the virtual machine as the target - The ssc evacuate host command with specifying the virtual machine as the target Note that there are no workarounds for this problem even if you shut down both the virtual machine and its depended machine. Solution: We have fixed the commands (2) Fixed the problem that when you create a report file by using a report template file with the chart template of Microsoft Excel 2013, the series of the created chart are displayed with the same color (#18636). Phenomenon: When you create a report file by using a report template file with a chart template added by using Microsoft Excel 2013, the series of the chart in the created report file are displayed with the same color (this phenomenon does not occur if the chart template is added by using Excel 2010). Problem Explanation: The chart series are added by the number of source table columns by using series data in the report template file when creating a report file. This problem occurs because of the difference of the series data format between Microsoft Excel 2010 and 2013. Solution: We have fixed the program to use the series data format of Microsoft Excel 2013 so that the series color will be selected automatically. (3) Fixed the problem that the collect settings, which is used for collecting performance data, of a monitoring profile created by specifying a report definition file are not reflected to System Monitor - Performance Monitoring Services (#18650). Phenomenon: When you create a monitoring profile by using the "ssc monitoringprofile create" command with the "-report" option, and then register it with a operation group, the collect settings, which is used for collecting performance data, of the monitoring profile are not reflected to System Monitor - Performance Monitoring Services, and thus the performance data cannot be collected. Problem Explanation: A monitoring profile created by using the "ssc monitoringprofile create" command with the "-report" option are disabled by default and thus cannot be reflected to System Monitor - Performance Monitoring Services even after registering it with an operation group. Note that to enable the monitoring profile, display the "Edit Monitoring Profile" screen in the Web Console, and then click "OK." Solution: We have fixed the program to enable the monitoring profile by default. (4) Fixed the problem that cannot create a report file by specifying a virtual machine server group that with a no resource pool (#18734). Phenomenon: Creating a report file by specifying a virtual machine server group ends abnormally when a resource pool is not prepared in the group. Problem Explanation: This creation is based on an assumption that the resource pool is prepared in the group. Thus, without the resource pool information, the creation process cannot continue and ends abnormally. Solution: We have fixed the program to specify a virtual machine server group that with a no resource pool when creating a report file. Note that in the created report file, resource pool related items are blanked. (5) Fixed the problem that cannot display multiple threshold areas in the chart of Web Console (#18788). Phenomenon: Displaying a chart to see the status of a group performance, to compare the performance of a machine, or to see all performance data is available in the Web Console. The problem is that when you specify multiple monitoring items (Upper-limit critical, Upper-limit warning, Lower-limit warning, Lower-limit critical) for each chart to display the threshold areas, only one threshold area is displayed. Problem Explanation: This problem occurs because the program refers only one monitoring value even when you specify the multiple monitoring items. Solution: We have fixed the program to refer all the values of the specified items. (6) Fixed the problem that cannot register a virtual machine with a DPM server automatically when the virtual machine is created by using a template created by using vCenter Server (#18860). Phenomenon: When you creating a virtual machine and registering it with a DPM server in an operation group by using such as the Create and Assign Machine feature, and when the virtual machine is created by using a template created by using vCenter Server, the registration sometimes fails. Problem Explanation: This problem occurs the following condition: (1) a DPM server is not configured in DPM Server (the operation group > Property > the General tab); and (2) the virtual machine is created by using a template created by using vCenter Server. Note that with this failure, the software distribution of DeploymentManager also fails if the distribution is configured to perform after the virtual machine is created. Solution: We have fixed the program. This program enables you to register a virtual machine with a DPM server in the following condition: (1) a DPM server is not configured in DPM Server (the operation group > Property > the General tab); (2) the virtual machine is created by using a template created by using vCenter Server; and (3) the software distribution of DeploymentManager is configured when the virtual machine is created. 1.2. Fixed a Problem in System Monitor - Performance Monitoring Services (1) Fixed the problem that the "Cannot collect the performance data from ESX Server." error occurs when collecting performance data from VMware ESX/ESXi (#18665). Phenomenon: When you collecting performance data from ESXi, sometimes an error, which is its ID is 70 and the message includes "Cannot collect the performance data from ESX Server." occurs in particular condition and then the collecting fails. Problem Explanation: This error occurs in particular condition that when there is a problem in the data processing method for the data collected from ESXi. Solution: We have fixed the data processing method to process the data correctly. 2. Functional Enhancements 2.1. Functional Enhancements in SystemProvisioning (1) Improved the recovery process of a virtual machine (#18702). Support Overview: Recovering a virtual machine fails after failing over the virtual machine between ESXi hosts because the source ESXi locks the configuration files of the virtual machine and the virtual machine remain inaccessible in the destination ESXi. Enhancement: This enhancement enables the virtual machine to recovery by reading the configuration files periodically until the source ESXi releases the locked configuration files. (2) Disabled an unnecessary warning message that related "waiting for services to start" in a Hyper-V virtual machine (#18888). Support Overview: With configuring related settings in a guest OS, service related information is collected from a Hyper-V virtual machine while performing Collect or Startup to the Hyper-V virtual machine, and if this fails, a warning message occurs. This enhancement enables the message is disabled for users who do not need to collect the service related information by configuring a management server. Enhancement: You can disable the message as the following configurations: - Enable/Disable collecting service related information - In the [Custom] tab Enable: SSC_ENABLE_COLLECT_SERVICE = TRUE (Default) Disable: SSC_ENABLE_COLLECT_SERVICE = FALSE - In the registry (*) Enable: EnableCollectService = 1 (Default) Disable: EnableCollectService = 0 (If both are configured, the [Custom] tab setting has priority.) - Enable/Disable the warning message - In the registry (*) Enable: EnableWarningOnErrorCollectService = 1 Disable: EnableWarningOnErrorCollectService = 0 (Default) * Registry Path: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\PVM\Provider\VM\HyperV\ Notes: - In these configurations, you do not have to restart the PVM Service. - The warning message is configured to Disable after this patch program is applied. (3) Update for supporting the modification of the SMI-S verification tool (#18540). Support Overview: We have detailed verification items for a target port as a result of the modification that the port information of a storage device is now available. This modification has no impact on SigmaSystemCenter directly. =============================================================================== 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. -------------------------------------------------------------------------------- [Terms of Use] Terms for use of this update module conform to "NEC Software License Agreement" of the product to which this software will be applied. -------------------------------------------------------------------------------- [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 2017