Running Setup on Client Computers

Now that you have created the administrative installation point, users can connect to that location, run client Setup, and install Office. This section describes the client installation process.

Tip   If you are installing Office in a server­based Windows environment, you need to perform an initial client Setup with write access to the shared Windows folders. For more information, see the topic, "Installing Office in Shared Windows for the First Time" in the Netwrk8.txt file on the Office CD.

The following procedures describe an interactive client Setup, which means the user selects options presented by Setup. Client Setup can also be run in batch mode, in which Setup options are determined by the client Setup script. For information about customizing the client Setup process, see Chapter 6, "Customizing Client Installations."

To start Office Setup on a client computer

1. Connect to the administrative installation point and open the folder containing the main Office application files.
2. Double­click Setup.
3. In the dialog box that appears, enter a user name.

   Setup automatically enters the organization name from the administrative installation point.

4. Click OK to verify the product ID.
5. Enter a name for the destination folder for the main Office files.

   This folder can be on your hard disk or it can be a network drive to which you have read, write, create, and delete permissions. If you run Office from the network, Setup still creates a folder on your hard disk with some user­specific files in it.

After you specify a location for the Office folder, Setup may ask for a destination location for shared applications (depending on the selections made during administrative Setup).

To select a location for shared applications

• To run shared applications over the network, click Server. Setup configures your system to point to the server share.

  – or –

  To install shared applications on your hard disk, click Local Hard Drive, and then enter a folder name. Setup copies shared application files to that folder.

  Next, Setup asks for the installation to use.

To select the type of installation

• To install a predefined set of the commonly used Office components, click Typical.

  – or –

  To select from a list of all the available Office features and components, click Custom.

  – or –

  To leave the main Office program files on the server and run them from the network, click Run from Network Server.

For More Information   about the options included with each installation, see Appendix D, "List of Installed Components."

Custom Installation

If you choose a Custom installation, Setup displays a series of windows with check boxes so you can select which options to install. The first window contains the main Office components:

• Microsoft Office Binder
• Microsoft Excel
• Microsoft Word
• Microsoft PowerPoint
• Microsoft Access (Professional Edition only)
• Microsoft Outlook
• Web Page Authoring (HTML)
• Data Access
• Office Tools
• Converters and Filters
• Getting Results Book

  
  

To view a list of additional options for each of these main options, select the one you want, and then click Change Option. Another window appears, with another set of check boxes. For example, when you select the Microsoft Word option and click Change Option, Setup displays the following list of options for Word:

• Microsoft Word Program Files
• Help
• Wizards and Templates
• Proofing Tools
• Address Book
• Word Mail in Exchange
• Text Converters

Each of these options may have additional options. If so, the Change Option button is available when the option is selected. You can select all or only some of a set of additional components:

• If a check box is selected, all of that option's additional components are selected.
• If a check box is cleared, none of that option's additional components are selected.
• If a check box is grayed, some of that option's additional components are selected. Click Change Option to see what those components are.

The Select All button allows you to select all the options displayed in the active window, along with all their additional components. For some options, you can also change the folder in which the component is installed. If the folder can be changed, the Change Folder button is available.

Note   If you are running Windows NT Workstation 3.51, Setup also asks for the Program Group for the program icons after you have finished selecting installation options.

After you select all the installation options you want, Setup checks for available disk space and begins copying files. If Setup determines that there is not enough disk space for all the options you have selected, you can do one of two things:

• You can specify a different destination folder for some components and install them on another hard disk. However, if you change the folder for every component, Setup still installs some files in the original Office folder you specified.
• You can exit and restart Setup, specifying an Office folder on a different hard disk.

Installing Office from the Office CD

To install Office throughout your organization from the Office CD, you must either purchase a copy of Office 97 for each user in your organization; or (if you have multiple licenses) copy the CD to a server and have users run Setup from there. The procedures in this section describe each scenario.

To install Office from the Office CD

