Is CPS a one-step process?
In many cases it's very close. However, since each customer's installation is unique, you might need to modify the CPS process. The additional steps can include such things as auto logon scripts, MS-Test scripts, batch or command files, custom programs, and so on.
It's best to think of CPS as a "starting point" to your installation process, rather than an "ending point."
Can I profile files with long filenames?
Long filenames are not supported by MS-DOS®. Since the files are copied from the distribution directory to the target computer using an MS-DOS program (WINNTP.EXE), only MS-DOS-based filenames (that is, those using the "8.3" format) are allowed.
As a workaround, you can use files that have 8.3 filenames in the WINNT system directories, and copy only the system directories using CPS. Then, after Windows NT has been installed on the target computer, use the xcopy command to copy the remaining files and directories.
I'm using TCP/IP. How can I assign an IP address during setup?
In the %systemroot%\SYSTEM32 directory there is a file named IPINFO.INF. See that file for information on manually configuring your IP addresses. Each target computer will require a unique IP address in the IPINFO.INF file. CPS will use the information from this file during setup.
If CPS won't transfer my application, service, or program, what should I do?
Some applications do not profile completely. If your installation requires an application that does not transfer correctly from the source to the target computers, the following steps can be taken:
1. Profile the system without the application(s) installed.
2. Install the application, while recording the steps using MS-Test. (MS-Test is a separate Microsoft product.)
3. Install the profiled system on the target computer.
4. Run the MS-Test script to install the application(s).
Why can't I just copy the contents on the hard disk from one computer to another?
Each computer is assigned a unique Security ID (SID) during setup so that it can be identified on the network. Most of the network services have this Security information encoded in their entries in the Registry during setup or subsequent installation. Copying the contents of one hard disk to another would give each computer the same SID, which would compromise security.
CPS works within this system by noting the network services that are installed on the source computer and then removing those entries from the profiled version of the Registry. During setup on the target computer, the target computer's unique SID is created, and then assigned to the network services that were found on the source computer as they are re-installed.
How do I get CPS to profile my network adapter?
If your network adapter card is not listed in the Registry under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft key, then you'll need to modify the CPS.INI file so as to point to the correct key. This is documented in online Help.
How can I use CPS to copy multiple network adapters, or Remote Access Service and a network adapter?
CPS is capable of profiling only a single-network adapter. RAS is configured to look like a network adapter and as such makes the system appear to have two network adapters, only one of which will be profiled and subsequently installed on the target computer.
As a workaround, complete the following steps:
1. Profile the system without the Remote Access Service (RAS) installed.
2. Install RAS, while recording the steps using MS-Test. (MS-Test is a separate Microsoft product.)
3. Install the profiled system on the target computer.
4. Run the MS-Test script to install RAS.
For multiple network adapters, follow the same steps, substituting the additional adapter(s) for RAS.
Why won't CPS copy the user accounts?
CPS only transfers domain accounts found on the source computer. (These are account names that are prefixed with a domain name, in the format DOMAIN\UserName). Local computer accounts are presumed by CPS to be unique to each computer. Also passwords are not copied from one computer to the next, for security reasons.
How can I transfer environment variables via CPS?
CPS does not copy environment variables to the target computer. As a workaround, complete the following steps:
1. Profile the system as usual.
2. Create a script file of the environment variables you want to copy. In the following sample file, lines without equal signs (=) designate a key path or subkey, and subkeys are indented. Lines that include an equal sign indicate a value. Use the value modifiers that appear in the Add Value dialog box in the Registry Editor.
\Registry\USER .DEFAULT Environment NewOne = REG_SZ new string S-1-5-21-2127521184-1604012920-1887927527-9600 Environment NewOne = REG_SZ new string
3. Install the profiled system on the target computer.
4. Use the regini command to change the Registry on the target computer, using the script created in step 2.
For more information on the Registry Editor, see Part IV, "Windows NT Registry," of the Windows NT Resource Guide. For information on regini, see the RKTOOLS Help file.
Can I use CPS to transfer disk shares?
CPS does not transfer disk shares. You'll need to create the shares after using CPS to copy the profile.
Where can I find information about the .INI & .INF files?
The INI file contents are documented in RKTOOLS Help. The INF file contents are described in the Programmer's Guide of the Windows NT Device-Driver Development Kit (DDK) documentation.
How can I get CPS to transfer my personal Program Groups?
CPS profiles only the "common" program groups. If you have personal program groups, load them by using the REGTOGRP and GRPTOREG utilities provided with this resource kit.