There is no supported solution. Thats why all papers stated to use DFS 
Working scenario in a testenvironment, definetly not supported 
- create a new GPO- create a new .aas file- copy the new .aas to your GPO folder in sysvol
- copypaste the old .aas filename, remove the old .aas file and rename the new one to the old name
- adsiedit.msc, navigate to CN_of_existing_GPO\Machine\Class Store\Packages
CN_of_existing_GPO\User\Class Store\Packages depending on the target object of the deployed software
- edit Attribute “msiFileList” to the new path- create a computer startup script and replace all %windir%\system32\appmgmt\MACHINE\{guid}.aas
- create a ADM Template and deploy the new path information to the client registry:
HKLM\SOFTWARE\Classes\Installer\Product\GUIDofApp\SourceList\Net “1″=”\\yourserver\share\”