1. Insert the Office CD into the CD­ROM drive.
2. In Windows 95 or Windows NT Workstation 4.0, double­click Setup in Windows Explorer; or click Run on the Start menu and type drive:\setup where drive is the letter of the CD­ROM drive.

   – or –

   In Windows NT Workstation 3.51, double­click Setup in File Manager; or click Run on the Program Manager File menu and type drive:\setup

3. Follow the instructions on the screen.

   If needed, give instructions about running Setup to your users before they install Office. Users can also get help while running Setup by pressing F1 or clicking the Help button.

4. Choose an installation type by clicking Typical, Custom, or Run from CD.

For a complete description of Office Setup and installation options, see "Running Setup on Client Computers" earlier in this chapter.

If you have a large number of users and multiple licenses, you can share the Office CD with a CD­ROM drive located on a network server, or you can copy the files from the CD to the server. Users can then run Setup from the server; Setup functions the same as it does when run from the CD (except that users cannot choose the Run from CD installation).

The advantage of sharing the CD on a server, instead of creating an administrative installation point, is that this method takes less server disk space because the shared files are not duplicated. However, it is less flexible and provides less opportunity for customizing. For information about creating an administrative installation point, see "Installing Office from the Network" earlier in this chapter.

To copy CD contents to a server

1. Create a folder on the server.

   The server must have enough space for the entire contents of the CD. Office Standard Edition for Windows requires about 330 MB; Office Professional Edition, about 630 MB.

2. Copy all the files from the CD to the folder on the server.
3. Make the server available to users.

Users can now connect to the server, open the folder, and run Setup as if they were installing directly from the Office CD.

Installing Office from Floppy Disks

If you are a Select CD customer, you can create a set of Office 97 floppy disks from the Select CD. For more information, see your Select CD documentation.

If you have multiple licenses, you can install Office throughout your organization from floppy disks either by creating multiple sets of disks from your Select CD, or by copying the floppy disks to a server and having users run Setup from there. The procedures in this section describe each scenario.

To install Office from floppy disks

1. Insert Disk 1 into the client computer disk drive.
2. In Windows 95 or Windows NT Workstation 4.0, double­click Setup in Windows Explorer; or click Run on the Start menu and type drive:\setup

   – or –

   In Windows NT Workstation 3.51, double­click Setup in File Manager; or click Run on the Program Manager File menu and type drive:\setup

3. Follow the instructions on the screen.

   If needed, give instructions about running Setup to your users before they install Office. Users can also get help while running Setup by pressing F1 or clicking the Help button.

4. Choose an installation type by clicking Typical or Custom.

For a complete description of Office Setup and installation options, see "Running Setup on Client Computers" earlier in this chapter.

If you have a large number of users and multiple licenses, you can copy the Office disks to a server. Users can then run Setup from the server; Setup functions the same as it does when run from the floppy disks, except that it does not prompt users to insert each disk.

The advantage of copying the floppy disks to a server, rather than creating an administrative installation point, is that this method takes less server disk space, because the files are compressed. However, it is much less flexible and provides little opportunity for customizing. For information about creating an administrative installation point, see "Installing Office from the Network" earlier in this chapter.

Because of the special compressed format of the Office floppy disks, you cannot use the Windows Explorer or MS­DOS® Copy command to copy the files from the floppy disk to a server. Instead, you must use the Extract program included on the Office Setup disk (Disk 1). For more information about Office floppy disks, see "Office Floppy Disks Use a Compressed Format" later in this chapter.

Users can now connect to the server, open the folder, and run Setup as if they were running Setup directly from the floppy disk set. Instead of prompting for each floppy disk, Setup goes to each subfolder on the server to find the next set of files.

