Hi, I have a requirement here. I dont know how best it can be handled. 1. i have a Image capture Task sequence which deploys a base OS, upon that installs some applications+settings and takes a capture. I then use this captured OS for deployment in the production using one more task sequence(which also has got some applications added). 2. i got a new request to add some of the applications(for Ex:Adobe) into this Image itself(either before capture or after capture). there is already a package created for these applications by distribution team , which is going as mandatory in the production environment. 3. I cannot use the package created by the distribution team to install in my TS as the option "Whether or not user is logged on" is not enabled in those packages since they are being published normally and not through TS. so i create another package for my TS with same source of Adobe but with the option "Whether or not user is logged on" enabled. Everything goes fine and i get a captured OS with Adobe(for Ex:) installed in it. Problem: When a machine is built with this machine(with Adobe installed in the Image) and user logs in, the mandatory adverts start running.since the distribution team would have already set another package of adobe as mandatory, adobe starts to reinstall again in the newly built machine(even if it is already exist in the image) I want a environment where even if the Adobe is installed in the image when it connects to network the mandatory advert of the Adobe should not run. open for any suggestions. Thanks in advance Nachi:)

First of all there is no need to create a new package. You can just create a new program within the existing package. This way you don't have to waste disk space by storing the same files twice. The easiest way to avoid installing the app twice is to use a condition for the mandatory installation: "cmd /c if not exist <path>\<file/folder> <installstring>

Hi, It's not a clean way, but you can export this registry key from a computer that already receive and execute with success the Adobe advertisement in mandatory assigement made by you distribution team: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Mobile Client\Software Distribution\Execution History\System\packageID Then import this keys during your installation of Adobe package when you built your machine. The consequence is you will deceive the SCCM client, it will thought that the mandary advertisement is already executed with success so he will not retry. Julien

Thanks Jdulongc :)....this is what i exactly was looking for. realy helpful solution. I would try this out and reply. @Eirik- thanks for your suggestion. I would try to implement this solutn for our future packages since we cannot edit the packages which are already in production. Regards, Nachi :)

Faking the registry works like charm....:)...thnx for the tweek...;) Regards, Nachi :)