| C H A P T E R 4 | Part 2 Deploying Microsoft Office | Microsoft Office Resource Kit |
| Installing Microsoft Office |
|
|
This chapter describes the basic installation for Microsoft Office 97 for Windows and Office 98 for the Macintosh. Because there is considerable flexibility in the installation process, the chapter begins with the planning phase and installation options, and then describes the specific procedures for installing Office. It concludes with a summary of licensing requirements and instructions for installing Office upgrades.
|
Running Windows and the Office applications locally is generally faster than running them over the network.
Sharing files on a server reduces the amount of disk space needed on client computers, but it increases the need for disk space on the server.
Files on a server can be maintained and updated more easily than files on client computers.
Programs installed locally are always available to users, while programs run from a server are not available when the network is offline.
Office program files can also be shared between the server and client computers, or between the hard disk and the Office CD, providing even more options for distributing disk space and managing the files.
Local or Shared Windows Installation
If Windows is installed locally, all Windows files remain on the client hard disk. When Windows is run from a network server, however, you can put most Windows files on the server, leaving only userspecific data files on the hard disk.
Office can be installed in either environment. Some files included with Office are systemlevel files; Setup installs them in the Windows folders. If Office is installed in a shared Windows environment, those systemlevel files are installed on the Windows server, and the space required by Office on the local hard disk is reduced, even if Office itself is installed locally.
Whether Windows is local or shared affects the amount of disk space available for Office, as well as the overall performance of the client computer. It also affects maintenance and support: Windows is easier to manage when it is installed once on a server, rather than separately on each client computer.
For More Information about Windows installation, see the Microsoft Windows 95 Resource Kit or the Microsoft Windows NT Server 4.0 Resource Kit and Microsoft Windows NT Workstation 4.0 Resource Kit. For more information about these and other Microsoft Press books, see "Microsoft Press Titles" in Appendix E, "Other Support Resources."
 | Tip In Windows 95 and Windows NT Workstation version 4.0, you can use a system policy to configure client computers from a network location, even if Windows is installed locally. For more information, see Chapter 7, "Customizing and Optimizing Microsoft Office." |
A Typical installation installs a predefined set of the most commonly used Office features.
A Custom installation lets you select from a list of all available Office features and components.
When you install Office from the CD, you can choose to leave some Office files on the CD and run them directly from there, rather than copy them to your hard disk.
When you install Office from a network server, you can choose to leave most Office files on the server, where multiple users can share them.
 | Tools and Utilities The Office Resource Kit Tools and Utilities include tools for creating a customized Setup script in which you define the features to be installed on the client computer. Setup is run in batch mode using this script, with no interaction by the user, and the components are installed as you define them. For more information, see Chapter 6, "Customizing Client Installations." |
