Server & Workstation Installation of Client Profiles for Windows

C ase Manag e m e n t by C l i e n t P rofiles Server & Workstation Installation of Client Profiles for Windows T E C H N O L O G Y F O R T H E B U S I N E S S O F L A W

General Notes to Prepare for Installing Client Profiles for Windows This page does not relate everything that you will need in order to install Client Profiles for Windows. However, it does list a number of things that are very important and which seem to have been overlooked in the past. 1. Is your network operating system Microsoft NT Server? If not, do you have a machine loaded with either Microsoft NT Server (if there are 15 or more network users) or Microsoft NT Workstation to work in conjunction with your Novell network? You must have either Microsoft NT Server or Microsoft NT Workstation somewhere in your network for Client Profiles for Windows to work properly. 2. Is there at least one machine in the office that can connect to the Internet and download files from an FTP site? Upgrades to the Client Profiles for Windows program are posted on an FTP site and it is the client s responsibility to download them. Just having an Internet connection doesn t satisfy the requirement of being able to download from an FTP site. Some Internet services are not capable of doing FTP downloads so you must test this ability on your network. 3. Has the desktop area for monitors on all workstations been adjusted to display in 800 by 600 pixel mode using Small Fonts? Client Profiles for Windows cannot be installed on a workstation with a 640 by 480 pixel resolution. All workstations must be capable of at least 800 by 600 pixel resolution. Video cards for some monitors or even monitors themselves must be replaced if 800 by 600 pixel resolution is not currently possible. 4. Has PCAnywhere been loaded on at least one machine on the network? Have you instructed at least two users on how to set up a machine to receive a call as a host from another PCAnywhere machine dialing in as a remote user? Unless and until a valid modem connection has been established from Custom Micro Systems to the client s office, Client Profiles for Windows cannot be fully supported and training dates will not be confirmed. For a full list of requirements please see the material on the following pages. P:\CPWin\HowTo\Server & Workstation Installation of CPWin.wpd Last Update: 3 October 2000 2000 Client Profiles, Inc. Page 1

Network & Workstation Requirements for Installing Client Profiles for Windows Network Notes: Software Microsoft NT Server 4.0 or; Make sure latest patches are loaded. Service Pack 4 or better is REQUIRED. Small Business Server will work for firms with 10 or less users. Novell NetWare 3.x or Novell NetWare 4.x Must have Novell NetWare version 3.12 or higher or any version of 4.x. Must also incorporate one machine in the overall network which will run either Microsoft NT Server (for 15 users or more) or Microsoft NT Workstation. This machine will act as the database server for Client Profiles for Windows. Hardware Intel processor strongly recommended. Non-Intel processors have repeatedly displayed errors not found with Intel machines. Minimum 200 MHZ processor with 128 MB RAM and 1 Gig free space on hard drive. Faster machines with more memory are always better. See workstation requirements also. Environment A directory named CPShare will be created on the server to which all users must have read/write access. A share to the CPShare directory will also need to be established. We recommend that the share name be set up as CPShare. Detailed steps are set out in this document. If using Novell and Microsoft NT together, user accounts will need to be set up on the NT server which echo user accounts from Novell. Setting up users with the exact same name and password on the NT server as they have in the Novell network will require only one network log on if you set up the workstations to log on to the Windows NT domain when setting up the Microsoft Client on each workstation. P:\CPWin\HowTo\Server & Workstation Installation of CPWin.wpd Last Update: 3 October 2000 2000 Client Profiles, Inc. Page 2

Set up a communication protocol which will be used for the link from the database server to each workstation. TCP/IP is REQUIRED. At least one workstation must be able to connect to the Internet and download files from an FTP site. Specific instructions are given below on the address of the site and the name of the file to be downloaded. A test of this ability is recommended before Client Profiles for Windows is installed. At least one workstation, preferably two, must have PCAnywhere loaded so that remote support can be provided. Having PCAnywhere installed is not useful if none of the network users know how to invoke PCAnywhere and set it up to receive a call. P:\CPWin\HowTo\Server & Workstation Installation of CPWin.wpd Last Update: 3 October 2000 2000 Client Profiles, Inc. Page 3

