Instructions for Installing MS Office 2000 with SMS 2.0

Article
02/20/2014

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Microsoft® Office 2000 is a suite of business products that includes word processing, spreadsheets, and presentation software, as well as other applications that are useful in a business setting. Microsoft® Systems Management Server (SMS) version 2.0 is a network administration tool that helps you deploy and maintain Microsoft Office 2000 in your organization.

This document supplements the Office 2000 documentation and the SMS 2.0 documentation by providing the additional information you need to deploy Office 2000 to SMS 2.0 clients in your organization. There are many features of Office 2000 Premium, and many tools and capabilities available with SMS. Only tools and features that directly apply to deploying Office 2000 using SMS 2.0 are described here.

Deploying Office 2000 with SMS is a process you should study carefully before you begin your rollout. Office 2000 uses the new Windows Installer, which provides new features (such as install on demand and resilient sources) that can affect the choices you make when planning your deployment.

When you install Office 2000 to Microsoft® Windows 95 and Microsoft® Windows 98 clients, you can use the general methods available for software distribution with SMS 2.0. When you install Office 2000 to Microsoft® Windows NT® 4.0 clients, keep in mind the following special considerations:

The installation must be done with administrative rights on Windows NT clients.

On Windows NT clients, the Office 2000 installation must be done with administrative rights on the local computer. Sometimes the logged-on user already has these rights. Otherwise, if you don't have administrative rights, you can use the SMS 2.0 administrative context to gain administrative rights to install Office 2000.

The SMS 2.0 administrative context cannot be used to install Internet Explorer 5 with Office 2000.

The SMS administrative context can be used to install Office 2000, a Windows Installer application, because Windows Installer elevates the user's rights after the reboot. However, the SMS administrative context cannot be used to distribute Microsoft® Internet Explorer 5, because Internet Explorer 5 is not a Windows Installer application. For more information, see "The SMS Software Distribution Process for Office 2000" later in this white paper.

If you want to distribute Internet Explorer along with your Office 2000 installation, you can use the O2KSetup SMS Installer script.

This white paper includes the following information:

A discussion of the important issues you need to consider before you install.
An explanation of the implications of distributing Office 2000 to Windows NT clients with users who do not have administrative rights.
A description of the preliminary steps you need to take before you begin installation.
A procedure for basic installation of Office 2000 Premium to your site hierarchy, using the SMS administrative context for some computers and the O2KSetup Installer file for other computers.
Procedures for the following advanced scenarios include: creating custom configurations for various groups of users, creating resilient sources, handling load balancing and fault tolerance, and chaining installations.

Background

Before you begin to deploy Office 2000 to your site hierarchy using SMS 2.0, make sure that your clients have the hardware and software required for Office 2000. You also need to review:

The terminology and processes of SMS 2.0 software distribution.
The features and options available with Office 2000.

It's important to choose which Office 2000 features you want to install and to determine the groups of users you want to receive each group of features, before you begin the deployment.

If you are not familiar with the issues discussed in the following sections, see "Where to Go for More Help" later in this white paper.

Only Windows 95, Windows 98, and Windows NT 4.0 clients are discussed in this white paper. Windows 2000 clients are not discussed.

Assumptions

This white paper makes the following assumptions:

You have working installations of Windows NT Server and SMS 2.0 in place within your organization. If you do not, use the Windows NT Server documentation and the SMS 2.0 documentation to assist you with this preliminary step.
You are familiar with Office 2000 features and SMS 2.0 features before you deploy Office 2000.
You are familiar with SMS 2.0 administration. If not, consult the Microsoft® Systems Management Server Version 2.0Administrator's Guide (referred to later in this paper as the SMS 2.0 Administrator's Guide) and other SMS 2.0 documentation.
You are familiar with the Microsoft®Office 2000 Resource Kit Readme and the issues from the Readme that apply to your situation. This white paper does not note all the instances where you need to take special precautions.

This white paper gives exact instructions for installing Office 2000 Premium. If you deploy a different Office 2000 family product, the process is the same, but you must use the correct package definition file (PDF) for your product. The O2KSetup.ipf script can be used with any Office 2000 product.

Requirements

Office 2000 requires a PC with an Intel Pentium 75 or higher processor (Pentium 125 or higher is recommended). If you plan to install Microsoft PhotoDraw®, you should have at least a Pentium 166. Table 1 lists the minimum hardware and software you must have in order to install the Premium version of Office 2000.

Table 1 Minimum Hardware and Software Requirements for Office 2000 Premium

Operating System	Office 2000 Feature	Memory	Disk Space	Other
Windows 95 or Windows 98	Basic features (Word, Excel, and PowerPoint)	16 MB of RAM plus at least 4 MB of RAM for each application running simultaneously (Some applications require more than an additional 4 MB for simultaneous running, and the space they require is noted in this column.)	252 MB (This number includes Word, Excel, Outlook, PowerPoint, Access, and FrontPage.)	CD-ROM drive (not needed for SMS deployment): VGA or higher resolution monitor (SVGA recommended); Microsoft® Mouse, Microsoft® IntelliMouse®, or compatible pointing device; and a network connection (needed for SMS deployment only)
	Outlook	8 MB
	Access	8 MB
	FrontPage	8 MB
	PhotoDraw	16 MB	100 MB
	Publisher, Small Business Tools		174 MB
	For performance: Free Space for user graphics and temporary image caches		100 MB
Windows NT 4.0 SP3 or later	Basic features (Word, Excel, and PowerPoint)	32 MB of RAM plus 4 MB of RAM for each application running simultaneously (Some applications require more than an additional 4 MB for simultaneous running, and the space they require is noted in this column.)	252 MB (This number includes Word, Excel, Outlook, PowerPoint, Access, and FrontPage.)	CD-ROM drive (not needed for SMS deployment); VGA or higher resolution monitor (SVGA recommended); Microsoft Mouse, Microsoft IntelliMouse, or compatible pointing device; and a network connection (needed for SMS deployment only).
	Outlook	8 MB
	Access	8 MB
	FrontPage	8 MB
	PhotoDraw	16 MB	100 MB
	Publisher, Small Business Tools		174 MB
	For performance: Free Space for user graphics and temporary image caches		100 MB

Note: Hard disk usage varies depending on the configuration you choose. The choices you make during custom installation will determine whether you need more or less hard disk space.

Refer to the Office 2000 documentation to see the requirements for other versions of Office 2000.

The space you need on the administrative installation point (which can be on the SMS site server or an auxiliary server) and on the client when you install Office 2000 depends on which Office 2000 family product you have chosen to deploy. The disk space required for installing each Office 2000 product is listed in Table 2.

Note: Table 2 also includes the PDF for each Office 2000 family product. SMS 2.0 uses PDFs to automatically create a package and all its command lines in a single step. The Office 2000 Resource Kit includes PDFs for all versions of Office 2000.

Table 2 Minimum Space Required for Office 2000 Family Products

Product	PDF (SMS 2.0)	Size of administrative installation point	Space required on client
Office Premium	Off9pre.sms	554 MB	252 MB for Disc 1 174 MB for Disc 2 100 MB for Disc 3 100 MB of free space for temporary cache and graphics store
Office Professional	Off9pro.sms	530 MB	217 MB for Disc 1 174 MB for Disc 2
Office Small Business	Off9sbe.sms	407 MB	178 MB for Disc 1 182 MB for Disc 2
Office Standard	Off9std.sms	484 MB	189 MB
Publisher	Pub2000.sms	—	—
Office Disc 2	Pff9cd2.sms	555 MB	—

The Microsoft® Office 2000 Resource Kit also includes PDFs for installing stand-alone Office 2000 family products. The PDFs for stand-alone products are not interchangeable. Use these PDFs only with the source files of the corresponding stand-alone product.

Important: If you want to install only a single Office family product from the Office 2000 source files, you cannot use the stand-alone PDFs. Instead, use the Off9pre.sms file and modify the installation using the Custom Installation Wizard (CIW). For more information, see "Custom Configurations" later in this white paper. Additional information about staged deployment is in the Readme on the Office 2000 Resource Kit CD. This Readme is also on the Office 2000 Resource Kit Web site:

www.microsoft.com/office/ork/2000/default.htm

If you want to install a single Office 2000 family product using the Office 2000 source files, the space you'll need on the administrative installation point for the specific product that applies is listed in Table 3.

Note: PDFs for SMS 2.0 have a .sms file extension (for example, Off9pre.sms), and PDFs for SMS 1.2 have a .pdf extension (for example, Off9pre.pdf).

Table 3 Space Required for Stand-Alone Office 2000 Family Products

Product	PDF (SMS 2.0)	Size of administrative installation point
Access	Acc2000.sms	416 MB
Excel	Xl2000.sms	338 MB
FrontPage	Fp2000.sms	301 MB
Outlook	Outl2000.sms	363 MB
PowerPoint	Ppt2000.sms	339 MB
Word	Word2000.sms	337 MB

The SMS 2.0 Software Distribution Process for Office 2000

This section briefly reviews the concepts and terms you need to know when you install Office 2000 with SMS 2.0. Each concept and term is further explained in the product documentation.

Creating the Package, Program, and Advertisement

The software distribution process in SMS 2.0 is different from the SMS 1.2 process. To use the SMS 2.0 software distribution feature, you must create an SMS package. A package is the basic unit of software distribution, and contains the source files for the program and the instructions that direct the software distribution process.

Each package must contain at least one program, which is a command line that runs on each targeted client computer. Programs can direct the installation of software, or they can contain any other command line to be run on each targeted client computer. Most packages also contain package source files, such as software installation files. The package source files for Office 2000 installations are created by setting up a customized installation called an administrative installation point.