Installing from a network server simplifies the distribution of Office to users, and it provides additional options for sharing files. But this choice requires a network connection during installation and, if you share Office files over the network, continuous network access while Office is running.
This media choice requires a CDROM drive, and it requires the installer to be physically present at the client computer.
If you are a Select CD customer, you can create Office 97 floppy disks from the Select CD for users who can not use the Office CD and who do not have network access.
Select the Installation Method
After you choose the client configuration, there are three methods that you can use to install Office:
Users run Setup themselves choosing the installation options they want. If Office is installed from the Office CD or floppy disks, this is the only method that can be used.
You create a customized Setup script that predefines all installation options for the user. When Setup is run using the script, installation occurs with minimal user interaction.
A push installation is run automatically on a client computer with no user intervention. You can do this by editing the logon script to launch the installation process when the user logs on to the network. Or you can use a tool such as Systems Management Server to perform the installation on remote computers.
| |
Note To install or update Office on a Windows NT Workstation client computer using the Windows NT File System (NTFS), you must have administrator privileges on the client computer. |
| | Tools and Utilities The Office Resource Kit Tools and Utilities include information about how to use and customize the default messaging profile used by Outlook and emailenabled Office applications. For more information, see "Outlook 97 Profiles" in Appendix A, "Microsoft Office Resource Kit Tools and Utilities." |
|
These methods of installing Office are described in the following sections.
Installing Office from the Network
To install Office throughout your organization from a network server, you must have an Office 97 user license for each user in your organization. A network installation involves this twostep process:
Creating an administrative installation point involves more than copying files from the Office CD to a server. Some or all of the Office program files can be shared from the administrative installation point. Shared Office applications, such as Clip Gallery, can be installed in a separate folder or even on a different server to allow for more flexibility in sharing Office components.
Tip You can modify the administrative installation point to control the way users install Office. For more information about customizing an administrative installation point, see Chapter 6, "Customizing Client Installations."
You use Setup to create the administrative installation point, and your users use the same Setup program to install Office; however, Setup runs in a different way for each of these tasks. In the following sections, these two Setup modes are referred to as follows:
Creating the Administrative Installation Point
To create the administrative installation point, first select the server and prepare it, making sure that there is enough disk space and that there are no viruses. Then install the Office program files on the server.
The administrative installation point contains two folders:
This folder contains the Office Setup program (Setup.exe) as well as folders containing all the Office program files. The default folder name is MSOffice.
This folder contains other program files used by more than one Office application. The default folder name is MSAPPS. The shared applications include the following: the spelling checker, WordArt, Microsoft Organization Chart, Microsoft Graph 5.0, Microsoft System Information, Microsoft Clip Gallery 3.0, graphics filters, text converters, and Excel sheet converters.
When you perform an administrative installation, Setup asks where you want these folders copied. Store them on a server so that users have access to them. You can store them on the same server or on two different servers. Later, when a user installs Office, Setup looks for the shared files at this location on the server.
The steps required to prepare the administrative installation point on the server are described in the following table.
| Task | Description |
| Make sure that there is sufficient disk space. | Office Standard needs about 280 MB for the administrative installation; Office Professional needs about 325 MB. |
| Make sure you have access to the folders. | You need read, write, delete, and create permissions to complete the administrative installation. |
| Make sure that all Office folders are empty. | If a previous version of Office exists, move any custom templates you want to save to another location, and then delete the Office files. |
| Make sure all users are logged off, and prevent network user access to the folders during the administrative installation. | You also must prevent access by users sharing applications or running shared Windows from this server. |
| Disable virus detection software. | This prevents erroneous virus detection triggers as Setup writes into various executable files. |
| Make sure the server is running the correct version of Windows. | To run Setup, you need Windows 95, Windows NT Workstation version 3.51 or later, or Windows NT Server version 3.51 or later. |
| Create and share the folder that contains the administrative installation point. | The shared folder will contain the folders created when you run administrative Setup. You can share this folder before or after running administrative Setup. |
| Set the appropriate permissions for the shared folder that contains the administrative installation point, and for the folders created by running administrative Setup. | Perform this task after running administrative Setup. For more information, see "Sharing and Security Permissions" later in this chapter. |
| | Tools and Utilities The Office Resource Kit Tools and Utilities include the file Top10.doc. This document describes how to prepare the server and client computers for installing Office in more detail. See "Microsoft Technical Support Documents" in Appendix A, "Microsoft Office Resource Kit Tools and Utilities." |
– or –
To install shared applications on each user's hard disk, click Local Hard Drive.
– or –
To allow users to choose where to install shared applications during client Setup, click User's Choice.
Setup checks for available disk space on the server and then copies all the Office files from the Office CD to the administrative installation point. Users can now run client Setup from this administrative installation point and install Office on their computers, based on the options you select while setting up the administrative installation point.
This level of customizing is sufficient for many installations, but there are additional elements of the client installation process that you can customize. For a description of all the ways you can modify the administrative installation point, see Chapter 6, "Customizing Client Installations."
Sharing and Security Permissions
After you run administrative Setup, you need to set the appropriate permissions for the shared folder that contains the administrative installation point, and for the folders created by running administrative Setup.
On Windows NT Server, there are two kinds of permissions: sharing permissions and security permissions. Sharing permissions determine the access available to users in folders shared across the network. This is the only file-system security available for drives formatted with the FAT file system. Security permissions provide additional control for folders and files, but security permissions are available only for folders and files on drives formatted with the NTFS file system.
Sharing permissions also determine the maximum level of security permissions available to users when they open folders and files within the shared folder. For example, if you set sharing permissions for a shared folder to Read, and then set security permissions for a folder within the shared folder to Add & Read, users accessing the contained folder from the shared folder are still restricted to Read permissions. The Add & Read permissions setting for the contained folder applies only to users who log on to the server directly (not through the network).
If you want network users to have Add & Read security permissions for the contained folder, you must set permissions for the shared folder to Add & Read or higher. Setting less restrictive sharing permissions does not override more restrictive security permissions set for folders and files contained in shared folders.
For More Information about Windows NT Server file and folder permissions, see the Windows NT Server manual, Windows NT Server Concepts and Planning, available in the Online Books folder of your Windows NT installation directory.
The interaction between sharing permissions and security permissions does not affect users of Office Standard Edition, or users of Office Professional Edition who do not choose the Run from Network Server installation. In these cases, setting both sharing and security permissions to Read is sufficient for all users.
However, for users of Office Professional Edition who choose the Run from Network Server installation, you must set appropriate sharing and security permissions: For example, Access users need Change permissions (the set of read, write, execute, and delete permissions) for the Workdir folder to run Access wizards from the server.
The following procedures describe how to set permissions for networks running Windows NT Server. If you are using another network operating system, set read-only permissions for all folders and files created when you run administrative Setup for users of Office Standard Edition, or for users of Office Professional Edition who do not choose the Run from Network Server installation. For users of Office Professional Edition who choose the Run from Network Server installation, you must set permissions for the Workdir folder so that users can read, write, and create files in that folder.
To set sharing permissions for the folder that contains the administrative installation point
– or –
In Windows NT Server 3.51, select the folder, click Share As on the File Manager Disk menu, and then click the Permissions button.
– or –
For users of Office Professional Edition who choose the Run from Network Server installation, set Change permissions for the Everyone group (or for the groups that use Access).
You must also set security permissions for the folders that are created within the shared folder when you run administrative Setup.
To set security permissions for the folders created when you run administrative Setup
– or –
In Windows NT Server 3.51, select the MSOffice folder, and then click Permissions on the File Manager Security menu. (The Permissions command is available only if the folders are located on an NTFS volume.)
| | Tools and Utilities Users can encounter sharing conflicts when running Access wizards from a network server. To avoid this problem without setting Change permissions in the Workdir folder, you can modify the STF file so that Access wizard files are copied to users’ hard disks. The Office Resource Kit Tools and Utilities include the file AcWizard.doc that describes how to modify the STF file in this way. See "Advanced Documentation" in Appendix A, "Microsoft Office Resource Kit Tools and Utilities." |
– 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
– 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."
| | Tools and Utilities The Office Resource Kit Tools and Utilities include the Setup Simulator, a series of HTML pages that guide you through the interactive client Setup process without copying any files or changing any system settings. For more information, see "Setup Simulator" in Appendix A, "Microsoft Office Resource Kit Tools and Utilities." |
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:
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:
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:
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
– or –
In Windows NT Workstation 3.51, doubleclick Setup in File Manager; or click Run on the Program Manager File menu and type drive:\setup
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.
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 CDROM 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
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.
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
– or –
In Windows NT Workstation 3.51, doubleclick Setup in File Manager; or click Run on the Program Manager File menu and type drive:\setup
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.
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 MSDOS® 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.
|
|
Tools and Utilities The Office Resource Kit Tools and Utilities include copies of these files: Extract, Wextra32 (a program similar to Extract that runs on Windows 95 and Windows NT Workstation), and two MS-DOS batch files (CopyAll.bat and CopyDisk.bat) that run Extract to copy the contents of the Office floppy disk set to a server folder. For more information, For more information, see "Tools for Extracting and Copying Files from Office Floppy Disks" in Appendix A, "Microsoft Office Resource Kit Tools and Utilities." |
|
|
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.
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.
| | Tools and Utilities The Office Resource Kit Tools and Utilities include the workbook Macoff98.xls. The worksheets in this workbook list the Office 98 files installed by different installation options. For more information, see "Informational Workbook for the Macintosh" in Appendix A, "Microsoft Office Resource Kit Tools and Utilities." |
This media choice requires a CD-ROM drive, and it requires the installer to be physically present at the client computer.
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:
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
– 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.
– 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.
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
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
| 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:
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.
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
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.
| | Tools and Utilities The Office Resource Kit Tools and Utilities include the workbook Macoff98.xls. The worksheet "Files Not Removed" in this workbook lists the Office 98 files that the Remove option in Microsoft Office Installer does not remove from the System Folder. For more information, see "Informational Workbook for the Macintosh " in Appendix A, "Microsoft Office Resource Kit Tools and Utilities." |
To start the Remove Old Office Versions application
– or –
If you copied the Value Pack folder to a network drive, connect to that drive.
– or –
Select Custom Remove, then select the specific applications you want removed.
| | Tools and Utilities The Office Resource Kit Tools and Utilities include the workbook Macoff98.xls. The worksheet "Remove Old Office Versions File List" in this workbook lists the Office 98 files that the Remove Old Office Versions application can remove. For more information, see "Informational Workbook for the Macintosh" in Appendix A, "Microsoft Office Resource Kit Tools and Utilities." |
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
– or –
If you copied the Value Pack folder to a network drive, connect to that drive.
– or –
To install all Value Pack components, click Select All.
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
– or –
If you copied the Value Pack folder to a network drive, connect to that 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:
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.
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.
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.
 |