Workstation Notes: Software Operating System Windows 95, Windows 98, Microsoft NT Workstation or Windows 2000 is required. Word Processing WordPerfect for Windows Version 7 or higher; WordPerfect for Windows is highly recommended for anyone converting from Client Profiles for DOS. or Microsoft Word 97 or newer Either WordPerfect for Windows or Microsoft Word 97 or newer is acceptable for new Client Profiles for Windows users. Hardware Intel processor strongly recommended. Non-Intel processors have repeatedly displayed errors not found with Intel machines. Minimum 200 MHZ processor with 64 MB RAM and 100 MB free space on hard drive. Slower processors with less memory will walk Client Profiles for Windows rather than run it. Monitor and/or video card must be capable of displaying desktop in 800 by 600 pixel mode with Small Fonts. Environment Installation of Client Profiles for Windows will require minor changes to the workstation s environment, specifically, an alteration of its PATH value. Client Profiles for Windows cannot even be installed on a workstation which cannot display 800 by 600 pixels. Logging onto a Novell system often overrides the PATH which was set when the machine booted up. If this happens on your network then you will have to add commands to the system login script which will provide the proper PATH statement to each workstation. P:\CPWin\HowTo\Server & Workstation Installation of CPWin.wpd Last Update: 3 October 2000 2000 Client Profiles, Inc. Page 4

Communication protocol must be properly installed on each workstation. TCP/IP is REQUIRED. If using Novell keep in mind that Novell s Netware Client has demonstrated problems which are not seen when Microsoft s Client for Netware is loaded on each workstation. General Preparation Prior to the Installation of Client Profiles for Windows on Your Network & Workstations Two key items must be addressed which are separate and distinct from the installation of Client Profiles for Windows itself: 1. You must install PCAnywhere for windows on at least one machine in the network. It is usually advisable to install at least one copy PCAnywhere on the machine running Microsoft NT Server or Microsoft NT Workstation so that if dial-in support is needed the support person can examine the database directly. Having PCAnywhere on one other workstation is also a good idea since servers tend to be located in out-of-the-way locations and a telephone may not be available for the user to speak to a support person who may be dialed-in to the network. 2. There must be a machine in the office that can connect to the Internet and download files from an FTP site. Updates to Client Profiles for Windows are posted to the ftp://ftp.clientprofiles.com/ site and clients must be able to download files from this site. A test of this capability is strongly recommended before Client Profiles for Windows is to be introduced to users. Please see step 6 in the Workstation Installation section below for details about exactly where you will find the files to be downloaded. P:\CPWin\HowTo\Server & Workstation Installation of CPWin.wpd Last Update: 3 October 2000 2000 Client Profiles, Inc. Page 5

Step by Step Instructions to Install Client Profiles for Windows on Your Network & Workstations Follow the steps below in order to install Client Profiles for Windows on both your network and all of the workstations in that network. Before following these steps it is recommended that you review the tables above which set out requirements for a successful installation. NOTE: NOTE: In the steps below the computer on which the Client Profiles for Windows database will be loaded will be referred to as the NT server. This may be a computer running Microsoft NT Server 4.0 or Microsoft NT Workstation. In the steps given below capitalization of commands and directory names is not important unless explicitly noted otherwise. Server Installation 1. LOG ON to the NT server USING the ADMINISTRATOR user ID. Use of any other ID may lead to problems with access privileges. COPY the contents of the CPWin folder on your Client Profiles for Windows installation CD to the NT server by FOLLOWING THESE STEPS: a. GO TO the MY COMPUTER icon on the NT server and MOVE TO the drive where you want to install the Client Profiles for Windows database, usually this is the C: or D: drive, and CREATE a new folder called CPShare on that drive. For purposes of this document, we will assume the C: drive was used. b. GO TO the MY COMPUTER icon on the NT server and MOVE TO the CD drive where the installation CD is located. c. DOUBLE-CLICK on the drive so that you can see the CPWin folder which is on the CD. d. RIGHT-CLICK on the CPWin folder and CHOOSE the COPY OPTION. e. On the NT server s C: drive double-click to MOVE INTO the CPShare folder then use the right-click to bring up the paste option and PASTE the contents of the CD to the NT server s CPShare folder. Copying all of the files from the CD may take some time. When you are done you should have CPShare in the root of the C: drive and CPWin as a folder within CPShare. 2. In many cases when files are copied from a CD they will be marked readonly on the NT server. This will cause problems later if this is not P:\CPWin\HowTo\Server & Workstation Installation of CPWin.wpd Last Update: 3 October 2000 2000 Client Profiles, Inc. Page 6

