
Date 11/29/1999

Getting StarOffice to work smoothly under WiseManager is a "bit" of a challenge.   We have reduced the process down to a manageable sets of steps.   The bad news is that it still requires a number of steps.   The good news is that the "dirty" works needs to be done only once.

It's best to do the following from the application server and the reference client machine should be a "destroyable" client machine.

----------------------------------------------------------

(A) Install Sun StarOffice 5.1a on the application server (can be the same as the RIPL server)

 1. From an OS/2 command window, issue the command: 

    X: <enter>

       where X is the drive letter for the StarOffice CD.

 2. Next issue the command:

    cd \os2\office51 <enter>

 3. Issue the command: 

    setup /net <enter>

 4. From within the Staroffice setup program, do the following:

    a.  Select custom installation
    b.  Set the destination directory to X:\TVOICE\WiseProg\StarOffice
              (ie. C:\TVoice\WISEPROG\StarOffice) 
              (note: do not use the default directory name of \Office51)
    c.  Besure to include ALL modules that might be needed
              (ALWAYS INCLUDE StarWriter and StarSchedule)

(B) When you're finished with (A), drag and drop StarOffice onto one of your WiseClient machines.   Keep the screen untouched (you will need it in step (D) below) and do the following from that WiseClient machine:

(C) From that reference WiseClient machine:

 a.  If the machine was on before you did the drag and drop, you will need to reboot that machine.
 b.  From that client machine, delete the file SVERSION.INI from the Z:\OS2 directory where Z: is the drive letter for that    machine's boot drive
 c.  From that client machine's desktop, run the desktop icon for StarOffice that was created by WiseManager.   This should bring up Staroffice in client setup mode.

 c.1 You should now be prompted for user data.

      Enter ONLY generic data.   The setup data you entered here will be used by ALL subsequent Staroffice users within your organization.   Any individualized data should be specified using the Staroffice OPTIONS menu later on from each client stations.

 c.2 Use standard workstation install.
 c.3 DO NOT change the default drive letter and path (ie. z:\office51).
 c.4 If you need to use Java with StarOffice it should be detected.
      If Java was not detected, cancel the install and verify that Java is setup properly.

 d. When you are done, you will see a new StarOffice folder on the desktop.   DELETE the StarOffice set up mode ICON   in step c above (not the one just created for you by StarOffice).

 e. Reboot the client machine.   Start up StarOffice using the StarOffice program object inside the Staroffice folder created in the step above.

 f. Now, you should see a "Installation is Incomplete (fonts StarBats and StarMath not found)" message.   Check the "Do not check during startup" and save it.    Shutdown StarOffice.

 g. Start StarOffice again.   You should see some additional messages - again check any "Do not check during startup" options and save them.   Shutdown StarOffice. 

The above 2 steps is necessary in order to supress StarOffice from displaying these very annoying messages to every client on every new installations.

(D) Go back to the application server (step (B) above), execute the "Reference -> Execute" command.   You will prompted for the "Reference" location.    This is what you need to put it:

   x:\tvoice\wisework\staroffice\group\user\soffice.ini

where 

   x is the drive letter for the TVOICE directory
   group is the workgroup for the reference WiseClient machine you worked with in step (C).
   user is the organizational user name (NOT the NETBIOS machine ID) for the reference WiseClient machine you worked with in step (C).

----------------------------------------------------------

(E) From this point on, you should be able to do a simple drag-and-drop deployment of StarOffice on any stations.   You should destroy the reference client machine used in step (C) above.






