Updating Acrobat through SCUP and InstallSource

My company has put a hold on deploying Adobe Acrobat and Reader updates through SCUP due to the load they are putting on our network.  When installing the update, the InstallSource registry key for the appropriate product is referenced to locate the original install media, and if the location no longer exists, it goes all the way back to our primary SCCM server to access it.  This kills network performance at remote sites, as they do not have enough bandwidth to handle the update and continue normal operations.

We had used a network alias prior to migrating to SCCM 2012, where the alias would direct a target WIndows machine to use the closest update server.  I've asked the install automation for Reader and Acrobat to set InstallSource to the cache located within C:\Windows\Installer.  This will take care of future installs.  For existing installs, I requested a new Group Policy Object to modify the registry to use this same value as InstallSource, but management is insisting that Adobe "fix" it.  Since Reader is a free product and we do not have a maintenance or ETLA agreement for Acrobat, I don't expect them to deliver me a solution.

Has anyone else experienced this problem?  How did you resolve it?  I am welcome to any suggestions you may have.  Thanks.