changed. FOLLOW THESE STEPS in order to MARK ALL FILES within the CPWin structure as READ-WRITE: a. GO TO a DOS prompt. b. You will probably be in the C:\WINDOWS directory. TYPE in CD \CPSHARE\CPWIN (without the quotes) and PRESS ENTER. You should now be in the proper directory. IF you copied the CD to a drive other than C:, you must first MOVE TO that drive, e.g by typing in D: and pressing Enter, then use the proper command to MOVE TO the desired directory. c. To make the files read-write, from within the CPWin directory, TYPE in the command attrib *.* -r /s (without the quote marks) and PRESS ENTER. This should remove the read-only attribute from all files in the CPWin directory and any directories below it. d. TYPE in exit and PRESS ENTER to leave the DOS prompt. 3. SET UP A SHARE for the CPShare directory by FOLLOWING THESE STEPS: a. GO TO the MY COMPUTER icon on your desktop and OPEN up the drive where you copied the contents of the installation CD. b. RIGHT CLICK on the CPShare folder. This should bring up a menu including an option for SHARING the folder. CHOOSE this option. c. Click on the button to ENABLE SHARING and for its share name put in CPShare. NOTE: If you are running in a WAN environment, you will need to load Adaptive Server Anywhere software version 6.0.x from Sybase on your NT Server and your workstations. If you are running a WAN, please consult the Server & Workstation Installation of Client Profiles for Windows (WAN Edition) manual for special instructions. You may ignore the rest of this manual. 4. INSTALL the database server software by FOLLOWING THESE STEPS: (For our purposes here, we will assume you have copied the contents of the installation CD to C:\CPShare\CPWin.) a. GO TO the MY COMPUTER icon and OPEN up the C: drive. b. OPEN the CPShare folder, then the CPWin folder, followed by the Install folder, and finally open up the SQLAny50 folder. c. LOCATE the Setup32.Exe icon and DOUBLE-CLICK on it to start the installation process. d. CHOOSE the option to LOAD the Sybase SQL Anywhere Server. DO NOT CHOOSE any option related to the SQL Anywhere Client or the Standalone Engine. e. The next question you see will relate to the version of server software to load. Make sure to PICK THE MICROSOFT NT VERSION, not the Novell version even if you have a Novell network. Your database server will be running from the NT server. P:\CPWin\HowTo\Server & Workstation Installation of CPWin.wpd Last Update: 3 October 2000 2000 Client Profiles, Inc. Page 7

f. CHOOSE the option to INSTALL the software. g. A series of questions will appear. For each one simply TAKE THE DEFAULT ANSWER making sure to check the items noted below. i. When asked where to put the software being loaded, MAKE SURE that it is all being installed either on the C: drive or on the same drive where you copied the CD. ii. When asked whether you want to let the installer make changes to the NT server s environment or make them yourself be sure to LET THE INSTALLER MAKE THE CHANGES. iii. MOST IMPORTANT OF ALL, when asked to select the method of licensing you are using, you MUST SELECT the Per seat license option. If you choose the Concurrent users option you will be asked for a disk containing a key and your installation will fail. When the process is done the installer will suggest that you may wish to RESTART YOUR MACHINE. You should TAKE THIS SUGGESTION. 5. Once the server software is installed, CREATE a new shortcut on your desktop to the database service manager. a. RIGHT-CLICK on the desktop to create a new shortcut. b. BROWSE into the C:\SQLAny50\Win32 directory and LOCATE DBSVMN50.EXE. DOUBLE-CLICK on it when you find it. c. We suggest naming the shortcut SQL Database Service Manager but you can name it anything you like. 6. DOUBLE-CLICK on your new shortcut to START the SQL Anywhere Service Manager. The Client Profiles for Windows database is called a service and you will need to DEFINE THE PARAMETERS for this service by FOLLOWING THE STEPS below: a. CLICK on the New button in the SQL Anywhere Service Manager. b. INDICATE that you want to CREATE a new Network Server. c. PUT CPWin_Server (without the quotes but using the underscores) in the Service Name field. d. In the Startup options area SELECT the Automatic option. P:\CPWin\HowTo\Server & Workstation Installation of CPWin.wpd Last Update: 3 October 2000 2000 Client Profiles, Inc. Page 8

