SigmaSystemCenter 3.3 Update Module (SSC0303-0011.zip) 

Patch Name         : SSC0303-0011
Patch Description  : A module to improve functions and problems considered
                     in SigmaSystemCenter 3.3.
Release Date       : May/31/2017
File Name          : SSC0303-0011.zip
Target Product     : SigmaSystemCenter 3.3.
Target Versions of Components *1:
  SigmaSystemCenter Version: 3.3-27515, SystemProvisioning 6.3.0025
Necessary Patch    : 
  SigmaSystemCenter: SSC0303-0007
Reboot             : N/A
Patches Contained in This Patch: SSC0303-0009,SSC0303-0010

*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.3-27515, SystemProvisioning 6.3.0025"
       (SigmaSystemCenter 3.3 SSC0303-0007 is already applied.)

This update module incorporates the following fixes and improvements
in SigmaSystemCenter 3.3.

1. Fixed Problems

1.1. Fixed Problems in SystemProvisioning

(1) Correction of the problem that deletion of the virtual machine registered 
    to the Hyper-V cluster fails intermittently.
    (#18348)

    Phenomenon:
    When you delete a virtual machine in SigmaSystemCenter,
    the deletion fails intermittently.

    Detail description:
    In a SigmaSystemCenter environment that is managing the Hyper-V cluster,
    when you delete a virtual machine registered to the cluster,
    intermittently following error occurs and you fail to delete it.

    'Virtual machine name' failed to delete configuration: Catastrophic failure (0x8000FFFF).
    (Virtual machine ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)

    This is because race condition occurs between cluster processing and Hyper-V processing
    in the Hyper-V host.

    Treatment:
    The process of deleting the virtual machine registered to the 
    cluster has been changed in order to avoid the race condition.

(2) Correction of the problem that quick migration fails after 
    storage migration of the VM registered to the cluster. 
    (#18506)

    Phenomenon:
    When you move a virtual machine in series (storage migration and quick migration),
    the second operation fails and the virtual machine becomes "Failed" state.

    Detail description:
    When you do storage migration of a virtual machine registered to the Hyper-V cluster
    by SigmaSystemCenter, and then do quick migration of the virtual machine, 
    the following error may occur and the virtual machine becomes "Failed" state.

      Failed to move VM (Virtual machine name). WMI Error: Generic failure

    This is because the registration information to the cluster becomes invalid by the 
    first move and the subsequent move fails because of the invalid information.

    Treatment:
    Fixed cluster information handling correctly after storage migration.


2. Functional Enhancements

2.1. Functional Enhancements in SystemProvisioning

(1) Fixed the problem that cannot retrieve a DatastoreTags property(#18149ASSC0303-0009)

    Corresponding Summary:
    Fixed the problem that the GetHostInformation API cannot retrieve a
    DatastoreTags property depending on the SQLServer data structure.


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