Office Floppy Disks Use a Compressed Format With the exception of the Setup disk (Disk 1), Office floppy disks are created in a format that compresses many files into a single cabinet (CAB) file on the disk. By reducing the gap between sectors, Office floppy disks contain up to 1.68 MB of data on a single, high­density 3.5­inch floppy disk. Because the Office floppy disks have a non­standard sector gap, you cannot use standard disk copying and examination utilities, and some low­quality or older disk drives may not read the disk. Disk 1 of the Office floppy disk set is a 1.44 MB read/write disk and can be handled using normal disk utilities. To extract and decompress files from a CAB file, use one of these two programs: Wextra32 runs on Windows 95 and Windows NT Workstation. Extract runs in MS­DOS and is available on Office Disk 1. Type Extract /? to display command­line options. Extract can also be used to copy a complete CAB file from a compressed floppy disk to a local disk or network share. Note that neither Extract nor Wextra32 can put new or changed files back into a CAB file; they only extract files from the CAB file. Both Wextra32 and Extract are available in the Office Resource Kit Tools and Utilities. For more information, see "Tools for Extracting and Copying Files from Office Floppy Disks" in Appendix A, "Microsoft Office Resource Kit Tools and Utilities."

At the same time you deploy Windows through ZAK, you can deploy Office 97 in run-from-server mode. This combination of Windows and desktop application deployment is referred to as AppStation mode. AppStation mode uses a simplified desktop to alleviate distractions. However, a few familiar elements of the Windows desktop are exposed in AppStation mode.

You can centrally control the items that appear on the Programs submenu (Windows Start menu). When a user logs on, the desktop interface contains only the AppStation Start menu, which you simplified to contain only essential items for the user's job, such as the Office applications.

Choosing to deploy Windows and Office through the Zero Administration Kit is a significant commitment to a specific set of network tools and protocols. You need to thoroughly evaluate and test ZAK before you decide where it fits into your Office deployment plans. To assist you in this evaluation, the Office Resource Kit Tools and Utilities include a training course about the Zero Administration Kit; more information about ZAK is available on the Web.

Installing Office

Office supports two distinct installation strategies:

• Run the Microsoft Office Installer program.

  Microsoft Office Installer supports two options: Easy Install and Custom Install.

  This installation option	Contains
  Easy Install	The Excel, PowerPoint, and Word components most Office users are likely to use regularly.
  Custom Install	Whatever Office components you select, except for Value Pack components and the Outlook Express e-mail program.

  Microsoft Office Installer also includes a Remove option, which uninstalls Office 98. For more information, see "Uninstalling Office 98" later in this section.

• Use the Drag-and-drop method to copy the Microsoft Office 98 folder from the Office CD or a network drive to a hard disk.

  Drag-and-drop refers to literally dragging the Microsoft Office 98 folder from the Office CD or a network drive to a hard disk. You can use the drag-and-drop method to copy either the folder that corresponds to an Easy installation, or the folder that corresponds to a Complete installation.

  Drag this folder	For this type of installation
  Microsoft Office 98 at the root of the Office CD	Easy
  Office Custom Install:Microsoft Office 98	Complete

  Drag-and-drop installation requires one additional step to complete the Office installation. The first time any Office application is run, Office copies several required files into the System Folder on the local hard disk. This process is referred to as First Run Installation. First Run Installation may take several minutes to complete, but after it is finished it is not normally required again and thereafter Office applications start more quickly.

  One benefit of First Run Installation is that if Office detects that any required files are missing from the local System Folder, it copies them from the Microsoft Office 98 folder. This gives Office a high level of resiliency; if the user inadvertently removes required Office files from the System Folder, Office replaces the missing files the next time an Office application is started.

  First Run Installation also allows Office 98 to resume working in the event a user performs a Clean System Install when upgrading to a new release of the Mac OS. Other changes to a hard disk, such as changing its name, do not prevent Office from recovering. Moving the entire Microsoft Office 98 folder around on a hard disk likewise does not affect Office. However, you should not alter the folder structure within the Microsoft Office 98 folder.

Office can be installed on a client computer using either of these media:

• Office CD

  This media choice requires a CD-ROM drive, and it requires the installer to be physically present at the client computer.

• Network

  Installing from a network server simplifies the distribution of Office to users. However, it requires a network connection during installation and, if you share Office files over the network, continuous network access while Office is running on the client computer.

Running Office from the Office CD or a Network

Office 98 can be run directly from the Office CD or from a network drive, but with lesser performance than when run locally. When running an Office application from the Office CD or a network drive, the system must preload the application and all shared libraries from the CD or network drive into memory before it can run. What this means for the user is that the application starts very slowly. However, once the application is running, it should perform normally.