e. In the Parameters area PUT IN something like the following: -ncmsserver -xtcpip -c4m C:\CPShare\CPWin\Windata\Windata.db -nwindata The -ncmsserver gives the database server a name by which workstations will know it. USE ALL CAPITAL LETTERS FOR THE SERVER. -xtcpip tells the service to start with the TCP/IP protocol. Be sure the NT server has been configured with the TCP/IP protocol. A cache memory area of 4 megabytes is reserved by the -c4m statement. We recommend no less than 2 megabytes of cache. Higher values lead to increased speed but if they are too high the service will not start at all. In general, the cache size should be no less than 15% of the overall size of the database. The location of the database file which the server will manage is specified in the C:\CPShare\CPWin\Windata\Windata.db line. You must make sure that you are accurately giving the service the location of this file or it will not start. The database itself is named by the -nwindata parameter. Enter the name of the database exactly as you see it here, capital W and all other letters in lowercase. f. VERIFY the information in the Path for executable area, MAKING SURE that the drive letter is specified correctly. g. Once all the information above has been entered correctly, CLICK on the OK button, then CLICK on the Start button of the SQL Anywhere Service Manager. The server should start within a minute or so. If it does not it will generate error messages that will point you toward an incorrectly entered parameter, missing system element, or having the wrong drive in the Path for executable parameter. Note: Certain screen saver programs running on the server can cause serious degradation of Client Profiles for Windows performance throughout the entire network. The worst screen saver is the 3D Text option which shows three dimensional text tumbling across the screen when it is active. We recommend any screen saver used be one which does not display any movement but rather a static image or no image at all. You have now completed the steps needed to put Client Profiles for Windows on your server. Now you must install software on the workstations. P:\CPWin\HowTo\Server & Workstation Installation of CPWin.wpd Last Update: 3 October 2000 2000 Client Profiles, Inc. Page 9

Workstation Installation The first workstation requires more work than all subsequent workstations. Make sure to follow each step below carefully as getting the first workstation installed correctly will more likely lead to all of the workstations being correctly installed. NOTE: During this process you will be asked to connect to the Internet and download a file from the Client Profiles FTP site. If you do not have an Internet connection this step can be skipped but in the long run you must have an Internet connection in order to receive upgrades of your software. 1. RIGHT-CLICK on a neutral area of your desktop, i.e. one where there is no icon, and SELECT the Properties option. a. Once inside the properties screen, SELECT the Settings tab and ADJUST the Desktop area to display in 800 by 600 pixels (or smaller). Client Profiles for Windows cannot be installed when resolution is set to 640 by 480 pixels. b. VERIFY that the Font size setting is on Small Fonts, then CLICK the OK button. Some machines will make you restart to change these settings. If these changes cannot be made you may have to adjust your drivers, get a new video card, or even a new monitor. 2. GO TO the NETWORK NEIGHBORHOOD icon on your desktop and START it up. If you cannot see your NT server then you have a fundamental network issue to resolve. Contact your network support organization and tell them that the machine on which you have installed the server for Client Profiles for Windows is not visible to the rest of your network and have them resolve this problem. 3. If you can see your NT server, VERIFY that you can see the shared folder that you set up on that machine. When you CLICK on the NT server s icon you should see the CPWin folder inside the CPShare folder. If you cannot, you may have not set up the share to that directory correctly. Go back to your NT server and make sure the share is properly configured. P:\CPWin\HowTo\Server & Workstation Installation of CPWin.wpd Last Update: 3 October 2000 2000 Client Profiles, Inc. Page 10

