Hi SCCM experts

i distributed Microsoft visio 2010 pro and visio 2013 pro to clients, the package was downloaded successfully to local ccm cache file, but the installation not continued, also I checked the installation script is fine, its working when I run the script locally. I created many package all working except visio 2010 and 2013, are there some differences?

Script C:\Windows\system32\CCM\Cache\CEN001D1.1.System\setup.exe" /config vispro.ww\config.xml

config.xml content

<Configuration Product="VisPro">

<!-- <Display Level="Basic" CompletionNotice="no" SuppressModal="no" AcceptEula="yes" /> -->

<!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office Visio Professional Setup(*).txt" /> -->

<!-- <USERNAME Value="Customer" /> -->

<!-- <COMPANYNAME Value="MyCompany" /> -->

<!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> -->

<!-- <LIS CACHEACTION="CacheOnly" /> -->

<!-- <LIS SOURCELIST="\\server1\share\Office;\\server2\share\Office" /> -->

<!-- <DistributionPoint Location="\\server\share\Office" /> -->

<!-- <OptionState Id="OptionID" State="absent" Children="force" /> -->

<!-- <Setting Id="SETUP_REBOOT" Value="Never" /> -->

<!-- <Command Path="%windir%\system32\msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> -->

</Configuration>

errors on SCCM

 The program for advertisement "CEN20234" ("CEN001D1" - "install") exceeded the maximum allowed run time of 120 minute(s). Systems Management Server (SMS) has stopped monitoring the program, and is unable to determine the status of the program. SMS will not automatically attempt to run this program again.  Possible causes: The program might have taken longer to run than expected, or the program might have experienced problems while running.  Possible solution: Make sure the maximum allowed run time specified for the program allows enough time for the program to finish running. If the program requires user input, ensure the program properties allow the user to interact with the program.

Information    Milestone       CEN 3/18/2015 1:58:30 AM   AUSYDLT04005    Software Distribution    10005     Program started for advertisement "CEN20234" ("CEN001D1" - "install").    Command line: "C:\Windows\system32\CCM\Cache\CEN001D1.1.System\setup.exe" /config vispro.ww\config.xml  Working directory: C:\Windows\system32\CCM\Cache\CEN001D1.1.System\  User context: NT AUTHORITY\SYSTEM

Logs on SCCM

Severity    Type Site code  Date / Time      System     Component      Message ID     Description

Error         Milestone         CEN 3/9/2015 8:57:49 AM      CNXMNLT08360       Software Distribution      10070      

The program for advertisement "CEN20234" ("CEN001D1" - "install") exceeded the maximum allowed run time of 120 minute(s). Systems Management Server (SMS) has stopped monitoring the program, and is unable to determine the status of the program. SMS will not automatically attempt to run this program again. 

Possible causes: The program might have taken longer to run than expected, or the program might have experienced problems while running.  Possible solution: Make sure the maximum allowed run time specified for the program allows enough time for the program to finish running. If the program requires user input, ensure the program properties allow the user to interact with the program.

 

Information      Milestone         CEN 3/9/2015 6:57:49 AM      CNXMNLT08360       Software Distribution      10005      

Program started for advertisement "CEN20234" ("CEN001D1" - "install").   

Command line: "C:\Windows\SysWOW64\CCM\Cache\CEN001D1.1.System\setup.exe" /config vispro.ww\config.xml  Working directory: C:\Windows\SysWOW64\CCM\Cache\CEN001D1.1.System\  User context: NT AUTHORITY\SYSTEM

 

Information      Milestone         CEN 3/9/2015 6:51:45 AM      CNXMNLT08360       Software Distribution      10035      

The program for advertisement "CEN20234 has not yet started because the content for the package "CEN001D1" - "install" (version 1) has not been acquired. Possible cause: The content for this program must be downloaded into the computer's cache, or the content could not be located.  

Solution: If the program is being downloaded, no action is required. The program will start once the download has been successfully completed. If the content can not be located, ensure that a distribution point with this content is available for this computer.  Distribution point availability can be affected by roaming boundary configuration which is used to determine whether distribution points are classified as local or remote, or by enabling distribution points as protected distribution points. Distribution point availability can also be affected if you are using branch distribution points and the advertisement is configured with the option Run program from distribution point instead of Download content from distribution point and run locally. This is because branch distribution points do not support advertisements that are configured to run directly from a distribution point.

 

