SigmaSystemCenter 3.1 Update Module (SSC0301-0005.zip) Patch Name : SSC0301-0005 Patch Description : A module to improve the problems considered in SigmaSystemCenter 3.1. Release Date : May/31/2013 File Name : SSC0301-0005.zip Target Product : SigmaSystemCenter 3.1 Target Versions of Components *1: DeploymentManager Version: 6.12 Necessary Patch : SSC0301-0002-update1 Reboot : N/A Patches Contained in This Patch : N/A *1) How to check target versions of components - DPM Server 1) Start the DPM Web Console. 2) Check that "DeploymentManager 6.12" is displayed at the bottom of the DPM Web Console. 3) After checking, end the DPM Web Console. This update module incorporates the following fixes in SigmaSystemCenter 3.1. 1. Fixed Problems 1.1. Fixed Problems in DeploymentManager (1) The problem may occur in DHCP operation and the Management Server cannot be searched over the network segment. (#13880, #13881) Phenomenon: When you use DPM Ver6.12, the following problems may occur: (a) When a DHCP server and a Management Server are on the same server and a DHCP server and a DHCP client are not on the same network segment, managed machines fail to get an IP address from the DHCP server. (b) When the Management Server and managed machines are not on the same network segment, managed machines (DPM Client) cannot search the Management Server. As a result, the following phenomena will occur: - Network communication cannot be performed in the DHCP environment. - When the scenario of OS installation by disk duplication is being executed, a parameter file cannot be downloaded to a managed machine and a scenario error occurs. - When you change the IP address of the Management Server, the following phenomena will occur: - An error will occur in shutdown of managed machines, scenario execution, or automatic update. - OS type of managed machines and patch status cannot be confirmed from the Management Server. - When you install DPM Client on the managed machine, registration of new machine by DPM Client is not performed if you omit to provide the IP address of the Management Server. Problem Explanation: (a) Both DHCP service and DPM service listen the data of DHCP on the same port (67). When the DPM service receives the data first, this phenomenon occurs because the DHCP service cannot receive the data. (b) This phenomenon occurs because the DPM service cannot respond to the DHCP communication from the managed machine. Solution: The following solutions are done: - By this update, the processing which was bound to the port (67) in the DPM service is changed so that it is bound only when there is no DHCP service on the Management Server. - The processing is changed so as to properly respond from the DPM service to managed machines over the network segment. To make this procedure effective, you need to configure the DPM Server so that it can use the port 4011 (UDP) on the Management Server. When a firewall, security software and so on are enabled, open the port 4011 (UDP). (2) DPM Client (Linux) stops after the managed machine is started. (#13770) Phenomenon: When the following conditions are met, the DPM Client (Linux) cannot start normally and ends abnormally. (a) When you install DPM Client newly, you install it without entering the IP address of the Management Server. (b) There is no Management Server on the same network with the DPM Client. Problem Explanation: The problem exists in the DPM Client processing when the IP address of the Management Server is not specified and the DPM Client cannot search the Management Server, which causes this phenomenon. Solution: DPM Client is fixed so that it does not end abnormally even if the DPM Client cannot search the Management Server. =============================================================================== 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 2013