I am having difficulty installing Visio Pro 2010 via SCCM 2007.  I read in a blog and was advised to create a XML file as follows

The XML file I used was as follows:

<Configuration Product="Visio">
<Display Level="none" CompletionNotice="no" SuppressModal="no" AcceptEula="yes" />

Name this as "config.xml" or equivelent and when creating the program in SCCM use the following: setup.exe /config <path to XML file>

I am confused with which command line to run in SCCM for this, i have placed the Config.xml file in the same location of the setup file, running this command line

setup.exe /config c:\visio pro\config.xml

but this is not working, nothing actually happens.  Can anyone advise me on how to install this via SCCM 2007?


2 Comments   [ + ] Show Comments


  • For your PIDKEY entry did you put dashes in?? Also what license approach are you taking, KMS or MAK?
  • another quick question, in your example...<PIDKEY Value="<ENTER CD KEY HERE>" /> you didn't leave the < inside the quote did you??
Please log in to comment


It could be down to the path for the XML file.
Running from SCCM is either going to run from a DP, or from the SCCM cache - unless you've specifically set the cache directory to 'C:\Visio Pro' it's not going to be in that location.

Try running:
setup.exe /config config.xml

If the config.xml is in the same location as the setup.exe it will be found and the installation run with it.

Answered 01/20/2015 by: dunnpy
Red Belt

Please log in to comment
I have always found that running setup /admin and generating an MSP file with the necessary configurations is totally reliable. Just drop the msp file in the updates folder on the source and run setup.exe with the silent switch to install. Job done.
Answered 01/20/2015 by: EdT
Red Belt

  • I have also tried this. Created an MSP file placed it in the updates folder, but when deploying via SCCM not happens. The package downloads to the Cache folder but the install does run. In the MSP file i have set the Licensing and User Interface to Accept The terms in the License Agreement, Display Level is None, and Suppress Modal. The Command line in SCCM is setup.exe as the Silent switch is already set in the MSP file. The MSP file is the first folder in the updates folder. Any advice?
    • As the underlying install is an MSI, enable verbose logging and examine the logfile for the cause of the installation failure. What you can also do is to configure the MSP file to basic UI in the display level and watch for any displayed errors. I am assuming you are deploying to XP as you have SCCM 2007, but if not it would be useful to know exactly what version of O/S you are deploying to.
Please log in to comment
I have run setup.exe /config config.xml

From Command prompt just to see if it runs before packaging for sccm.  But it fails and errors saying xml file is not valid.  Run setup again without usinga Setup configuration file, or fix teh configuration file.

So this suggests the xml file has an issue, can you help and see if anything is wrong with the xml.  All I have added to the XML file is the PID Key for Visio Pro
Answered 01/20/2015 by: goggles
White Belt

Please log in to comment

In your first example, is there an actual "C:\Visio pro" folder? Leave the config in the folder with the setup.exe just use "config.xml"  (it looks like you have sorted this bit)

I partly agree with EdT, use an MSP, but put it next to the exe NOT in the updates folder. (this allows you to use multiple custom MSP's if needed, more useful with Office and Enterprise media)

the command line to use is:

"%~dp0setup.exe" /config "%~dp0VisioStd_config.xml" /adminfile "%~dp0Visio_2010_Std_01.msp"

The %~dp0 makes it fill in the path to the files, not really needed for SCCM, we use it so people can run batch files from UNC paths.

If you are getting an issue with the XML, try dragging it into IE, if it does not display correctly, sort your XML. I had this a while back, I could not see anything wrong, but decided to copy it from the Visio.ww folder, it was all OK.

Remember, you have to take the comments out of both ends of the line.

Answered 01/20/2015 by: Badger
Red Belt

Please log in to comment

Hi Guys,

Ihave found the solution to this that worked for me.  I have managed to install Visio Pro 2010, viaSCCM 2007 using a config.xml file.

Thedetails in the config file are as follows

<DisplayLevel="none" CompletionNotice="no"SuppressModal="no" AcceptEula="yes" />
<USERNAMEValue="" />

Notethe the Configuration Product for Visio Pro is Visio, for any other Visio edition check the Product ID and usethat.
The PIDKEY value again is specific to Visio Pro, you will need to use thePIDKEY for your edition of Visio.

Isaved the config.xml file in the same location as the setup.exe file.


1.     Packaged Visio in SCCM saying the Package hasa Source directory (this will be the UNC path of the config.xml file andsetup.exe file), put that in the Source Directory

2.    I used the Command line setup.exe /config config.xml

     Make sure you make the Advertisement to Download content from Distribution Point andrun locally.



The Pidkey isthe KMS Client Key for Visio, below are the keys to use for the edition ofVisio you are installing.


Visio Premium2010


VisioProfessional 2010


Visio Standard2010


A big thank you to Dunnpy, EdT and Badger, a great help.  

Answered 01/21/2015 by: goggles
White Belt

Please log in to comment
Answer this question or Comment on this question for clarity