When an Office 98 application is initially run directly from the Office CD or from a network drive, First Run Installation copies Office system files to the System Folder, and creates Preference files in the System Folder:Preferences folder. After that's completed, the application starts normally. When the application is subsequently run, First Run Installation is not repeated so start-up time improves.

Customizing Client Installations

The following strategy is recommended for creating customized client installations:

1. Use the Custom Install option in Microsoft Office Installer to create a custom Office installation point on a network drive. Choose the applications and options you want in Microsoft Office Installer.
2. (Optional) Copy the file Microsoft Office 98 from the Office CD to clear the user and organization name on the network installation point.
3. Further customize this installation with your own templates, Value Pack components, and so on as needed.
4. Drag the Microsoft Office 98 folder from the network drive onto local hard disks.
5. (Optional) Start an Office application on the local hard disk to complete the First Run Installation process.

The following sections describe each of these steps in more detail.

Create an Office Network Installation Point

Creating a network installation point requires a Macintosh file server, Windows NT Server, or other type of server properly configured to work with Macintosh client computers.

To create a network installation point for Office

1. Insert the Office CD into the appropriate drive.
2. Open the Office Custom Install folder.
3. Double-click Microsoft Office Installer.
4. Select Custom Install.
5. Choose the specific Office components you want installed.
6. In the Install Location list, select the network drive at the root of which you want to create the customized network installation point.

   – or –

   In the Install Location list, select Select folder and then select the specific folder in which you want to create the customized network installation point, and then click Select.

7. Click Install.
8. Enter the name and organization you want used in all subsequent installations of Office created from this network installation point.

   – or –

   Enter any values you want now; later, you can undo this action so that during subsequent installations of Office from this network installation point the user is prompted for this information.

9. Enter and confirm your 10 digit CD key.

   Microsoft Office Installer then installs the Office components you selected onto the network drive you specified.

If you want to, you can clear the user name and organization information you entered previously for your network installation point. When Office is later installed onto client computers, Office prompts for this information. Skip this step if you do not want users prompted again during Office deployment.

To clear user name and organization information

1. Insert the Microsoft Office CD into the appropriate drive.
2. On the Office CD, open the folder Microsoft Office 98:Office and copy the file Microsoft Office 98 to the folder Microsoft Office 98:Office on the network drive.

Customizing the Office Network Installation Point

You can add your own custom components to the Microsoft Office 98 folder on the network drive. For example, you can add Value Pack components, custom templates, and startup documents.

To customize the Office network installation point

1. On the network drive, open the Microsoft Office 98 folder.

2. Customize Office as needed. Some options include:

   To	Do this
   Add custom templates to Office	Copy your custom templates for Excel, PowerPoint, or Word to one of the folders in the Microsoft Office 98:Templates folder.
   Open a document each time its related application is started	Copy the document to the Excel, PowerPoint, or Word folder in the Microsoft Office 98:Office:Startup folder.
   Add a custom add-in to Excel	Copy your custom add-in to the Microsoft Office 98:Office:Excel Add-ins folder.
   Add an Office Value Pack component to Office	In most cases, you can drag the Value Pack component directly from the Value Pack folder to the network installation point. Some Value Pack components must be copied into the System Folder on the local hard disk. For more information, see "Installing Value Pack Components" later in this section.

These are just a few of the ways you can customize an Office network installation point. After you have finished customizing it, you are ready to roll out Office to the client computers in your organization.

Rolling Out Office to Client Computers

Depending on your network environment and administration tools, there are several strategies you can use to roll out Office to the client computers in your organization:

