/build/static/layout/Breadcrumb_cap_w.png

Difficulties when Installing Office 2010 as a K2000 Scripted Installation Post Install Task

Really hoping someone can help me with an irritating issue when installing MS Office 2010 as a K2000 Post Install task!

 

This used to always work without an issue before the upgrade that required the start and wait commands to be removed. Now, the software will sometimes install and sometimes not. We have used the /adminfile command to install Office 2010 and this is in a .bat file in the zip folder with the command line in KACE set to install.bat however when the build gets to this task, it will normally pop up with a dialog box stating "You can only run one instance of setup at a time" and then if you click ok, the task fails and so do subsequent tasks.

 

Really i am asking how others have setup Office to install as a post install task on K2000.

 

Hoping someone out there can help!


1 Comment   [ + ] Show comment
  • Can you post the tasks.xml section for Office? - cserrins 9 years ago
    • sorry, do i get that when it fails? I have never had to find it before.
      Thanks - samuel.baker 9 years ago

Answers (1)

Answer Summary:
Thanks to LBarclay for the hint, I moved the task to be the first application that is installed and it seems to work without any issues at all now! Cn't believe i didnt think of this as it is so simple but thanks!
Posted by: LBarclay 9 years ago
Orange Senior Belt
0
Have you tried changing the task to "application" then putting the command in the that way? Can you post your full command?

Comments:
  • Hi, I have a ZIP File containing all the office files and setup.exe as well as an install.bat file containing this command
    setup.exe /adminfile Deployment.MSP

    In the post-istallation task settings on K2000 for this software, i have filled the command line box with install.bat

    Type is already application. - samuel.baker 9 years ago
    • Instead of install.bat, put your command in there directly. No point going through a bat file in this instance when you can call it directly in the command line box. So replace "install.bat" with "setup.exe /adminfile deployment.msp" - LBarclay 9 years ago
      • I used to have it setup with the command line straight in the box but i got the same issues. It seems to try and run 2 instances of setup each time producing the popup. If I click OK to the box, the task fails, if i leave it, it sometimes completes succesfully, sometimes not.

        Do you have this setup yourself? if so, would you mind sharing how yours is setup?

        Thanks - samuel.baker 9 years ago
      • This is the way we used to do it, although we don't do it this way anymore as I coded a new small app which we can custom select which applications to install on the fly. Anyways we still have the old task there that we used to use and it's the same as yours and always worked.

        There isn't any other conflicting tasks near by is there? It might be worth re-ordering them a little to see if that helps. Perhaps one of the previous tasks hasn't quite finished when office tries to run. - LBarclay 9 years ago

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