SigmaSystemCenter 3.3 Update Module (SSC0303-0007.zip) 

Patch Name         : SSC0303-0007
Patch Description  : A module to improve functions considered
                     in SigmaSystemCenter 3.3.
Release Date       : Dec/22/2015
File Name          : SSC0303-0007.zip
Target Product     : SigmaSystemCenter 3.3.
Target Versions of Components *1:
  SigmaSystemCenter Version: 3.3-26097, SystemProvisioning 6.3.0024
Necessary Patch    : 
  SigmaSystemCenter: SSC0303-0003
Reboot             : N/A
Patches Contained in This Patch: SSC0303-0004, SSC0303-0005, SSC0303-0006

*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-26097, SystemProvisioning 6.3.0024"
       (SigmaSystemCenter 3.3 SSC0303-0003 is already applied.)

This update module incorporates the following improvements in 
SigmaSystemCenter 3.3.


1. Functional Enhancements

1.1. Functional Enhancements in SystemProvisioning

(1) Added a new registry key, "VimServiceTimeout," for VMware Web services 
    (#16912, SSC0303-0004)

    Support Overview:
    We added a new registry key called VimServiceTimeout so that users can 
    change a timeout value. The value applies to when waiting for API responses
    of VMware Web services, such as when retrieving information from or 
    operating vCenter Server or ESXi.

    In the existing system, if the response time is 100 seconds or more, the
    API request fails because of exceeding the .NET Framework timeout period 
    and then SystemProvisioning produces the following massage:

      uAn unexpected  error has occurred in communication with the vCenter 
        Server or ESX.
        Reason: The operation has timed-out.v

    The response time, however, sometimes need more than 100 seconds when the
    management server is under heavy load. As the solution, we enabled the 
    timeout value is configurable by specifying the value in the registry.

      Procedure
      1. Set the number of seconds (default: 0 = 100 seconds) to the following
         registry key:
         [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NEC\PVM\Provider\VM\VMware]
         VimServiceTimeout (DWORD)

      2. Restart PVMService service.


(2) Fixed the problem and improved the issue with performing datastore
    operations when the management server is under heavy load.

(2-1) Fixed the problem with a timeout error of datastore operations
      (#16871, SSC0303-0004)

    Support Overview:
    We fixed the problem that a timeout error occurs when a datastore operation
    time is getting longer because the management server is under heavy load.

    When performing datastore operations via VMware Web API, each API request
    does not return until the vCenter server has finished processing the 
    request. In the existing system, if the process time exceeds the .NET 
    Framework timeout period, the API request fails even in the processing 
    phase and then SystemProvisioning produces the following massage:

      uAn unexpected  error has occurred in communication with the vCenter 
        Server or ESX.
        Reason: The operation has timed-out.v

    To solve this, we provide the following feature: (1) if detect the .NET 
    Framework timeout error; (2) SigmaSystemCenter searches the API request 
    that led to the error instead of producing the error massage; and 
    (3) waits for the request to be completed.

    Please note that the longer operation time may cause SSC command timeout.
    To avoid this, you must set a preference timeout time to the following at 
    <the SSC installed folder>\bin\ssc.exe.config:

      <binding name="NetTcpBinding_IUniversalConnectorServer" ... 
      openTimeout="00:03:00" receiveTimeout="00:10:00"sendTimeout="<preference
      timeout time>"


(2-2) Improved the issue with the processing time when operating datastores
      and networks concurrently (#17028, SSC0303-0005)

    Support Overview:
    Network operations, such as creating or deleting port groups, have short 
    processing times compared with datastore operations. With this in mind, we 
    improved the total processing speed by giving a priority to network 
    operations when performing network and datastore operations at the same 
    time.

    SystemProvisioning performs exclusively not only each network operation and
    datastore operation destined for same ESXi but subsequent each updating
    process of the database. Users, therefore, sometimes had to keep waiting 
    for long time when executing multiple of these operations.


(3) Improved the issue with debug logs of datastore and network operations
    (#16932, SSC0303-0005)

    Support Overview:
    We disabled the debugging log of the database by default (in either 
    multiple port groups or datastores environment, the database logs updating 
    processes, which triggered by datastore or network operations) because
    there was a possibility that the log overwrites existing debug logs. Even 
    so, if you want to activate the debugging log, set debug log level to 4.


(4) Enhanced Web API functions (#17249, SSC0303-0006)

(4-1) Added mixed OS types support for Group

    Support Overview:
    Mixed OS types are now available in Group. The OS type will be determined
    by the following order of precedence:
    1) The OS type that is specified in API requests (HostProfile.OSType).
    2) The OS type that is associated from a specified OS name in API requests
       (HostProfile.OSName).
    3) The OS type that is specified in Template.
    4) The OS type that is specified in Group.


(4-2) Added a new property, "DefaultAPIVersion"

    We added a new property called DefaultAPIVersion to specify an API version 
    in an API request. The specified version of API will be used if users skip 
    specifying an API version when creating an API request. To specify this, 
    you must modify DefaultAPIVersion at PVM/bin/PVMServiceProc.exe.config.

         <configuration> 
           <applicationSettings> 
             <Nec.SystemProvisioning.WebConnector.Properties.Settings> 
               <setting name="DefaultAPIVersion" serializeAs="String"> 
                 <value>2013-10-13</value> <!-- SSC 3.3 --> 
               </setting> 
             </Nec.SystemProvisioning.WebConnector.Properties.Settings> 
           </applicationSettings> 
         </configuration> 

    Please note that if this is not specified, the latest version will be 
    applied as the same in the existing system.


(4-3) Fixed the problem that the GetPerformanceInformation API does not respond
      to requests

(4-4) Fixed the problem that the API returns NullReferenceException when 
      specifying NULL to FirstLogonCommands

(4-5) Fixed the problem that the API returns NullReferenceException when 
      creating a VM on a logical network without defining a port group to the 
      network

(4-6) Fixed the problem that the API returns NullReferenceException when 
      specifying NULL to a host profile when crating a template

(4-7) Fixed the problem that cannot retrieve a DatastoreTags property


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