• Push the Microsoft Office 98 folder to client computers by dragging the folder to each hard disk from a network server. This requires that you have read-write access to the client computer, and File Sharing on each client computer is properly enabled.
• Pull the Microsoft Office 98 folder to client computers by dragging the Microsoft Office 98 folder from the network installation point. This requires that you or the end users initiate the drag-and-drop installation from each client computer.
• Install the Microsoft Office 98 folder to client computers by using a third party Macintosh network management program. For example, many such programs can copy a script to the System Folder:Startup Items folder on a client computer. The script then copies the Microsoft Office 98 folder from the network installation point to the hard disk. Some popular third party Macintosh network management programs include:
  • File Wave Enterprise Edition from Wave Research
  • Net Octopus from Dr. Solomon's Software
  • Microsoft Systems Management Server 1.2 (supports Macintosh client computers running System 7.x only)

Depending on the rollout method you use, you may also want to incorporate First Run Installation into your rollout. This saves end users from spending time waiting for First Run Installation to complete, and may avoid calls to your organization's help desk about slow startup.

Uninstalling Office 98

Microsoft Office Installer can remove Office 98 from a local or network drive, regardless of how Office was initially installed on that drive.

To uninstall Office 98

1. Insert the Microsoft Office CD into the appropriate drive.
2. Open the Office Custom Install folder.
3. Double-click Microsoft Office Installer.
4. Select Remove.
5. In the Install Location list, select the local or network drive that contains the Office installation you want removed.
6. Click Remove.

Microsoft Office Installer does not remove files from the System Folder on the local hard disk, because Microsoft Office Installer cannot determine if such files may be used by other applications. In addition, Microsoft Office Installer does not remove any Value Pack components or other files in the Microsoft Office 98 folder that were not put there by the initial Office installation.

Note   Rather than running Microsoft Office Installer to remove Office, you can delete the Microsoft Office 98 folder by dragging it to the Trash. However, by doing so you also delete any Value Pack components or other files (including data files) stored in the Microsoft Office 98 folder.

Removing Previous Versions of Office Applications

When you install Office 98 by dragging the Microsoft Office 98 folder, Office 98 does not remove files from any previous versions of Office or Office applications from your hard disk. When you run Microsoft Office Installer, the Installer offers to remove installations of previous versions of Office. However, you may not want to remove old Office applications at that time. The Office 98 Remove Old Office Versions application allows you to find and remove most files left behind by previous installations of Office or Office applications (Excel, PowerPoint, or Word). This section describes how to use Remove Old Office Versions and how you can customize its operation.

Note   The information in this section applies to Office for the Macintosh. For information about removing previous versions of Office for Windows, see "Removing Previous Versions of Office" in Chapter 9, "Troubleshooting Installation."

Using Remove Old Office Versions

Remove Old Office Versions helps you find and Remove Old Office Versions that you no longer need on your computer. Remove Old Office Versions can remove components of the following versions of Office applications:

• Microsoft Office 4.2.1a and earlier versions (this includes Excel 5.0, PowerPoint 4.0, and Word 6.0)
• Excel 4.0
• PowerPoint 3.0b
• Word 5.0, 5.1 and 5.1a

To start the Remove Old Office Versions application

1. Insert the Microsoft Office CD into the appropriate drive.

   – or –

   If you copied the Value Pack folder to a network drive, connect to that drive.

2. Open the Value Pack:Administration Tools folder.
3. Double-click Remove Old Office Versions.
4. Select Remove All.

   – or –

   Select Custom Remove, then select the specific applications you want removed.

5. Click the Remove button.

Installing Value Pack Components

The Value Pack components fall into two categories:

• Components that can be dragged from the Value Pack folder onto a local or network drive.
• Components that must be installed to a hard disk using the Value Pack Installer.

  Value Pack Installer does not support installation to a network drive as Microsoft Office Installer does. You can run Value Pack Installer from a network drive to install components onto a hard disk, but you cannot use it to install components onto a network drive.

To install Value Pack components onto a hard disk

1. Insert the Microsoft Office CD into the appropriate drive.

   – or –

   If you copied the Value Pack folder to a network drive, connect to that drive.

2. Open the Value Pack folder.
3. Double-click Value Pack Installer.
4. Choose the specific Value Pack components you want to install.

   – or –

   To install all Value Pack components, click Select All.

5. Click Install.

   Value Pack Installer then installs the components the Microsoft Office 98 folder or System Folder.