Note: SMS 2.0 programs perform a function similar to SMS 1.2 package command lines.

The properties of the package and each of its programs can be set up in the SMS Administrator console as you create the package, or they can be imported from a package definition file (PDF). PDFs are text files that describe the properties of a package and all its programs. When you use a PDF that you have created or one created by the software vendor, you can create the package and all its command lines in a single step.

You should install Office 2000 by importing a PDF, rather than by choosing options in the SMS Administrator console, because the PDF already contains tested combinations of software distribution options that work for most Office 2000 distributions. When you distribute Office 2000 with SMS 2.0, you also have the option of modifying the resulting package and programs after you create the package from the PDF.

Packages include information about how and when to update distribution points. Distribution points are shares on SMS site systems. Package source files are copied to distribution points where client computers can access them. Before you can distribute software, you must choose the distribution points you want to use for the package.

Note: SMS 2.0 distribution points perform a function similar to SMS 1.2 distribution servers.

You can use the Create Package from Definition Wizard or the Distribute Software Wizard to create and distribute packages, or you can create the packages manually using the SMS Administrator console. When a package has been created, use the SMS Distribute Software Wizard, or use Distribution Points under the package in the SMS Administrator console to choose the distribution points.

After you create the package, you advertise the package's programs to your users by creating an advertisement. An advertisement specifies which program is made available to the client computers, identifies the collection of client computers or users that will receive the advertisement, and specifies the schedule.

Note: SMS 2.0 advertisements have a function similar to SMS 1.2 jobs.

The administrative context is a software distribution option. If you choose this option, SMS does the following:

Creates an account with administrative rights on the local system
Logs on with that account
Runs a software distribution program

When the program has run, SMS removes the account.

Even though the Office 2000 installation requires administrative rights after a reboot, the SMS administrative context can be used to install it, because Windows Installer automatically elevates the user's rights after the reboot. However, you cannot use the administrative context to install Internet Explorer 5, because Internet Explorer 5 is not a Windows Installer application. When a user without administrative rights logs on after the reboot, the installation fails.

SMS 2.0 installations can be attended or unattended. Attended installations permit user interaction during the installation and usually allow the user to choose exactly how the software should be installed. Unattended installations do not allow user interaction, except that the user can initiate an unattended installation and the user can log on again after a reboot.

Distributing the Software

After you have created the package, the programs, and the advertisement, and you have selected the distribution points for the package, the distribution begins automatically. The advertisement might not appear at the client immediately.

When you choose distribution points for your software distribution, SMS copies the package source files to the distribution points.
When you create an advertisement, SMS copies the advertisement to client access points (CAPs). In SMS 2.0, CAPs always serve as communication points between the SMS site server and the site's client computers. In software distribution, the Advertised Programs Client Agent uses the advertisements and package information stored on the CAPs to determine which advertisements are applicable to the client computer or the logged-on user.

Figure 1: The software distribution process
When software distribution is enabled for a site, SMS installs the Advertised Programs Client Agent on all client computers in the site. This client agent periodically checks the CAP to see if any advertisements are available to the client computer or the logged-on user. The client agent determines which advertisements are available, then processes any applicable advertisements. Assigned (mandatory) advertisements are scheduled to run by the client agent, and the user has no control over them. Optional programs that the user is scheduled to run, or those that have already run at least once, are added to the list of programs displayed in the Advertised Programs Wizard in Control Panel on the client computer. Assigned programs that the user is allowed to run before the scheduled time are scheduled to run and are also placed in the Advertised Programs Wizard.
Depending on the properties you configure for the advertisement, the program either runs automatically or runs when a user initiates it. When the program runs, if there are package source files, the client agent checks the CAP for the list of distribution points that contain the package and selects one. The client agent connects to the distribution point and runs the specified program's command line. If there are no package source files, the client agent runs the program's command line without making any connections.

If your package is propagated to other sites, SMS compresses all the files to be sent between sites. You can also create and use a compressed copy of the package source files within the originating site.

For more information, see the SMS 2.0 Administrator's Guide.

Office 2000 Specifics

There are several important concepts for Office 2000 that you should be familiar with before you begin to install. They are:

Transform files
Install on Demand
Resilient sources

Transform Files

When you want to create any kind of customization in an Office 2000 command line, you can create a transform file with the Custom Installation wizard.

When you distribute Office 2000 with SMS 2.0, you might want to create transform files for:

Adding resilient sources
Creating customized programs for different sets of users
Selecting the Office features that you want to install
Modifying shortcuts
Customizing options for Internet Explorer 5 and Microsoft® Outlook
Adding custom files to the installation.

Transform files have a .mst extension (*.mst). For more information about the Custom Installation Wizard, see "Office Custom Installation Wizard" in the Office 2000 Resource Kit.

Important: Do not create separate transform files for different kinds of customizations. You must put all the customizations for a single client into a single transform file. Only one transform file can be applied to any client unless you reload Office 2000.

Install on Demand

Windows Installer contains a new kind of installation called advertising or Install on Demand. Install on Demand can install just the instructions for setting up an application, rather than the application itself. To do this, Windows Installer places icons on the desktop or in the Start menu, and when users click the icon for the first time, Windows Installer installs the application on the local hard drive.

Both Office 2000 and SMS have a concept called advertising, but each concept refers to an entirely different feature. They are not the same. Because of this, the concept of advertising, also called Install on Demand, will be called Install on Demand in this white paper.

Resilient Sources

Resilient sources are administrative installation points that are available to the clients throughout the life of the applications. Windows Installer requires users to retain access to the source files throughout the life of the applications, so that advanced features, such as application repair and Install on Demand, can work. Office 2000 gives you the option of establishing a valid UNC path (for example, \\<Server>\<Share>) or a list of valid UNC paths for the source files.

If you choose to use resilient sources, which are optional, client computers will use those sources whenever the original distribution point becomes unavailable.

Use the SOURCELIST command line parameter or the Custom Installation Wizard to specify your resilient sources as you install Office 2000. For more information, see "Resilient Sources" later in this white paper.

Issues to Consider Before You Install Office 2000

Before you install Office 2000 with SMS 2.0, there are a number of important issues you need to consider to help you choose the right methods for your installation. Reviewing the questions listed below will help you determine the exact nature of your Office 2000 package and programs. These issues are explained in the section that follows.

What operating systems do your clients have?
Do you have Windows NT users without administrative rights for their computers?
What version of Internet Explorer do your clients have now? Do you want to include Internet Explorer 5 in your installation?
Will you be doing an attended or unattended installation? Mandatory or optional?
Which programs do you need from the PDF (what kind of customizations do you need)?
Do you want to upgrade existing Office installations, remove them, or remove them and reinstall?
What configuration or configurations of Office 2000 components do your users require?
Do you want to create resilient sources?

The method you choose for installing Office 2000 depends on the answers to these questions. Table 4 shows your installation options, and the information in the table is expanded in the sections that follow.

Table 4 Installation Options for Office 2000 Using SMS

Windows 95, Windows 98, Windows NT 4.0 with administrative rights	Windows NT without administrative rights Internet Explorer 5 option
	Want to install Internet Explorer 5	Do not want Internet Explorer 5 or already have Internet Explorer 5
Use the programs in the Off9pre.sms PDF. They trigger installation of Office 2000 if it is not already installed.
Use TYPICAL if you have no transform file and the setup is unattended. Use MANUAL if you have no transform file and the setup is attended. Modify and use CUSTOM if you have a transform file and the setup is unattended. Modify and use CUSTOM if you have a transform file and the setup is attended.	Use O2KSetup Installer File. Triggers installation of Internet Explorer 5 if it is not already installed.	Use TYPICAL, MANUAL, or CUSTOM programs and create new programs, as needed, after importing the PDF.
	Install Internet Explorer 5 first independently. Then, use Office 2000 Setup.exe. Use TYPICAL, MANUAL, or CUSTOM programs, and create new programs, as needed, after importing the PDF.

What operating systems do your clients have?

Before you create the package, determine which operating systems and how many different operating systems your clients have. You must create separate programs for at least two groups:

Windows 95 and Windows 98 clients, and Windows NT 4.0 clients where the logged-on user has administrative rights.
Windows NT 4.0 clients where the logged-on user has no administrative rights, or where there is no logged-on user.

Windows 95 and Windows 98 clients use the same instructions for installation. Windows NT 4.0 clients, if the logged-on user has administrative rights on the local computer, use the same installation instructions as Windows 95 and Windows 98 use. If the logged-on user has no administrative rights, or if there is no logged-on user, you must use one of the solutions described in "Administrative Rights" later in this white paper.

Do you have Windows NT users without administrative rights on their computers?

If the logged-on user does not have administrative rights, or if there is no logged-on user, you have several choices for installations:

Use the O2KSetup Installer file for installation. This file lets you install Office 2000 and Internet Explorer 5 in the same program.
Use the basic Office 2000 Setup.exe program, but do not include Internet Explorer 5 in the installation.
Use Setup.exe /jm to create an Install on Demand program. You can follow this with a full installation of the entire Office 2000 suite or you can fully install selected applications, leaving others to be installed on demand.

What version of Internet Explorer do your clients have now? Do you want to include Internet Explorer in your installation?

Office 2000 works best with Internet Explorer 5, which can be installed as part of the Office 2000 Setup. If you do not want your clients to install Internet Explorer 5, you can still install Office 2000, but there are issues you should be aware of with certain configurations. If you don't want to install Internet Explorer 5 on your clients, read carefully the documentation at

