my pictures wouldnt stay, so have put them into a PDF in DropBox (remove space between https and :):
the above are pictures of what i currently have setup for one of the applications - the Business version. this application is split into 4 smaller sections - Install of the SAP program and a Print fix which all work fine - and are the basis of each of the 3 applications.
now comes the different parts - the third part of 4 removes the SAP config files that are no longer needed, and as part of the vbs that runs copies 2 files onot the system for versioning and verifying what type of install is installed. these files are needed for the detection method.
by default the machine is left in the collection post install it is not removed. this means everytime the machine policy is refreshed the detection method is re-run. if only one version has been pushed to the machine then all is good. when the machine is added to another SAP collection (so it is now in 2 SAP collections) it recognises that the SAP GUI and Print Fix are not needed to be installed (detection methods), and sees that its newly requested install detection method is not met, so it runs its vbs script. this removes all signs of the previously install SAP config files and versioning, and then puts it own in place.
when the original applcation checks itself, due to it being in the oroginal collection still, it will detect that its files are not there, and hence will remove the files recently installed and set itself back up.
i believe that i am using the app model, but please do correct me if im wrong.
<message edited by chrisbirley on Tuesday, September 16, 2014 8:27 AM>