3 Replies Latest reply on Jan 2, 2008 5:24 AM by map

    Problems packaging Office 2007

    MedSol Rookie
      I am having issues with packaging office 2007 since the setup.exe needs to be launched with an msp file instead of the traditional MSI\Transform installation. 

      I created a custom msp file for office 2007 enterprise and setup a custom config.xml.  I stored the source files in a netinstall project database so that i could just use an execute script to install it using TUS like any other package i would create.  After adding a test computer to the correct security group for the project, I can fast install it, but it will not autoinstall when I login to the test PC.

      I really do not want to use Netinstall Spy since it uses MSI packages, but I can't seem to get the execute script to kick off.  Any suggestions?
        • 1. Re: Problems packaging Office 2007
          map Specialist

          if fastinstall works but autoinstall doesn't, that gives a few hints.

          fastinstall working means that paths in the install script are correct and all the necessary files are where they should be. That is a good start.

          The difference between fastinstall and an autoinstall on a testmachine is merely in the targetting. For Autoinstall, you need an autoinstall permission set and an autoinstall schedule, for fastinstall interactive permission and schedule are sufficient.

          A common pitfall is also to test on the same machine that you already fastinstalled the same package on... (without reverting it) - if NetInstall has already marked the product as installed, Autoinstall won't install it again!

          A look in the client's autoinstall logfile (niai32.log) should reveal details too. Make sure you have the clients logfile level set to "debug" (0), this can easiest be done using the netinstall monitor (nimoni.exe) on the client.

          Oh, and its a bad idea to repackage MS Office (>2000) using spy. Though it is possible to repackage MSIs, its not recommended as it requires a lot of inside knowledge. The MSI works very nice, and it is best practice to pick for each product the method that works best...
          • 2. Re: Problems packaging Office 2007
            MedSol Rookie
            Thanks for the response, but my issues with office 2007 are rather unique.  With office 2003, you could target an MSI package and supply a transform file from the office resource kit.  With office 2007, Microsoft chose to give each application a separate msi file and have the installing technician use the setup.exe with a supplied .msp file and config.xml for the correct suite (office 2007 enterprise for us). 

            Normally i would just use the MSI package tool in netinstall 5.8, but it can't target .exe files.   As a work around, i decided to use the netinstall script editor to execute the .exe file using the service account.  I then created an AD group with autoinstall and interactive install permissions.  It is fast installing correctly, as well as, interactive installing correctly.

            Is there a limitation with using autoinstall for scripts that have no other package data?
            • 3. Re: Problems packaging Office 2007
              map Specialist

              using the execute command with the setup.exe is absolutely the way to go.
              There are no restrictions whatsoever for what commands you can use inautoinstall scripts. Only if you use the service to install, you can't have packages that try to interact with the user by message boxes etc.

              please check the logfile to find out whether the package does not start at all, which would hint to
              o autoinstall permisson
              o autinstall schedule/package already installed; or does start but not end, which would hint to the setup trying to interact with the user (which doesnt work for the service).

              As the logfiles are excellent, there's really no need to start a guessing game...