Installing Office 2019 via Scripted Install from SDA 6.1


I have been working on trying to install Office 2019 by using the SDA inside of a scripted installation.  It runs the tool for a few moments, checks that it completed, and moves on.  It will not install.

I have setup as suggested in this article: https://www.itninja.com/blog/view/installing-microsfot-office2019-project-2019-or-visio-2019-via-sda-or-sma

I have verified that it will run from command line standalone.  

Is there a way to verify what happened, or to make the system pause to complete the full installation? 

Any help would be appreciated!!

Windows 10 EDU 1809

Office 2019 32 bit


0 Comments   [ + ] Show comments

Answers (1)

Posted by: SMal.tmcc 4 years ago
Red Belt

That is typical if it does not find the config file. You need the full path. Being in the directory does not seem to make a difference.
Here is my batch script (note the path for the config call)


setup.exe /configure c:\temp\kms\configuration.xml

c:\windows\w2d\ksleep 10

exit /b 0

  • Thank you! I will give that a shot today. - dadyjj73 4 years ago
    • Let me know if that does not help. We have used that batch for about 2k machines this semester's image cycle. - SMal.tmcc 4 years ago
      • I see from your other posts, that you are preloading the files in your image. We are working with a purely scripted installation. The change from MSI to Clicktorun is throwing a big wrench. We can install from a managed installation from the K1000. I was hoping perhaps you know what the working folder for the K2000 post install files would be? - dadyjj73 4 years ago
      • Yes you need the kace path. All post tasks are copied to the local drive as one of the hidden Kace tasks at the end of mid.

        They can be found on system drive. Say c: is the system drive. they will be under c:\kace\applications\in numbered sub dirs. to get the directory name for that task go to the post task library page and point your mouse at that task. Look at the bottom of your browser and you see id=### some number (lets use id=123). So that tasks files will be copied on the local drive to c:\kace\applications\123. so the call for the config file you need to use that absolute path. I would also put in the notes for that task you are using an absolute path and if this task is duplicated you will need to repeat the process for the copy since it will get a new id.

        If you want to see what the script is showing for the task, open explorer and connect to \\ikbox samba share using the account admin and samba share password. point your mouse at the scripted install and get its ID. on the kbox go to \\ikbox\peinst\scripts and find that deployments task script. be named tasks_###.xml. open that file and scroll down to the id of the task itself in that file. look at the line <commandline> - SMal.tmcc 4 years ago
      • Thank you SMal.tmcc! I am giving that a try now. - dadyjj73 4 years ago
      • OK, the full path worked!! thank you so much for the help! - dadyjj73 4 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


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