4. You must MAP a network drive to your shared folder using the following steps: a. With the NT server located in the Network Neighborhood, DOUBLE-CLICK on the NT server and you should see the CPShare shared folder. RIGHT-CLICK on CPShare and then SELECT the Map Network Drive option. You may CHOOSE any letter that has not already been taken but whatever letter it is must be mapped identically by all users, e.g. you can t have some people mapping to the share as P: while others map to it as F:. We prefer that you use P:, F: or G: if possible. Make sure to CHECK THE BOX to reconnect at logon and make sure you remember which letter you chose. Mapping to drive P: is assumed within this document. b. As soon as you map the drive you should see the CPWin folder on that drive. 5. On the drive you have just mapped, GO TO the CPWin\Install\CPClient folder. In that folder you will FIND a file named CP5Ixxxx.Exe where the xxxx will be a three or four-digit number. This is the Client Profiles for Windows Installation program. a. DOUBLE-CLICK on the CP5Ixxxx.Exe icon to begin the workstation installation. b. ALLOW the InstallShield Wizard to get started and SELECT the location where you want Client Profiles for Windows to be installed. We recommend you use the default which is C:\Program Files\CMS\Client Profiles for Windows but you can place the program on any drive in any folder. c. From this point on simply ACCEPT DEFAULT CHOICES as prompted by the installer. When the installation is complete you must RESTART your machine. 6. ESTABLISH a connection to the Internet. (If you cannot connect to the Internet this entire step may be omitted. However, unless you have the ability to connect to the Internet and download updates for Client Profiles for Windows you will not be running on current versions of the program.) a. IF your Internet connection is not on your NT server you should MAP a drive to your NT server using the steps described above. You can map it with the same letter which you used for the workstation above. If your Internet connection is on the NT server then you do not need to map a network drive. b. Once on the Internet, GO TO ftp://ftp.clientprofiles.com/. This is a file transfer site so it isn t as pretty as most places you go on the web but it serves a very important purpose. c. Once at the site CLICK ON the Pub folder, then the Windows folder, and finally the Upgrade folder. Within this folder you will FIND a P:\CPWin\HowTo\Server & Workstation Installation of CPWin.wpd Last Update: 3 October 2000 2000 Client Profiles, Inc. Page 11

file named CP5Ixxxx.Exe where xxxx is a three or four-digit number representing the latest revision of Client Profiles for Windows. This is a self-extracting zip file which you must download in order to make sure you have the most recent version of the software. d. DOWNLOAD the CP5Ixxxx.Exe file. Different browsers will accomplish this task in different ways. With some browsers you will have to right-click on the file then use whichever option allows you to grab the file, e.g. Save Link As. We recommend saving the file to the CPWin\Xfer directory on your NT server. If your Internet connection is on the NT server you will see this location as CPShare\CPWin\Xfer. If you had to map a drive to the NT server you will find the location on the mapped drive as CPWin\Xfer because the CPShare directory will not be visible. e. Once the file is downloaded GO TO the CPWin\Upgrade folder on your NT server and DELETE all files located there. f. EXTRACT the CP5Ixxxx.Exe file into the Upgrade directory. i. DOUBLE-CLICK on the CP5Ixxxx.Exe file to begin the extraction process. ii. You will need to INDICATE A DESTINATION in the Extract to field. CHOOSE P:\CPWin\Upgrade, then PRESS the Extract button. If you are asked to confirm replacement of existing files, click on the Yes to All button. 7. Ever since restarting your workstation after running the installer program, you should SEE a new icon on the desktop for Client Profiles for Windows. DOUBLE-CLICK on this icon to start the program. (You may want to refer to the Getting Started Guide which provides amplified details on preparing Client Profiles for Windows for its first use.) a. You will be asked for a User ID and Password. USE Admin (without the quotes) for both the User ID and Password. b. You will see a message saying that Client Profiles for Windows can t access a particular network path. PRESS and hold the CTRL button and CLICK on the OK button which appears in the message area to get past it. If you don t use Ctrl-OK you won t be able to do the next few steps. c. Once in the program, GO TO the Administration menu along the top row and CHOOSE the System Setup option. d. Within the System Setup area CHOOSE the File Locations icon. CHANGE the value of the Program Upgrade Path field to an appropriate value for your system. (You can change other values too but the Program Upgrade Path must be changed before any other workstations are installed.) If you mapped to the P: drive then the proper value for the Program Upgrade Path would be P:\CPWin\HowTo\Server & Workstation Installation of CPWin.wpd Last Update: 3 October 2000 2000 Client Profiles, Inc. Page 12

