SigmaSystemCenter 3.2 Update Module (SSC0302-0002.zip) 

Patch Name         : SSC0302-0002
Patch Description  : A module to improve the problems considered in 
                     SigmaSystemCenter 3.2.
Release Date       : Oct/31/2013
File Name          : SSC0302-0002.zip
Target Product     : SigmaSystemCenter 3.2
Target Versions of Components *1:
  DeploymentManager Version: 6.2
Necessary Patch    : N/A
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.2" 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.2.

1. Fixed Problems

1.1. Fixed Problems in DeploymentManager

(1) GetBootServerIP.exe ends by an application error when DPM Client searches
    the Management Server.(#14587)

    Phenomenon:
    If all the following conditions are met, GetBootServerIP.exe ends abnormally.

    (a) When you install DPM Client newly, you install it without entering the
        IP address of the Management Server. Or you change the IP address
        or the port number of the Management Server.
    (b) The DPM environment is either of the following.
        - You operate DPM without a DHCP server, and you configure DPM Server and
          a DHCP server on the same machine.
        - You operate DPM with a DHCP server, and you configure DPM Server and
          the DHCP server on a different machines.
    (c) A response packet to the DPM Client's packet (the port number:67) 
        for searching the Management Server is not returned from DPM Server
        because of the network problem.
    (d) DPM Client fails to send the second packet to search the Management
        Server(the port number:4011).

    As a result, you cannot register machines on the Management Server
    or various instructions from the Management Server cannot be done
    because DPM Client cannot find the Management Server.
    Also, OS installation by disk duplication(Windows) cannot be completed if this phenomenon
    occurs in the individual setting during the duplication.

    Problem Explanation:
    GetBootServerIP.exe cannot output the log file and ends abnormally
    because there is a problem in the log output in case of error
    in the processing to send the second packet to search the Management
    Server from DPM Client.

    Solution:
    Fixed to output the log file correctly.


===============================================================================
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 2013
