Advanced Windows PE scripting in Ghost Console tasks using Windows PE PreOS to resolve network latency.
There have been network latency issues observed on slower networks with Ghost. These issues can be resolved when booting to a Windows PE boot disk by exiting Ghost, and performing the Release and Renew commands for IPCONFIG, or by editing the START.BAT file at the end of the Ghost Boot Wizard by adding these commands. In the Ghost Console, it is not very clear how to do this. These steps will clarify that:
When Ghost executes a task that requires booting to Windows PE, it executes a file called START.BAT. This file automates the launch of the Ghost client executable, ngctw32.exe. Though not recommended, it is possible to add custom commands to this batch file. Please note that this batch file affects all tasks that run in a specific build of Windows PE. By default, Ghost has two builds of Windows PE, winpe and winpe-512. It is recommended that you make a copy on the Windows PE build and that you edit the START.BAT associated with only your copy.
The location of the START.BAT file is in the directory C:\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template\common\<name of Windows PE build>\ghost. By default, this file is a text file with this text:
if exist start.cmd call start.cmd x: cd \ghost gdisk32 /revert >> x:\ghost\startlog.txt ghost32 /setosdrives /blind >> x:\ghost\startlog.txt if exist setupnet.bat call setupnet.bat start ngctw32 -console
Custom commands should, in most cases, start on the line prior to "start ngctw32 -console". As an example, a DHCP latency issue was once resolved by adding these lines:
To save the file, make sure that you remove the Read Only attribute.
Alternately, there is a modified start.bat file attached to this blog entry; you may download this file, unzip it and save it to the location specified above.