Ghost Solution Suite

 View Only

  • 1.  AI Builder and MS Office

    Posted May 31, 2007 12:53 PM
    This is probably something simple, but I haven't found an answer here in the forum.  I am using GSS 2.0. AI Builder to create our software packages.  I install office (or any single component)  launch and configure the application before comparing and building the install.  When I deploy the package, I receive a message asking for the disk to install components for the user.  How do I get around this?

    Thanks for any help --
    Judy


  • 2.  RE: AI Builder and MS Office

    Posted May 31, 2007 05:53 PM
    Someone here can probably give you a more specific answer. Meantime, I can point you in the right direction.

    By default, during installation, Office creates an installation source directory. You can disable it by choosing to 'remove files used for installation'. When a new user starts Office, access is required to this directory. This directory can be network hosted if required to save space on your clients.

    I'd guess there are two or three possible scenarios which would lead to this message.

    This page and the links from it should allow you to determine and resolve the isssue.

    Let us know how you get on.

    Thanks,
    Xan



    Message Edited by Xan Todd on 06-01-200711:04 AM



  • 3.  RE: AI Builder and MS Office

    Posted Jun 06, 2007 10:44 AM
    Judy, actually if you are using Office 2003, they way around it is to package it without the service pack.  Then run the service pack afterwards and you will be fine.


  • 4.  RE: AI Builder and MS Office

    Posted Jun 06, 2007 11:13 AM
    Matt and Xan,

    Thank you for your responses.  I am still working on this.  I haven't gotten to the Office 2003 package yet.  I am still working with the Office XP. I started all over and packaged just office.  It installed fine.  I ran SP3 and packaged the program and found the same thing that Matt stated -- it is the service pack that confuses things.  I created a slipstream disk with SP3 and tried creating a package that way.  It worked for the entire office package, but not when I tried to create packages for each separate component.  I am going back to my original image and including the slipstream package on that image before I sysprep and close it.  That way I will have the files on each image.  We have enough space on our machines, but this isn't an optimal solution.

    I'll send an update.


  • 5.  RE: AI Builder and MS Office

    Posted Jun 06, 2007 03:50 PM
    Judy,
     
    I was able to package Office XP fine, I did slipstream the service pack into the install and was able to package it without any problems.  However, with Office 2003, unless your users all have admin rights, slipstreaming will not work.  It will keep asking for creditals everytime a non-admin launches the program.  The only way I found around this was to package without the service pack then run it afterwards.  What i did was just copy the service pack to the hard drive as park of the package, then in my task did a remote command after the package was deployed.  Hope this helps.
     
    Later
    Matt