Good Morning.
I have built a custom Update for the New Adobe Acrobat Reader DC version.. I do have a issue which may be a setting I did not know about since this is the first .msp I have pushed. Our Test PC's see the package, install it, but then it will keep seeing it and install it again.. Is there a setting that needs to be done for a .msp that after it is installed, it will not try to keep downloading as an update..
Any advice is appreciated..
Thanks
~J
Comments: Hi, First why do you create a Custom Update instead of a classic update ? What "Actions' do you have set in this Custom Update ? Secondly, if clients computers try to install again, that means they have evalued the "IsInstalled" rule to False and the "IsInstallable" to True. So, what do you have set as "IsInstalled"/"IsInstallable" rules ?
I have built a custom Update for the New Adobe Acrobat Reader DC version.. I do have a issue which may be a setting I did not know about since this is the first .msp I have pushed. Our Test PC's see the package, install it, but then it will keep seeing it and install it again.. Is there a setting that needs to be done for a .msp that after it is installed, it will not try to keep downloading as an update..
Any advice is appreciated..
Thanks
~J
Comments: Hi, First why do you create a Custom Update instead of a classic update ? What "Actions' do you have set in this Custom Update ? Secondly, if clients computers try to install again, that means they have evalued the "IsInstalled" rule to False and the "IsInstallable" to True. So, what do you have set as "IsInstalled"/"IsInstallable" rules ?