WorkSpace On-Demand 2.0 Feature for Windows ... - IBM Redbooks

Note
The Windows NT client image resides on the boot server. If you have
multiple boot servers, copy the client application files to the Windows NT
client image on every boot server, and update the CMDLINES.TXT file and
$$RENAME.TXT file on every boot server.
4.4.3 Updating the Windows NT client image
If the application is a Windows NT application, and you created the
application package on a client running Windows NT, copy the client
application files to the Windows NT client image. Update the CMDLINES.TXT
file to run the RENFILE.BAT file and a script that adds application package
registry information to the client system registry when the operating system is
installed on the client. Complete the following steps:
1. Log on to the boot server as an administrator. If you have HPFS386,
logging on as administrator ensures that the user access controls are
inherited when directories are created.
2. Change to the \IBMLAN\RPL\NT40\I386\$OEM$ directory. Verify that the
$OEM$ directory contains a $WINTEMP subdirectory. If you do not have a
$WINTEMP subdirectory, you must create one. At a command prompt,
type: MD $WINTEMP
3. Change to the \WIN32APP\CLIENT\ appid\C\WINNT
directory. This directory is on the primary domain controller. Compare the
files in the WINNT directory to the files in the
\IBMLAN\RPL\NT40\I386\$OEM$\$WINTEMP directory. If any of the files
are the same, place only the most recent version of the file on the client
image.
Note
You do not need to compare files if you update the client image every
time you create an application package on the sandbox.
4. Copy the contents of the
c:\IBMLAN\DCDB\WIN32APP\CLIENT\appid\C\WINNT directory to the
Windows NT client image at
c:\IBMLAN\RPL\NT40\I386\$OEM$\$WINTEMP.
At a command prompt, type:
XCOPY c:\IBMLAN\DCDB\WIN32APP\CLIENT\appid\C\WINNT\*.*
X:\IBMLAN\RPL\NT40\I386\$OEM$\$WINTEMP/S /E /T /H
106 WorkSpace On-Demand 2.0 Feature for Windows Clients