Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

We have created an application deployment using SCCM 2012 for Ultra VNC. however we also want to deploy the settings file.
We have created a package for this that when run deploys the settings file correctly.
Is there a way of forcing this package to be deployed when the application is run forcing the settings file over as well?

share|improve this question
    
do you want to force the file do be deployed when the sccm application is run or do you mean when ultra vnc is run? –  weberik Jul 9 '13 at 14:28
    
@weberik When Ultra VNC is deployed onto the client machine I want the settings file to be deployed also. Kind of like a 2 for 1 deal –  Joe Taylor Jul 10 '13 at 15:07
    
Sidenote - I'm curious which feature Ultra VNC is providing you that SCCM2012 Remote Control Viewer doesn't. –  Bad Dos Aug 8 '13 at 15:29
    
@BadDos - none, we were doing things just because we always had. A bad habit. UVNC no longer exists on our systems. Cheers for the nudge in the right direction. –  Joe Taylor Aug 27 '13 at 13:51

2 Answers 2

up vote 3 down vote accepted

You could also send the files out as an Application (script install deployment) with the main Ultra VNC app as a dependency.

In fact you can set them both up in the same "Application", we do something similar to deploy Foxit Reader's install along with some extra files (the XML files for Foxit MUIs in our case).

Just set the script that deploys the settings file up as the priority 1 Deployment Type, and set VNC install as the Priority 2 Deployment Type in the Application:

Script deployment type as priority one, and the actual app as priority 2

And then set the main installer for VNC to be a dependency for the settings file. This should then install them both:

script deployment with the main install as a dependency

share|improve this answer

You could just put your settings file with the MSI and create a single batch file and set that up as a script installer. Creating artificial dependency chains using multiple deployment types isn't the best way to do it.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.