SigmaSystemCenter 3.3 Update Module (SSC0303-0002-update1.zip) Patch Name : SSC0303-0002-update1 Patch Description : A module to improve functions and problems considered in SigmaSystemCenter 3.3. Release Date : Dec/01/2014 File Name : SSC0303-0002-update1.zip Target Product : SigmaSystemCenter 3.3 Target Versions of Components *1: SigmaSystemCenter Version: 3.3-24989, SystemProvisioning 6.3.0015 DeploymentManager Version: 6.3 System Monitor - Performance Monitoring Services Version: 5.4.1030.0 NEC ESMPRO Manager Version: 5.74 Necessary Patch : SigmaSystemCenter: N/A DeploymentManager: N/A System Monitor - Performance Monitoring Services: N/A NEC ESMPRO Manager: N/A Reboot : Required Patches Contained in This Patch : 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.3-24989, SystemProvisioning 6.3.0015" (SigmaSystemCenter 3.3) - DPM Server 1) Start the DeploymentManager Web Console. 2) Check that "DeploymentManager 6.3" is displayed at the bottom of the DeploymentManager Web Console. 3) End the DeploymentManager Web Console. - 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.4.1030.0 - NEC ESMPRO Manager 1) Click the [Start] button - [All Programs] -[NEC ESMPRO Manager] - [About NEC ESMPRO] - [Version Detector] dialog. 2) Select the [Manager] tab and check Current Version. Target Versions of Components: 5.74 This update module incorporates the following fixes and improvements in SigmaSystemCenter 3.3. 1. Fixed Problems 1.1. Fixed Problems in SystemProvisioning (1) An error occurs when you output a CSV file to display a group performance graph. (#15767) Phenomenon: An error may occur when you output a CSV file after displaying a group performance graph for an operation group. Problem Explanation: This error is triggered by the situation when multiple models, both valid and invalid models of the collecting performance data setting, are registered under the operational group which is to be output. Solution: Fixed so that the collecting performance data setting can properly handle the procedure when both valid and invalid models exist. (2) VM Evacuation operation fails when the dependency setting is configured. (#15552) Phenomenon: When the dependency setting is configured and the VM Placement Rule is not configured, VM Evacuation may be aborted and this operation fails. Problem Explanation: In VM Evacuation process, when processing dependencies, SystemProvisioning confirms the VM Placement Rule and decides a destination in order not to breach the rule. This confirmation process is controlled not to be executed when the VM Placement Rule is invalid or is not configured. Under a specific condition, however, this process may be executed and causes the abnormal end. Solution: Fixed so that the confirmation process will not be executed when the VM Placement Rule is invalid or is not configured. (3) The details of hardware status of machine are set [Investigate] when the machine starts up. (#15868) Phenomenon: While managed machines are being monitored by PET, the details of hardware status of machine [System Event] may be set [Investigate] if you execute Power On. Problem Explanation: The details of hardware status of machine are automatically updated referring a PET report from managed machines. When the [Normal] event is noticed by the PET report, the [Investigate] status will be set because it cannot be judged based on the PET report if the status is definitely normal. However, the status is set even though the detail of hardware status is [Normal] so unnecessary warning may occur. This event is a display-issue only and does not affect any policy actions and power operations. Solution: Fixed so that SystemProvisioning can properly handle as [Normal] in the normal status. (4) The change of running virtual machine server types is not recognized properly. (#15195) Phenomenon: When the type of a running virtual machine server has been changed (from ESXi to Hyper-V, for example) in the operation group, this change is not recognized properly. This causes the issue in which the concerned server cannot be executed the operations. Problem Explanation: In the state of changing the type of a running virtual machine server in the operation group, when you perform the operations such as Collecting, Registering Sub System and Adding virtual machine server, new virtual machine server information is registered holding old machine server information because of the function which suspends deleting running machine information. Therefore, when you execute the operation to the concerned server, SystemProvisioning cannot specify correct virtual machine server information and is aborted and this operation fails. Solution: Fixed so that when detecting the change of the running virtual machine server in the operation group, a warning outputs without registering virtual machine server information. If you intend to reflect the change of the running virtual machine server to SigmaSystemCenter, you need to execute [Collect] releasing allocated virtual machine server information to the operation group. (5) Modification of the start process if there is Dependency from a virtual machine to a current virtual machine server. (#15267) Phenomenon: If there is Dependency from a virtual machine to a current virtual machine server, the concerned virtual machine does not start up on the current virtual machine server. Problem Explanation: SystemProvisioning judges if the concerned virtual machine can start up on the current virtual machine server by the status of the starting time of the virtual machine server. If the [Optimized Startup Function] is invalid, the start of the concerned virtual machine is aborted to end. If valid, the start on other virtual machine server is prioritized. Solution: Fixed the process above so that the concerned virtual machine can start up, without moving the virtual machine, after the current virtual machine server starts up. 1.2. Fixed Problems in DeploymentManager (1) You cannot execute OS installation by disk duplication (Linux) when there is not DNS server configuration file (resolv.conf) (#15020) Phenomenon: If you execute OS installation by disk duplication (Linux) when there is not /etc/resolv.conf on the master machine, an error occurs after the image is restored on the duplication destination machine. Problem Explanation: In OS installation by disk duplication (Linux), DeploymentManager saves resolv.conf on the duplication destination machine after the image is restored. If there is not the file, an error occurs. Solution: Fixed so that the processing of OS installation by disk duplication (Linux) can continue even if there is not resolv.conf. (2) Deploy-OS cannot connect to the network on the VMware ESXi virtual machine (#15103) Phenomenon: If you execute backup, restore, disk configuration check, or OS installation by disk duplication in the environment that the following conditions are met, an error occurs when Deploy-OS is started. a) VMware ESXi virtual machine b) [EFI] is selected as boot firmware in the setting of the virtual machine. c) [E1000E] is selected as network adapter in the setting of the virtual machine. d) The scenario is executed after restarting the machine on which OS is running. Problem Explanation: Initialization by Deploy-OS driver fails because the status of virtual network adapter is not initialized after the machine is restarted. Therefore, Deploy-OS cannot connect to the network and an error occurs. Solution: Fixed the setting of the driver so that Deploy-OS driver can recognize the status of the network adapter automatically and can act. (3) In disk configuration check, GPT disk on VMware is displayed as "UNKNOWN" (#15348) Phenomenon: In the environment that the following conditions are met, when you execute disk configuration check, the disk is displayed as "UNKNOWN". In this case, when you execute backup, a scenario execution error occurs. a) VMware ESXi virtual machine b) [EFI] is selected as boot firmware in the setting of the virtual machine. c) The disk size is 8000MByte or less. d) Windows OS is installed. e) The disk type is GPT disk. Problem Explanation: Deploy-OS cannot calculate correct position of Backup Partition Table which exists at the end of the disk because the recognized disk size differs between Windows OS driver and Deploy-OS driver. Therefore, an error occurs because Deploy-OS recognizes the disk as incorrect when it is analyzing the disk. Solution: Fixed so that Deploy-OS calculates the position of Backup Partition Table by the offset in Primary Partition Table not at the end of the disk but at the beginning of the disk. (4) DPM Client service cannot start (#15534) Phenomenon: When the following conditions are met, DPM Client (Windows) cannot start. a) DPM Client was newly installed by DeploymentManager Ver6.2x, or in the environment that DPM Client was newly installed by DeploymentManager Ver6.2x, DPM Client was overwritten by DeploymentManager Ver6.30. b) The path of the installation folder includes a space character and there is a file or a folder which path is the character string before the space character. Example) In the case of DPM Client installation folder: C:\Program Files\NEC\DeploymentManager_Client The folder "C:\Program" exists. Problem Explanation: This problem occurs because the path of DPM Client installation folder is not bracketed by "(double quotation) when DeploymentManager set the path in the registry.This problem does not occur when DPM Client is newly installed by DeploymentManager Ver6.30. Solution: Fixed so that the character string in the registry is checked and it is bracketed by " " when DPM Client is overwritten. (5) It fails to execute OS installation by disk duplication depending on the boot order of the duplication destination machine of UEFI boot (#15666) Phenomenon: When the following conditions are met, it may fail to execute OS installation by disk duplication. a) The order of OS boot entry on the master machine is more than the numbe of NICs on the duplication destination machine. b) The duplication destination machine has two or more NICs. Problem Explanation: When you backup or restore UEFI machine, UEFI boot order is also backed up or restored. In restoring the image, when the order of OS boot entry on the master machine is more than the number of NICs on the duplication destination machine, the boot order is configured on the duplication destination machine as follows and the order of NICs is changed. Therefore, it may fail to get a disk duplication data file. The boot order of The boot order of The boot order the master machine the duplication after restoring destination machine 0 UEFI:LAN1 0 UEFI:LAN3 0 UEFI:LAN3 1 UEFI:USB 1 UEFI:LAN4 1 UEFI:USB 2 FC LU0 2 UEFI:Built-in EFI 2 FC LU0 3 Windows Boot Manager 3 UEFI:USB 3 UEFI:LAN4 4 UEFI:LAN2 4 Windows Boot Manager 4 Windows Boot Manager 5 UEFI:Built-in EFI 5 FC LU0 5 UEFI:Built-in EFI Solution: Fixed the processing of restoring UEFI boot order so that the order of NICs is not changed. 1.3. Fixed Problems in System Monitor - Performance Monitoring Services (1) An error occurs when you specify 30 minutes or more as collecting intervals for the VMware ESXi collecting performance data. (#15497) Phenomenon: When you specify 30 minutes or more as collecting intervals for the VMware ESXi collecting performance data, the error occurs. Problem Explanation: System Monitor - Performance Monitoring Services operates to obtain the five-minute-interval performance data of the targeted VMware ESXi when you specify 30 minutes or more as collecting intervals. However, the collecting of the five-minute-interval performance data is no more supported and the error occurs. Solution: Fixed so that to obtain the 20-second-interval performance data of the VMware ESXi when you specify 30 minutes or more as collecting intervals for the VMware ESXi collecting performance data. You cannot specify one hour or more because the 20-second-interval performance data of the VMware ESXi holds only one hour or less. (2) Modification of the issue which Hole punching of a firewall is performed to some profile while installing, when multiple profiles are valid in Windows Server 2008 R2 or later. Phenomenon: In Windows Server 2008 R2 or later, when you install it in the environment in which multiple profiles are used, hole punching of a firewall is performed to the most restricted profile. Problem Explanation: In Windows Server 2008 R2 or later, different profile can be allocated and used in each network and interface. This improvement is expected that the most restricted profile which operates in the original OS version will be used. The order of the most restricted profile is as follows (from left to right): [Public],[Private] and [Domain]. Solution: Fixed so that hole punching of a firewall is performed to all valid profiles in Windows Server 2008 R2 or later, which is the environment of multiple profiles are valid. When you update from SigmaSystemCenter3.3, hole punching of a firewall is performed to the concerned profile. 1.4. Fixed Problems in NEC ESMPRO Manager (1) "Delay Time" of "Power Restore Delay Setting" is not displayed correctly Phenomenon: In the case of the managed component in which EXPRESSSCOPE Engine3 is integrated, "Delay Time" of "Power Restore Delay Setting" may not be displayed correctly. Problem Explanation: In the case of the managed component in which EXPRESSSCOPE Engine3 is integrated, "Delay Time" of "Power Restore Delay Setting" may not be displayed correctly depending on the "Delay Time" setting on "Power Restore Delay Setting". (Setting is done correctly.) Solution: Fixed the above problem. (2) Progress rate of "NEC ExpressUpdate" is not updated as 99% Phenomenon: When you execute "NEC ExpressUpdate", the progress rate may not be updated as 99%. Problem Explanation: When you execute NEC ExpressUpdate via a Management Controller, the progress rate may not be updated as 99%. (Update of BMC firmware is completed correctly.) Solution: Fixed the above problem. (3) The download process of NEC ExpressUpdate may fail Phenomenon: When executing "Download Update Packages" of NEC ExpressUpdate features, the download process may fail. Problem Explanation: When "Download Update Packages" is executed under the conditions that network to the Update Package Server is busy, downloading of update packages may fail. Solution: Fixed the above problem. 2. Functional Enhancements 2.1. Functional Enhancements in SystemProvisioning (1) Enhanced Web graph display in the Web Console Support Overview: For the graph display of the Web Console, the new function is added to specify the end time in the case of specifying the display period of time, when you intend to display a history graph. (#15437) The display style of the performance data value on the graph displayed in the Web Console is revised. (#15029) The condition of the displaying object(Model/Group), which is displayed in the [Group Performance Summary] screen by default, is changed. If the Model setting is performed, Model is displayed by default. If not, Group is displayed by default. (#15147) In the [Saving Graph Setting] screen, [Cancel] is added. (#15317) (2) Enhanced policy action Support Overview: In the contents of email by [Notification/E-mail Reporting] of the policy action, the latest performed action information is listed in the items of [ActionSummary], [ActionDiscription], [ExceptionMessage] and [WarningMessage]. (#15614) [Notification/Event Log] is added in the policy action. By setting this action in the policy, Event Log can be output in the timing of Start or Finish (and so on) of each action. (#15614) [Action for machine/Power OFF] is added in the policy action. By setting this action in the policy, a machine can be Power OFF. (#12923) (3) Enhanced policy setting Support Overview: When you intend to creat a new policy by manually, the Suppression Settings, which is the [General] tab under the Property Setting, is selected by default. However, the suppression functions of the standard policy, which is registered automatically when PVMService starts, is invalid.(#15668) (4) Enhanced event detecting Support Overview: By describing in an event definition file, receiving arbitrary SNMP Trap, events can be output in the [Event History] screen. However, the event which is intended for a device cannot be the timing of the policy action. (#13837) (5) Enhanced periodical collection Support Overview: If the periodical collection is executed when the normal job starts, the periodical collection will be canceled. The canceled job will start when the other job completes. (#14947) (6) Addition of the Custom Setting Support Overview: The [Custom] tab, which configures unique information, is added to the Property Settings of Group/Host/Machine. (#5068) (7) Enhanced collaboration with a LDAP server Support Overview: By obtaining user information, which is under the specific group, from the LDAP server, users can be registered in SystemProvisioning's users. (#14703) (8) Enhanced monitoring profile setting Support Overview: The monitoring profile can be configured in the host. (#14462) By editing the monitoring profile, the Public Scope can be changed. (#15341) (9) Enhanced ssc command Support Overview: Following features are now added to ssc command: - The command which performs Add/Delete/Display of the custom setting is added. (#5068) - The command which performs the synchronization with the LDAP server is added. (#14703) - By a command which is configured in the monitoring profile, the host can be specified to the object. (#14462) - The renewal command of the monitoring profile can be changed the Public Scope. (#15341) - When creating a disk volume, Shared/Unshared can be specified. (#15590) - Share Status and Management Status of a disk volume can be changed. (#15590) - A disk array list can be displayed. (#15860) - A disk array can be registered. (#15588) - For assign or release the disk volume, the access control to multiple machines, in specifying the operation group, can be executed collectively. (#15592) - The HBA setting of the machine and the list of path of a disk array can be displayed. (#11907) - Enhance the check function so that the unshared disk volume cannot be added to more than one host definition. (#15030) - Enhance the check function so that the unshared disk volume cannot be added to more than one machine. (#15030) - Enhance the check function so that the disk volume cannot be released from a running machine. (#15030) - Enhance the check function so that the disk volume, which is allocated to machine or is added to host definition, cannot be deleted. (#15030) - Storage subsystem can be registered. (#15587) (10) Enhanced Virtual environment management Support Overview: Unique information can be reflected when importing a virtual machine of Standalone ESX or Hyper-V. ((#15676)) Modification of the procedure when a virtual machine server, a virtual machine and templates move over the subsystem. Previously, you need to conduct following procedures such as the releasing them from a operation group, collecting a destination subsystem, collecting original subsystem and reregistering again to the operation group. Now that only collecting the destination subsystem is needed. (#15515) (11) Enhanced collaboration with VMware Support Overview: Even if a guest OS of a virtual machine is Linux, you can execute an extended-setting command. (#15197) For a VMware HA event of event ID [VM is restarted by VMwareHA], [vSphere HA failover action initiated] and [vSphere HA failover action completed], same event can be notified as a group event. You can execute a policy action to these events. (#15476) The virtual machine's SATA storage controller which is supported in VMware vSphere 5.5 is now available. (#14518) The virtual machine's number of cores per socket and type of a NIC can be specified. (#14689) (12) Enhanced tag cloud Support Overview: The tag cloud feature is added to the details of Operation Group. (#8988) (13) Enhanced Storage Topology feature Support Overview: The [Topology] tab, which is displayed the tree view of the storage pool, the disk volume and managed machines, is added to the details of Disk Array in the Resource view. (#13807) (14) Enhanced collaboration with KVM Support Overview: KVM on Red Hat Enterprise Linux 7 is now supported. (#15302) Hot Plug/Unplug of VM disks is now supported. (#15682) (15) Enhanced VM Placement Rule Support Overview: The VM Placement Rule feature has been improved so that it controls multiple virtual machines are placed in different virtual machine servers from each other. (#15448) In the environment which is updated from SigmaSystemCenter 3.1 or earlier to 3.1 Update1 or later, the EQ rule which was configured in SigmaSystemCenter 3.1 or earlier is invalid in the case that when you do not execute the operation to validate the placement rule settings (ssc vmop verify-rule command) though the EQ rule was configured. Additional placement rule setting is not available for the model above. Before or after updating SigmaSystemCenter, perform the updating of VM Placement Rule referring to Subsection3.5.5, "If You Upgraded From SigmaSystemCenter 2.0 or Later" in SigmaSystemCenter Installation Guide. (16) Enhanced Dependency Support Overview: Enable/Disable dependency of sequence control can be now configured in the each operation (Start, Shutdown, Restart and VM Evacuation). Also, you can group dependency and allow them to be set different configuration each other. This helps you to perform a flexible configuration such as controlling the moving sequence when perform VM Evacuation triggered by virtual machine server's failure. (#15432) For sequence control of dependency, although the operation of dependee or dependent fails, following procedure can be progressed.(Weak Dependency) (#15434) (17) Enhanced collaboration with Hyper-V Support Overview: A share function of a virtual machine disk in Windows Server 2012 R2 Hyper-V is added. (#14633) An added function of SCSI disk in running virtual machines is supported. (#11612) A new function, which can be changed the running disk size in Windows Server 2012 R2 or later, is supported. (#14555) For specifying the option [Exclude extended disk] of Storage Migration, a virtual machine Generation 2 is supported. (#15255) (18) Enhanced collaboration with DeploymentManager Support Overview: In the software package option whose type is "Application and Update", variables which is similar to an environmental variable can be specified. (#15299) Unique information configured in the Custom setting can be specified as an environmental variable of local script and a software package option whose type is "Application and Update" (#5068, #15299) The type of a backup image of a backup scenario is checked. (#15622) When the result of software distribution whose type is "Application and Update" outputs to the operation log, the number of letters to be output can be configured in the registry. (#15644) In Linux OS, the extended-setting command of a host profile can be executed through DeploymentManager. (#15197) If the machine specific information when creating a virtual machine is necessary and if a DPM server is not configured in the operation group and model, the machine specific information is reflected through DeploymentManager, selecting a DPM server automatically. (#14134) (19) The Connection timeout value of SLB and vFirewall is stored in the registry. (#15713) Support Overview: The Connection timeout value of SLB and vFirewall can be configured in the registry. The default value is 60 seconds. 2.2. Functional Enhancements in DeploymentManager (1) You can save the type of the backup image (#1188) Support Overview: When you create a backup scenario, you can specify either of - Image for OS installation by disk duplication - Image for recovery for the backup image. You can check whether was specified in the detailed information of the backup image. (2) You can backup or restore two or more disks (#4461) Support Overview: In the backup or restore scenario, you can specify two or more disks as the target. By this function, when the system disk of OS is on two or more disks, you can backup or restore disks by one scenario. (3) Built-in scenarios are added (#10078, #11011) Support Overview: The following built-in scenarios are added. a) Scenario for changing IP address You can change the setting of IPv4 address, gateway, DNS, and WINS of the managed machine. b) Scenario for changing the machine name You can change the machine name of the managed machine. c) Scenario for changing the password of Administrator or root You can change the password of Administrator or root of the manage machine. The managed machine of the following OSs is supported. - Windows OS Windows Server 2008/Windows Vista or later - Linux OS Red Hat Enterprise Linux 6 or later SUSE Linux Enterprise 10 or later (4) Image Builder is improved (#11677) Support Overview: When you create Windows package by Image Builder, you can enter "-"(hyphen), "."(period), and "_"(underscore) in MS number. You needed to use PackageDescriber to enter "-", ".", and "_". You can also enter them by Image Builder. (5) Standard mode in Internet Explorer 9 and 10 is supported (#11988) Support Overview: On the Web Console, standard mode in Internet Explorer 9 and 10 is supported When you use Internet Explorer 9 and 10, you do not need to set compatible mode. (6) Wrong operation in batch execution is prevented on the Web Console (#12374) Support Overview: To prevent wrong operation in batch execution, the following operations are improved. - Screen transition in batch execution of scenario assignment or scenario execution get the same with the operation for each machine. - When you execute batch execution, warning screen appears if you select each machine. (7) The order of recognized disk in backup or restoring is improved (#12685) Support Overview: When you backup or restore the managed machine to which two or more iStorage are connecting by FC switch, the order of disks which is recognized by DeploymentManager was not constant. By this improvement, the order is constant and you can execute the scenario in the iStorage environment that disks which are not backed up or restored are connected. You need to execute disk configuration check in advance. (8) OS clear installation in UEFI environment is supported (#13516) Support Overview: OS clear installation (Linux) is supported for the managed machine in UEFI mode. (9) Batch creation of disk duplication data files (Windows parameter file(Express)) is supported (#14299) Support Overview: You can execute batch creation of Windows parameter file(Express) in the same way with Windows parameter file. (10) Red Hat Enterprise Linux 7 is supported (#15102) Support Overview: Red Hat Enterprise Linux 7 is supported as OS of the managed machine. (11) Setup parameter of a package is enhanced (#15371) Support Overview: The following is enhanced about setup parameter in [Package] tab of the scenario. a) Character string is enhanced The maximum length of character string of setup parameter for one package is enhanced to 128KB. You can specify 2MB or less for one scenario totally. b) DeploymentManager specific variable is supported As DeploymentManager specific variable, MAC address, UUID, IP address, and machine name are supported. By these variables, you can use machine specific information as setup parameter for each managed machine on which a scenario is executed. (12) Characters that you can specify for a folder are unified (#15462) Support Overview: About the following DeploymentManager related folder, characters that you cannot specify as folder name are unified. - Folder for Image - Folder for Backup Image - TFTP root folder You cannot specify the following characters. - Characters that cannot be used in Windows OS (/ : * ? < > | ") - Semicolon(;) As DeploymentManager installation folder, "%" and "=" cannot be also entered except the above characters. (13) JRE8 is supported (#15586) Support Overview: On JRE8, you can create a parameter file for OS clear installation or a disk duplication data file (Linux) by Image Builder or you can use PackageDescriber. (14) In file distribution (Linux), specifying the permission is improved (#15859) Support Overview: You can set the permission of the directory and the file in the destination. 2.3. Functional Enhancements in System Monitor - Performance Monitoring Services (1) Enhanced monitoring infrastructure Support Overview: The new function, which is collecting the performance data of NEC Storage logical disk from storage and displaying a graph on the Web console, is now offered. (#14747) The new procedure, which will retry a prompt set when it fails after logging in a Linux machine to collect Linux data, is added. (#15214) (2) Enhanced log function Support Overview: Output folder of Debug log of System Monitor - Performance Monitoring Services can be changed. (#14878) (3) Other enhancement Support Overview: The default value of the database capacity warning value of System Monitor - Performance Monitoring Services is improved to 9.0 GB. (#15349) 2.4. Functional Enhancements in NEC ESMPRO Manager (1) Update the certificate of the Java applications Support Overview: - Updated the certificate of the Java applications included in NEC ESMPRO Manager. =============================================================================== 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. =============================================================================== Abount Manuals on Components =============================================================================== Manuals of DeploymentManager are stored in this software. Please inquire about manuals of other components. =============================================================================== 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 2014