Deploying Office 2000 from Command Lines
Chapter 1 helped you choose the best deployment methods for the different demographics in your organization. No matter which method you're using, whether you deploy Office 2000 from logon scripts or SMS, you're in the business of pushing command lines. If you customize your transforms and Setup.ini files appropriately, your command line should be nothing more than Setup.exe or possibly something similar to Setup.exe /settings sales.ini. You can specify the transform and user-interface level in Setup.ini.
One particular scenario is useful if you're deploying Windows 2000 from a network share using an answer file. You can run Office 2000's Setup program at the end of the Windows 2000 setup process. That is, you can instruct Windows 2000 to install Office 2000 after the installation of Windows 2000 itself is finished. To do that, add the [GuiRunOnce] section to your answer file. Within that section, add the command to run Office 2000's Setup program. For example, the following addition would automatically install Office 2000 the first time a user logs on to the computer:
[GuiRunOnce]
\\Server\Share\Setup.exe /settings Sales.ini
If you want to install Office 2000 automatically by logging on as administrator, add the following lines to your answer file:
[GuiRunOnce]
\\Server\Share\Setup.exe /settings Sales.ini
[GuiUnattended]
AdminPassword=*
AutoLogon=Yes
AutoLogonCount=1
This approach has a drawback in that you must put the local administrator's password in the answer file. The benefit is that you don't need for a user to log on to the computer before Office 2000 is installed. Another benefit is that Office 2000 will install per machine rather than per user, since it's installing from the Administrator account. Per-machine installations are preferable to per-user installations, since they make Office 2000 available to all users who log on to the computer.