Ver 2.00 11/10/97 LOTUS NOTES APPLICATION SET UP ______________________________ This section covers the setup and installation required to run Lotus Notes 4.51 as a public application on a WorkSpace On-Demand client. This setup utilizes a Lotus Notes shared installation that installs a public copy of the workstation software in a file server's shared directory. The access to the shared installation is handled with a redirected drive set up with the WorkSpace On-Demand's public application capability. These directions describe how to work with the WorkSpace On-Demand server and a WorkSpace On-Demand client from each machine class to prepare for a roll-out of WorkSpace On-Demand clients that have Lotus Notes 4.51. Following these directions, when the end-user logs on to any of the WorkSpace On-Demand clients, assuming that they are all the same machine class and have the same communications cards and protocol (NetBios, TCPIP, Ether Net), the end-user sees a Lotus Notes icon on their Desktop. When the end-user double-clicks on that icon, they shall see their Lotus Notes Desktop. Running Lotus Notes involves three servers: the WorkSpace On-Demand server, the Lotus Notes Domino server, and the application server. While it is possible to have all three servers in one computer, the system administrator may use three computers so that each server is located in its own computer. Besides the Lotus Notes Domino server, when a WorkSpace On-Demand client is running Lotus Notes, three sets of files are used. The first set of files are located on the application server and are shared by all the clients using Lotus Notes. The second set of files are the files that follow the user. These files reside on the Domain Controller and are accessed through changes in the User FIT file. The third set of files are acclimated with a particular WorkSpace On-Demand client. These files reside on the WorkSpace On-Demand server and are accessed by changes in the machine FIT file. In this document, when directory structures are given, upper-case text are the exact file structure. Two lower-case strings are used: When ncc_machine_name appears in a directory structure. It is replaced with the name of the WorkSpace On-Demand client. When ncc_user_id appears in a directory structure it is replaced with the name of the WorkSpace user ID. That is the ID used to logon to the WorkSpace On-Demand client. The following instructions cover the installation steps: 1: Install the WorkSpace On-Demand server. This is performed at the WorkSpace On-Demand server. 2: Install your Lotus Notes Domino server. This is performed at the Lotus Notes Domino server. 3: Perform a shared installation to install a public copy of the workstation software in a file server's shared directory. This is performed at the application server. 4: There is an additional step for TCP/IP clients. This is performed at the WorkSpace On-Demand server. 5: Setting up the machine FIT file and creating a remote IPL requester. These are performed at the WorkSpace On-Demand server. 6: Setting up the User FIT file and creating a WorkSpace On-Demand user ID: ncc_user_id. This is performed at the Domain controller. 7: Special setup for the machine and user ID that perform the node install. This is performed at the WorkSpace On-Demand server and the application server. 8: Perform a Lotus Notes node install to use a public copy of the Lotus Notes on a file server. This is performed on the RIPL client. 9: Saving the files created and the and OS2.INI file that was modified by the Lotus Notes node install. This is performed on the WorkSpace On-Demand server. 10: Defining Lotus Notes as a public application. This is performed on the WorkSpace On-Demand server. 11: Lotus Notes invoked for the first time by each user ID. This is performed at the WorkSpace On-Demand client. 12: Creating additional WorkSpace On-Demand user ID's that are using Lotus Notes. This is performed on the WorkSpace On-Demand server. 13: Creating additional WorkSpace On-Demand remote IPL requesters where Lotus Notes may be used. This is performed at the WorkSpace On-Demand server. 1. Install your WorkSpace On Demand server. This is performed at the WorkSpace On-Demand server. Instruction for the installation will not be covered in this document. When you are presented with the Netscape work_item installation selection screen please select REXX. NET START SERVER and NET START RIPL were placed in the a startup.cmd file so that they would be started whenever the server was booted. 2. Install your Lotus Notes Domino server. This is performed at the Lotus Notes Domino server. Work_item: For external publication remove this statement. Here at IBM Austin the Lotus Notes CD-ROM may be accessed with a net use to \\DEPTVKZ\NOTES451. You need to perform a Server installation to put Lotus notes on your server. From the Lotus Notes CD ?:\OS2\INSTALL\INSTPM.EXE As part of this installation you will need to supply a Notes directory and a Notes Data directory. Here are the selections that were made for our server. The '?' will be used in this document to indicate a drive letter that you select. Notes Directory: ?:\NOTES_S Notes Data Directory: ?:\NOTES_S\DATA Here is the tree that was created by our selections. ?:\NOTES_SÂÄDATAÄÄÄÂÄDOC ³ ÃÄDOMINOÄÄICONS ³ ÃÄMAIL ³ ÃÄMODEMS ³ ÀÄOS2 ÃÄDBCS ÀÄVDKHOMEÂÄENGLISH ÃÄLEGACY ÀÄSTYLE Instructions for the installation will not be covered in this document. The name of the server that is supplied at this installation will be needed the first time a particular user logs on the a WorkSpace on Demand client and double clicks on the Lotus Notes icon. Please note that this information is part of setting up files associated with the end users ID and this setup procedure as described latter in these directions may be performed by a single person using one WorkSpace on Demand clients. When creating Lotus Notes user ID's, File -> Tools -> Server Administration -> People -> Register Person -> Other, the ID file may be put on a disk or placed in the address book. It is reconnected that the ID file be placed in the address book. Start the Domino server to ensure that the setup is correct. On our server the Domino server icon was placed in the start up folder so it would be started when the server was booted. 3. Perform a Shared installation to install a public copy of the workstation software in a file server's shared directory. This is performed at the application server. Do not perform this install from a WorkSpace On-Demand client. Stop the Domino Server. Go to the Domino Server full-screen session and type EXIT. From the Lotus Notes CD-ROM drive, type: ?:\OS2\INSTALL\INSTPM.EXE You need to perform a Shared installation to install a public copy of the workstation software in a file server's shared directory. These files will be shared by the the WorkSpace On-Demand clients. If you accept the default update config.sys the contents of config.sys are not changed. There is no need to update config.sys On our server all the components were installed. As part of this installation you will need to supply a Notes directory. Here is the selection that were made for our server. Notes Directory: ?:\NOTES_AC\NOTES_C Here is the tree that was created by our selections. ?:\NOTES_ACÄÄÄÄNOTES_CÂÄDATAÄÄÄÂÄDOC ³ ÃÄMODEMS ³ ÃÄOS2 ³ ÀÄVDKHOMEÄÄENGLISH ÃÄDBCS ÀÄVDKHOMEÂÄENGLISH ÃÄLEGACY ÀÄSTYLE Start the Domino Server. If you compare the structure created installing Lotus notes on the server with the structure created installing shared Lotus Notes to be shared by workstations the structures are similar. No work has been done to determine if the same directory may be used for both the server and the shared installation of Lotus Notes. On our server a notes alias with a path of ?:\NOTES_AC was created for the clients to access the public copy of the workstation software. On the WorkSpace On-Demand server there is a RPLGROUP that will contain all of the WorkSpace On Demand client machine names. The group needs to have read and execute the notes alias. On our server a group, LN_USERS, was also created to contain all the users who would be using Lotus Notes with the WorkSpace On-Demand client machines. This group also needs to have read and execute the Notes alias. 4. Additional step for TCPIP clients. Performed at the WorkSpace On-Demand server. If the Lotus Notes Domino server name is not the same as the TCP/IP name associated with that machine the following step must be performed: If the WorkSpace On-Demand clients will be using Lotus notes with TCP/IP a HOSTS file is required to associate the TCPIP address of the Domino server machine with the network name of the Domino server machine with the Lotus Notes name of the Domino server. Here is a sample host file that contains one line. The first entry is the TCP/IP address of the Domino server machine, the second entry is the network name of the Domino server machine, and the third entry is the Lotus Notes name of the Domino server. 9.3.163.236 d9ualab06.austin.ibm.com LNBVTA The host file is needed for every client. The HOST file should be placed in the location pointed to by the environment variable ETC. In most cases this will be in the MPTN\ECT directory. If a HOST file is put in the ?:\IBMLAN\RPLUSER\BB10.US\MPTN\ETC directory before WorkSpace on Demand clients are created each client when it is created will have a host file. If all clients should not have a host file or if the clients already have been created a host file can be placed in the ?:\IBMLAN\RPLUSER\ncc_machine_name\MPTN\ETC directory. 5. Setting up the machine fit file and creating a Remote IPL Requester. Perform at the WorkSpace On-Demand server. On the WorkSpace On-Demand RIPL server in the ?:\IBMLAN\RPL\FITS there is a file DFBB10US.FIT. This file is the default remote IPL requester FIT file. This FIT file maps the machine dependent files. Assuming that all of our machines will use Z as the boot drive and all machines will use Lotus Notes the following lines should be added at the end of the DFBB10US.FIT file. It is preferred that all non-comment line in FIT files be upper case. The second set of lines are only needed if a node install will be performed from this client. In this example RPLSERVERR needs to be replaced with the name of your WorkSpace On-Demand server. ; Needed to run Lotus Notes 4.51 Z:\NOTES \\RPLSERVERR\WRKFILES\DEFAULT\NOTES ; ; Needed to run the Lotus Notes 4.51 node install Z:\OS2\SYSTEM\EPF* \\RPLSERVERR\WRKFILES\DEFAULT\OS2\SYSTEM Z:\OS2\SYSTEM\$EPFINST \\RPLSERVERR\WRKFILES\DEFAULT\OS2\SYSTEM\$EPFINST Z:\CONFIG.ADD \\RPLSERVERR\WRKFILES\DEFAULT\CONFIG.ADD From the LAN Server Administration panel, double-click on the Local Workstation server_name icon. Double-click on the Remote IPL Requester folder. Create a new requester by dragging a copy of the WorkSpace On-Demand template. The Identity the Machine ID field must be filled in. For this document, assume that our machine ID is ncc_machine_name. After the creation of the remote IPL requester on our server, in the ?:\IBMLAN\RPL\FITS subdirectory there exists a ncc_machine_name.FIT file that contains the following lines. The second set of lines are only needed if a node install will be performed from this client. In this example RPLSERVERR needs to be replaced with the name of your WorkSpace On-Demand server. ; Needed to run Lotus Notes 4.51 Z:\NOTES \\RPLSERVERR\WRKFILES\ncc_machine_name\NOTES ; ; Needed to run the Lotus Notes 4.51 node install Z:\OS2\SYSTEM\EPF* \\RPLSERVERR\WRKFILES\ncc_machine_name\OS2\SYSTEM Z:\OS2\SYSTEM\$EPFINST \\RPLSERVERR\WRKFILES\ncc_machine_name\OS2\SYSTEM\$EPFINST Z:\CONFIG.ADD \\RPLSERVERR\WRKFILES\ncc_machine_name\CONFIG.ADD 6. Setting up the User FIT file and creating creating a WorkSpace On-Demand user ID, ncc_user_id. Perform at Domain controller. On the Domain Controller, there is a BB10USDU.FIT file in the ?:\IBMLAN\DCDB\ directory contains the default User FIT entries. Assuming that all of our machines may be used by Lotus Notes users placing the following lines at the end of the default User FIT file will allow the Lotus Notes user-specific files to be associated with the user. To separate the Lotus Notes files from other files that may have the same name a separate subdirectory should be created to hold the user-specific files for Lotus Notes. In the default User FIT table, the subdirectory's name is UNOTES. For each WorkSpace On-Demand user ID that is created under ?\:IBMLAN\DCDB\USERS\ncc_user_id a UNOTES subdirectory must be created. In the next set of lines that are placed in the default or User FIT file, the '?' character should NOT be changed. When the User FIT file is processed the '?' character is automatically changed to the boot drive letter, is changed to the Domain Controller name and is changed to the user ID name. ?:\NOTES\DATA\CACHE.DSK \\\IBMLAN$\DCDB\USERS\\UNOTES\CACHE.DSK ?:\NOTES\DATA\CLUSTER.NCF \\\IBMLAN$\DCDB\USERS\\UNOTES\CLUSTER.NCF ?:\NOTES\DATA\DESKTOP.DSK \\\IBMLAN$\DCDB\USERS\\UNOTES\DESKTOP.DSK ?:\NOTES\DATA\*.ID \\\IBMLAN$\DCDB\USERS\\UNOTES ?:\NOTES\DATA\JOBSCHED.NJF \\\IBMLAN$\DCDB\USERS\\UNOTES\JOBSCHED.NJF ?:\NOTES\DATA\NAMES.NSF \\\IBMLAN$\DCDB\USERS\\UNOTES\NAMES.NSF ?:\NOTES\DATA\NOTES.INI \\\IBMLAN$\DCDB\USERS\\UNOTES\NOTES.INI ?:\NOTES\DATA\PERNAMES.NTF \\\IBMLAN$\DCDB\USERS\\UNOTES\PERNAMES.NTF ?:\NOTES\DATA\USER.DIC \\\IBMLAN$\DCDB\USERS\\UNOTES\USER.DIC Double-click on the User Account folder and drag a copy of the User ID template to create a new user. Fill in the user ID and password of the user. The user ID should be added to the group of users who will be using Lotus Notes with the WorkSpace On-Demand client machines. If the default User FIT table, BB10USDU.FIT, is not modified for each user must have their own FIT file in the ?:\IBMLAN\DCDB\USERS\ncc_user_id directory. The name of the FIT file will be user_id.FIT . If this FIT table is supposed to be used along with the default user fit table the last line of the fit table needs to be #include BB10USDU.FIT. 7. Special setup for the machine and user ID that will perform the node install. Performed at the WorkSpace On-Demand server and the application server. In the next step a Lotus Notes node install will be performed at one WorkSpace on Demand client from each machine class. The files generated during this install and the OS2.INI file that received additional entries will be saved and then used to replicate the results of the node install to the other WorkSpace On-Demand clients in the same machine class. This eliminated the step of having a person perform the install at each WorkSpace On-Demand client. This is performed at the WorkSpace On-Demand server. To perform the node install the machine that will be used needs to have the following lines in its machines FIT file, ncc_machine_name.FIT. In this example RPLSERVERR needs to be replaced with the name of your WorkSpace On-Demand server. ; Needed to run the Lotus Notes 4.51 node install Z:\OS2\SYSTEM\EPF* \\RPLSERVERR\WRKFILES\ncc_machine_name \OS2\SYSTEM Z:\OS2\SYSTEM\$EPFINST \\RPLSERVERR\WRKFILES\ncc_machine_name\OS2 \SYSTEM\$EPFINST Z:\CONFIG.ADD \\RPLSERVERR\WRKFILES\ncc_machine_name \CONFIG.ADD This is performed at the application server. The person who performs the node install needs to have have read, write and execute access to one file on the shared Lotus Notes workstation software. The Net Access command needs to be performed at the server while the user ID is logged on as an administrator. NET ACCESS ?:\NOTES_AC\NOTES_C\SHARED.PKG /ADD one_user:RWX where ?:\NOTES_AC\NOTES_C\SHARED.PKG is the path to the file on the shared installation that the client will have write access. where one_user is a person who will be performing the performing the next phase of the install. More information on the Net Access command. >>ÄÄNET ACCESSÄÄÄÄresourceÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄ>< ÃÄ/ADDÄÄrightsÄÄÄÄÄÄÄÄÄÄ´ ÃÄ/CHANGEÄÄrightsÄÄÄÄÄÄÄ´ ÀÄ/GRANTÄÄrightsÄÄÄÄÄÄÄÄÙ Parameters resource Names the resource whose permissions you are viewing, modifying, or applying. The resource can be a disk, directory, file, spooler queue, serial device, or named pipe. Resource names that are spooler queues, serial devices, or named pipes must be preceded by \PRINT\, \COMM\, or \PIPE\, respectively. If the /APPLY parameter is specified, the resource must be a directory. /ADD Creates an access control profile with associated permissions for users and groups to the resource specified. You must create an access control profile before you can modify it. If access has previously been given to a resource, use the /GRANT parameter to add more users. /CHANGE Changes the permissions of users or groups for a resource. /GRANT Adds new user names or group names, as well as corresponding permissions, to an existing access control profile. If access has not previously been given to a resource, use the /ADD parameter to add users. 8. Perform a Lotus Notes node install to use a public copy of the Notes on a file server. This is performed on the RIPL client. A Lotus Notes node install will be performed at one WorkSpace On-Demand client from each machine class. The files generated during this install and the OS2.INI file that received additional entries will be saved and then used to replicate the results of the node install to the other WorkSpace On-Demand clients in the same machine class. This eliminated the step of having a person perform the install at each WorkSpace On-Demand client. An application, node Install, needs to be created and associated with the user ID that will be performing the Lotus Notes node install to use a public copy of the Notes on a file server. The command for the application is EPFIDLDS.EXE. The program location is on the server and in our example it is accessed with the notes alias. In our work we accessed the Notes alias as drive X but another drive could be used. The remaining path to the program is \NOTES_C. A working directory should not be specified. If a working directory is not specified the WorkSpace On-Demand application launcher will use the location of the executable as the working directory. Remember to associate this application with the person performing the node installation. When the Note Install public application is run, the selection should be made not to update CONFIG.SYS. If this option is selected the changes will be placed in CONFIG.ADD that is mapped to the section of the file system that follows the machine. Only Notes Data should be selected to be installed on the client. Because our workstation is booting on drive Z here are the selections that were made for our installation. Notes Directory: X:\NOTES_C Notes Data Directory: Z:\NOTES\DATA If you receive the error that CONFIG.SYS is locked, you may have checked to have CONFIG.SYS updated. There is no need to uninstall the file that were installed. Just reinstall selecting not to update CONFIG.SYS. The node install creates a Lotus Notes application folder on the Desktop. This folder will not allow the user to access Lotus Notes applications and should be removed from the Desktop. To remove the Lotus Notes application from the Desktop, go into the Read/Write area on the WorkSpace On-Demand server for this machine, ?:\IBMLAN\RPLUSER\ncc_machine_name\DESKTOP and perform a RD, Remove Directory, on the Lotus Notes application subdirectory under the Desktop directory for this machine. Type: RD "Lotus Application". The quotes are needed because there is a space in the subdirectory name. The Lotus Application folder will not be on the Desktop after the next reboot. If this install is repeated a error popup may be generated concerning the install programs inability to remove the icon in the Lotus Application folder. Proceed with the install. At this point please shut down the WorkSpace On-Demand client and leave it shut down while the following step is performed. This is required to flush the contents of the OS2.INI files back to the server. 9. Saving the files created and the and OS2.INI file that were modified by the Lotus Notes Node install. Performed on the WorkSpace On-Demand server. This step saves the files that were generated or modified by the node install. Saving these files will eliminate the need to perform the node install at each WorkSpace On-Demand client. The previous install created files and modified the OS2.INI file. Some of the files are associated with the user and some files are associated with the machine. By saving the files to another location the files and OS2.INI file entries can be propagated to the WorkSpace on Demand clients that will be supplied to end users. Two REXX programs will be supplied to assist in automating the propagation process but we must first address saving the files. 1: The first set of files we will save are those files that are associated with the user ID. If our example of the user file fit has been followed these files will be located in the ?:\IBMLAN\DCDB\USERS\ncc_user_id\UNOTES directory. The three files that should exist there at this time are DESKTOP.DSK, NOTES.INI and PERNAMES.NTF. These three occupy approximately 0.5 Meg. Additional Information: After executing notes.exe for the first time there will be a up to 9 files that follow the user and these files will occupy approximately 1.8 Meg We copied these files to ?:\SEED_XXX\USER.LN XCOPY ?:\IBMLAN\DCDB\USERS\ncc_user_id\UNOTES\*.* ?:\SEED_XXX\USER.LN 2: The next set of files are associated with the machine. There are located under the ?:\IBMLAN\RPLUSER\ncc_machine_name\NOTES directory. ?:\IBMLAN\RPLUSER\ncc_machine_name\NOTESÄÄÄÄDATAÂÄDOC ÃÄMODEMS ÀÄOS2 We copied these files to ?:\SEED_XXX\MACH.LN XCOPY ?:\IBMLAN\RPLUSER\ncc_machine_name\NOTES\*.* ?:\SEED_XXX\MACH.LN /S /E The node installation places 232 files for a total of approximately 7.5 Meg under the ?:\IBMLAN\RPLUSER\ncc_machine_name\NOTES directory. The Lotus Notes Node install always installs the modem files. If your WorkSpace On Demand clients will not require a modem all of these files in the MODEMS directory may be erased. Erasing the modem files results reduces the number of files associated with each machine to 69 for a total approximately of 7.0 Meg. 3: The next file we need to save is the OS2.INI file associated with the machine. The Lotus notes INI file entries will be extracted from this file and placed in the OS2.INI file of the WorkSpace On Demand clients. The OS2.INI file is located in the ?:\IBMLAN\RPLUSER\ncc_machine_name\OS2 directory. We copied the OS2.INI iles to ?:\SEED_XXX\OS2.LN COPY ?:\IBMLAN\RPLUSER\ncc_machine_name\OS2\OS2.INI ?:\SEED_XXX\OS2.LN If the client is shut down the OS2.INI file should be visible when a dir command is performed. If the client is shut down and the OS2.INI file is not visible the command ATTRIB OS2.INI will show the file and its attributes. The command ATTRIB OS2.INI -R -S -H will turn off the attributes so the file will be visible to a dir and may be copied. 10. Defining Lotus Notes as a public application. Performed on the WorkSpace On-Demand server. A public application to run Lotus notes needs to be be created. The application needs to be associated with all user ID's that will be using Lotus Notes as a public application. The command for the application is NOTES.EXE. The program location is on the application server and in our example it is accessed with the notes alias. In our work we accessed the Notes alias as drive X but another drive could be used. The remaining path to the program is \NOTES_C. A working directory should not be specified. If a working directory is not specified the WorkSpace on Demand application launcher will use the location of the executable as the working directory. Remember to associate this application with the group of Lotus Notes users. Two parameters need to be associated with the Lotus Notes public application. To confirm these setting for your environment look in the config.add file on the machine where the Node install was performed. The third parameter is not required by Lotus notes. The Lotus Notes notes.exe starts another process. When the process is started there will be either a full screen flicker or a brief appearance of a OS/2 window. The third parameter is a WorkSpace on Demand setting that will not be but into the environment but will start the notes.exe with a minimized setting so there will be no full screen flicker or brief appearance of an OS/2 window. The forth parameter is not required by Lotus notes. The Lotus Notes notes.exe starts several other processes then terminates. When notes.exe terminates the application launcher will attempt to disconnect the network resources that were attached for the application. In the Lotus Notes case the network resources are still required for the other processes. The WSOD_LAUNCH_NODROP parameter will signal the application launcher to leave the network resources attached. Parameter settings Name Append Value ÄÄÄÄÄÄÄ ÄÄÄÄÄÄÄ ÄÄÄÄÄÄÄ Libpath Begin X:\NOTES_C Path Begin X:\NOTES_C;Z:\NOTES\DATA; WSOD_LAUNCH_MINIMIZED Begin 1 WSOD_LAUNCH_NODROP Begin 1 11. The first time Lotus Notes is invoked by each user ID. This is performed at the WorkSpace on Demand client. This phase of the Lotus Notes setup invokes Lotus Notes completing the construction of the files that are associated with the user. Using a WorkSpace on Demand client from the same machine class with the same communications card and protocol (NetBios, TCPIP, Ether Net) as the end user, personnel preparing for a roll out involving Lotus Notes may log on to this one WorkSpace on Demand client as one of the end users, double click on the Lotus Notes icon and have Lotus Notes complete the construction of the files that are associated with the user. At this point Lotus data bases and applications may be associated with the the users desktop so they are in place the first time the end user double clicks on the Lotus Notes Icon. When Lotus Notes is invoked for the first time Lotus Notes will bring up a Notes Workstation setup window. A Network connection radio button is selected. Please confirm that is the Network connection that you want. There is a check box if the users Notes user ID was supplied to you in a file. Please check if appropriate. If the Notes user ID was supplied as a file when you are asked if you want your ID file copied to your data directory please select "Yes". When you are asked for the name of the Lotus Notes server that was used fill in the Home Server Name. This is the name of the Lotus Notes server that was used when Lotus notes was installed on the server. 12. Creating additional WorkSpace on Demand user ID's that will be using Lotus Notes. Performed at the WorkSpace on Demand server. This step needs to be performed after the creation of the WorkSpace on user ID. The program LN_USER.CMD supplied in or with this readme will perform the copy command for you. The program LN_USER.CMD has hard coded drive letters and paths. Before using the program please ensure that the drive letters and paths are correct for your environment. Copy the three files, DESKTOP.DSK, NOTES.INI and PERNAMES.NTF, that were saved in the ?:\SEED_XXX\USER.LN directory to ?:\IBMLAN\DCDB\USERS\ncc_user_id\UNOTES. XCOPY ?:\SEED_XXX\USER.LN\*.* ?:\IBMLAN\DCDB\USERS\ncc_user_id\UNOTES 13. Creating additional WorkSpace on Demand Remote IPL Requesters where Lotus Notes may be used. Performed at the WorkSpace on Demand server. This step needs to be performed after the creation of the WorkSpace on Remote IPL Requester. The program LN_MACH.CMD supplied in or with this readme will perform the copy command and the OS2.INI file updates for you. The program LN_MACH.CMD has hard coded drive letters and paths. Before using the program please ensure that the drive letters and paths are correct for your environment. Copy the set of files saved under the ?:\SEED_XXX\MACH.LN directory to ?:\IBMLAN\RPLUSER\ncc_machine_name\NOTES XCOPY ?:\SEED_XXX\MACH.LN\*.* ?:\IBMLAN\RPLUSER\ncc_machine_name\NOTES /S /E An OS2.INI file contains application names. Under application name there are keys and keys are associated with values. The OS2.INI file that was saved in ?:\SEED_XXX\OS2.LN contains entries for an application "Notes". These are four keys under the "Notes" application, "LSXBE", "LSXODBC", "PATH" and "Release". The "Notes" application with its four keys and the values associated with the four keys need to be placed in the OS2.INI file associated with each WorkSpace on Remote IPL Requester that will be used by a Lotus Notes user ID. The OS2.INI files may be manipulated with the OS/2 Prf APIs documented in the Presentation Manager Programming Reference Vol I or with REXX commands. The supplied LN_MACH.CMD program manipulates the OS2.INI file with REXX commands. The location of the OS2.INI file that needs the additional entries is located in the ?:\IBMLAN\RPLUSER\ncc_machine_name\OS2\OS2.INI directory. Trouble If you get into trouble go to Lotus Notes address book on the server and delete the user ID's that have been created. Perform a logoff at the RIPL clients. From the network GUI delete the RIPL machines that were created. Erase the files that Lotus Notes may have created that follow the user. These are the file that were fit mapped: CACHE.DSK CLUSTER.NCF DESKTOP.DSK *.ID JOBSCHED.NJF NAMES.NSF NOTES.INI PERNAMES.NTF USER.DIC. Create new Lotus notes ID's. Create new RIPL machines.