https://www.microsoft.com/office/ork/2000/one/10t2.htm

If you want to install Internet Explorer 5 on Windows NT 4.0 clients without administrative rights, you must use one of the options described in "Installing Without Administrative Rights" later in this white paper.

For more information about deploying Internet Explorer 5, see the Microsoft® Internet Explorer Administration Kit 5. For information about installing Internet Explorer 5 using SMS 2.0, see the document found on the following Web page:

https://technet.microsoft.com/sms/bb676797.aspx

Be sure the DLLs are dated May 1999 or later.

Will you be doing an attended or unattended installation? Mandatory or optional?

Decide early whether to do an attended or unattended installation so you can set up the programs and advertisements for the kinds of installation you want. Some differences between attended and unattended installations are shown below:

Table 5 Attended and Unattended Installations

Attended	Unattended
User has more control.	Administrator has more control.
You do not need to customize command lines. The users decide which applications and options they want to install.	You create the configuration you want for each client.
Installations are easier for administrators to set up, because there is no need to create a transform file for each set of users.	Installations tend to run more smoothly because they are completely determined before you begin the installation. There is less need for consultation with the system administrator.

You should also decide if your installation will be mandatory or optional. If the installation is mandatory, you also have the option to allow users to install it before the scheduled time. If users do not run it early, it will automatically run at the scheduled time.

Which programs do you need from the PDF?

There are four programs included in the Off9pre.sms file, one for uninstall and three for installation. You can add more installation programs after the package is created from the PDF, and you can modify the existing programs at that time.

TYPICAL programs use the /qb- mode (modal dialog boxes suppressed, error messages suppressed, only a progress indicator is displayed) and are meant to be used for unattended installations without a transform file.
CUSTOM programs also use the /qb- mode, but are meant to be used with unattended installations where you want to use a transform file.

Note: If you want a program for attended installations where you supply a transform file, remove the /qb- parameter from the CUSTOM program after you have created the package from the PDF, or create a new program without the /qb- parameter at that time. For more information, see "Custom Configurations" later in this paper.
MANUAL programs use the default mode, full UI, and are meant to be used with attended installations without a transform file.
UNINSTALL programs uninstall the software.

For more information about program command line options, see the Office 2000Resource Kit documentation.

Do you want to upgrade existing Office installations, remove them, or remove them and reinstall?

The default unattended Office 2000 Setup program (/qb- mode) removes existing Office products before it begins the Office 2000 installation. Usually, this is acceptable, but sometimes you want to keep the older version. If you do an attended installation, each user can choose whether to keep or remove previous installations. If you have an unattended program, you can choose to keep previous installations, but you must customize the program using a transform file (described in "Custom Configurations" later in this white paper).

Note: If you plan a staged deployment of Office 2000 applications to systems that contain earlier installations of existing Office products, and you have changed the default removal properties of the Office 2000 Setup program, see the README.doc in the Office 2000 Resource Kit for important information.

What configuration or configurations of Office 2000 components do your users require?

Often, organizations have several sets of users that each require different configurations of Office 2000. Some users might require more features than others, and others might have more powerful computers and more available disk space.

When you have several sets of users, you can let users create their own configurations by using an attended installation, or you can create custom programs for each group by modifying the PDF programs and creating new ones after you create the package from the PDF.

This option is explained in "Custom Configurations" later in this white paper.

Do you want to create resilient sources?

Resilient sources are administrative installation points that are available to the clients for the life of the application.

The path you use when you install Office 2000 using SMS 2.0 serves as a single resilient source, so you do not need to set up resilient sources when you install. However, you might want to consider adding more resilient sources to benefit your installation.

Additional resilient sources that you create directly are valuable because:

They provide greater fault tolerance.
They release disk space on the site server and distribution points for subsequent software distributions.

For more information, see "Resilient Sources" later in this white paper.

Installing Without Administrative Rights

Both Office 2000 and Internet Explorer 5 require the logged-on user to have administrative rights to install on Windows NT clients. If users have administrative rights to install software on their clients, then the programs for installing Office 2000 and Internet Explorer 5 provided in the Office 2000 Resource Kit can be used for Office 2000 installation. If users do not have administrative rights, then you must choose from several options for installing Office 2000 and Internet Explorer 5. The Office 2000 Resource Kit contains more information about the recommended order of installing Office 2000 and related applications.

There are a number of ways to install Office 2000 on these client computers using SMS 2.0. Some of them use the Windows Installer functionality.

Note: All of these scenarios install Office 2000 per computer (and not per user).

There are three basic ways to deploy Office 2000 to computers where the logged-on user does not have administrative rights:

Using the programs from Off9pre.sms
Using Office Install on Demand
Using the O2KSetup Installer script

Using the Programs from Off9pre.sms

Use the programs from the PDF (whose command line is the Setup.exe program) and run them in the SMS 2.0 administrative context. Customize Office 2000 so that Internet Explorer 5 is not installed during the installation.

When you use the SMS administrative context, even when a user without administrative rights is logged on, the Office 2000 installation can be run within the SMS administrative context, which is active until the reboot. After the reboot, Windows Installer will elevate the rights of the logged-on user whenever this is needed to complete the Office installation. Only Windows Installer programs have these elevated rights after the reboot. (The Internet Explorer 5 installation cannot provide elevated rights after the reboot because it is not a Windows Installer application.)

When you perform this type of installation, use the Custom Installation Wizard to configure Office Setup so that Internet Explorer 5 is not installed. If you do not remove Internet Explorer 5 from the Office 2000 installation, the post-reboot portion of Internet Explorer 5 setup will fail after the user without administrative rights logs on.

Note: For information about installing Internet Explorer 5 using SMS 2.0, see the document found on the following Web page:

https://technet.microsoft.com/sms/bb676797.aspx

Make sure the DLLs are dated May 1999 or later.

Using Office 2000 Install on Demand

Use the Install on Demand feature (Setup /jm) to install Office 2000 and run it in the SMS administrative context.

Install on Demand causes shortcuts to be displayed on the client's desktop, but the applications themselves are not actually installed until the user double-clicks the icon, triggering installation of the program.

Because the user initiates subsequent installations rather than SMS, you will not receive status about the installation in the SMS Administrator console.

Note: To create desktop icons, the Install on Demand method requires that the Active Desktop code be present on the computer, even if it isn't installed. This means that your clients must have Internet Explorer 4.01 or later installed. There are several other issues you need to consider when your users have earlier versions of Internet Explorer installed. For more information, see

https://www.microsoft.com/office/ork/2000/one/10t2.htm

Using the O2KSetup Installer Script

Use the O2KSetup SMS Installer script provided in the Office 2000 Resource Kit to install Office 2000 together with Internet Explorer 5.

The O2KSetup Installer script provides an administrative context that survives a reboot and elevates the rights for the entire Office 2000 installation, including the Internet Explorer 5 installation. You must customize the script so that it is specific to your environment.

Because the Setup script logs on as a user with administrative rights, the mouse and keyboard for the client computer are locked until installation is complete. Because the keyboard and mouse are not available to the user during installation, the O2KSetup script should only be used for unattended installations. For instructions about modifying and using the O2KSetup SMS Installer script, see "Preparing for O2KSetup Installations" later in this white paper.

Summary of the Methods Discussed Above

In summary, the following methods are available to you for installing Office 2000 to users without administrative rights, or to clients where no user is logged on.

Table 6 Office 2000 Installation Methods

Method	Can be used to install Office 2000 without Internet Explorer 5	Can be used to install Office 2000 including Internet Explorer 5
Default Office 2000 Setup.exe command line in the SMS administrative context	Yes	No
Install on Demand (Setup /jm) in the SMS administrative context	Yes	No
O2KSetup SMS Installer script	Yes	Yes

Note: If you cannot install Internet Explorer 5 within your Office 2000 installation program, you should install it before you install Office 2000.

Extending the Install on Demand Method

The basic methods of installing Office 2000 on client computers without administrative rights can be customized and extended to help support your specific deployment needs. After the Install on Demand Setup.exe has been executed, additional Office 2000 setup command lines can be sent to clients to trigger the installation of a specific Office 2000 application. This can be helpful if you want to stage your Office 2000 deployment.

For example, you might want to install the full version of Microsoft Word and Microsoft Excel on the client computers and also might want to make Microsoft PowerPoint and Microsoft Access available to be installed on first use. By setting some of the applications to install on first use, the network bandwidth required at initial deployment time is reduced. Later, if you want to make sure that all clients have PowerPoint and Access installed in full, you can send the additional Office 2000 Setup programs to accomplish this. More information about staging your Office deployment can be found in the Office 2000 Resource Kit documentation.

The installation methods discussed here are somewhat more complicated than a typical Office 2000 installation. You should be sure to test the deployment method you decide to use in your own environment to ensure that Office and Internet Explorer 5 are installed correctly and that they are installed the way you expect.

Where to Go for More Help

This white paper does not give complete information about Office 2000 or about SMS 2.0. For more information, see the following sources:

For more information about Office 2000 features, see the Office 2000 Resource Kit. The Office 2000 Resource Kit can be purchased in bookstores (includes a Tools CD) or it is available from the following Web page

https://www.microsoft.com/office/ork/2000/default.htm
For more information about SMS 2.0 features, see the SMS 2.0 Administrator's Guide and the Microsoft® Systems Management Server Version 2.0 Resource Guide (referred to later in this paper as the SMS 2.0 Resource Guide) in the Microsoft® BackOffice® 4.5 Resource Kit.

