/build/static/layout/Breadcrumb_cap_w.png

.MSP Files

We have Microsoft Visio 2007. In order to install this you need to run Setup.exe /admin to open up the new Office Install tool for Visio 2007 (just like ORK for Office). This works fine but there is nowhere in this tool to genereate a log file. There is no PROPERTY for the log file.....it is done from the command line and everytime we run this .MSP file from a command line it does not support the /L*V+! "c:\logs\Visio2007.log"

We can run the Visio 2007 install like this: Setup.exe /adminfile \\Server\Share\Visio2007.MSP and it works fine. Also, within the Office Install tool we can specify PROPERTIES for reboot (example: REBOOT=R) but can not set any logging for the MSP itself.

Another issue.....if you run the following command msiexec.exe /p \\Server\Share\Visio2007.MSP you get an error saying the product you are trying to upgrade needs to be on the system....etc....etc..... so we have to run this using the command line of setup.exe /adminfile \\Server\Share\Visio2007.MSP yet don't see a way to generate a verbose log using this command.

Has anyone been able to do this?

0 Comments   [ + ] Show comments

Answers (1)

Posted by: reds4eva 12 years ago
Second Degree Blue Belt
0
You can use logging in the config.xml file. Just specify the XML on the command line.
setup /adminfile file.msp /config file.xml

Inside the XML you can choose the type of logging, eg. standard, verbose etc.
<!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office Enterprise Setup(*).txt" /> -->


Also, the MSP isnt a traditional msp as such, you have to use setup.exe and the msp together.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
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