nhottinger Posted November 27, 2013 Report post Posted November 27, 2013 We have packaged an app (easy part) and now need to copy a file to the local pc once the install is complete. Is there an easy way to add a batch file to do this, or some other way to get the file copied over from a shared location once the software package installs? Quote Share this post Link to post Share on other sites More sharing options...
Iroqouiz Posted November 29, 2013 Report post Posted November 29, 2013 Just use a simple bat script in the task sequence. Quote Share this post Link to post Share on other sites More sharing options...
ozthe2 Posted November 29, 2013 Report post Posted November 29, 2013 If you would like to do this via an msi (which makes life extremely easy) I thoroughly recommend this brilliant piece of software that has helped me out countless times - it's called wItem and you can download it from here: http://www.witemsoft.com/ In your case, you could use wItem to create an msi that deploys the file that you want copied and use dependencies in Config manager to chain your first app with it. Quote Share this post Link to post Share on other sites More sharing options...
nhottinger Posted December 2, 2013 Report post Posted December 2, 2013 Iroqouiz, I'm new to SCCM, I'm not sure how to use a task sequence to install software. When I have tried that in the past, the task sequence never shows up in the Software Center. Quote Share this post Link to post Share on other sites More sharing options...
nhottinger Posted December 2, 2013 Report post Posted December 2, 2013 ozthe2, We have software to create .msi's (EMCO msi builder) but don't know if I can use that in the same way you are talking. As you saying I should create an msi, package it, create a batch file to copy the file and in the deployment properties of the software, make a dependency to run the batch file once the software is complete? I tried something similar and it never ran the batch file. I'm sure I did something wrong though. Quote Share this post Link to post Share on other sites More sharing options...
Peter33 Posted December 2, 2013 Report post Posted December 2, 2013 If you are using a packaging program like EMCO you can simply add or replace the file with the editor. You can also save the changes as transforms file (MST), so the original file will not be modified. This way you can deploy the MSI as regular application without any additional wrapper like batch files or scripts. Regarding the Task sequences. You have to tick the check box in the deployment/advertisement, which allows the user the run the task sequence from the software center. It's not a default setting. Quote Share this post Link to post Share on other sites More sharing options...
ozthe2 Posted December 2, 2013 Report post Posted December 2, 2013 witem creates an msi for you. Within the witem interface you are able to specify a file or files that you want copied to a location specified by yourself on the local computer - it then adds this to the msi that it builds. It's then very easy to deploy the msi using Config Manager. Quote Share this post Link to post Share on other sites More sharing options...
nhottinger Posted December 3, 2013 Report post Posted December 3, 2013 I'll try these suggestions. When I used EMCO the other day, I started the monitoring, installed the application, manually copied the file to the location needed, then stopped the monitoring. It created the .msi for me but did not include the file copy for some reason. I'll try again. Thanks for your input. Quote Share this post Link to post Share on other sites More sharing options...
nhottinger Posted December 5, 2013 Report post Posted December 5, 2013 I ended up creating a task sequence for this. The first part installs the software, then a cmd line copies the file over. Thanks for everyone's help. Quote Share this post Link to post Share on other sites More sharing options...
