================================================================================ DeploymentManager Ver6.1 Update Module Release Notes (DPM610-003) ================================================================================ NEC Corporation [Table of Contents] May 2013 1. Introduction 2. Target Product 3. Before Installation 4. Installation Procedure 5. Fixed Problems 6. Release Modules List 7. Trademark and Copyright Information ================================================================================ 1. Introduction This module is an update module for DeploymentManager Ver6.1. 2. Target Product - DeploymentManager Ver6.1(Version:6.12) 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 software 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] 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 in (1). 3.2 Unzipping this software Copy this software (DPM610-003.zip) to an arbitrary folder (operation folder) and unzip it. 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. Hereinafter, the folder after DPM610-003.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) - DPM Client (Linux) - When you install this update module, you need to do the followings. - Be sure to upgrade DPM Client. - For OS installation by disk duplication, you need to recreate the master image if you specified no IP address of DPM Server or a wrong address when you prepared to create a master image or if you created a master image by using a built-in scenario. - When installing this software remotely, do not use remote management software (Terminal Services and so on) except Remote Desktop. (The name is changed from "Terminal Services" to "Remote Desktop Services" in Windows Server 2008 R2 or later. - If DPM Server is installed in the cluster environment, see [Installation Procedure to the Cluster Environment]. - If you do not intend to install this update module, configure the DHCP server on a different machine from the machine running DPM Server and set the IP address of DPM Server to DPM Client correctly to avoid the problem of (1) in "5. Fixed Problems". - In the following case, use the files in this software (described in [DeploymentManager (TOOLS)] of [6. Release Modules List]). Also, replace the file paths in the following description of user's guide with them of this software. - When executing OS installation by disk duplication For details, see 3.3, "OS Installation by Disk Duplication (Windows)" and 3.4, "OS Installation by Disk Duplication (Linux)" in DeploymentManager Operation Guide. - 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 Server 2012 / Windows 8 1) On Windows Desktop, hover the mouse cursor in the upper (or lower) right corner to show the charms, and then click [Settings] on the charms. 2) On [Settings], click [Control Panel], then click [Programs], and then click [Programs and Features]. - For Windows Server 2008 / Windows Vista / Windows 7 Open [Programs and Features] by selecting [Control Panel] from the [Start] menu. * If the [Version] is not displayed, perform the following 1) and 2). 1) Right-click the [Name] in the center of the screen and select [More...]. 2) Select the [Version] check box in the [Choose Details] screen and click [OK]. - For OS other than the above 1) Open [Add or Remove Programs](or [Add or Remove Applications]) by selecting [Control Panel] from the [Start] menu. 2) Select the target application and click [Click here for support information]. - Before installing this software, it is recommended that you execute backup of the data, seeing 9.3, "Data Backup Plan" in DeploymentManager Reference Guide. [DPM Server] The operating system does not have to be restarted after installation. - Even if you install this update module, you do not need to install the module for the machine model. Do not install DPM60_006(the module for the machine model), because the module will be replaced by the older one for DPM Ver6.11 if you install it. - To make the procedure described in (1) in "5. Fixed Problems" effective, you need to configure the DPM Server so that it can use the port 4011 (UDP) on the Management Server. When a firewall, security software and so on are enabled, open the port 4011 (UDP). (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(before installing this software) 1) Start Web Console. 2) Check that "DeploymentManager 6.12" is displayed at the bottom of Web Console. 3) After checking, end Web Console. (3) Before updating files - End all DPM-related processes (such as Web Console, Image Builder, automatic update, scenario execution). 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. - End all the running applications and the Web browser. (4) Executing the Installer 1) Copy the following folder to the arbitrary place of the machine on which the DPM Server is installed. \DPM610-003\Setup\DPM 2) Execute "DPM61300001_MNG.exe" in the folder which was copied in 1). If "DPM61300001_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." 3) The installer will be activated and the installation of the software 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 installing this software) 1) Start Web Console. 2) Check that "DeploymentManager 6.13" is displayed at the bottom of Web Console. 3) After checking, end Web Console. The installation of DPM Server is completed. The folder which was copied in procedure (4) is unnecessary after the installation. Delete it. [DPM Client (Windows)] The operating system does not have to be restarted after installation. - The DPM Client can be upgraded by using a scenario. (For details, see 3.3.2, "Manually Upgrading the DPM Client" in DeploymentManager Installation Guide.) - If you install the DPM Client newly, install this software directly. You do not need to install the DPM Client in advance. (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) Check the version (before installing the software) 1) Open [Programs and Features] by selecting [Control Panel] from the [Start] menu. 2) Check that the [Version] of [DeploymentManager] is "6.12.000". (3) Before updating files Ensure that no scenario is being executed on the machine on which this software is installed. If there is a scenario that is being executed, wait until the scenario is completed, or stop the scenario and ensure that the stopping process has been completed. (4) Executing the installer 1) Copy the following folder to the arbitrary place of the machine on which the DPM Client is installed. For the x86: \DPM610-003\TOOLS\SERVICES\IA32 For the x64: \DPM610-003\TOOLS\SERVICES\AMD64 2) Execute "setup.exe" in the folder which was copied in 1). 3) A confirmation message will appear. Click [OK]. 4) 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. 5) Installation of the module will begin. (5) Check the version (after installing this software) 1) Open [Programs and Features] by selecting [Control Panel] from the [Start] menu. 2) Check that the [Version] of [DeploymentManager] is "6.13.000". The installation of DPM Client (Windows) is completed. The folder which was copied in procedure (4) is unnecessary after the installation. Delete it. [DPM Client (Linux)] The operating system does not have to be restarted after installation. - The DPM Client can be upgraded by using a scenario. (For details, see 3.3.2, "Manually Upgrading the DPM Client" in DeploymentManager Installation Guide.) - If you install the DPM Client newly, install this software directly. You do not need to install the DPM Client in advance. (1) Log in to a machine Log in to the managed machine, on which the DPM Client is installed, with the root account. (2) Check the Version(before installing the software) Execute the following command and check that the displayed version is "DeploymentManager Ver6.12" cd /opt/dpmclient/agent/bin depagtd -v (3) Before updating files Ensure that no scenario is being executed on the machine on which this software is installed. If there is a scenario that is being executed, wait until the scenario is completed, or stop the scenario and ensure that the stopping process has been completed. (4) Execute the Installer 1) Copy the following folder to the arbitrary place of the machine on which the DPM Client is installed. \DPM610-003\Linux Hereinafter, the procedure is described as an example when the folder is copied to "/tmp/dpm" directory. 2) Go to the following directory that was copied in step (1). # cd /tmp/dpm/Linux/ia32/bin/agent 3) Execute "depinst.sh". # ./depinst.sh 4) The following message will appear. Enter the IP address of the Management Server and press the [Enter] key. - "Enter the IP address of the management server." - When you omit the IP address, the Management Server is automatically searched after the installation is completed. It takes some time to search. (5) Check the version (after installing this software) Execute the following command and confirm that the displayed version is "DeploymentManager Ver6.13" cd /opt/dpmclient/agent/bin depagtd -v For other precautions, see 2.2.2, "Installing the Linux (x86/x64) Version" in DeploymentManager Installation Guide. The installation of DPM Client (Linux) is completed. The folder which was copied in procedure (4) is unnecessary after the installation. Delete it. [Installation Procedure to the Cluster Environment] If the DPM Server is installed in the Cluster environment, install this software by following the procedures below. The following procedures can be applied to Cluster systems of both of shared disk type/mirror type. (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 this software to an Active Node Server Install this software to the active node server by seeing the above [Installation Procedure]. (4) Installing this software to the Standby Node Server Install this software to the standby node server by seeing the above [Installation procedure]. Replace step 1) and 2) in [(4) Executing the Installer] of [DPM Server] with the following. 1) Copy the following folder to the arbitrary place of the machine on which the DPM Server is installed. \DPM610-003\Setup\DPM 2) Start the command prompt and go to the folder which is copied in 1) and execute "DPM61300001_MNG.exe" with the parameter as the following. DPM61300001_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. Fixed Problems [Fixed problems from DPM Ver6.12] The following problems are fixed. (1) The problem may occur in DHCP operation and the Management Server cannot be searched over the network segment. (#13880, #13881) Phenomenon: When you use DPM Ver6.12, the following problems may occur: (a) When a DHCP server and a Management Server are on the same server and a DHCP server and a DHCP client are not on the same network segment, managed machines fail to get an IP address from the DHCP server. (b) When the Management Server and managed machines are not on the same network segment, managed machines (DPM Client) cannot search the Management Server. As a result, the following phenomena will occur: - Network communication cannot be performed in the DHCP environment. - When the scenario of OS installation by disk duplication is being executed, a parameter file cannot be downloaded to a managed machine and a scenario error occurs. - When you change the IP address of the Management Server, the following phenomena will occur: - An error will occur in the shutdown of managed machines, scenario execution, or automatic update. - OS type of managed machines and patch status cannot be confirmed from the Management Server. - When you install DPM Client on the managed machine, registration of new machine by DPM Client is not performed if you omit to provide the IP address of the Management Server. Problem Explanation: (a) Both DHCP service and DPM service listen the data of DHCP on the same port (67). When the DPM service receives the data first, this phenomenon occurs because the DHCP service cannot receive the data. (b) This phenomenon occurs because the DPM service cannot respond to the DHCP communication from the managed machine. Solution: The following solutions are done: - By this update, the processing which was bound to the port (67) in the DPM service is changed so that it is bound only when there is no DHCP service on the Management Server. - The processing is changed so as to properly respond from the DPM service to managed machines over the network segment. To make this procedure effective, you need to configure the DPM Server so that it can use the port 4011 (UDP) on the Management Server. When a firewall, security software and so on are enabled, open the port 4011 (UDP). (2) DPM Client (Linux) stops after the managed machine is started. (#13770) Phenomenon: When the following conditions are met, the DPM Client (Linux) cannot start normally and ends abnormally. (a) When you install DPM Client newly, you install it without entering the IP address of the Management Server. (b) There is no Management Server on the same network with the DPM Client. Problem Explanation: The problem exists in the DPM Client processing when the IP address of the Management Server is not specified and the DPM Client cannot search the Management Server, which causes this phenomenon. Solution: DPM Client is fixed so that it does not end abnormally even if the DPM Client cannot search the Management Server. 6. 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 [%ProgramFiles%] with [%ProgramFiles(x86)%]. In the DPM Server folder (The default installation folder: %ProgramFiles%\NEC\DeploymentManager\) pxeprs.dll 76,152 bytes 05/14/2013 4:29 PM pxesvc.exe 80,248 bytes 05/14/2013 4:29 PM Source\SHARE\AgentUpgrade\ AgentUpgrade.zip 2,870,611 bytes 05/08/2013 0:58 PM LinuxAgentUpgrade.zip 92,163 bytes 05/08/2013 0:58 PM Source\SHARE\PP\ AgentUpgrade.zip 2,870,611 bytes 05/08/2013 0:58 PM LinuxAgentUpgrade.zip 92,163 bytes 05/08/2013 0:58 PM LinuxMasterSetup.zip 71,366 bytes 04/25/2013 1:47 PM WindowsMasterSetup.zip 1,823,320 bytes 05/08/2013 0:58 PM WindowsMasterSetupVM.zip 1,829,101 bytes 05/08/2013 0:58 PM Source\SHARE\PP\AgentUpgrade\ AgentUpgrade.xml 2,964 bytes 04/26/2013 5:35 PM Source\SHARE\Sysprep\Windows\AMD64\ GetBootServerIP.exe 634,744 bytes 05/08/2013 0:44 PM Source\SHARE\Sysprep\Windows\IA32\ GetBootServerIP.exe 634,744 bytes 05/08/2013 0:44 PM Source\SHARE\Sysprep\Linux\ia32\agent\ dpmversion.inf 84 bytes 04/26/2013 5:35 PM depagtd 150,834 bytes 04/19/2013 0:13 PM GetBootServerIP 52,634 bytes 04/25/2013 10:04 AM Source\SHARE\exports\daemon\redhatall\ia32\ dpmversion.inf 84 bytes 04/26/2013 5:35 PM depagtd 150,834 bytes 04/19/2013 0:13 PM GetBootServerIP 52,634 bytes 04/25/2013 10:04 AM WebServer\App_Data\Config\ Manifest.xml 433 bytes 05/15/2013 8:11 AM In the folder for Image (The default folder: C:\Deploy\) AgentUpgrade\ AgentUpgrade.zip 2,870,611 bytes 05/08/2013 0:58 PM LinuxAgentUpgrade.zip 92,163 bytes 05/08/2013 0:58 PM PP\ AgentUpgrade.zip 2,870,611 bytes 05/08/2013 0:58 PM LinuxAgentUpgrade.zip 92,163 bytes 05/08/2013 0:58 PM LinuxMasterSetup.zip 71,366 bytes 04/25/2013 1:47 PM WindowsMasterSetup.zip 1,823,320 bytes 05/08/2013 0:58 PM WindowsMasterSetupVM.zip 1,829,101 bytes 05/08/2013 0:58 PM PP\AgentUpgrade\ AgentUpgrade.xml 2,964 bytes 04/26/2013 5:35 PM Sysprep\Windows\AMD64\ GetBootServerIP.exe 634,744 bytes 05/08/2013 0:44 PM Sysprep\Windows\IA32\ GetBootServerIP.exe 634,744 bytes 05/08/2013 0:44 PM Sysprep\Linux\ia32\agent\ dpmversion.inf 84 bytes 04/26/2013 5:35 PM depagtd 150,834 bytes 04/19/2013 0:13 PM GetBootServerIP 52,634 bytes 04/25/2013 10:04 AM exports\daemon\redhatall\ia32\ dpmversion.inf 84 bytes 04/26/2013 5:35 PM depagtd 150,834 bytes 04/19/2013 0:13 PM GetBootServerIP 52,634 bytes 04/25/2013 10:04 AM DPM Client (Windows[x86/x64]) installation folder (The default installation folder of x86: C:\WINDOWS\system32\) (The default installation folder of x64: C:\WINDOWS\SysWOW64\) GetBootServerIP.exe 634,744 bytes 05/08/2013 0:44 PM DPM Client (Linux[x86/x64]) installation folder (The default installation folder: /opt/dpmclient/agent) /bin depagtd 150,834 bytes 04/19/2013 0:13 PM GetBootServerIP 52,634 bytes 04/25/2013 10:04 AM /etc dpmversion.inf 84 bytes 04/26/2013 5:35 PM DeploymentManager (TOOLS) Use the modules accordingly seeing [4. Installation Procedure] - in this document. In the folder for the OS installation by disk duplication in the Linux OS Linux\ia32\bin\linuxrep\ depuninst.sh 3,346 bytes 05/03/2012 5:16 PM GetBootServerIP 52,634 bytes 04/25/2013 10:04 AM linuxrep.cfg 4,771 bytes 11/02/2012 5:38 PM LinuxRepClean 31,067 bytes 11/12/2012 10:16 AM LinuxRepSetUp 26,155 bytes 12/10/2012 4:20 PM LinuxSysprep.sh 1,304 bytes 12/07/2012 4:44 PM In the folder for the OS installation by disk duplication in the Windows OS TOOLS\SYSPREP\Windows\ COPYSYSPREP.VBS 38,530 bytes 05/22/2012 5:32 PM TOOLS\SYSPREP\Windows\AMD64\ CHKVITA.exe 91,552 bytes 04/23/2012 5:47 PM deplan.ini 30 bytes 04/21/2011 10:42 AM GETNTVER.EXE 42,392 bytes 11/13/2007 7:15 PM getntver.vbs 13,703 bytes 07/30/2009 9:25 AM GETNTVR2.EXE 93,632 bytes 11/26/2012 2:41 PM GetBootServerIP.exe 634,744 bytes 05/08/2013 0:44 PM SetAdminAccount.exe 84,928 bytes 05/22/2012 5:32 PM svcctrl.exe 560,032 bytes 05/08/2012 10:08 AM Sysprep.inf 501 bytes 10/22/2007 7:48 PM Unattend.xml 3,379 bytes 12/10/2009 3:27 PM winchk 16 bytes 07/09/2008 1:50 PM winftc.exe 140,736 bytes 05/22/2012 5:33 PM $$\blankdir 8 bytes 11/06/2009 1:40 PM $OEM$\CMDLINES.2ND 58 bytes 01/20/2002 4:15 PM $OEM$\CMDLINES.BAT 110 bytes 07/28/2009 1:33 PM $OEM$\CMDLINES.TXT 111 bytes 01/20/2002 2:58 PM $OEM$\CMDLINES_2ND.BAT 59 bytes 07/28/2009 1:33 PM $OEM$\SHELL.REG 140 bytes 03/10/2000 4:12 PM EN\deplan.exe 548,800 bytes 11/26/2012 2:41 PM EN\PROID.EXE 554,400 bytes 04/23/2012 5:48 PM EN\server.ini 149 bytes 05/25/2012 5:22 PM EN\SYSPREP.BAT 11,461 bytes 05/25/2012 5:17 PM EN\$$\blankdir 8 bytes 11/06/2009 1:40 PM EN\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM EN\I386\blankdir 8 bytes 11/06/2009 1:40 PM EN\SYSTEM32\DEPPREP.BAT 10,606 bytes 11/26/2009 1:43 PM ES\$$\blankdir 8 bytes 11/06/2009 1:40 PM ES\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM ES\I386\blankdir 8 bytes 11/06/2009 1:40 PM ES\SYSTEM32\blankdir 8 bytes 11/06/2009 1:40 PM FR\deplan.exe 548,800 bytes 11/26/2012 2:41 PM FR\PROID.EXE 554,400 bytes 04/23/2012 5:48 PM FR\server.ini 149 bytes 05/25/2012 5:22 PM FR\SYSPREP.BAT 11,461 bytes 05/25/2012 5:17 PM FR\$$\blankdir 8 bytes 11/06/2009 1:40 PM FR\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM FR\I386\blankdir 8 bytes 11/06/2009 1:40 PM FR\SYSTEM32\DEPPREP.BAT 10,606 bytes 11/26/2009 1:43 PM I386\blankdir 8 bytes 11/06/2009 1:40 PM JA\deplan.exe 548,800 bytes 11/26/2012 2:41 PM JA\PROID.EXE 227,232 bytes 04/23/2012 5:48 PM JA\server.ini 149 bytes 05/25/2012 5:22 PM JA\SYSPREP.BAT 12,067 bytes 05/25/2012 5:17 PM JA\$$\blankdir 8 bytes 11/06/2009 1:40 PM JA\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM JA\I386\blankdir 8 bytes 11/06/2009 1:40 PM JA\SYSTEM32\DEPPREP.BAT 10,267 bytes 10/19/2011 11:24 AM KO\$$\blankdir 8 bytes 11/06/2009 1:40 PM KO\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM KO\I386\blankdir 8 bytes 11/06/2009 1:40 PM KO\SYSTEM32\blankdir 8 bytes 11/06/2009 1:40 PM SYSTEM32\ALOGON.REG 322 bytes 11/20/2001 10:19 AM SYSTEM32\ALOGON_WIN2008.REG 388 bytes 07/28/2009 1:32 PM SYSTEM32\DEPDELF.REG 360 bytes 07/07/2002 8:45 AM SYSTEM32\dpmnetch.exe 121,280 bytes 11/12/2012 11:08 AM SYSTEM32\GETNTVER.EXE 42,392 bytes 11/13/2007 7:15 PM SYSTEM32\getntver.vbs 13,703 bytes 07/30/2009 9:26 AM SYSTEM32\SLEEP.VBS 12,996 bytes 03/16/2011 2:55 PM SYSTEM32\SMENUSET.VBS 10,887 bytes 03/16/2011 2:55 PM ZH\$$\blankdir 8 bytes 11/06/2009 1:40 PM ZH\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM ZH\I386\blankdir 8 bytes 11/06/2009 1:40 PM ZH\SYSTEM32\blankdir 8 bytes 11/06/2009 1:40 PM TOOLS\SYSPREP\Windows\IA32\ CHKVITA.exe 91,552 bytes 04/23/2012 5:47 PM deplan.ini 30 bytes 04/21/2011 10:42 AM GETNTVER.EXE 42,392 bytes 11/13/2007 7:15 PM getntver.vbs 13,703 bytes 07/30/2009 9:26 AM GETNTVR2.EXE 93,632 bytes 11/26/2012 2:41 PM GetBootServerIP.exe 634,744 bytes 05/08/2013 0:44 PM SetAdminAccount.exe 84,928 bytes 05/22/2012 5:32 PM svcctrl.exe 560,032 bytes 05/08/2012 10:08 AM Sysprep.inf 501 bytes 10/22/2007 7:48 PM Unattend.xml 3,369 bytes 12/10/2009 3:27 PM winchk 16 bytes 07/09/2008 1:50 PM winftc.exe 140,736 bytes 05/22/2012 5:33 PM $$\blankdir 8 bytes 11/06/2009 1:40 PM $OEM$\CMDLINES.2ND 58 bytes 01/20/2002 4:15 PM $OEM$\CMDLINES.BAT 110 bytes 07/28/2009 1:33 PM $OEM$\CMDLINES.TXT 111 bytes 01/20/2002 2:58 PM $OEM$\CMDLINES_2ND.BAT 59 bytes 07/28/2009 1:33 PM $OEM$\SHELL.REG 140 bytes 03/10/2000 4:12 PM EN\deplan.exe 548,800 bytes 11/26/2012 2:41 PM EN\PROID.EXE 554,400 bytes 04/23/2012 5:48 PM EN\server.ini 147 bytes 05/25/2012 5:22 PM EN\SYSPREP.BAT 11,461 bytes 05/25/2012 5:17 PM EN\$$\blankdir 8 bytes 11/06/2009 1:40 PM EN\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM EN\I386\blankdir 8 bytes 11/06/2009 1:40 PM EN\SYSTEM32\DEPPREP.BAT 10,606 bytes 11/26/2009 1:43 PM ES\$$\blankdir 8 bytes 11/06/2009 1:40 PM ES\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM ES\I386\blankdir 8 bytes 11/06/2009 1:40 PM ES\SYSTEM32\blankdir 8 bytes 11/06/2009 1:40 PM FR\deplan.exe 548,800 bytes 11/26/2012 2:41 PM FR\PROID.EXE 554,400 bytes 04/23/2012 5:48 PM FR\server.ini 147 bytes 05/25/2012 5:22 PM FR\SYSPREP.BAT 11,461 bytes 05/25/2012 5:17 PM FR\$$\blankdir 8 bytes 11/06/2009 1:40 PM FR\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM FR\I386\blankdir 8 bytes 11/06/2009 1:40 PM FR\SYSTEM32\DEPPREP.BAT 10,606 bytes 11/26/2009 1:43 PM I386\blankdir 8 bytes 11/06/2009 1:40 PM JA\deplan.exe 548,800 bytes 11/26/2012 2:41 PM JA\PROID.EXE 227,232 bytes 04/23/2012 5:48 PM JA\server.ini 147 bytes 05/25/2012 5:22 PM JA\SYSPREP.BAT 12,067 bytes 05/25/2012 5:17 PM JA\$$\blankdir 8 bytes 11/06/2009 1:40 PM JA\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM JA\I386\blankdir 8 bytes 11/06/2009 1:40 PM JA\SYSTEM32\DEPPREP.BAT 10,267 bytes 10/19/2011 11:24 AM KO\$$\blankdir 8 bytes 11/06/2009 1:40 PM KO\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM KO\I386\blankdir 8 bytes 11/06/2009 1:40 PM KO\SYSTEM32\blankdir 8 bytes 11/06/2009 1:40 PM SYSTEM32\ALOGON.REG 322 bytes 11/20/2001 10:19 AM SYSTEM32\ALOGON_WIN2008.REG 388 bytes 07/28/2009 1:32 PM SYSTEM32\DEPDELF.REG 360 bytes 07/07/2002 8:45 AM SYSTEM32\dpmnetch.exe 121,280 bytes 11/12/2012 11:08 AM SYSTEM32\GETNTVER.EXE 42,392 bytes 11/13/2007 7:15 PM SYSTEM32\getntver.vbs 13,703 bytes 07/30/2009 9:26 AM SYSTEM32\SLEEP.VBS 12,996 bytes 03/16/2011 2:55 PM SYSTEM32\SMENUSET.VBS 10,887 bytes 03/16/2011 2:55 PM ZH\$$\blankdir 8 bytes 11/06/2009 1:40 PM ZH\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM ZH\I386\blankdir 8 bytes 11/06/2009 1:40 PM ZH\SYSTEM32\blankdir 8 bytes 11/06/2009 1:40 PM TOOLS\SYSPREP\Windows\IPF\ CHKVITA.exe 229,272 bytes 07/16/2010 9:03 AM deplan.ini 30 bytes 04/21/2011 10:42 AM GETNTVER.EXE 42,392 bytes 11/13/2007 7:15 PM getntver.vbs 13,703 bytes 07/30/2009 9:26 AM GETNTVR2.EXE 230,296 bytes 08/19/2010 8:32 PM svcctrl.exe 330,648 bytes 08/22/2008 9:50 AM SYSPREP.INF 501 bytes 10/22/2007 7:48 PM Unattend.xml 3,374 bytes 12/10/2009 3:27 PM winchk 16 bytes 07/09/2008 1:50 PM winftc.exe 371,096 bytes 12/03/2007 10:30 AM $$\blankdir 8 bytes 11/06/2009 1:40 PM $OEM$\CMDLINES.2ND 58 bytes 01/20/2002 4:15 PM $OEM$\CMDLINES.BAT 110 bytes 07/28/2009 1:33 PM $OEM$\CMDLINES.TXT 111 bytes 01/20/2002 2:58 PM $OEM$\CMDLINES_2ND.BAT 59 bytes 07/28/2009 1:33 PM $OEM$\SHELL.REG 140 bytes 03/10/2000 4:12 PM EN\deplan.exe 1,955,736 bytes 07/16/2010 9:02 AM EN\PROID.EXE 1,963,416 bytes 07/16/2010 9:02 AM EN\server.ini 137 bytes 09/25/2004 3:30 PM EN\SYSPREP.BAT 11,461 bytes 05/25/2012 5:17 PM EN\$$\blankdir 8 bytes 11/06/2009 1:40 PM EN\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM EN\I386\blankdir 8 bytes 11/06/2009 1:40 PM EN\SYSTEM32\DEPPREP.BAT 10,606 bytes 11/26/2009 1:43 PM ES\$$\blankdir 8 bytes 11/06/2009 1:40 PM ES\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM ES\I386\blankdir 8 bytes 11/06/2009 1:40 PM ES\SYSTEM32\blankdir 8 bytes 11/06/2009 1:40 PM FR\deplan.exe 1,955,736 bytes 07/16/2010 9:02 AM FR\PROID.EXE 1,963,416 bytes 07/16/2010 9:02 AM FR\server.ini 137 bytes 09/25/2004 3:30 PM FR\SYSPREP.BAT 11,461 bytes 05/25/2012 5:17 PM FR\$$\blankdir 8 bytes 11/06/2009 1:40 PM FR\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM FR\I386\blankdir 8 bytes 11/06/2009 1:40 PM FR\SYSTEM32\DEPPREP.BAT 10,606 bytes 11/26/2009 1:43 PM I386\blankdir 8 bytes 11/06/2009 1:40 PM JA\deplan.exe 1,955,736 bytes 07/16/2010 9:02 AM JA\PROID.EXE 1,962,904 bytes 07/16/2010 9:04 AM JA\server.ini 137 bytes 09/25/2004 3:30 PM JA\SYSPREP.BAT 12,067 bytes 05/25/2012 5:17 PM JA\$$\blankdir 8 bytes 11/06/2009 1:40 PM JA\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM JA\I386\blankdir 8 bytes 11/06/2009 1:40 PM JA\SYSTEM32\DEPPREP.BAT 10,267 bytes 10/19/2011 11:24 AM KO\$$\blankdir 8 bytes 11/06/2009 1:40 PM KO\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM KO\I386\blankdir 8 bytes 11/06/2009 1:40 PM KO\SYSTEM32\blankdir 8 bytes 11/06/2009 1:40 PM SYSTEM32\ALOGON.REG 322 bytes 11/20/2001 10:19 AM SYSTEM32\ALOGON_WIN2008.REG 388 bytes 07/28/2009 1:32 PM SYSTEM32\DEPDELF.REG 360 bytes 07/07/2002 8:45 AM SYSTEM32\dpmnetch.exe 329,624 bytes 07/16/2010 9:03 AM SYSTEM32\GETNTVER.EXE 42,392 bytes 11/13/2007 7:15 PM SYSTEM32\getntver.vbs 13,703 bytes 07/30/2009 9:26 AM SYSTEM32\SLEEP.VBS 12,996 bytes 03/16/2011 2:55 PM SYSTEM32\SMENUSET.VBS 10,887 bytes 03/16/2011 2:55 PM ZH\$$\blankdir 8 bytes 11/06/2009 1:40 PM ZH\$OEM$\blankdir 8 bytes 11/06/2009 1:40 PM ZH\I386\blankdir 8 bytes 11/06/2009 1:40 PM ZH\SYSTEM32\blankdir 8 bytes 11/06/2009 1:40 PM TOOLS\SYSPREP\Windows\MESSAGE\ EN\SysprepMsg.txt 999 bytes 03/15/2011 1:09 PM ES\blankdir 8 bytes 11/06/2009 1:40 PM FR\SysprepMsg.txt 999 bytes 03/15/2011 1:09 PM JA\SysprepMsg.txt 913 bytes 02/20/2011 10:06 PM KO\blankdir 8 bytes 11/06/2009 1:40 PM ZH\blankdir 8 bytes 11/06/2009 1:40 PM TOOLS\ExpressSysprep\Windows\ Copy-ExpressSysprep.vbs 42,855 bytes 11/06/2012 8:11 PM Copy-ExpressSysprepVM.vbs 43,911 bytes 11/12/2012 11:08 AM SysprepUtilities\AutologonDel.reg 374 bytes 01/14/2011 4:05 PM SysprepUtilities\CHKVITA.exe 91,552 bytes 04/23/2012 5:47 PM SysprepUtilities\DepConfig.ini 24 bytes 07/14/2010 4:27 PM SysprepUtilities\DepFnChk.EXE 70,048 bytes 04/23/2012 5:47 PM SysprepUtilities\deplan.ini 30 bytes 04/21/2011 10:42 AM SysprepUtilities\dpmnetch.exe 121,280 bytes 11/12/2012 11:08 AM SysprepUtilities\Express-Alogon.reg 444 bytes 05/18/2012 11:17 AM SysprepUtilities\Express-DepDel.reg 376 bytes 02/14/2011 1:28 PM SysprepUtilities\Express-Server.ini 135 bytes 05/25/2012 5:22 PM SysprepUtilities\GETNTVR2.EXE 93,632 bytes 11/26/2012 2:41 PM SysprepUtilities\GetBootServerIP.exe 634,744 bytes 05/08/2013 0:44 PM SysprepUtilities\pwdProcess.exe 84,896 bytes 04/23/2012 5:48 PM SysprepUtilities\REGWRITE.VBS 10,766 bytes 03/16/2011 2:54 PM SysprepUtilities\SetAdminAccount.exe 84,928 bytes 05/22/2012 5:32 PM SysprepUtilities\SETVALUE.VBS 11,982 bytes 03/16/2011 2:54 PM SysprepUtilities\SLEEP.VBS 12,996 bytes 03/16/2011 2:55 PM SysprepUtilities\SMENUSET.VBS 10,887 bytes 03/16/2011 2:55 PM SysprepUtilities\svcctrl.exe 560,032 bytes 05/08/2012 10:08 AM SysprepUtilities\unzip.exe 159,744 bytes 08/20/2010 1:44 PM SysprepUtilities\winchk 16 bytes 07/09/2008 1:50 PM SysprepUtilities\winftc.exe 140,736 bytes 05/22/2012 5:33 PM TOOLS\ExpressSysprep\Windows\SysprepUtilities\EN\ deplan.exe 548,800 bytes 11/26/2012 2:41 PM Express-Depprep.bat 4,997 bytes 11/30/2012 4:25 PM Express-Depprep-VM.bat 5,009 bytes 11/30/2012 4:25 PM Sysprep.bat 3,328 bytes 11/09/2012 2:10 PM TOOLS\ExpressSysprep\Windows\SysprepUtilities\FR\ deplan.exe 548,800 bytes 11/26/2012 2:41 PM Express-Depprep.bat 4,997 bytes 11/30/2012 4:25 PM Express-Depprep-VM.bat 5,009 bytes 11/30/2012 4:25 PM Sysprep.bat 3,328 bytes 11/09/2012 2:10 PM TOOLS\ExpressSysprep\Windows\SysprepUtilities\JA\ deplan.exe 548,800 bytes 11/26/2012 2:41 PM Express-Depprep.bat 4,559 bytes 11/30/2012 4:25 PM Express-Depprep-VM.bat 4,571 bytes 11/30/2012 4:25 PM Sysprep.bat 3,361 bytes 11/09/2012 2:10 PM TOOLS\ExpressSysprep\Windows\SysprepUtilities\MESSAGE\ EN\SysprepMsg.txt 999 bytes 03/15/2011 1:09 PM ES\blankdir 8 bytes 11/06/2009 1:40 PM FR\SysprepMsg.txt 999 bytes 03/15/2011 1:09 PM JA\SysprepMsg.txt 913 bytes 02/20/2011 10:06 PM KO\blankdir 8 bytes 11/06/2009 1:40 PM ZH\blankdir 8 bytes 11/06/2009 1:40 PM 7. 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