Hi Fletch,
This one is a long one, sorry
You do not need that long setup command line.
If you place your mst file in the same dir of the msi file (Which is the
recomended way), simply change the setup.ini/setuppro.ini file. The file
resides in ..\FILES\SETUP
In there locate the [MST] section and change the name of the mst file name
to match yours.
Simply running setup.exe without anything else will do.
It automatically calls setup.ini to read the install instructions.
You may have problems then, that are related to relative paths of the
install files so here is what i usually do:
It goes without saying that this will work only with Enterprise/Volume
license media and CDkey...
Server Side:
-----------------
On a file server you normally use, that might be already mapped to users,
make sure this is your directory structure (example):
D:\Apps\Office\Office2003\ <- in here lies the admin point.
Both MSI and MST should be in it. This structure is needed mainly
for security reason.
D:\Apps should be shared, and then mapped as a drive, say P:
so users will see this:
P:\office\office2003
Using a mapped drive is better in this case, as any MSI install records the
original location from where is was installed and then looks for that
location in cases where a reinstall is requested or it needs install source
to fix itself.
Thus if at a later point the original file server that hosted the admin
point is not available, all you need to do is to copy the entire admin point
to another server and simply map the same drive letter to the new server.
If the installation isnt done from a mapped drive, then the user will have
to direct to the new install point (that might be an issue) or youll need a
script to add/change the source location in the registry for each station.
With correct planning you can even overcome this one, In the MST file you
can add install locations, so you can add P:\Office\Office2003 and also
\\Server\Apps\Office\Office2003 thus giving Office better resiliency in
finding the paths and you can even enhance that by creating 2 admin points on
2 servers, and add both locations in the MST file, as long as you remember
the paths should be the ones the end user will see from his station. This is
usually the scenario with big companies that have dispersed file servers and
want the minimize bandwidth consumption by directing users to the closest
file server (using Windows DFS also helps in this case).
In your MST file, make sure you added the NOUSERNAME=True property.
You can also use this property on the command line, so youll not have to
create 2 identical MST files, one for Ghosting an Image and one for normal
use (If you have stations you only want Office 2003 installed on their
existing OS).
More info:
http://www.microsoft.com/office/ork/2003/two/ch5/DepC05.htm
Last thing, edit the setup.ini to include full paths, both uder the MSI
and the MST sections. Use the drive letter for this.
Pre-Ghosted station side:
-------------------------------
Make sure the Drive P: is mapped
Run setup.exe -> P:\Office\Office2003\Setup.exe
You can also add the NOUSERNAME property as discussed above.
(use the newer version of enterprise setup.exe)
Do NOT open any Office application after setup finishes.
Run sysprep, with your custom sysprep.inf, and immediatly after it restarts,
use a GHOST floppy (with or without network) you created to take a GHOST of
the station.
I would recommend you use the Ghost enterprise product (7.5+) as it holds
much more then simple GHOST.
Print this (it is long...), read and then execute.
Safe deployment !
Arie H.