Many SMS features that are not covered in this document are very useful for analyzing your network before you deploy Office 2000 with SMS 2.0, and to maintain the Office 2000 installations. These features are described in SMS 2.0 documentation, and their uses with Office 2000 deployment are described in the Office 2000 Resource Kit documentation. They include:
- Inventory
- Queries
- Network Monitor
- Network trace
- SMS Status System
For more information, see the SMS 2.0 Administrator's Guide.

Preparing for Office 2000 Installation

When you've decided exactly how you plan to distribute Office 2000, you are ready to begin. No matter which installation method you choose, you must always do the following before you install Office 2000:

Create an administrative installation point.

An administrative installation point is a special Office installation that installs the source files for later installation on target computers.

Apply the SMS 2.0 hotfix.

Before you install Office 2000, you need to apply the Sms20O2K.exe hotfix that is in the Office 2000 Resource Kit if your version of the Advertised Programs Manager is earlier than 100.1239.003.

If you are using the O2KSetup Installer script, modify the script.

Modify the script for your environment. Create a transform file and name it within the script if you need customizations. After you have created the package from the PDF, you must create a new program for this installation method.

Creating the Administrative Installation Point

An administrative installation point is a server share that contains all the files you need to distribute Office 2000 using SMS. The administrative installation point includes all the files on the Office 2000 installation CD. You will need to copy some additional files to the administrative installation point to support O2Ksetup deployments. When SMS 2.0 packages are distributed, the files in the administrative installation point are copied to distribution points.

Using the administrative installation point eliminates interactions you do not want for your clients, such as prompting for a CD key.

To create an administrative installation point for distributing Office 2000 with SMS 2.0

Create a share on a server that is available to the SMS Service account. This share must contain at least 554 MB.
On the computer that contains the share you created, insert the Office 2000 installation CD Disc 1 in the CD-ROM drive. If the computer with the share is not available, insert the installation CD Disc 1 in the CD-ROM drive of any computer running Windows 95, Windows 98, or Windows NT 4.0, and connect to the server share. When the installation program appears, close it in order to modify the Setup program.
On the Start menu, click Run, and then click Browse. Select Setup.exe on the CD-ROM and then click Open.
On the program following Setup.exe, type /a data1.msi. For example:

W:\Setup.exe /a data1.msi

Click OK. The installation program reappears.
On the Welcome to Microsoft Office 2000 page, enter your CD Key and organization name.
The License and Support Information page appears (not shown). Click I accept the terms of the License Agreement and then click Next.
When prompted for the installation location, enter the path name to the administrative installation point share you created.
The Setup program copies all the necessary files from Office 2000 Disc 1 to the administrative installation point share, creating a hierarchy of folders within the root folder of the share. Setup also modifies the Windows Installer package for Office (Data1.msi) to identify the share as an administrative installation point.

For more information about creating an administrative installation point, and customizing Office 2000 in other ways, see "Basic Installation Methods" in the Office 2000 Resource Kit.

Applying the SMS 2.0 Hotfix

The Sms20O2K.exe file is necessary if you have a version of Smsapm32 that is earlier than to 100.1239.003. This fix is necessary for accurate status reporting when you install Office 2000 or any other Windows Installer application using SMS 2.0. Installing the hotfix to later versions, might cause problems, so check your version of Smsapm32 first.

To check the version of Smsapm32 on a client

From the Start menu, point to Settings and click Control Panel. Click Systems Management.
On the Components tab, check the version of the Available Programs Mgr Win32. This version number should be earlier than 100.1239.003. If it is not, you don't need the hotfix and should not install it because it could cause errors if installed on a newer system.

Note: If the hotfix is applied to clients that have later versions of Smsapm32, the CAPs are updated with the older files, which causes the clients to be updated with the older files as well.

Before you begin applying the hotfix to SMS 2.0, install the Office 2000Resource Kit on your primary site server, or some other server or client you can use to obtain the files you need to install.

To apply the hotfix to your clients

Close the SMS Administrator console if it is open.
On a computer with the Office 2000 Resource Kit installed, from the Start menu, point to Programs, Microsoft Office Tools, and Microsoft Office 2000 Resource Kit Tools, and then click Package Definition Files.
Double-click sms20o2K.exe to execute the file. This is a compressed file that contains all the files necessary for the hotfix and installs these files in the correct directories on the site server.

When you have executed this file, the hotfix is applied. You might need to wait up to 24 hours for the hotfix to be installed on clients before you attempt any Office 2000 installations. Or, you can force clients to install the hotfix by clicking the Systems Management icon in Control Panel.

To verify that the fix has been successfully installed on a client, check the version of Smsapm32 as directed in this section.

Preparing for Custom Programs

If you need customized programs that are different from the ones included in the PDF, modify the programs from the PDF after the package is created (you can also create new programs at that time). For more information about customizations, see "Custom Configurations" later in this white paper.

Preparing for O2Ksetup Installations

No special preparations are needed for using the PDF programs or using the PDF programs with Install on Demand. However, if you want to provide an O2KSetup Installer script installation, you must modify the script before you start the installation.

The O2KSetup.ipf file is in the Office 2000 Resource Kit. You modify this file and then compile it to create the O2KSetup.exe file.

The O2KSetup.ipf script assumes the following:

You are using SMS Installer as shipped with SMS 2.0 (Build 2.0.45.00) or later.
SMS clients use Windows NT 4.0, SP4 or later.
SMS logon servers and distribution servers are Windows NT Servers.

There are four lines in the O2KSetup.ipf script that must be modified. These modifications are very easy and do not require advanced SMS Installer knowledge.

After you modify the O2KSetup.ipf file, save it in a secure directory. Compile it, and copy the O2KSetup.exe file to the top-level directory of your administrative installation point. Also copy the Shutdown.exe file to that directory.

Tip Open SMS Installer files within SMS Installer. You can open these files in other text editors, but what you see in any other editor is the source for the Installer file, which is more difficult to interpret. Also, you will not be able to compile the script after making your changes.
The text of the O2KSetup.ipf file is included in the Appendix.

To modify the logon information and the command line in the O2KSetup.ipf SMS Installer file

Install the SMS Installer program by running the Smsinstl.exe installation program. You can get this program from the %SMS%\Sms_inst\i386 directory on your SMS 2.0 site server, or you can find it at

https://www.microsoft.com/smsmgmt
Open the Installer program from the Start menu by selecting Programs, Microsoft SMS Installer, Microsoft SMS Installer 32.
On a computer that has the Office 2000 Resource Kit installed, from the Start menu, point to Programs, Microsoft Office Tools, Microsoft Office 2000 Resource Kit Tools, and then click Package Definition Files. Copy the Shutdown.exe file to the top-level directory of your administrative installation point.
To open the O2KSetup.ipf file on a computer that has the Office 2000Resource Kit installed, from the Start menu, point to Programs, Microsoft Office Tools, Microsoft Office 2000 Resource Kit Tools, and then click Package Definition Files. Double-click O2KSetup.ipf to open it in the Installer in Script Editor mode.
Look for the "ADD IN DOMAIN SPECIFIC INFORMATION HERE" line as shown above. Each time you double-click a "Set Variable…" line in the Script Editor, the Set Variable dialog box appears. Type the new value for the "Set Variable…" line in the Set Variable dialog box.
In the Script Editor, double-click the "Set Variable DOMAIN to MyDomain" line. In the Set Variable dialog box that appears, in the New Value text box type in the domain name to which the installation account belongs. Click OK.
In the Script Editor, double-click the "Set Variable SVCACCT to MyAdmin" line. In the Set Variable dialog box, in the "New Value" text box, type the name of an account that has local administrative rights on your NT Workstations and also access to your SMS distribution points. Click OK.
In the Script Editor, double-click the "Set Variable SVCACCTPW to MyPassword" line. In the Set Variable dialog box, in the New Value text box, replace the MyPassword field with the password for the administrator account you chose. Click OK.
In the Script Editor, double-click the "Set Variable Transforms to" line. (A transform file is a set of instructions to customize your installation. If you do not have a transform file, remove this line.)
In the New Value section, type:

TRANSFORMS= < name of your custom transform file >

Click OK.
Point to the Menu item File and click Save as and save to a secure directory. Then point to Installation and click Compile. This creates the O2KSetup.exe file. Move this file to the top-level directory of your administrative installation point.

Security Tip After you've modified it, the IPF file contains a logon and password that allows anyone to have administrative access to your client accounts. Be careful where you copy or move this file. For example, do not save it to the source file directory. You should either keep it on a secure share or destroy it directly after the .exe file is compiled, to protect the administrative account password. Also, you might want to create a new account just before installing, and then disable it immediately after installation is complete for all clients.

Basic Office 2000 Installation

This section describes the steps required to successfully create your Office 2000 Package for SMS 2.0 clients. To complete this section, you must already have created the Office 2000 administrative installation point and copied all supporting files to that location.

To install Office 2000, you must first import the Office 2000 PDF. This PDF creates everything you need for a basic Office 2000 installation, except the program for O2KSetup. Next, if you need to modify the CUSTOM program command line or create new programs, you should do so, and then create the program for the O2KSetup Installer script and any other new programs you need. After these steps are completed, there will be one SMS Package that is capable of a variety of setup methods.

Importing the PDF

You can use the Create Package from Definition Wizard to create a package from a PDF, or you can use the Distribute Software Wizard. Both wizards create a package by importing a PDF, but the Distribute Software Wizard also includes the following functions:

Enabling and disabling distribution points for the package
Creating an advertisement for the package