Information      Milestone         CEN 3/9/2015 6:51:44 AM      CNXMNLT08360       Software Distribution      10002      

Advertisement "CEN20234" was received from site "CEN".   

The client passes any supported platform requirements and the SMS will add the advertisement's program to the list that will be displayed to users and/or run via assignment. If an advertisement is received but not displayed on a client, verify that the current time on the client is between the advertisement start and expiration times, and that the program specified in the advertisement is enabled.

Exceeded maximum run time almost always means that the command-line yo configured is displaying a UI but because ConfigMgr is running it as local System, this UI is being displayed on a hidden desktop and so no one can respond to the UI. AFter a while, ConfigMgr gives up watching the process and issues this error.

Make sure you always test your command-line outside of ConfigMgr first to ensure that no UI is being inadvertently displayed.

Hi Jason

thanks for your reply.

do you mean i need to change the display level =no on the  config.xml file?

config.xml content

<Configuration Product="VisPro">

<!-- <Display Level="Basic" CompletionNotice="no" SuppressModal="no" AcceptEula="yes" /> -->

Bruce 

That will help, but there are other things that may display also. I'm not an expert on Office setup so there may be additional things which is why you should make the change and test outside of ConfigMgr to make sure that the setup is totally unattended meaning that it requires no user interaction. You should also refer to the Office setup documentation on TechNet as its very detailed instead of just making guesses.

May I suggest using the OCT file instead of config.xml? I use the OCT method for all of my Project and Visio installs and it works flawlessly. If you must use the config.xml file and you want a silent install, you need to change it to look like this:

<Display Level="none" CompletioNotic="no" SuppressModal="yes" AcceptEula="yes" />

May I suggest using the OCT file instead of config.xml? I use the OCT method for all of my Project and Visio installs and it works flawlessly. If you must use the config.xml file and you want a silent install, you need to change it to look like this:

<Display Level="none" CompletioNotice="no" SuppressModal="yes" AcceptEula="yes" />

• Edited by tremmurph 17 hours 34 minutes ago

May I suggest using the OCT file instead of config.xml? I use the OCT method for all of my Project and Visio installs and it works flawlessly. If you must use the config.xml file and you want a silent install, you need to change it to look like this:

<Display Level="none" CompletioNotice="no" SuppressModal="yes" AcceptEula="yes" />

• Edited by tremmurph Friday, April 24, 2015 2:02 PM

May I suggest using the OCT file instead of config.xml? I use the OCT method for all of my Project and Visio installs and it works flawlessly. If you must use the config.xml file and you want a silent install, you need to change it to look like this:

<Display Level="none" CompletioNotice="no" SuppressModal="yes" AcceptEula="yes" />

• Edited by tremmurph Friday, April 24, 2015 2:02 PM

May I suggest using the OCT file instead of config.xml? I use the OCT method for all of my Project and Visio installs and it works flawlessly. If you must use the config.xml file and you want a silent install, you need to change it to look like this:

<Display Level="none" CompletioNotice="no" SuppressModal="yes" AcceptEula="yes" />

• Edited by tremmurph Friday, April 24, 2015 2:02 PM

May I suggest using the OCT file instead of config.xml? I use the OCT method for all of my Project and Visio installs and it works flawlessly. If you must use the config.xml file and you want a silent install, you need to change it to look like this:

<Display Level="none" CompletioNotice="no" SuppressModal="yes" AcceptEula="yes" />

• Edited by tremmurph Friday, April 24, 2015 2:02 PM

May I suggest using the OCT file instead of config.xml? I use the OCT method for all of my Project and Visio installs and it works flawlessly. If you must use the config.xml file and you want a silent install, you need to change it to look like this:

<Display Level="none" CompletioNotice="no" SuppressModal="yes" AcceptEula="yes" />

• Edited by tremmurph Friday, April 24, 2015 2:02 PM

May I suggest using the OCT file instead of config.xml? I use the OCT method for all of my Project and Visio installs and it works flawlessly. If you must use the config.xml file and you want a silent install, you need to change it to look like this:

<Display Level="none" CompletioNotice="no" SuppressModal="yes" AcceptEula="yes" />

• Edited by tremmurph Friday, April 24, 2015 2:02 PM

see if this helps you

https://sccmpackager.wordpress.com/2012/06/15/12/