Works: Installing Works 4.x to a Network or Shared Folder Part 1

MORE INFORMATION

1. Ask all users who are sharing Windows or Microsoft applications to disconnect from the network file server or shared folder.
2. Start Microsoft Windows 95, and quit any other programs.
3. Insert the Microsoft Works for Windows 95 Setup Disk 1 in your floppy drive.
4. In Windows 95: Click Start, and then click Run.
   
   In Windows NT: On the File menu in Program Manager or File Manager, click Run.
5. Type the following and press ENTER:

   drive:\setup /a

   where drive is the letter of the drive containing the installation disk or CD-ROM.
   
   NOTE: If you are installing Works 4.5 from Works Suite 99, you need to type the following line:
   
   

   drive:\msworks\setup /a

6. Setup prompts for an organization name. When users perform workstation installations from this installation point, the client Setup program asks users only for their name. Setup uses the organization you specify here as their organization.
7. In Setup, check the product identification number.
8. In Setup, specify the folder on the server where you want to install the main program files.
9. In Setup, specify the folder where you want to install shared components. The shared components are accessories that are used with Microsoft Works and can be used by other Windows applications. The shared components included with Microsoft Works are:

   ClipArt Gallery
   System information
   WordArt
   Proofing tools
   Equation Editor
   Graphics filters
   Draw
   Text converters
   Note-It

10. Setup attempts to detect the network path for the shared components folder. This part of the setup allows you to specify how network users can connect to the shared components folder.

    Networks Supporting UNC Paths

    If your network supports the use of UNC paths of the form:

    \\server\share

    you can specify the network location of the shared components using the UNC path. For example, if you are installing shared components to c:\msapps on server SERVER1, and you share that folder as msapps, then specify the following information:

    Network Server: \\SERVER1\msapps
    Network Path: <blank>

    and click the Server Name option to indicate that the shared components folder is accessed using the UNC path.
    
    Or, if you are installing onto c:\Msworks\Msapps and are sharing the c:\MSWORKS folder, specify the following information:

    Network Server: \\SERVER1\MSWORKS
    Network Path: \msapps

    and click the Server Name option to indicate that the shared components folder is accessed using the UNC path.

    Networks Not Supporting UNC Paths

    If your network does not support UNC, you can specify the network location of the shared components using a logical drive letter. For example, if you are installing the shared components onto c:\msapps on the server SERVER1, with the folder shared as "MSAPPS" and, you will always have drive G mapped to the MSAPPS folder on SERVER1, then specify the following information here,

    Network Server: <blank>
    Network Path: <blank>
    Drive: G:

    and click the Drive Letter option to indicate that the shared components folder is accessed using a logical drive letter instead of the UNC path.
11. Setup asks how the shared components are going to be installed by the end user; this determines if the user has the choice of installing the shared components locally or running them off the server. The options are the following:
    • Server: Shared components are run from the server and users do not have a choice during the client installation.
      
      
    • Local hard disk: Shared components are installed on the users hard disk; users do not have a choice during the client installation.
      
      
    • Users choice: Users are asked during the client installation if they want to run the shared components from the server or install them on their hard disk.
    
    
12. Setup checks for available disk space on the server and then copies all the files from the floppy disks to the administrative installation point.
    
    If you are running a shared copy of Windows, some system files are also be copied to the Windows System folders. This allows all workstations that use the shared copy of Windows to have access to the necessary system files.
13. Set the access privileges to Read-only for the server folders where you installed the Microsoft Works components, and make sure all users who may need to install Microsoft Works from the network have read privileges for those folders.