Jump to content

dangermouse

Member
  • Posts

    3
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

About dangermouse

dangermouse's Achievements

0

Reputation

  1. This worked perfectly for me, although I made the schoolboy error of putting the dashes into the product code the first time I wrote the batch file!! Having fixed that issue, the installer works perfectly, although as I'm on OEM media, I seem to be unable to slipstream the service packs in.
  2. You are the man... I searched for a previous topic but didn't find it. The only query I have is that the document that you link to reference the slipstream install is the one that states that I can't slipstream with OEM software - I guess I'm scuppered with that then?
  3. Hi Forum members, I normally don't like to post so soon after joining a forum, but this is somewhat of an emergency so I hope you'll forgive me. My situation is this: I am trying to automate the installation of Office 2003 onto a number of workstations using an mst file. I have created said transform file using the Office resource kit, and tested it - it works fine, however... The MST file I built to test the install included the office product key. since we buy OEM software, I can't do this for all my installs, I therefore need to setup the transform file so that it prompts for the CD Key the first time the software is run. I am also trying to get the installer to apply the service pack at the same time by adding its location into the additional programs to install field of the mst file, but although the mst file size increases to 110mb, the service pack isn't installed. Any gurus able to help me out - virtual pints shall be yours!!
×
×
  • Create New...