MSI File creation

  • Thread starter Thread starter wedmonds
  • Start date Start date
W

wedmonds

Hi People,

I am attempting to create an .msi file that i will then assign via
Group Policy to specific OU. e.g so that one group receives Excel and
another group receives Excel & Outlook.

I have the Winstall directory shared and also have installed the setup
files from office via the setup.exe /a.

I have been able to log onto my clean machine and run discoz.exe from
the command line and done the first snapshot as administrator. All
works fine.

I have been able to then run setup from my clean machine from the
command line and installed the application required ( in this case
Word ). Then tested the application and confirmed all as working.

I have been able to log onto my clean machine and run discoz.exe once
more to perform the after snapshot, again without any problems.

This left me with an MSI file of my creation in the shared directory.

I then assign this MSI file to the approriate group and logged in with
an approriate user in that group.

The user in question logs on and receives the approriate application
and it all appears to be ok. HOWEVER, when attempting to execute the
application the install screen appears, completes & then nothing
happens.

When looking at the event log you are provided with two entries within
the "application log" which states an event ID of 1001. Along the
lines of
Detection of product {99E0b3 bla blah blah } feature 'WIFEAT000000004'
failed during request for component'

If anyone out there has any thoughts on this i would welcome there
input as i am willing to try anything at this moment in time.

Many Thanks all


Mr Edmonds
 
To deploy Office you should use the Office XP or 2003 Resource Kit. It is
very simple. You just:
- Create a network distribution point by running setup /a
- Use Custom Installation Wizard to create a Transform for each of the ways
you want to deploy it
- Create a user or computer group for each deployment
- Create a policy with the software package plus modification (Transform)
and set the ACL on the policy to apply to the group you want (and remove
Authenticated Users so it does not apply to all)
I have found it best to make the least possible modications to the standard
installation.
Anthony
 
Back
Top