Deploying Applications without using client cache

Question

Hi,
We use Configuration Manager 2012 R2 for client deployment and application deployment.  Our ICT Suite computers did have an image of 23GB to deploy previously, but for ease of updating I am now using a task sequence with a common base image and
installs applications depending on collection.  Then also using that Application list to give our staff ability to choose applications to install onto their laptops using Software Centre.
As all application installations will occur over gigabit network or fast wireless connections I don't want the clients using the local cache to download the installations first (especially as some applications are 5GB and the cache doesn't empty straight
away).  I found that putting a full path to execute in the installation program field (i.e.
msiexec /I \\server\application$\program\install.msi
/q) and leaving the content location blank works to deploy applications to collections for installation.  But when the PXE task sequence is run I get the error:
If I create a second Deployment Type with content and distribute the content to the distribution point and set requirements that none of our clients would pass the software still installs (using the Deployment Type with no content).  This all seems
a bit of a hack to do a simple task.  Is there a better way to do this?  I just don't want the extra step of the stations downloading the setups into the client configuration manager cache folder.  I also don't want to use Packages as I can't
publish these into the Applications list in Software Centre for the clients.
Thanks,
Andy

Answer 1

I'm not sure why Microsoft provide such a great way of combining things like Application Library and automated deployment, then make it so difficult to actually use it.   Is there a command that will just clear the cache that I can run at the end
of the sequence?
I keep the cache at 20GB anyway as teachers like to deploy large applications to their laptops one after the other and as the cache fills up and hits max as it only clears after a minimum of 24 hours (another annoying attribute).  It then starts failing
to deploy.  But as some of our laptops have smaller SSD drives, they can't have huge caches as well as the applications installing using double the space the application actually requires.
For the task sequence (station building), I guess I could create a Package called Software and set the content to the share where all of our software is stored.  Then set it as direct access only, then list all of the software to install direct from
the package one after the other?