copy packages used during deployment

[rddvls1999]

Hi,

 

I have a working Windows 7 x64 deployment (via SCCM 2007 R3) using the "Access content directly from a distribution point when needed by the running task sequence" option on the advertisement.

 

We have a captured Windows 7 x64 image, and are scripting our software installs (office 2010, acrobat x, dms, etc) after the wim file is laid down. Since some of the computers are laptops and are used while away from the office, there are times when a user may need to reinstall an application offline (e.g. VPN has stopped working and needs to be reinstalled). I'm wondering if anyone knows of a way to script it so that all (or ones that are deemed necessary) software packages used during the OSD phase are copied to a pre-determined directory for later use?

 

All suggestions are welcome.

 

Thanks!

[P@docIT]

Off the top of my I would say create two task sequences. One that installs the software and one that then copies the setup or source files to a chosen destination on the machine. i am by no means an expert and have only been using SCCM since the end of June. So please take my advice with a grain of salt. i personally use the scripts\custom scripts folder to store any files I need to "copy" to the machine, this will be dependent on a task sequence called "Use Toolkit Package" which is part of the MDT 2010 toolkit. I then create a TS with a command line along the lines of xcopy "%deployroot%\Scripts\CustomScripts\folder" "C:\folder" /E /C /I /Q /H /R /Y /S. I'm sure there is a more elegant way but it has been working for me.

[Lucid]

Just tossing this idea out there, not sure if it'll work or not, but... You could think about making Packages of your apps (you should be doing that anyway) and then set up a separate Program that can be advertised to your machines so that it lists the software in the Add Programs section (under "Install a program from the network") of the Control Panel. That way your user could navigate to there and trigger a reinstall... Also, if you're not there yet, investigate internet-based clients so you could just have the user call into a support line and a techie could kick out a package and reinstall the app via SCCM as long as the device can connect to the internet...