World Wide Web For the latest information about or to download the IEAK, connect to the Microsoft Internet Explorer Administration Kit home page at: |
|
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
Word Processors
Spreadsheets
Presentation Graphics
Databases
Scheduling
Project Management
Contact Microsoft Product Support for additional help with specific upgrading situations.
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.
|
The SR1 Enterprise Update requires a full reinstallation of Office 97, and you install it in the same way that you originally installed Office. The SR1 patch is designed to upgrade your Office 97 installation in place, by updating only those files that have changed in SR1. The patch contains the most significant enhancements in SR1, 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 SR1.
| In this scenario | Deploy this configuration of SR-1 |
| Office 97 not yet installed | SR1 Enterprise Update |
| Office 97 running from network servers | SR1 Enterprise Update |
| Office 97 installed locally, but Outlook 97 not installed | SR1 Patch |
| Outlook 97 installed locally with Office 97 instead of with Exchange Server 5.0 | SR1 Patch |
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:
|
| 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: |
The SR1 patch requires the following service packs be installed before running the patch:
|
| 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: |
The SR-1 patch updates only the files for applications that you have on your computer. When you run the patch, the patch executable file finds the Office 97 files on your computer, determines which components you currently have installed from Office 97, writes the SR1 changes to those files, and then makes appropriate changes to your Windows registry.
Note This SR1 patch does not upgrade the International English version or localized versions of Office 97 for Windows products. For information about international versions of the Office 97 SR-1 patch, contact your local subsidiary.
|
| World Wide Web The SR1 patch is available on the World Wide Web and on CD or floppy disk. For information about obtaining the patch, connect to the Office 97 Service Release page at: |
Before you begin the updating process, prepare the server just as you did when you installed Office originally:
Note If you have customized the Setup.stf (STF) file, do not copy this file into the updated Office folder. Instead, customize the new STF file that is included with the updated version of Office. For more information about STF files, see Chapter 6, "Customizing Client Installations."
To
update the Office administrative installation point with the same
configuration
– or –
In Windows NT Workstation 3.51, click Run on the Program Manager or File Manager File menu, and then type drive:\setup /a (where drive is the letter of the CDROM drive).
This installs the new version of Office into the same folders as the previous version.
Specify this location in the same way you did when you installed Office originally — with the same drive letter or the same UNC path.
After the administrative installation point is updated, users' computers can be updated.
To
update client computers with the same Office configuration
As during the original installation of Office, you can have users run Setup themselves, or you can automate the process using the techniques described in Chapter 6, "Customizing Client Installations."
Note If you purchased the Office 97 Standard Edition, you cannot use the standalone Access product to update your Office installation. If you want to add Access to your Office installation, you must purchase Office 97 Professional Edition. After you purchase the Professional Edition, follow the steps described earlier in this section for updating Office software.
Installing from CD or Floppy Disks
If your users originally installed Office from the Office CD or floppy disks, they can install the Office update in the same way.
To update Office from CD or floppy disks
Updating Office with a New Configuration
When you update Office software, you can change the way Office is configured on your network. With your original installation, client computers may have been configured so that all Office programs are located on the user's hard disk, or some or all of the Office components are shared on a network server. When installing an Office update, you can change this configuration. For example, you may have upgraded your network servers and would now like users to run the shared Office applications from a network server, rather than store the applications on their hard disks.
Changing your Office configuration is a twostep process. First, you need to create or update your administrative installation point with updated software and with new configuration options. Second, users must uninstall Office and then reinstall it to get the new version.
If your users originally installed Office from the CD or floppy disks, you need to create an administrative installation point on a network server from which users can install Office. For information about creating an administrative installation point, see "Installing Office from the Network" earlier in this chapter.
Before you begin the updating process, make sure all users are logged off, and prevent network access to the folders during the updating process.
To
create an Office administrative installation point with a new
configuration
Do not delete the existing Office folder structure; users must use the original Setup program to remove their existing Office installations.
– or –
In Windows NT Workstation 3.51, click Run on the Program Manager or File Manager File menu, and then type drive:\setup /a (where drive is the letter of the CDROM drive).
Once you have created the new administrative installation point, you can use the Network Installation Wizard to further customize the installation. For more information, see Chapter 6, "Customizing Client Installations."
Next, because configuration information is being changed, your users must remove their existing version of Office and then install the new version.
To
update client computers with a new Office configuration
As during the original installation of Office, you can have users
run Setup themselves, or you can automate the process using the
techniques described in Chapter 6, "Customizing
Client Installations." To automate the uninstall
of Office, use the /u commandline option. For more
information, see Appendix B, "Setup Command-Line Options and File Formats."
|