These instructions use the Create Package from Definition Wizard. The Distribute Software Wizard is described in "Assigning Distribution Points and Creating Advertisements" later in this white paper.

To create a package with the Create Package from Definition Wizard

Open the SMS Administrator console and navigate to Packages.
Right-click Packages and select New, Package from Definition.
The Create Package from Definition Wizard page appears. Click Next.
The Package Definition wizard page appears, but the Office 2000 Off9pre.pdf file does not appear in the list (it has not been imported into the SMS Administrator console). Click Browse.
Browse to the directory that contains the PDF (<driveletter>:\ORKTools\ToolBox\Tools\Package Definition Files\Office Premium on a computer holding the Office 2000 Resource Kit) and select Off9pre.sms PDF. Click Open.
Make sure that the correct Package Definition is selected, and then click Next.
On the Source Files wizard page, select Always obtain files from a source directory and then select Create a compressed version of the source if you need a compressed version within your site. (A compressed version is always created between sites. For more information on these items, see the SMS 2.0 Administrator's Guide.) Click Next.
On the Source Directory wizard page, specify the location of your administrative installation point. You must specify a local path on the site server or a network path.
Click Browse and navigate to the location of these files. Click Next.
Verify that the information is correct and click Finish.

Creating Programs for Office 2000 Setup.exe

If you need to modify any of the programs that were imported with the PDF (TYPICAL, MANUAL, or CUSTOM), or if you need to create new command lines, do so at this point. For more information about customizing command lines, see "Custom Configurations" later in this white paper.

Creating Programs for Office 2000 Install on Demand

If you want to use Install on Demand, you need to create a new program, and make this program Install on Demand by adding the /jm option on the command line.

The command line to install Office 2000 Disc 1 on demand is:

Setup.exe /wait /jm data1.msi /t <transform name> /m off2000

Note: In this command line:

/wait is necessary for status reporting
/jm causes Install on Demand installation
/t names your transform file if you have one
/m creates a MIF file so more detailed status is possible

Additional command line options should not be necessary for Install on Demand, and all customizations should be made in the transform file. Note that when you install Office 2000 using Install on Demand, the computer does not reboot. Also note that if you plan to customize Office 2000 installations using the Custom Installation Wizard, the transform file name must be specified on the initial command line (the Setup /jm line) and not on subsequent Office command lines that might be run on the same clients.

If the initial installation for a Windows Installer application is performed in an administrative context, then subsequent installations of that same application also run in an administrative context. This means that if you run a Setup /jm installation for Office 2000 in an SMS administrative context, then the rest of the Office installation, whenever that might be triggered, is also run in an administrative context. This is true only for Windows Installer applications. All Office 2000 applications are Windows Installer applications, except for Internet Explorer 5. See the Office 2000 Resource Kit for more information.

Creating a New Program for O2KSetup

When you use programs from the PDF, you don't need to create a program for O2KSetup. But if you need to use the O2KSetup Installer script, you must create a program for the script.

Note: Do not create a new program for O2KSetup by merely modifying one of the PDF program command lines. The options specified in the following procedure are necessary for correct installation.

To create a program for O2KSetup

In the SMS Administrator console, navigate to Packages and select your newly created Office 2000 Package.
In the details pane, right-click Programs and select New Program. The Program Properties dialog box appears.
Enter a name and comment for this program that you can easily identify. In the After running box, select Program restarts computer.
For the command line, enter O2KSetup.exe.

Tip Click Browse to select the program executable file, and to ensure that the information is correct.
Click the Requirements tab and select X86 NT 4.0 Service Pack 3 clients. Click the Environment tab.

This program must be run in an administrative context on the client computer. If you want the program to run only when a user is logged on then you must select the Run with administrative rights check box.

If you use either Whether or not a user logged on or Only when no user logged on, the program automatically runs in an administrative context.
Make sure that Drive Mode is set to Runs with UNC name.
After you have finished making your selections, click OK to create the program.

Assigning Distribution Points and Creating an Advertisement

When you create your package and programs using the Create Package from Definition Wizard, you also need to assign distribution points and create an advertisement. You can do these tasks using Advertisements and Distribution Points on the SMS Administrator console, or you can use the Distribute Software Wizard to do both tasks.

When you are ready to deploy Office 2000 to all of your clients, run the Distribute Software Wizard to create the distribution points and the advertisement.

To create the advertisement and assign distribution points with the Distribute Software Wizard

In the SMS Administrator console, right-click your package**,** point to All Tasks, and click Distribute Software.
On the first Distribute Software Wizard page that appears (not shown here), click Next.
The Package wizard page appears. Select Distribute an existing package and then select Office 2000 Premium. Click Next.
On the Distribution Points wizard page that appears, select the distribution points you want for the Office 2000 distribution. Click Next.
On the Advertise a Program wizard page that appears, select Yes for Do you want to advertise a program to a collection? and then select the program that you want to include in this advertisement. Click Next.
On the Advertisement Target wizard page that appears, select Advertise the program to an existing collection, and then choose a collection from Collections. Or, select Create a new collection and advertise the program to it to create a new collection. Click Next.
On the Advertisement Name wizard page that appears, type in a unique name and add a comment. Click Next.
On the Advertise to Subcollections wizard page that appears, select the option you want and click Next.
On the Advertisement Schedule wizard page that appears, select the schedule you want, and determine whether you want the advertisement to expire. If you are using the distribution points as resilient sources, select No. This advertisement never expires. When you use resilient sources, you can set the advertisement to expire at a certain time when you expect all your installations to be complete. It isn't necessary to have the advertisement expire; you can remove it manually when all your installations are complete if you like. Click Next.
On the Assign Program wizard page that appears, choose Yes. Assign the program. if you want your program to be mandatory, and enter all the necessary information. Click Next.
On the Completing the Distribute Software Wizard page that appears, read carefully the information in the Details text box to make sure it is all correct. Click Finish to initiate the distribution (if you have not scheduled it for later).

Monitoring the Installation

When your distribution has begun, you can monitor it with the SMS Status system. The SMS 2.0 Status system gives detailed status for your packages and advertisements, and you should use it first as a way to monitor the distribution. In SMS 2.0, you can get detailed package status and also advertisement status. For detailed information about using the status system, see the SMS 2.0 Administrator's Guide.

Also consult the SMS 2.0 Administrator's Guide for flow charts that show the steps for distributing an installation package, the files that are created, and troubleshooting tips. These flow charts can be used, along with diagnostic tools such as SMS Trace, to follow the distribution as it is completed.

Troubleshooting Tips and FAQ

This section includes information that might help you while troubleshooting problems with Office 2000 installations, and also includes questions and answers that frequently appear in discussion aliases and on customer visits.

The information in the previous section, "Monitoring the Installation," is useful for troubleshooting as well as monitoring. Use it along with the following tips to create a successful installation.

Troubleshooting Tips

The following are selected tips that might assist you if your installations fail.

Creating a Chained Setup

The Office 2000 Resource Kit contains an alternate version of Setup.exe that allows you to combine installations of Office 2000 with related installations such as the Office Disk 2. For more information, see "Chaining Installations" later in this white paper.

Troubleshooting the O2KSetup Installation Method

If the O2KSetup.exe script does not run correctly, troubleshoot it using the following instructions, beginning with the first, because they are arranged in order of likelihood.

First, look for the presence of the O2Kinstall.log in the Temp directory. If this file does not exist, then the script did not run.

Possible reasons:

The O2Ksetup.exe was not in your package directory. Make sure that this file exists in your source directory and the package directory on your distribution servers.
The account running the SMS package did not have access to the Temp directory. Check the Smsapm32.log for details.

If these steps do not pinpoint the problem, open the O2Kinstall.log in Notepad, if the log exists. This log shows you what phase the script was in when it failed. Compare this log to the example in "O2Kinstall.log File" later in this white paper. The log is easy to read and it should be easy to identify if and where the script encountered a problem.

Sometimes it might not be the script itself that failed but the Office 2000 Setup program instead. The Office 2000 Setup program creates two logs in the Temp directory that should be checked for errors. The first log to check is the OFFICE 2000 PREMIUM SETUP(XXXX).TXT, where XXXX is a four-digit number. This log shows whether you specified the wrong name for a transform file or you didn't include your transform file in the package directory. This log also shows you the Setup parameters that are being used and the distribution point for Office 2000. After Msiexec is successfully launched, this log stops.

The next log to look at is OFFICE 2000 PREMIUM SETUP(XXXX) _MSIEXEC.TXT. This is the log that Windows Installer produces. This log contains every action that Windows Installer performed on the client. The last line in the log tells you whether the installation succeeded or failed.

If you find that the installation failed in either of the Office 2000 logs, use the Office 2000 Resource Kit to interpret the error codes that you find in the logs.

Frequently Asked Questions

This section is a compilation of questions that appear frequently in discussion groups and at presentations.

What if I have already installed Office 2000, and I want to add another application to the installation, such as Microsoft® PowerPoint or Outlook?

You can do this as part of a staged deployment. You should accomplish the first stage by using a transform file and subsequent stages by calling an INI file (on the program) that adds components from the MSI database. The Word2000 PDF is for Microsoft® Word as a stand-alone application and should not be changed. When you add applications to your installation, do not use the PDFs for single applications, but instead use the PDF for Office applications and create a transform using the Custom Installation Wizard (CIW). The installation of applications and features of a product that is already installed (for example, Office Premium) can be triggered by using the program. This program could be sent using SMS 2.0 software distribution. For more information, see the Office 2000 Resource Kit documentation and the Office 2000 Resource Kit Readme.

What if I want to chain other applications, such as Office Disk 2? Can I add these to the installation?

An alternate version of Office 2000 Setup.exe is provided on the Office 2000 Resource Kit CD for assistance in chaining together Office and related installations. See the Readme.doc at the root of the Office 2000 Resource Kit CD for more information about using this version of Setup.exe.

Can I create Outlook Profiles while I am installing Office 2000?

You can create a batch file to set user environment variables for Outlook. Set these variables before you run the script that normally creates Outlook profiles (Newprof.exe). You can specify the environmental variables in one of several ways:

Modify the autoexec.bat file. You can use SMS software distribution for this.
In the CIW, on the Customize Outlook Installation Options page, modify or add environmental variables.
Add an Outlook.prf file containing your changes, or create a batch file. Add either of these files to your installation using the CIW.
Use the Environment tab of the Desktop Properties dialog box. From the desktop, right-click and select Properties to see the dialog box.

Advanced Office 2000 Installation

The previous sections of this white paper outlined a basic Office 2000 Premium installation with SMS 2.0. This section describes advanced installation options, including:

Resilient sources
Custom configurations
Load balancing and fault tolerance
Chaining installations

Resilient Sources

One reason you might use resilient sources is to provide greater fault tolerance. Normally, the path to the distribution point you use for installation servers is stored by default as a resilient source. But if servers go down, or if the space on the hard disk for the source files is needed for another use, the distribution point path is no longer available. By using the CIW or the SOURCELIST parameter at installation time, you can set up a list of sources for the program to use when it requires source files. Establishing resilient sources is more stable than merely using the distribution point path.

Note: For the latest information about resilient sources, see the Web site:

https://www.microsoft.com/Office/ORK/2000/default.htm

The resilient source list remains available throughout the period when Office 2000 is installed on the client computers. If Windows Installer needs to repair or load a file, it tries all the resilient sources. If none of them are available, the user is instructed to provide a path to the Office 2000 source files.

You must have the name of each server you want to use for resilient sources in order to use SOURCELIST.

The SOURCELIST parameter can be set up in either of two ways:

It can be a parameter of the Setup command line in the SMS software distribution program or the O2KSetup.ipf file.
It can be set up using the Custom Installation Wizard.

Tip If you use resilient sources that name specific shares, and you have more than one site in your hierarchy, you might need to create a separate transform, and then a separate SMS program within your package, for each site. This is true because the transform or command line parameter must be different if the server names are different for each site.

If you use the CIW, on the Identify Additional Servers page, enter the server names you want to use as resilient sources.

If you modify an SMS program in your batch file or IPF file, add the SOURCELIST=\\<server>\<share parameter>. For example:

setup.exe /qb- /wait REBOOT=ReallySuppress 
SOURCELIST=\\myserver\myshare1;\\myserver\myshare2 /m off2000

You can set up a single server or a list of servers as the source list.

If you don't have the names of all the server shares containing the administrative installation point, or if your organization is so large that it's not practical to use a list of server names, there is another option. Instead of a server name, you can use a mapped drive letter. This makes your installation flexible, and it means that you can use the same program to install on multiple sites. But it also means that administrators must make sure that the drive letters are always mapped to servers containing the source files in the specified directory. If you modify the program in the batch file or in the SMS Administrator console, add the SOURCELIST parameter like this:

setup.exe /Typical SOURCELIST=g:\Office;s:\Office

You can change the program directly, or in the O2KSetup.inf file.

Note: For continuing updates on resilient sources, see the following Web page:

https://www.microsoft.com/Office/Ork/2000/Default.htm

Custom Configurations

When you deploy Office 2000 to a large set of users, some users might require different configurations. When you have different configurations, you can create customizations and distribute only the features needed by each user in your organization. You have two choices in this situation:

Use an attended installation and let users choose their options.
Create a transform file for each set of users and use it in custom programs that are created in the SMS Administrator console after the package is created from the PDF.

When you create a set of programs within the package, you must:

Create a set of transform files. Give each file a unique name and be sure that the set includes all of your users.
Create a package by importing the PDF.
Create new custom programs for each transform file. Name the transform files in the program command line using the TRANSFORMS= parameter as directed later in this section.
Create advertisements for each collection of users.

If some of your users require only certain applications from Office 2000, for example only Word 2000, you can install the single application or a subset of applications using the administrative installation point. If you have a separate CD for the program you want, such as the stand-alone Word 2000, you can use it to install, and use the PDF file found in the Office 2000 Resource Kit. (For a list of such PDFs, see "Requirements" earlier in this white paper.) Remember that if some users need only Word while others need the entire Office 2000 Premium suite, the space required on distribution points and resilient sources will be smaller if you install both from the same source files.

Changing Installation Options

Many installation options are available with Office 2000. However, when you install Office 2000 using SMS, changing some installation options to the default Office Setup program (such as changing the user interface mode or removing parameters) might cause unwanted results when SMS installs Office 2000 on the client computer. For example, changing the UI mode might result in dialog boxes' being displayed to users who should not view them. You must fully test the customizations you make to the Office 2000 program in a lab environment, especially when you change installation options.

There are five installation options that you should be familiar with:

Table 7 Installation Options

Option	Description
/qn	No user interface at all. This option is useful for unattended installations.
/qr	Reduced user interface. This option might be useful for attended or unattended installations.
/qb-	Basic installation. There is no user interface except a progress monitor.
None	This option displays the entire user interface, as if you installed from the CD. It is the default when you do not specify any installation option for UI display. It is useful for attended installations.
/jm	Install on Demand. This option installs shortcuts to the installation programs of the components you specify. The first time the user clicks the shortcut icon, they are installed.

In general, stay as close as possible to the general defaults in the Office 2000 PDF file (Off9pre.sms). When you do make modifications, keep in mind that SMS should restart the computer after the office installation is complete. You should not change the following PDF key:

AfterRunning=SMSRestart

Using AfterRunning=SMSRestart ensures that the status MIF file that Office 2000 Setup writes will be properly interpreted by SMS. For the same reason, do not remove the REBOOT=ReallySuppress option from the command line.

Creating Customizations

When you create customizations, you can use the Custom Installation Wizard (CIW) to create a set of transform files for each customization.

Creating a Transform File

To create a transform file

Install the Office 2000 Resource Kit on your site server or on any other server or client where you can obtain the required files.
To open the Custom Installation Wizard, from the Start menu, point to Programs, Microsoft Office Tools, Microsoft Office 2000 Resource Kit Tools, and then click Custom Installation Wizard.
When the wizard prompts you for an MSI file on the Open the MSI File wizard page, browse to the data1.msi file in the top-level directory of your administrative installation point and select it. Then click Next.

Note: The MSI file contains all the installation instructions for Office 2000. The MST file is the transform file, created with the CIW that modifies the MSI file. After you apply an MST file to an MSI file you cannot apply another transform file, unless you reinstall Office 2000. You can install other Office 2000 applications after the first installation, but you must use command line parameters to do so.
When the wizard prompts you for an existing MST file, click Do not open an existing MST file, because you are creating a new transform file. To edit an existing MST file, click the other option, Open an existing MST file, and browse to the name of the existing file.
When the wizard prompts you for the name of the new MST file, enter a path to the top-level directory of your administrative installation point, using a UNC path or a relative path from the administrative installation point, and name the transform file.
Click Next.
Continue through the wizard, modifying the default behavior as necessary for your installation.

Tip If you decided on additional customizations, you can add them to the transform file as you go through the wizard, or you can edit the transform file later. For example, if you want to create a resilient source list, or create different customizations for different user groups, you can do so within the wizard.
Click Finish when you have created the transform file.

Recognizing a Transform File

After you create the transform file, you must add it to your Setup command line. Merely creating the transform file does not change your installation.

Make sure the transform file is in the top-level directory of your administrative installation point, and modify the program to include the TRANSFORMS= parameter. For example:

     setup.exe /qb- /wait TRANSFORMS="<Transform file name>.mst" 
     REBOOT=ReallySuppress

If you install Office 2000 from O2KSetup.exe, you must modify the script so that the transform name is correct. For more information, see "Preparing for O2Ksetup Installations" earlier in this white paper.

Load Balancing and Fault Tolerance

When you use SMS to distribute Office 2000, SMS attempts to balance the load when it selects the distribution point that a specific client connects to for installations. In some ways, the administrator also contributes to load balancing by selecting collections and distribution points for an installation. For example, if you choose to install Office 2000 to 10,000 users simultaneously, you will probably be creating stress on your network. SMS provides tools for simulating your network traffic and estimating the results of such actions. For more information, see Chapter 11, "Configuring and Populating Pilot Sites," in the SMS 2.0 Resource Guide, part of the BackOffice 4.5 Resource Kit.

After you install Office 2000, there is additional stress to the system as installations are repaired and Install on Demand features are installed. You can provide greater balance for the load by providing additional resilient sources for installation of these components rather than just the installation distribution point.

Fault tolerance for Office 2000 installations consists largely of keeping the Office 2000 source files available to all users after an initial installation. For more information, see "Resilient Sources" earlier in this white paper.

Chaining Installations

When you install Office 2000 with SMS, you might want to also install Office 2000 Disc 2 or some other program at the same time. There are two options:

You can use SMS dependent programs.

To use SMS dependent programs, create a program for the application you want to install last, then create a second program for the application you want to install first, and make the second program dependent on the first. In that way, when you try to install the main (last) program, it checks to see if the dependent (first) program has been run, and if not, SMS runs it.

You can use the Office 2000 Custom Installation Wizard.

The Custom Installation Wizard in the Office 2000 Resource Kit can run additional installations after Office 2000 has been installed. For example, within the wizard you can specify that Office 2000 Disc 2 Setup is performed after Office 2000 Disc 1 setup is completed. The additional programs you select are launched after the post-reboot portion of Office 2000 setup is completed. If you choose this option, be sure to use the chained version of Office 2000 Setup.exe, which is on the Office 2000 Resource Kit CD.

Appendix

This appendix includes the following topics:

The Off9pre.sms file
The O2KSetup.ipf file

PDF for Office 2000

This section provides the text of the Off9pre.sms file included on the Office 2000 CD and tells you how to change it. It also gives you some information about installing selected features of Office 2000.

Text of Off9pre.sms File

[PDF]
Version=2.0
[Package Definition]
Publisher=Microsoft
Name=Office 2000 Premium
Version=9.0
Language=English
Programs=Typical, Custom, Manual, Uninstall
MIFVersion=ENG Office Premier Ship
[Typical]
Name=Typical
CommandLine=setup.exe /qb- /wait REBOOT=ReallySuppress /m off2000
AdminRightsRequired=True
UserInputRequired=False
DriveLetterConnection=False
AfterRunning=SMSRestart
CanRunWhen=AnyUserStatus
SupportedClients=Win NT (I386), Win 9x
Win NT (I386) MinVersion1=4.00.0000.0
Win NT (I386) MaxVersion1=4.00.9999.9999
Win NT (I386) MinVersion2=5.00.0000.0
Win NT (I386) MaxVersion2=5.00.9999.9999
Win 9x MinVersion1=0.00.0000.0
Win 9x MaxVersion1=99.99.9999.9999
[Custom]
Name=Custom
CommandLine=setup.exe /qb- /wait
 TRANSFORMS="New Custom Setup File.MST"
  REBOOT=ReallySuppress /m off2000
AdminRightsRequired=True
UserInputRequired=False
DriveLetterConnection=False
AfterRunning=SMSRestart
CanRunWhen=AnyUserStatus
SupportedClients=Win NT (I386), Win 9x
Win NT (I386) MinVersion1=4.00.0000.0
Win NT (I386) MaxVersion1=4.00.9999.9999
Win NT (I386) MinVersion2=5.00.0000.0
Win NT (I386) MaxVersion2=5.00.9999.9999
Win 9x MinVersion1=0.00.0000.0
Win 9x MaxVersion1=99.99.9999.9999
[Manual]
Name=Manual
CommandLine=setup.exe /wait REBOOT=ReallySuppress /m off2000
UserInputRequired=True
AdminRightsRequired=True
DriveLetterConnection=False
AfterRunning=SMSRestart
SupportedClients=Win NT (I386), Win 9x
Win NT (I386) MinVersion1=4.00.0000.0
Win NT (I386) MaxVersion1=4.00.9999.9999
Win NT (I386) MinVersion2=5.00.0000.0
Win NT (I386) MaxVersion2=5.00.9999.9999
Win 9x MinVersion1=0.00.0000.0
Win 9x MaxVersion1=99.99.9999.9999
[Uninstall]
Name=Uninstall
CommandLine=setup.exe /qb- /wait REBOOT=ReallySuppress /m off2000 /x
AdminRightsRequired=False
UserInputRequired=False
DriveLetterConnection=False
AfterRunning=SMSRestart
CanRunWhen=AnyUserStatus
SupportedClients=Win NT (I386), Win 9x
Win NT (I386) MinVersion1=4.00.0000.0
Win NT (I386) MaxVersion1=4.00.9999.9999
Win NT (I386) MinVersion2=5.00.0000.0
Win NT (I386) MaxVersion2=5.00.9999.9999
Win 9x MinVersion1=0.00.0000.0
Win 9x MaxVersion1=99.99.9999.9999

O2KSetup.ipf File

This section explains the functions and syntax for the O2KSetup.inf SMS Installer file. It gives an example of this file. For instructions on how to change this file, see "Installing Without Administrative Rights" earlier in this white paper.

Security Tip After you have modified the IPF file, it contains a logon and password that allows anyone to have administrative access to your client accounts. You should keep it on a secure share or destroy it directly after the .exe file is compiled, in order to protect the password of the Administrative account. Also, you might want to create a new account just before installation and then disable it immediately after the installation is complete for all clients.

Script Overview

This script was written to accommodate software installations where an administrator on the local computer must install the software, and the same administrator must log on to the computer after the installation is complete so that critical parts of the operating system can be updated.

The script accomplishes this by specifying an account that has local administrative rights to the computer and has access to the SMS distribution server.

The script has three phases:

SMS copies the script executable file and the Shutdown.exe file to the client. A reboot occurs.
The administrator account from the script is logged on, and the installation occurs. A reboot occurs.
Critical parts of the operating system are updated, and the computer is returned to its original state.

Preparatory Phase

The preparatory phase is called phase null. The script reads the OFFK2NT_PHASE is set to "" then this phase begins.

The script then determines whether the INST variable contains a colon or not. If there is a colon, then this package is from an SMS 1.2 server. The information contained in the %inst% variable is parsed. The variable is stored in the client's registry of the client for later use by the program.

If there is no colon, then this package is from an SMS 2.0 server. SMS 2.0 has the option of installing software from a UNC path, and it must be set up this way to install Office 2000. The script parses the value in the INST variable and stores it in the registry of the client.

The script then copies O2KSetup.exe and Shutdown.exe from the distribution point to the System32 directory on the client. The script then checks for the existence of Shutdown.exe, and stops if this file does not exist in the System32 directory.

The script then gathers current user information and stores it in the registry so the current user state can be restored when installation completes. Next, the auto-admin logon keys are set so that, when the computer reboots, the administrator account specified in the script will automatically log on to the computer to allow installation to continue.

The mouse and keyboard are disabled so that, users do not have access while the administrator is logged on to the computer.

Note: Users do not lose access to the computer until after the first reboot.

The installation path, obtained from either the pcmunc variable (SMS 1.2) or the inst variable (SMS 2.0) is written to the registry. O2KSetup.exe is written to the Run section of the registry so that the script runs when the administrator logs on. The OFF2KNT_PHASE value is changed to 1 and Shutdown.exe is called to reboot the client.

This completes the preparatory phase.

Note: The text in the following report has been wrapped for clarity.

Rem THIS IS WERE THE SCRIPT ACTUALLY STARTS
Rem ****************ADD IN DOMAIN SPECIFIC INFORMATION HERE**************************
Rem ****************SET DOMAIN ADMIN ACCOUNT NAME HERE*******************************
Set Variable SVCACCT to MyAdmin
Rem ****************SET DOMAIN ADMIN'S ACCOUNT PASSWORD******************************
Set Variable SVCACCTPW to MyPassword
Rem ****************SET DOMAIN NAME HERE*********************************************
Set Variable DOMAIN to MyDomain
Rem ****************SPECIFY A CUSTOM SETUP TRANSFORM*********************************
Rem ****************FOR EXAMPLE: TRANSFORMS="New Custom Setup File.mst***************
Set Variable TRANSFORMS to 
Rem *********************************************************************************
Continue/Start writing to installation log
Get Registry Key SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon place in Varia
If OFF2KNT_PHASE Equals "" then
   Rem                     THIS PHASE IS RUN FIRST IN THE CONTEXT OF A DOMAIN ADMIN A
   Add "This is where the script begins. Phase=Null" to INSTALL.LOG
   Add "*****************************************************************************
   Add "*****************************************************************************
   If INST Contains ":" then
      Rem A mapped drive was detected, assuming that we're running on SMS 1.2
      Rem We will get the path to the source from the PCMUNC Variable
      Get Environment Variable PCMUNC into Variable OFF2KNT_PATH
      Add "PHASE=Null  Mapped Drive source detected, getting install path from PCMUNC
   Else
      Rem A mapped drive was not detected, assuming that we're running on SMS 2.0
      Set Variable OFF2KNT_PATH to %INST%
      Add "PHASE=Null  UNC Source detected, Path to source from INST="%OFF2KNT_PATH%"
   End Block
   Get Environment Variable windir into Variable WINDIR
   Copy local file from %INST%\shutdown.exe to %SYS32%\shutdown.exe
   Copy local file from %INST%\O2kSetup.exe to %SYS32%\O2kSetup.exe
   Add "PHASE=Null   Checking for %SYS32%\Shutdown.exe, if absent
   we'll abort before 
   Check If File or Directory doesn't exist %SYS32%\shutdown.exe
   Add "PHASE=Null  %SYS32%\Shutdown.exe, is present, proceeding " to INSTALL.LOG
   Get Registry Key SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon place in Va
   Rem We stop writing to log here for security reasons
   Stop writing to installation log
   Edit 6 registry keys
   Rem NTFS Locked down systems may have a key "DontDisplayLastUserName" set, we'll d
   Registry Key SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon = 0
   Continue/Start writing to installation log
   Add "PHASE=Null  Autoadmin login & path to source files set in reg" to INSTALL.LOG
   Rem DISABLE KEYBOARD and mouse, enable AutoAdminLogon, and WRITE SETUP PHASE # to 
   Edit 2 registry keys
   Add "PHASE=Null  Mouse & Keyboard disabled" to INSTALL.LOG
Registry Key SOFTWARE\Microsoft\Windows\CurrentVersion\Run = %SYS32%\O2KSetup.exe
   Registry Key SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon = %OFF2KNT_PATH
   Get Registry Key SOFTWARE\Microsoft\Windows\CurrentVersion\Run place in Variable R
   Get Registry Key SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon place in Va
   Add "PHASE ""  Wrote %OFF2KNT_PATH%\ to OFF2KNT_PATH, Wrote "%RUNKEY%" to the run 
   Rem  Since the admin may be a new user to the client, we're disabling the welcome.
   Get Environment Variable WINDIR into Variable WINDIR
   Rename %WINDIR%\Welcome.exe to Welcome.old
   Search for file welcome.old in Path and place into Variable WELCOMEOLD
   Search for file welcome.exe in Path and place into Variable WELCOMEEXE
   Add "PHASE ""  Renamed Welcome.exe. Welcome.old: "%WELCOMEOLD%", Welcome.exe: "%WE
   Add "PHASE ""  Calling Shutdown.exe" to INSTALL.LOG
   Execute %SYS32%\SHUTDOWN.EXE /L /R /T:10 "Office 2000 Setup is shutting down this 
End Block

Phase 1

During this phase, the actual installation of Office 2000 takes place. After the administrator logs on to the computer, the script checks the value of OFF2KNT_PHASE in the registry and determines that this is Phase 1. The auto-admin logon keys are reset to perform another login after the reboot. The script next sets OFF2KNT_PHASE to 2. The script then uses the UNC path (from the registry key where it was stored during phase null) to call the Office 2000 Setup program. The script waits for Office 2000 Setup to be completed, and then Shutdown.exe is called again to reboot the computer.

Note: The Office 2000 Setup is run from the same distribution point where phase null was executed.

This completes phase 1.

If OFF2KNT_PHASE Equals "1" then
   Rem                     THIS PHASE IS RUN SECOND IN THE CONTEXT OF SVC ACCT
   Rem                     MACHINE WILL AUTOLOGON WITH MOUSE & KEYS DISABLED. 
   Rem                     AFTER REACHING THE SHELL, SETUP WILL LAUNCH FROM THE RUN K
   Rem                     AFTER SETUP COMPLETES WE RUN SHUTDOWN.EXE AND REBOOT AGAIN
   Add "*****************************************************************************
   Add "*****************************************************************************
   Add "PHASE=1  Entering Off2KNT_PHASE %OFF2KNT_PHASE%" to INSTALL.LOG
   Get Registry Key SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon place in Va
   Add "PHASE=1  Got %OFF2KNT_PATH%\ from OFF2KNT_PATH, resetting AutoAdmin Logon & c
   Rem CHANGE PHASE to 2 and reseting AutoAdminLogon
   Stop writing to installation log
   Edit 4 registry keys
   Continue/Start writing to installation log
   Execute %OFF2KNT_PATH%\setup.exe /qb- /wait REBOOT=ReallySuppress /m off2000 %TRAN
   Add "Executing %OFF2KNT_PATH%\setup.exe /qb- /wait REBOOT=ReallySuppress /m off200
   Add "PHASE=1  Finishing Off2KNT_PHASE=1, setup should have finished, calling shutd
   Rem Strong Shutdown to get around anything from the startup group
   Execute %SYS32%\SHUTDOWN.EXE  /L /R /Y /T:10 "Office 2000 is shutting down this sy
   Exit Installation
End Block

Phase 2

During this phase, critical parts of the operating system are updated. After the administrator logs on to the computer (automatically, as the auto-admin logon keys are set), the O2KSetup.exe script executes again from the Run section of the registry. This time, the script checks the value of OFF2KNT_PHASE in the registry to determine that this is phase 2. The registry values that existed prior to the installation are restored, and the mouse and the keyboard are enabled. Shutdown.exe is again called to reboot the computer for the last time. The O2KSetup.exe file deletes the Shutdown.exe file and the computer reboots.

This completes phase 2.

If OFF2KNT_PHASE Equals "2" then
   Rem                     THIS PHASE IS RUN THIRD IN THE CONTEXT OF SVC ACCT
   Rem                     MACHINE WILL AUTOLOGON WITH MOUSE & KEYS DISABLED. 
   Rem                     AFTER REACHING THE SHELL, SETUP WILL LAUNCH FROM THE RUN K
   Rem                     AFTER SETUP COMPLETES WE RUN SHUTDOWN.EXE AND REBOOT AGAIN
   Add "PHASE=2  Got %OFF2KNT_PATH%\ from OFF2KNT_PATH, changing phase to "" for fina
   Add "*****************************************************************************
   Add "*****************************************************************************
   Get Registry Key SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon place in Va
   Rem Stop writing to log for security reasons.
   Stop writing to installation log
   Edit 5 registry keys
   Continue/Start writing to installation log
   Rem Re-enable "DontDisplayLastUserName" (NTFS Locked down systems only)
   Rem UN-REMARK NEXT LINE TO SET "DontDisplayLastUserName" TO " 1 "
   /* Registry Key SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon = 1
   Rem REMOVE AUTOLOGON; ENABLE KEYS & MOUSE
   Edit 2 registry keys
   Registry Key SOFTWARE\Microsoft\Windows\CurrentVersion\Run = 
   Add "PHASE=2  Disabled autoadmin logon and turned keyboard / mouse back on. About 
   Get Environment Variable WINDIR into Variable WINDIR
   Rename %WINDIR%\Welcome.old to Welcome.exe
   Execute %SYS32%\SHUTDOWN.EXE /L /R /T:30 "Office 2000 setup is shutting down this 
   Delete File(s) %SYS32%\shutdown.exe
   Add "O2KSETUP SCRIPT COMPLETED " to INSTALL.LOG
   Exit Installation
End Block

O2Kinstall.log File

If the installation does not proceed as planned, look in "Troubleshooting Tips and FAQ" earlier in this white paper. The O2Kinstall.log file records all the steps in the installation and gives valuable information about an installation that has failed. Following is an example of this log to compare with the log from a failed installation:

This log is from an SMS 2.0 client.
_**  Installation Started 2/8/99 5:09:19  **_
Title: O2kSetup
Source: E:\B2800002\O2KSetup.EXE
This is where the script begins. Phase=Null
_*************************************_
PHASE=Null  Mapped Drive source detected, getting install path from PCMUNC=
"\\B28TB\SMS_PKGE\B2800002\File Copy: C:\WINNT\System32\shutdown.exe
File Copy: C:\WINNT\System32\O2kSetup.exe
PHASE=Null   Checking for C:\WINNT\System32\Shutdown.exe, if absent
we'll abort before setting automated install settings 
PHASE=Null  C:\WINNT\System32\Shutdown.exe, is present, proceeding 
PHASE=Null  Autoadmin login & path to source files set in reg
RegDB Key: SYSTEM\CurrentControlSet\Services\Kbdclass
RegDB Val: 4
RegDB Name: Start
RegDB Type: 3
RegDB Root: 2
RegDB Old: 1
RegDB Key: SYSTEM\CurrentControlSet\Services\Mouclass
RegDB Val: 4
RegDB Name: Start
RegDB Type: 3
RegDB Root: 2
RegDB Old: 1
PHASE=Null  Mouse & Keyboard disabled
RegDB Key: SOFTWARE\Microsoft\Windows\CurrentVersion\Run
RegDB Val: C:\WINNT\System32\O2KSetup.exe
RegDB Name: OFF2KNT_RUN
RegDB Root: 2
RegDB Key: SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
RegDB Val: \\B28TB\SMS_PKGE\B2800002\RegDB Name: OFF2KNT_PATH
RegDB Root: 2
PHASE ""  Wrote \\B28TB\SMS_PKGE\B2800002\\ to OFF2KNT_PATH, Wrote 
"C:\WINNT\System32\O2KSetup.exe" to the run key, about to reboot, Set 
Default User to "smsadmin"
PHASE ""  Renamed Welcome.exe. Welcome.old: "
C:\WINNT\welcome.old", Welcome.exe: ""
PHASE ""  Calling Shutdown.exe
_**  Installation Started 2/8/99 5:11:45  **_
Title: O2kSetup
Source: C:\WINNT\System32\O2KSetup.exe
_*************************************_
PHASE=1  Entering Off2KNT_PHASE 1
PHASE=1  Got \\B28TB\SMS_PKGE\B2800002\\ from OFF2KNT_PATH, resetting 
AutoAdmin Logon & changing phase to 2
Executing \\B28TB\SMS_PKGE\B2800002\\setup.exe /qb- /wait REBOOT=ReallySuppress /m off2000 
PHASE=1  Finishing Off2KNT_PHASE=1, setup should have finished, calling 
shutdown.exe
_**  Installation Started 2/8/99 5:43:24  **_
Title: O2kSetup
Source: C:\WINNT\System32\O2KSetup.exe
PHASE=2  Got \ from OFF2KNT_PATH, changing phase to "" for final phase
_*************************************_
RegDB Key: SYSTEM\CurrentControlSet\Services\Kbdclass
RegDB Val: 1
RegDB Name: Start
RegDB Type: 3
RegDB Root: 2
RegDB Old: 4
RegDB Key: SYSTEM\CurrentControlSet\Services\Mouclass
RegDB Val: 1
RegDB Name: Start
RegDB Type: 3
RegDB Root: 2
RegDB Old: 4
RegDB Key: SOFTWARE\Microsoft\Windows\CurrentVersion\Run
RegDB Val: 
RegDB Name: OFF2KNT_RUN
RegDB Root: 2
RegDB Old: C:\WINNT\System32\O2KSetup.exe
PHASE=2  Disabled autoadmin logon and turned keyboard / mouse back on. 
About to reboot again. Run Key Shows ""
O2KSETUP SCRIPT COMPLETED