P:\CPWin\Upgrade\. Note that CPShare should not appear within any of the File Location values. e. CLICK on the OK button to save your changes then exit Client Profiles entirely. 8. ALLOW the workstation a moment to completely close all files used by Client Profiles for Windows then RESTART the program using the Admin User ID and Password. a. IF you downloaded an updated version of Client Profiles for Windows from the Internet you will be told that a SYNCHRONIZATION PROCESS is about to run. This is because the Client Profiles for Windows program will always go out and check the Upgrade directory to see if it has files that are newer than what is installed on the workstation itself. If so, the new files are copied. b. After the copying is done START up the program using the Admin User ID and Password. This time you should not see any copying activity but you may see messages indicating that the database is being examined and updated. The Admin user (or a user with administrative rights) must always be the first user into Client Profiles for Windows after a new version has been put into the Upgrade directory. At this point you have successfully loaded the server software required by Client Profiles for Windows and you have one workstation running the program. The program must be loaded on all workstations where Client Profiles for Windows will be used. Please refer to the last page of this document for an abbreviated set of instructions on how to quickly install Client Profiles for Windows on all other workstations. Setting Up the Backup Process Which Will Allow a Copy of Windata.DB to be Made Which can be Copied to a Backup Tape It is very important that the Client Profiles for Windows programs database, Windata.db, be backed up on tape to preserve its contents should the system ever experience a hard drive crash. On most systems once the database service which manages Windata.db is started it will be allowed to run continuously. Since this is true, some tape backup software won t be able to make a copy of the Windata.db file. To alleviate this problem, and also to make sure the Windata.Log file,which records changes made to the database, does not get too large, take the following steps to set up a process P:\CPWin\HowTo\Server & Workstation Installation of CPWin.wpd Last Update: 3 October 2000 2000 Client Profiles, Inc. Page 13

which will both make a copy of Windata.db which can be copied to tape and will also keep the Windata.Log file from growing too large. 1. GO to the NT server and MAKE SURE that the scheduling service has been turned on and that it is set to start automatically. a. CLICK on the Start button, then CHOOSE Settings, followed by Control Panel. In the window which will appear LOCATE and DOUBLE-CLICK on the Services icon. b. MOVE DOWN the list of services until you SEE one named Task Scheduler. ADJUST its startup parameter to be automatic and, if the schedule service is not already running, START IT up. 2. MARK the C:\CPShare\CPWin\Windata\Backup directory so that it is not a Read-Only directory. a. USE the My Computer icon on the NT server to go to the C:\CPShare\CPWin\Windata directory. b. RIGHT-CLICK on the Backup folder and CHOOSE the Properties option. MAKE SURE the Read-Only attribute is not marked, then EXIT the properties area. 3. GO to the C:\CPShare\CPWin\Windata\Backup directory and EDIT the BackupDB.CMD file you will find there. a. MOVE DOWN in the file to a line which reads SET DRIVE=C:. MAKE SURE the letter for the drive on your system corresponds to where the Windata.db file is actually stored on the NT server, i.e. change C: to D: if you put your copy of Windata.db on the D: drive. b. MOVE DOWN again in the file until you see a line which reads SET SQLDIR=C:\SQLAny50\Win32". MAKE SURE that this refers to the location where you put the server software for the Sybase program. c. IF you have chosen not to take the default values suggested in this document for names of directories, MOVE DOWN in the file until you see SET DATADIR=%DRIVE%\CPShare\CPWin\Windata and CHANGE it to correspond to whatever location you may have chosen to put the basic Client Profiles for Windows files. AFTER all the changes suggested above are complete, SAVE the BackupDB.CMD file and exit it. 4. From the C:\CPShare\CPWin\Windata\Backup directory TYPE in the command BackupDB and PRESS Enter. a. You should SEE a process start up which will make a copy of Windata.db which can be copied to a tape. The process should take no more than 2 or 3 minutes to run. b. IF the process does not run properly DO the following: P:\CPWin\HowTo\Server & Workstation Installation of CPWin.wpd Last Update: 3 October 2000 2000 Client Profiles, Inc. Page 14