You can include Value Pack components in a customized Office network installation point. The following procedure requires you to have previously created a network installation point in a folder named Microsoft Office 98. For information about creating a network installation point, see "Customizing Client Installations" earlier in this chapter.

To install Value Pack components onto a network installation point

1. Insert the Microsoft Office CD into the appropriate drive.

   – or –

   If you copied the Value Pack folder to a network drive, connect to that drive.

2. Open the Value Pack folder.
3. In the Value Pack folder, drag the specific components you want into the appropriate location within the Microsoft Office folder on your network drive.

   Some Value Pack components such as text converters must be copied to a specific folder to function properly. In most cases the Value Pack folder in which these components reside correspond to the Microsoft Office folder name into which they should be copied. For example, the Value Pack:Text Converters folder contains items that should be copied to the Microsoft Office 98:Shared Applications:Text Converters folder.

While most components can be copied directly from the Value Pack folder to the network installation point, a few Value Pack components must be installed to the System Folder on the client hard disk to work properly. Examples of such components include fonts and the Microsoft Office Manager control panel. If these components are copied from a network installation point to a client computer, they do not work properly without additional steps.

Your options for deploying such components include:

• Run Value Pack Installer locally or from a network drive, and install the components you want onto the correct location on the client hard disk.
• Manually copy Value Pack components to the correct location on the client hard disk.

  For example, manually copy fonts from the Value Pack:Fonts folder to the System Folder:Fonts folder on each client computer on which you want the fonts.

• Use a Macintosh network management program to push these components from a network drive to the correct folder on a client hard disk.

  For example, use a third party network management program to push the Microsoft Office Manager control panel from a network location to the System Folder:Control Panels folder on each client hard disk.

In fact, you can use any of these options for deploying any Value Pack component. These options may be the most useful if you decide to deploy a Value Pack component after deploying Office and you don't want to reinstall Office (with Value Pack components added) on your client computers.

Installing Outlook Express and Microsoft Internet Explorer

Microsoft Outlook Express 4.0 for the Macintosh is a new application that builds upon Microsoft Internet Mail and News. Outlook Express allows Macintosh users to communicate with others on the Internet through e-mail and newsgroups. For more information about Outlook Express, see "Intelligent Applications in Microsoft Outlook Express" in Chapter 2, "What's New in Microsoft Office."

The Microsoft Internet folder on the Microsoft Office CD includes Microsoft Internet Explorer 4.0 and Outlook Express. The Microsoft Internet Explorer and Outlook Express installation is not integrated into the Office or Value Pack installation process. Because both Outlook Express and Microsoft Internet Explorer require configuration settings beyond Office, you should deploy both in a separate rollout effort.

For corporate rollouts, the Microsoft Internet Explorer Administration Kit (IEAK) 4.0 enables you to deploy, customize, and maintain Microsoft Internet Explorer and Outlook Express from one central location across multiple computer platforms.

This section describes the product identification method used by Microsoft; explains compliance checking, which verifies that the user has an appropriate older version of Office or competitive product installed before upgrading to Office; and covers the licensing options available from Microsoft.

Product Identification

The product ID for Office is a unique identifier for each license of Office. The complete product ID consists of 20 digits and is handled slightly differently depending on the media used to install Office.

Network

Every installation done from the administrative installation point is given a unique, 20­digit product ID with a common root (the first 15 digits). The complete ID is written into the main Office executable files (Winword.exe, Excel.exe, and so forth) on the user's hard disk.

Office CD

For the Office CD, a portion of the product ID is printed on the CD package; the user running Setup is asked to enter that portion manually during the installation process. The complete ID is written into the main Office executable files (Winword.exe, Excel.exe, and so forth) on the user's hard disk.

Select CD When installing Office from a Select CD (from the Select customer program), the user is not prompted to enter any product ID information. A portion of the ID is stamped on the CD and includes the product code and a Select ID. The remainder of the total product ID is generated at the time the software is installed and is unique for each installation. Multiple client installations of Office from a single Select CD have a common root in the product ID that identifies each installation as coming from the same Select CD.

Floppy Disks

