/build/static/layout/Breadcrumb_cap_w.png

Post Install Task (V3.6) - Office 2010 Error

We have a post install task for Office 2010 that ran fine in Version 3.5, but is generating an error in 3.6.  Command we are using -> "setup.exe" /adminfile "office2010smdhu.msp".

The error is with the switch /adminfile - advises it can only be used on the initial installation.  Since this is the initial installation, not sure why it is failing.  The other strange this is Office does install.


4 Comments   [ + ] Show comments
  • I recommend to install Office 2010 into image, since you can install it with ADM file and you can install office updates into image. This will save time when deploying images - josefino 9 years ago
  • We have not installed it in the image for a reason. What I would like to know is why it worked fine when running in 3.5 - but now generates an error when running in 3.6. The task itself has not changed. - hutcha4113 9 years ago
    • Your not the only one.. Many of my scripts are now failing even the runonce converter - LS-NetTech1 9 years ago
      • Runonce converter should not be used with 3.6. The purpose of it was to allow reboots between tasks. The K2000 now has that ability built in and works more reliably than the script.

        Corey
        Lead T3 Enterprise Solutions Consultant, K2000 - cserrins 9 years ago
  • The strange thing - now the install task is working fine. No idea why. - hutcha4113 9 years ago
  • I would love to know this too - same problem here! - zschuetz 9 years ago

Answers (0)

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