Hi guys.

I have deployed office 2016 successfully as a post install task in the k2.

 I now need to install Office 2016 proofing tools (German only).

I would like to add this as a post install task too.

Now I have seen a few post about how to deploy proofing tools

silently, by configuring The config.xml in the proofkit.ww folder......

But the problem Is they all launch the program by pointing

a path to a config file which is in a folder within a folder.

\setup.exe /config "C:\Users\USERNAME\Desktop\Microsoft Office Professional Plus 2013 Proofing Tool 15\proofkit.ww\config.xml"

or like TechNet says in their version of proofing tools deployment....

Note that you must use a fully qualified path; for example: \\server\share\Office14\Proof.WW\setup.exe /config \\server\share\Office14\Proof.WW\Config.xml

where Office14 is the root of the network installation point.

My problem is how do I point to this config file when I have zipped

all the files and uploaded to the k2.

Anyone have any idea how to deploy proofing tools as a post install task?

0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity


The solution will be to wrap the command line in abatch file and use the "%~dp0" dodge:
"%~dp0setup.exe" /config "%~dp0Config.xml"
Note that that environment variable includes a trailing backslash.
Answered 10/04/2017 by: VBScab
Red Belt

  • so are you saying I should use this......

    "%~dp0setup.exe" /config "%~dp0Config.xml"

    in the parameters field of the post install task...?

    or could you be a bit more specific
  • Thanks @VBScab. finally got it to work after a little fiddling about and comparing it to my office 2013 deployment. this is what worked for me.
    "setup.exe" /config "proofkit.ww/config.xml"
    The proofing tools has the same file structure as the MS-Office.....so was able to figure it out.
Please log in to comment