A portion of the product ID is stamped on the floppy disks during manufacturing, and another portion is generated at the time the software is installed. The complete ID is written into the main Office executable files (Winword.exe, Excel.exe, and so forth) on the user's hard disk.

If multiple installations are done from the same set of floppy disks, a different product ID is generated for each installation and is associated with the license for that particular installation. Each product ID consists of a common root (the first 15 digits) that identifies each installation from the same floppy disk set.

When installing from floppy disks, Setup keeps track of the number of installations performed from the same floppy disk set and displays a warning if the legal number is exceeded. Selecting Remove All from Setup does not decrement the installation counter. If you hold multiple licenses, you can use a command­line option for Setup to specify the number of licenses you have. For more information about this option, see Appendix B, "Setup Command-Line Options and File Formats."

Compliance Checking

Office 97 is available as an upgrade for those who have a previous version of Office, or for those who are moving to Office from a competitive product. If you purchase Office 97 as an upgrade, client Setup performs a compliance check to verify that the upgrade is being installed in accordance with the upgrade agreement. It verifies that you have an appropriate older version or competitive product installed before it proceeds.

The verification procedure is performed according to a table defined by Microsoft for each upgrade and may vary for each application, each version, and each language, depending on international competitive markets. The table consists of a list of products and product versions that satisfy the compliance check, along with a signature for each product that defines how Setup detects that the product is installed.

The signature can consist of one or more of the following items:

• Product files, including a file name, size, and folders to search. The signature can indicate whether to search one or more default folders only, or to search the entire disk.
• INI file entries, including an INI file name, key, and value
• Registry entries key and value

At the beginning of the client installation process, Setup searches the client computer for indications that at least one of the products on the list is installed. The first product it finds satisfies the search, and Setup proceeds with the installation. If the table instructs Setup to search the entire disk, Setup displays a message to this effect and lists the products it is looking for.

If no products from the list are found, Setup gives the user a chance to insert the installation floppy disk for a complying product. If the user does not have such a disk, Setup ends and does not install the upgrade. In some cases, the compliance checking table for an upgrade may specify that Setup can continue without finding a compliant product, in which case Setup displays a warning and then continues with the upgrade. This depends on how Microsoft has defined the compliance checking rules for a particular product upgrade.

The following lists the products that Setup searches for when you upgrade to Office 97.

Office Suites

• Microsoft Office for Windows (all versions)
• Microsoft Works for Windows (all versions)
• Borland Office, version 2.0
• Corel WordPerfect Suite 7
• Lotus SmartSuite, version 2.0 or later
• Novell PerfectOffice, version 3.0 or later

Word Processors

• Microsoft Word for MS­DOS, version 2.0 or later
• Microsoft Word for Windows, version 1.0 or later
• Microsoft Word for Windows NT Workstation, version 6.0
• Ami Pro for Windows, version 1.0 or later
• WordPerfect for MS­DOS, version 4.0 or later
• WordPerfect for Windows, version 5.1 or later
• Word Pro 96 Edition for Windows and Windows 95
• WordStar for MS­DOS, version 1.0 or later
• WordStar for Windows, version 1.0 or later
• WordStar 2000 for MS­DOS, version 3.0 or later
• WordStar Pro for MS­DOS, version 1.0 or later

Spreadsheets

• Microsoft Excel for Windows, version 3.0 or later
• Microsoft Excel for Windows NT Workstation, version 5.0
• Microsoft Multiplan®, all versions
• Borland Quattro Pro for MS­DOS, version 1.0 or later
• Borland Quattro Pro for Windows, version 1.0 or later
• Borland Quattro Pro Special Edition, version 1.0
• Lotus 1­2­3 for MS­DOS, release2.01 or later
• Lotus 1­2­3 for Windows, release 1.0 or later
• SuperCalc for MS­DOS, version 3.1 or later

Presentation Graphics

