Jump to content

Unattended installation of Office 2000


aviram

Recommended Posts

Hi everybody

I'm working on a DVD which includes some versions of OS's and also Office 2000, XP and 2003.

After bad experience with Administrative installations (I had problems to update from the web after installing using administrative sharepoints), I decided to install the office versions part after part.

(for instance: office 2000 installation: Unattended installation of Office 2000, then SR-1 update, then SP3 update and then all post-SP3 updates).

I'm having some problems with this:

1. Unlike Office 2003's CIW, the CIW of Office 2000/XP does not allow you to integrate the product key into the MST file, and as a result after installing the office, in the first open of an office application I'm required to enter the product key and company name.

2. Office 2000 SR-1 update installation doesn't WAIT - which means even if I'm using "start /wait" before the setup file, the update is running and letting the batch file continue to the next step (SP3 installation) before SR-1 update was finished, and then I'm getting an error message.

I would very appreciate if anyone can advice.

Thanks in advance,

Aviram.

Link to comment
Share on other sites

  • 3 months later...

As the above post states. Do an Administrative install (Setup.exe /a). This will create your admin point. After this edit the setup.ini file to include your serial, company and name. Example,

; Microsoft Office 2000 Windows installer setup.exe information file.
; If a file exists in the same directory as setup.exe named "setup.ini", or
; /settings <path to ini file> is passed on the command line, that file will
; be read and modify the default behavior of setup as shown below.

[MSI]
; If a value is present, the MSI section gives the name of the MSI file to install.
; This file must be in the same directory as setup.exe, and both must be in the root
; of the installation tree.
; If no value is present, setup.exe will look for exactly one file matching "*.msi"
; in its directory and if found, use that.
;
MSI=data1.msi

[MST]
; If a value is present, the MST section gives the full path to a transform to apply.
; Specify it in the form MST1=path to MST
; Remember to uncomment both the section name and the value names.
;
;MST1=\\server\share\some transform.mst
;MST1=D:\transforms\my transform.mst
MST1=H:\O2K\D1\Setup1.MST
;MST1=file-server\applications\O2K\D1\Setup1.MST

[Options]
; If a value is present, the [Options] section gives the values of properties to apply to
; this installation. Specify them in the format:
; PropName=PropValue
; Remember to uncomment both the section name and the value names.
;
;USERNAME=Customer
USERNAME=Why Do You Need To Know
COMPANYNAME=Home
PIDKEY=Serial Number Here xxxxxxxxxxxxxxxxxxxxxxxxx
INSTALLLOCATION=H:\O2K\Office

[Display]
; If a value is present, the [Display] section overrides default UI modes.
; Display has one of the following values:
; quiet, none, basic, reduced, full
; CompletionNotice - if this value is present gives whether or not to display
; a setup completion noticefor otherwise quiet setups. The completion notice will
; only appear if Setup does not need to reboot to complete the installation.
; Remember to uncomment both the section name and the value names.
;
Display=None
CompletionNotice=NO

[Logging]
; If a value is present, the logging section provides default logging information.
; There are three possible values, all are optional and have defaults as shown below
;
; Value Default Description
; Type <none> Logging mode to use, e.g. ea
; Use * to get all logging modes; + to append to the
; logfile if it exists.
; Path %TEMP% Path to create logfiles in. May contain environment variables.
; Final component may be non-existent and will be created.
; Template SetupLog(*).txt File name for log file. May contain environment variables.
; Should end in "(*).txt"; the * is replaced with a zero-padded
; 4 digit number to make the file name unique.
;Type=icewarmup
;Path=\\OfficeServer\logfiles\
;Template=Office %UserName%(*).txt
Template=Office 2000 SR-1 Premium Setup(*).txt
Type=piwae

In the serial number DO NOT use the "-" group all serial number keys together and that should work. You will also need to change the file paths, as mine are for my setup and will not work under your system. The MST is used with Office tools to create a "CUSTOM" install which can be found here.

http://office.microsoft.com/en-us/assistan...1383061033.aspx

As far as the updates for an admin install there's info all over for that.

Good Luck

jd

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...