================================================================================ DeploymentManager Ver6.1 Update Module Release Notes (DPM610-001) ================================================================================ NEC Corporation [Table of Contents] Oct 2012 1. Introduction 2. Target Product 3. Before Installation 4. Installation Procedure 5. Functional Enhancements 6. Fixed Problems 7. Release Modules List 8. Trademark and Copyright Information ================================================================================ 1. Introduction This module is an update module for DeploymentManager Ver6.1. 2. Target Product - DeploymentManager Ver6.1(Version:6.10) 3. Before Installation By installing this software, the services of DeploymentManager are stopped. Make sure that it does not hinder your system operation when installing this software. 3.1 Notes on unzipping this update module 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 the Windows OS (such as Windows Server 2008, etc.). 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 processes may not start. (1) Checking and changing the policy setting (Hide mechanisms to remove zone information): 1) Click the [Start] menu, 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 in (1). 3.2 Unzipping this update module Copy this update module (DPM610-001.zip) to an arbitrary folder (operation folder) and unzip it. Hereinafter, the folder after DPM610-001.zip is unzipped will be referred to as the "unzipped folder". 4. Installation Procedure The procedures of installing the following modules will be explained: - DPM Server - DPM Client (Windows) - Image Builder (Remote Console) - DPM Command Line If DPM Server is installed in the cluster environment, see [Installation Procedure to the Cluster Environment]. - When you open ports by seeing Section 7.1.2, "Executing the Tool on Each Machine" in DeploymentManager ReferenceGuide, use files in this software (described in [DeploymentManager (TOOLS)] of [7. Release Modules List]). (Also, replace the description of the file path with the file path of this update module.) - In this guide, the description as menu of Windows OS is followed by Windows Server 2008. When you use other Windows OSs, the display or the procedure may be different. Replace the description. Example) - For Windows Vista / Windows 7 1) Open [Programs and Features] by selecting [Control Panel] from the [Start] menu. 2) If the [Version] is not displayed, perform the following 3) and 4). 3) Right-click the [Name] in the center of the screen and select [More...]. 4) Select the [Version] check box in the [Choose Details] screen and click [OK]. - For Windows XP / Windows Server 2003 1) Open [Add or Remove Programs] by selecting [Control Panel] from the [Start] menu. 2) Select the target application and click [Click here for support information]. [DPM Server] The OS does not have to be restarted after installation. - There is a case that you need to install the module for the machine model depending on the machine model of the managed machine. Contact your sales or support representative to confirm whether you need to install the module for the machine model. Even if the module is already installed, install the latest module for the machine model. (1) Log on to the machine Log on to the machine where the DPM Server is installed with a user with Administrator rights (usually Administrator). (2) Check the Version Check the version by following the procedures below. 1) Start the DPM Web Console. 2) Check that "DeploymentManager 6.1" is displayed at the bottom of the DPM Web Console. 3) After checking, end the DPM Web Console. (3) Before updating files End all DPM related processes (DPM Web Console, Image Builder, automatic update, scenario execution, etc.). If there is a scenario that is being executed, either wait until the scenario is completed, or stop the scenario and check to see that the process of stopping has been completed. If there is an automatic update that is being executed, wait until the update has been completed. (4) Executing the Installer 1) Copy "\DPM610-001\Setup\DPM" folder in the unzipped folder to the arbitrary folder on the machine where the DPM Server is installed. Execute "DPM61100001_MNG.exe" in the copied folder. If "DPM61100001_MNG.exe" is executed to an inapplicable version, the following message will appear: "Installed DPM Server is the version that does not support for update." 2) The installer will activate and the installation of the update module will start. Then, follow the procedures that will be displayed on the screen and perform installation. The message, which means that DeploymentManager API Service was stopped, may appear. Select [Close] button because there is no problem. (5) Check the version after installation After installation, check the version by following the procedures below. 1) Start the DPM Web Console. 2) Check that "DeploymentManager 6.11" is displayed at the bottom of the DPM Web Console. 3) After checking, end the DPM Web Console. The installation is completed. The folder which was copied in procedure (4) is unnecessary after the installation. Delete it. [DPM Client (Windows)] The OS does not have to be restarted after installation. If you install the DPM Client for the first time, directly install this update module. You do not need to install the DPM Client in advance. Also, if the DPM Client is already installed, you do not need to install this software. (1) Log on to the machine Log on to the machine where the DPM Client will be installed with a user with Administrator rights (usually Administrator). (2) Executing the installer 1) Copy "\DPM610-001\TOOLS\SERVICES" folder in the unzipped folder to the arbitrary folder on the machine where the DPM Client will be installed. Execute "setup.exe" in the copied folder. For the x86: SERVICES\IA32\setup.exe For the x64: SERVICES\AMD64\setup.exe 2) A confirmation message will appear. Click [OK]. 3) The [Enter IP Address] screen will appear. Enter the IP address of the machine where the DPM Server is installed and click [Next]. - When you omit the IP address, the Management Server is automatically searched after the installation is completed. It takes some time to search. 4) Installation of the module will begin. (3) Check the version after installation After installation, check the version by following the procedures below. 1) Open [Programs and Features] by selecting [Control Panel] from the [Start] menu. 2) Check that the [Version] of [DeploymentManager] is "6.10.000". The installation is completed. The folder which was copied in procedure (2) is unnecessary after the installation. Delete it. [Image Builder (Remote Console)] The OS does not have to be restarted after installation. Install this software following the procedures below only when Image Builder (Remote Console) is installed to a machine where the DPM Server is not installed. (1) Log on to the machine Log on to the machine where the Image Builder (Remote Console) is installed with a user with Administrator rights (usually Administrator). (2) Check the version Check the version by following the procedures below. 1) Open [Programs and Features] by selecting [Control Panel] from the [Start] menu. 2) Check that the [Version] of [DeploymentManager(Image Builder)]. The target component version: "6.10.000". (3) Before updating files End the Image Builder (Remote Console). (4) Executing the Installer 1) Copy "\DPM610-001\Setup\DIB" folder in the unzipped folder to the arbitrary folder on the machine where the Image Builder (Remote Console) is installed. Execute "setup.exe" in the copied folder. 2) The installer will activate and the installation of the update module will start. Then, follow the procedures that will be displayed on the screen and perform installation. (5) Check the version after installation After installation, check the version by following the procedures below. 1) Open [Programs and Features] by selecting [Control Panel] from the [Start] menu. 2) Check that the [Version] of [DeploymentManager(Image Builder)]. The component version: "6.11.000". The installation is completed. The folder which was copied in procedure (4) is unnecessary after the installation. Delete it. [DPM Command Line] The OS does not have to be restarted after installation. Install this software following the procedures below only when the DPM Command Line is installed to a machine where the DPM Server is not installed. (1) Log on to the machine Log on to the machine where the DPM Command Line is installed with a user with Administrator rights (usually Administrator). (2) Check the Version Check the version by following the procedures below. 1) Open [Programs and Features] by selecting [Control Panel] from the [Start] menu. 2) Check [Version] of [DeploymentManager (Command Line)]. The target component version: 6.10.000. (3) Before updating files If you use the DPM Command Line, end it. (4) Executing the Installer 1) Copy "\DPM610-001\Setup\CMD" folder in the unzipped folder to the arbitrary folder on the machine where the DPM Command Line is installed. Execute "setup.exe" in the copied folder. 2) The installer will activate and the installation of the update module will start. Then, follow the procedures that will be displayed on the screen and perform installation. (5) Check the version after installation After installation, check the version by following procedures below. 1) Open [Programs and Features] by selecting [Control Panel] from the [Start] menu. 2) Check [Version] of [DeploymentManager (DPM Command Line)]. The component version: 6.11.000 The installation is completed. The folder which was copied in procedure (4) is unnecessary after the installation. Delete it. [Installation Procedure to the Cluster Environment] If DPM Server is installed in the Cluster environment, install this update module by following the procedures below. The following procedures can be applied to both of shared disk type/mirror type Cluster systems. (1) Suspending the Cluster Suspend the Cluster by seeing the procedures of the Cluster Software that is being used. (2) End Monitored Services End the monitored services by seeing the procedures of the Cluster Software that is being used. (3) Installing the Update Module to an Active Node Server Install this update module to the active node server by seeing [Installation Procedure] that is explained earlier in this manual. (4) Installing this Update Module to the Standby Node Server Install this update module to the standby node server by seeing [Installation procedure] that is explained earlier in this manual. Replace step 1) in [(4) Executing the installer] of [DPM Server] with the following. 1) Copy "\DPM610-001\Setup\DPM" folder in the unzipped folder to the arbitrary folder on the machine where the DPM Server is installed. Start the command prompt and go to the copied folder. Execute "DPM61100001_MNG.exe" with the parameters as below. DPM61100001_MNG.exe NODB=1 NOSERVICE=1 NOREGISTRY=1 NOSHAREDISKDATA=1 (5) Resuming the Cluster Resume the Cluster by seeing to the procedures of the Cluster Software being used. (6) Activate the resources in the failover group on the Standby Node Server Activate the resources in the failover group on the standby node server by seeing the procedures of the Cluster Software being used. (7) Start monitoring of the monitored services Activate monitoring of the monitored services by seeing the procedures of the Cluster Software being used. The installation is completed. 5. Functional Enhancements [Functional Enhancements from DPM Ver6.10] The followings are enhanced. (1) vSphere 5.1 is supported. (#12641) Support Overview: vSphere 5.1 is supported. (2) The function of MAC Address Allocation in vSphere is supported. (#12763) Support Overview: In the early version, when the managed machine (virtual machine) was registered on DPM, the machine was not powered off after the registration. This is done by describing the MAC address in the following file. \Datafile\forceskip.ini However, in the function of MAC Address Allocation in vSphere 5.1, MAC address can be specified arbitrarily. Therefore from this version, the specification is changed not to power off the machine after the registration, regardless of whether the managed machine is physical or virtual. If you want to power off the machine after registering the machine, configure the above file by seeing Section 2.2.1.1, "Automatically Acquiring the Information of a Managed Machine and Registering the Machine on DPM" in DeploymentManager OperationGuide. (3) Windows Server 2012 is supported. (#12793) Support Overview: Windows Server 2012 is supported as a managed machine. Only the following functions are supported in this version. Backup/restore/disk configuration check Power on/shutdown Status check of power on/off Obtaining the information of OS/service packs/hotfixes/applications 6. Fixed Problems [Fixed problems from DPM Ver6.10] The following problems are fixed. (1) DeploymentManager API Service ends abnormally. (#12784) Phenomenon: If you repeat the operation of obtaining the computer information, DeploymentManager API Service may end abnormally. Problem Explanation: If you execute the operation of obtaining the computer information (refreshing the screen, referring to/obtaining the computer information, etc.), a memory leak occurs when DPM obtains the applications/hotfixes information of the managed machine. As a result, if used memory exceeds the maximum limit of usable memory, the phenomenon that DeploymentManager API Service ends abnormally occurs. Solution: Fixed not to leak the memory. 7. Release Modules List The modules released with this software are as follows: The following files overwrite the existing files. The followings are for the x86. For the x64, replace [C:\Program Files] with [C:\Program Files(x86)]. In the DPM Server folder (The default installation folder: C:\Program Files\NEC\DeploymentManager\) apiserv.exe 441,792 bytes 09/03/2012 10:52 AM dbadmin.exe 102,336 bytes 09/03/2012 10:52 AM db_install.sql 303,724 bytes 09/26/2012 05:41 PM dpmcmd.exe 227,776 bytes 09/03/2012 10:52 AM DmSrvapi.dll 838,592 bytes 09/03/2012 10:52 AM PmInfo.dll 189,376 bytes 09/10/2012 09:28 AM Datafile\ forceskip.ini 3 bytes 09/04/2012 04:07 PM Source\SHARE\AgentUpgrade\ AgentUpgrade.zip 2,851,575 bytes 09/10/2012 10:19 AM Source\SHARE\PP\ AgentUpgrade.zip 2,851,575 bytes 09/10/2012 10:19 AM Source\SHARE\ClStatus\common\I386\$oem$\$$\SYSTEM32\ DepInfo.dll 350,656 bytes 09/03/2012 10:52 AM rupdsvc.exe 600,512 bytes 09/10/2012 09:28 AM Source\SHARE\Sysprep\Windows\AMD64\ DepInfo.dll 350,656 bytes 09/03/2012 10:52 AM rupdsvc.exe 600,512 bytes 09/10/2012 09:28 AM Source\SHARE\Sysprep\Windows\IA32\ DepInfo.dll 350,656 bytes 09/03/2012 10:52 AM rupdsvc.exe 600,512 bytes 09/10/2012 09:28 AM WebServer\App_Data\Config\ Manifest.xml 433 bytes 09/26/2012 06:06 PM manual\ DPM_FirstStepGuide.pdf 1,050,364 bytes 10/10/2012 10:56 AM DPM_InstallationGuide.pdf 11,031,067 bytes 10/10/2012 11:17 AM DPM_OperationGuide.pdf 3,197,530 bytes 10/10/2012 11:35 AM In the Image folder (The default installation folder: C:\Deploy\) AgentUpgrade\ AgentUpgrade.zip 2,851,575 bytes 09/10/2012 10:19 AM PP\ AgentUpgrade.zip 2,851,575 bytes 09/10/2012 10:19 AM Sysprep\Windows\AMD64\ DepInfo.dll 350,656 bytes 09/03/2012 10:52 AM rupdsvc.exe 600,512 bytes 09/10/2012 09:28 AM Sysprep\Windows\IA32\ DepInfo.dll 350,656 bytes 09/03/2012 10:52 AM rupdsvc.exe 600,512 bytes 09/10/2012 09:28 AM ClStatus\common\I386\$oem$\$$\SYSTEM32\ DepInfo.dll 350,656 bytes 09/03/2012 10:52 AM rupdsvc.exe 600,512 bytes 09/10/2012 09:28 AM DeploymentManager (TOOLS) Use the modules accordingly by seeing [4. Installation Procedure] - in this document. In the folder for opening a port TOOLS\OPENPORT\ DepOpnPt.exe 162,752 bytes 09/03/2012 10:52 AM 8. 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 2012