• Microsoft PowerPoint for Windows, version 2.0 or later
• Aldus Persuasion for Windows, version 2.0 or later
• ASAP, version 1.0 or later
• ASAP WordPower, version 1.0 or later
• Harvard Graphics for MS­DOS, version 2.3 or later
• Harvard Graphics for Windows, version 1.0 or later
• Lotus Freelance for MS­DOS, release 4.0
• Lotus Freelance for Windows, release 1.0 or later
• WordPerfect Presentations for MS­DOS, version 2.0
• WordPerfect Presentations for Windows, version 2.0 or later

Databases

• Microsoft Access, version 1.0 or later
• Microsoft FoxPro® for MS­DOS, version 2.0 or later
• Microsoft FoxPro for Windows, version 2.5 or later
• Microsoft Visual FoxPro® for Windows, version 3.0
• Borland dBASE 5.0 for MS­DOS
• Borland dBASE 5.0 for Windows
• Borland dBASE IV for MS­DOS, version 1.0 or later
• Borland Paradox for MS­DOS, version 4.5 or later
• Borland Paradox for Windows, version 1.0 or later
• Claris FileMaker Pro for Windows, version 2.0 or later
• DataEase 5.0 for Windows
• Lotus Approach for Windows, version 1.0 or later
• Personal Oracle7 for Windows
• Superbase versions 1.2, 1.3, 2.0, 4.1.3
• Superbase for Windows 95, version 3.0
• Symantec Q&A for MS­DOS, version 4.0
• Symantec Q&A for Windows, version 4.0

Scheduling

• Microsoft Schedule+, version 7.0

Project Management

• Microsoft Project, version 1.0 or later

Contact Microsoft Product Support for additional help with specific upgrading situations.

Licensing

Every user must have an Office license, no matter how you install Office in your organization. One license is provided with each retail package of Office.

If you do not want to purchase a complete copy of Office for every user, you can purchase a License Pak. Each License Pak allows you to make and use one additional copy of Office. You do not need to store extra copies of Office or the documentation, and it is less expensive than purchasing a retail package. For more information, ask your reseller about licensing options.

You can update Office software without modifying the configuration of your client computers, or you can change the way your client systems are configured. For example, you may want to change whether shared applications are installed on users' hard disks or shared on the network. The following sections describe the steps you follow in either case.

Installing the Office 97 Service Release 1

The Office 97 Service Release 1 (SR­1) is an update to Office 97 suites and applications. Office 97 SR­1 contains all of Office 97 for Windows plus a number of enhancements, including the new Word 6.0/95 Binary Converter for Word 97.

Office 97 SR­1 is distributed by Microsoft in two configurations:

• SR­1 Enterprise Update, available on CD or floppy disks
• SR­1 patch, available on the World Wide Web, on CD, or on floppy disks

The SR­1 Enterprise Update requires a full reinstallation of Office 97, and you install it in the same way that you originally installed Office. The SR­1 patch is designed to upgrade your Office 97 installation in place, by updating only those files that have changed in SR­1. The patch contains the most significant enhancements in SR­1, including the Word 6.0/95 Binary Converter for Word 97 and the Outlook Internet Mail Enhancement Patch.

Use the following criteria to help determine which configuration to use to install Office 97 SR­1.

If you installed Outlook with Exchange Server 5.0, you can update both Office 97 and Outlook 97 to the SR-1 version in one of two ways:

• To update Office and Outlook together, install the SR­1 Enterprise Update.
• To update Office and Outlook separately, install the SR­1 patch to update Office, and then install the Exchange Server 5.0 Service Pack 1 to update Outlook.

In this scenario	Deploy this configuration of SR-1
Office 97 not yet installed	SR­1 Enterprise Update
Office 97 running from network servers	SR­1 Enterprise Update
Office 97 installed locally, but Outlook 97 not installed	SR­1 Patch
Outlook 97 installed locally with Office 97 instead of with Exchange Server 5.0	SR­1 Patch
	World Wide Web   For more information about Office 97 SR-1, including the SR-1 patch, connect to the Office 97 Service Release page at: http://officeupdate.microsoft.com/Articles/sr1fact.htm

World Wide Web   For more information about installing service packs on computers running the Windows NT operating system, connect to the Windows NT Server Technical Support page at: