Deploy a Application with SCCM using local data files on client machine as source

Yes, you just need to point the sources location to the path of your choice in the command line in your script or directly in the cmd in deployment type of your application or you can even use a TS to prepare the cmd and set the source location. There are multiple ways you can achieve this.

Once for something large, we did it this way.

1. it's a package/program/Advertisement
2. you already KNOW at least a week in advance, who will be getting that large thing.

Within the Package for <ginornous thing>, two programs. one is the actual deployment of the thing. the other is literally just cmd.exe /c

You deploy as required the cmd.exe /c program to the target collection a week or at least a few days before the deployment of <real install> is set to install.

The client will download the content of the packageID into cache. Presuming you don't have aggressive cache cleanup routines; the package contents will still be there in cache when <real install> deadline or available hits.

So to the end user... it appears "fast", but you know it was just timing trickery.

Of course, this only works if your cache size is big enough, and that you already know the targets.... So this won't work for net-new installs usually... but if it's upgrades it's "a way".

So how are you getting the data files to the computer? if you are manually coping them then you are using SMB which is not network aware.