The information in this article applies to:
SUMMARY
It is possible to install Microsoft Office 4.x, Microsoft Office 95, or
Microsoft Office 97 as a shared application to be run with Program Group
Control (PGC). However, each of these versions of Office are somewhat
unique in installation and behavior when used as a Systems Management
Server shared application. This article highlights some of the similarities
and differences to expect between the Office versions.
MORE INFORMATION
The following setup procedures are consistent across all versions of
Office:
Microsoft Office 4.2x and 4.3PDFs are available for Office 4.2a, 4.2c, 4.3 and 4.3c. Use the Msapps.pdf file for the Msapps package.Office 4.x requires the appropriate Smsproxy directory (located in the Primsite.srv\Import.src\Enu directory) to be copied to the source of the administrative share. Smssetup.exe runs the configuration command line. Program Group Control (PGC) creates an icon for each Office application when the user's User Groups are enumerated. As the user clicks on each application, the application runs its own one-time installation as described above. You must run the one-time installation for each Office application (that is, once for Microsoft Word, once for Microsoft Excel, once for Microsoft Access, and so on). Microsoft Office 95PDFs are available for Office 95 and 95a. The Office Standard PDF is Ofs95.pdf. The Office Professional PDF is Ofp95.pdf. Use the Msapps32.pdf for the Msapps package.Office 95 does not use SMSPROXY. Smsacm32.exe runs the configuration command line for Office 95. Program Group Control creates a single MSOffice icon when the user's User Groups are enumerated. When the user double-clicks the icon, the one-time installation runs for all Office applications at once and creates the program items for each application. Microsoft Office 97You must download the Office 97 Professional PDF (Of97prof.pdf) and the Msapps PDF (Msapps97.pdf) for sharing fromhttp://microsoft.com/smsmgmt/pdfs.htm.the Office 97 Resource Kit includes additional PDFs for specific applications and the Office 97 Standard version. Office 97 does not use SMSPROXY. Smsacm32.exe runs the configuration command line for Office 97. A white paper called "Using Microsoft Systems Management Server to Install Office 97" is available at http://www.microsoft.com/smsmgmt.Download this paper and read it for step-by-step instructions. Running Office 97 as a shared application requires Systems Management Server 1.2 Service Pack 1 or later. With client computers running Windows NT, the one-time Office 97 Setup installs the icons in a global (All Users) group. This means that the program items are not generated dynamically for each user, and it is up to you to monitor your own Office license usage. Also, the shortcuts for the program items point to the UNC name for the distribution share from which the one-time installation was run, and the applications will always run from that share. Load-balancing will not be performed (as it is with Appstart in Office 95 or Office 4.x), and if the distribution server is unavailable for some reason, the Office 97 shared application will fail to start. In Systems Management Server 1.2, Windows 95 introduced the Network Naming Provider (NNP) to dynamically choose a distribution server. If the distribution server is unavailable, another distribution server will be chosen. The following list contains additional articles in the Microsoft Knowledge Base that may be of interest:
Additional query words:
Keywords : kbinterop smspgc |
Last Reviewed: September 1, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |