NETWORK INSTALLATION If you have a license to install Microsoft Office on more than one client computer, there are two ways you can install Office in your organization. You can distribute the Office disks to each end user or you can install Office on a network and have each end user install from there. The information in this file explains the second option. =========================================================== CONTENTS: INSTALLING MICROSOFT OFFICE ON A NETWORK Creating the administrative installation point Administrative installation Client installation INSTALLATION ISSUES Installing Office in Shared Windows for the First Time Creating "My Documents" Folder on a Server for Multiple Users Microsoft Access Network Installation Support for Long File Names on Novell Servers Run From Network Server Errors on Novell 3.11 Installing to Windows NT 3.51 from a Novell Server Installing Bookshelf on a Network COPYING DISKS AND EXTRACTING FILES MANUALLY FOR MORE INFORMATION =========================================================== INSTALLING MICROSOFT OFFICE ON A NETWORK Installing Office over the network is a two step process: 1. The administrator creates the administrative installation point by creating the set of folders that will hold all the Office software and from which client installations will be done. 2. Users install Office by running Setup from the administrative installation point. The same Setup.exe is used for each of these steps, although in two different modes. To avoid confusion in the discussion below, these two modes will be referred to as follows: * Administrative Setup - To create the administrative installation point, you run Setup.exe from the physical media with the /a command line option. * Client Setup - To perform a client installation, a user runs Setup.exe from the administrative installation point without the /a command line option. Creating the administrative installation point ---------------------------------------------- You need to run administrative Setup under Windows 95, Windows NT 3.51 (or later), or Windows NT Advanced Server 3.51 (or later). The administrative installation point must have at least 190MB of disk space, and you (the administrator) must have read, write, delete, and create permission to this location. Users need read access as well. If your users will be running in a shared Windows environment, you need to run Setup in that same environment and you need write and create permissions to the Windows folders. Using the administrative mode of Setup, you need to install all of the Office files from the CD or floppy disks to the administrative installation point. This consists of two primary folders which will be created by Setup: 1. \Msoffice - The main Office application files, such as Microsoft Word and Microsoft Excel will be installed in this folder. 2. \Msapps - Shared components, such as Art Gallery and Word Art, will be installed in this folder. Administrative installation --------------------------- Before doing the administrative installation of Office, make sure: - Destination folders are empty. If a previous version of Office exists, delete all of it. - Users sharing applications or running shared Windows from this server are logged off. - Folders are locked to network user access during administrative installation. - Virus detection software is disabled. To install Office on the administrative installation point: 1. Run Setup.exe from the CD or floppy disk with the command line option /a: "setup.exe /a". Setup.exe must be run from a workstation with write access to the server, not directly on the server itself. NOTE: Double-clicking on Setup.exe in the File Manager (Windows NT) or Explorer (Windows 95) will not work. You need to use the Run command on the File menu of Program Manager or File Manager (Windows NT), or the Run command in the Start menu (Windows 95) to use the command line option /a. If you double-click on Setup.exe it will perform a client installation. 2. Follow the instructions on the screen. NOTES: - The organization name you enter will be used for all client installations of Office from this network location. - When asked for the server and path for the shared applications folder, enter the name in the same way that users will specify it when installing Office. You can specify whether the server will be accessed by users with a drive letter (for example, G:\) or a UNC path (for example, \\server\share). If you select drive letter, users installing Office will need to have that drive letter mapped to this folder before running client Setup. - When Setup asks where you want the shared application files installed, the option you select controls the choices your users will have during client Setup: + Server............The shared application files will remain on the server and run remotely; the user won't get a choice during client Setup. + Local Hard Drive..The shared application files will be copied to the user's local hard drive; the user won't get a choice during client Setup. + User's Choice.....The user will be asked to choose Server or Local Hard Drive during client Setup. Setup then copies all files from the CD or floppy disks to the administrative installation point. After the installation is complete, share the two folders (\Msoffice and \Msapps) on the network, either creating a single share that contains both folders, or creating two separate shares, one for each folder. Client installation ------------------- To install Office on the client computers, users will: 1. Connect to the main Office folder on the administrative installation point. 2. Run Setup.exe. When users run client Setup from this administrative installation point, they will see the Run From Network Server option in addition to the other installation options. If a user selects this option, the main Office application files are left on the server and run remotely. Note that when using the Run From Network Server option, Setup will place approximately 13 megabytes of files in the user's Office and Windows folders; Windows will use some extra disk space for temporary storage during Setup. For workarounds that can reduce this disk space usage, see chapter 8, "Installing Microsoft Office" in the "Microsoft Office for Windows 95 Resource Kit," or contact Product Support Services. See "For More Information" at the end of this file for instructions on obtaining the resource kit or connecting to support resources. It is recommended that users have a read-only connection to the server Office folder when they are running Setup, and also when they are running the applications after a Run From Network Server installation. =========================================================== INSTALLATION ISSUES Installing Office in Shared Windows for the First Time ------------------------------------------------------ The first time Office is installed to a user's computer in a shared Windows environment, Setup will attempt to copy a few Office files into the shared Windows folder. Although users normally have read-only access to the shared Windows folder, the first client installation of Office does require write access to copy these files. After the first installation is completed, the first user's access rights to the shared Windows folder can be set back to read-only. Subsequent users installing Office need only read-only access to the Windows folder since the needed files will already be present and Setup won't attempt to copy them again. Creating "My Documents" Folder on a Server for Multiple Users ------------------------------------------------------------- If you have users who install Office in a user folder on a network share (for example, users running on diskless workstations), the Office client installation process must be planned carefully to insure that multiple users do not share the same "My Documents" folder for their personal documents. "My Documents" is the default folder used by Office applications for saving the user's personal document files. Office Setup will create the folder "My Documents" in the root of the drive to which Office is being installed. For example, if a user installs Office to c:\Msoffice, then Setup will create the folder "c:\My Documents" for that user's personal documents. If a user installs Office to a user folder on a network share, "My Documents" will be created at the root of that share. If multiple users, then, install Office to separate user folders on a single network share, a single "My Documents" folder will be created at the root of that share for all users. This can cause document sharing issues because they will all be using the same "My Documents" folder for their personal documents. For example, suppose two users have drive letter G mapped to the same network server share: user1 - g: mapped to \\Server\Share user2 - g: mapped to \\Server\Share The two users run Office Setup and install Office into subfolders of this server share: user1 - g:\User1\Msoffice = \\Server\Share\User1\Msoffice user2 - g:\User2\Msoffice = \\Server\Share\User2\Msoffice As each user runs Setup, it will create the folder "My Documents" at the root of drive G. Because each user's drive G is mapped to the same network location, Setup will actually create a single "My Documents" folder at the root of the share: user1 - g:\My Documents = \\Server\Share\My Documents user2 - g:\My Documents = \\Server\Share\My Documents Both users will then be using the same "My Documents" folder for their personal documents, with each user having access to the other user's documents. To avoid this situation, users must be mapped directly to their own specific subfolder on the network share. Following the previous example, suppose each user has drive letter G mapped directly to their own subfolder on the server share: user1 - g: mapped to \\Server\Share\User1 user2 - g: mapped to \\Server\Share\User2 Each user then installs Office to "g:\" and Setup will create the "My Documents" folder at the root of that drive. Because each user has mapped drive G to a separate folder, they will each have their own "My Documents" folder: user1 - g:\My Documents = \\Server\Share\User1\My Documents user2 - g:\My Documents = \\Server\Share\User2\My Documents Before any users install Office to network locations, you need to insure that each user is mapped to a separate folder on the network share. This means that you need to make sure the appropriate network shares are defined in advance, and you need to edit user login scripts where the mapping occurs or inform users of the correct mapping procedure. For additional information and workarounds, see chapter 8, "Installing Microsoft Office" in the "Microsoft Office for Windows 95 Resource Kit." See "For More Information" at the end of this file for instructions on obtaining the resource kit. Information on this issue can also be obtained by contacting Product Support Services, or connecting to the support resources outlined in the individual product helpfiles under "Getting Help", "Connect to Microsoft technical resources." Microsoft Access Network Installation ------------------------------------- (Microsoft Office Professional Edition only) If your users are sharing Access files on the network, make sure that the workgroup information file, the sample database files, and the files for the Microsoft Access Wizards are not in a read-only folder. Office Setup automatically puts a default workgroup information file (System.mdw) and Wizard files in a subfolder of the Microsoft Access program folder named Workdir. Make sure that this folder is not read-only. You can use this folder for any shared Microsoft Access files that users may update. If your operating system does not allow you to have a single read/write subfolder of a read-only shared folder, make the Microsoft Access program folder read/write, but make all the files in the Microsoft Access program folder and its subfolders (except for the WORKDIR subfolder) read-only. You must create a shared workgroup information file for each Microsoft Access workgroup in your system. If you need more than one workgroup information file, you should also put them in the WORKDIR subfolder. For details on creating and maintaining Microsoft Access workgroups, see Chapter 14, "Securing and Delivering Your Application," in Building Applications with Microsoft Access for Windows 95. Support for Long File Names on Novell Servers --------------------------------------------- In order to use long file names on Novell Netware 3.11 servers, you need to obtain a patch from Novell. For Netware 4.x servers, you must load the OS/2 Namespace NLM that is supplied with the server software. To support long file names on your Novell 3.11 server, obtain the file OS2OPNFX.NLM, available as part of the 311PTD.EXE file available from Novell. Once this patch is installed on the Novell 3.11 server, make sure the long file name feature of Windows 95 is turned on by setting the following entry in the Windows 95 system.ini file: [nwredir] SupportLFN=2 Long file name support is not necessary in order to perform an administrative installation of Office to a Novell server. The administrative installation is always created with short file names, and all user installations performed over the network will make appropriate folder and file name choices based on the user's environment. Once long file name support is enabled on the server, users can store or share files on the server using long file names. Run From Network Server Errors on Novell 3.11 --------------------------------------------- On some network configurations, the Run From Network Server client installation option may fail when the DEC EtherWorks Turbo / TP (DE201) network adapter is being used on a Netware 3.11 server. Some of the error messages that can occur are: 1. BOOTSTRP caused a general protection fault in module SETUP.EXE. 2. The ordinal 65535 could not be located in the dynamic link library Kernel32.dll. 3. The application failed to initialize properly (0xc0000005). To avoid such errors, a different network adapter should be used in the server. Installing to Windows NT 3.51 from a Novell Server -------------------------------------------------- If you plan to perform installations to machines running Windows NT 3.51 from a Novell server, you need to obtain the NT Service Pack 2 to perform a successful installation, or else you will receive error messages during setup. You can download the Service Pack from a number of online locations, including: The Microsoft Network: Service Pack 2 can be found in the Microsoft area on MSN, in the Microsoft BackOffice & Windows NT Workstation Software Library. Microsoft World Wide Web site: Service Pack 2 for Windows NT 3.51 can be found at the following address: http://198.105.232.5/kb/softlib In the Free Software Web page, choose Windows NT in the Explore list, and click the GO! button. You can then select and download the appropriate Service Pack software for Windows NT 3.51. CompuServe: Log onto CIS and type the following: Go microsoft 7 (Microsoft Support Forums and Services) 1 (US Product Support) 8 (Microsoft Operating Systems) 6 (Microsoft Windows NT Service Pack Download Area) Download latest Service Pack for NT 3.51 Microsoft FTP server on the Internet: Enter the following: ftp ftp.microsoft.com logon anonymous cd bussys/winnt/winnt-public/fixes/nt351 bin get Installing Bookshelf on a Network --------------------------------- (Microsoft Office Professional Edition, CD-ROM version only) A Network Administrator's Guide for Microsoft Bookshelf has been added to the online version of the Microsoft Office for Windows 95 Resource Kit. This Guide describes how to install and use Bookshelf in a network environment. The Guide has been added as a section in Chapter 15, Using Workgroup Features and Applications with Office." (The information was not available in time to be included in the printed version of the Resource Kit.) See below for information on accessing the online version of the Office Resource Kit. Please note that to use Bookshelf 95 from the network, the contents of CD2 must be accessible to users. You can do this in either of the following ways: 1. Set up the server to share the CD-ROM drive and keep CD2 in this drive. If you are using Netware 3.12 or 4.0x, obtain the updated CDROM.NLM available from Novell in the CDROM3.EXE file in NOVLIB4 on CompuServe. 2. Copy the entire contents of CD2 to a folder on the server. Users must know the full network path to the contents of CD2 in order to use Bookshelf. When asked to insert the Bookshelf Disc, users should enter the full network path to CD2. =========================================================== COPYING DISKS AND EXTRACTING FILES MANUALLY Your Microsoft Office disks use a format called DMF (Distribution Media Format), which increases the capacity of a 3.5-inch floppy disk. WARNING Because DMF is a newer format, many existing utilities such as Norton Disk Doctor, Microsoft ScanDisk, MS-DOS DiskCopy, and Microsoft Windows Copy Disk do not recognize DMF. Do not use disk utilities to examine a DMF formatted disk, as these utilities can corrupt the DMF disk. You cannot copy DMF formatted disks using MS- DOS DiskCopy or Microsoft Windows Copy Disk. For a complete discussion of DMF format, see the "Microsoft Office for Windows 95 Resource Kit," or see, "Using Disks with Distribution Media Format," in the Office Readme file, OFREADME.TXT located in your Office folder. =========================================================== FOR MORE INFORMATION Only the basic installation information has been described here. For more details, including how to customize a network installation for your specific needs, you should obtain a copy of the "Microsoft Office for Windows 95 Resource Kit." The Resource Kit is designed to help you successfully roll out and support Office 95 and its component applications in your organization. It includes information such as the architecture of Office applications, detailed information about the installation process and tools you use to customize this process, maintenance and support information including frequently asked questions and troubleshooting tips, information on how to use Office in a workgroup, and how to switch from other applications. There is also a CD-ROM with valuable tools and utilities, including an electronic copy of the book itself. Look for Microsoft Office for Windows 95 Resource Kit at your local bookseller's. You can also order theMicrosoft Office for Windows 95 Resource Kit directly from Microsoft Press: 1. In the U.S., call 1-800-MSPRESS, Dept. FSUP. 2. In Canada, call 1-800-667-1115. 3. CompuServe members may order through GO MSP. 4. Outside the U.S. and Canada, fax to International Coordinator, +(206) 936-7329, or contact your local Microsoft subsidiary. The Resource Kit is also available online in the following locations: 1. Microsoft TechNet - The Resource Kit will be included with the TechNet CD some time after the release of Office Professional. 2. Microsoft Network - The Office Resource Kit is located under the TechNet forum on Microsoft Network. The TechNet forum can be reached by entering the Go word "Technet". To enroll in Microsoft TechNet in the U.S. and Canada, Simply contact you authorized reseller or call (800) 344-2121, dept. 3118 with your credit card information. You can call between 7:30 a.m. and 6:30 p.m. (PST), weekdays. Outside the U.S. and Canada contact your local Microsoft subsidiary. 3. World-Wide Web - The Office Resource Kit is located under the TechNet forum on the Web. The Resource Kit is located at "http://www.microsoft.com/technet/desk/office/orkf/orkftoc.htm". The TechNet forum is located at "http://www.microsoft.com/technet/default.htm". More information on issues presented in this file can also be obtained by contacting Product Support Services, or connecting to the support resources outlined in the individual product helpfiles under "Getting Help", "Connect to Microsoft technical resources."