i. BACK UP to the C:\CPShare\CPWin\Windata directory and CREATE a new directory called B2. ii. COPY the BackupDB.CMD file from the Backup directory to the B2 directory. iii. DELETE the entire Backup directory. iv. RENAME the B2 directory to Backup. v. GO to C:\CPShare\CPWin\Windata\Backup and TYPE in BackupDB again and PRESS Enter. IF the process does not run this time LOOK inside BackupDB.CMD again and MAKE SURE you have made all the appropriate changes suggested above, then TRY running BackupDB again. IF it still does not work CALL Custom Micro Systems for support. 5. GO to a DOS prompt and TYPE in AT. If you had to start the Task Scheduler service you will probably see that no entries are in the list. If you did not have to start the service you may or may not see entries. a. TYPE in the following command, MAKING ADJUSTMENTS for the actual location of the BackupDB.CMD file on your system. You should also ADJUST the time if you know that the tape backup is going to be running close to 10:00 p.m. If the command line spills into multiple lines just keep typing. at 22:00 /interactive /every:m,t,w,th,f C:\CPShare\CPWin\Windata\Backup\BackupDB.CMD b. PRESS the Enter key when done typing the command, then TYPE AT again. The system should report that the BackupDB.CMD file is set to run each business evening at 10:00 p.m. The Task Scheduler service will run the BackupDB.CMD file each day at this time so that you can have your tape backup come in at a slightly later time and make a copy of the Windata.db and Windata.Log files. These files would be critical if the hard drive on the server ever failed. P:\CPWin\HowTo\Server & Workstation Installation of CPWin.wpd Last Update: 3 October 2000 2000 Client Profiles, Inc. Page 15

The steps below describe what is needed to load the program on all the remaining workstations. These steps are a subset of what was presented above and are given using slightly less detail than was originally given. If you forget how to do something, refer to the instructions for setting up the first workstation. Repeat the steps below for all workstations. (The information on this page has been set up to be contained on exactly one page so that it can easily be copied and carried around to workstations as a reference.) 1. ADJUST the workstation display to 800 by 600 pixels with Small Fonts. 2. MAP a drive to the CPShare shared folder, making sure to use the same drive name, e.g. P:, for all users 3. GO TO the CPWin\Install\CPClient folder and run the CP5Ixxxx.Exe installation program. a. MAKE SURE the TCP/IP protocol is loaded and properly configured on the workstation. b. RESTART the workstation after the installation finishes. 4. After the workstation restarts, DOUBLE-CLICK on the Client Profiles for Windows icon and go into the program as the Admin user. a. If you copied files from the Internet to your CPWin\Upgrade directory then you will see files being copied the first time you start the program. After the copying is done, start the program. b. If Client Profiles for Windows does not start, check the following items first: i. Is the workstation configured with the TCP/IP protocol? Check properties in the Network Neighborhood to answer this question. ii. Does the PATH value for the workstation include the value C:\SQLANY50\WIN32"? Check this by going to a DOS prompt and typing in SET then pressing Enter. A number of variables will appear. If C:\SQLANY50\Win32" appears anywhere within the PATH variables value then this is not the problem. However, if no reference to C:\SQLANY50\WIN32" is found you may have to make an adjustment to the network s system login script in order to set that value on the workstation. iii. Go to the Network Neighborhood and see if the NT server is visible. If it is not then the workstation s connection to the network may not be stable. Check the network card and cabling. P:\CPWin\HowTo\Server & Workstation Installation of CPWin.wpd Last Update: 3 October 2000 2000 Client Profiles, Inc. Page 16