The user has to uninstall the 4.2 version from Software Center. This will make it so it's only "available" on that system. Once you install a product from the catalog, you're essentially creating a policy for that user on that computer for a REQUIRED deployment. Each time Application Discovery evaluation happens, SCCM wants to remediate all required deployments and reinstalls the 4.2 version. So, by uninstalling via software center, the tech would essentially be removing the "required" policy for that user on that computer.
Once the tech uninstalls, they will still be prompted for new software since the app is no longer installed but it's available. Also, you should investigate your supersede rules to ensure you're not going to have a scenario where the user installs both at the same time. -Nick- From: [email protected] [mailto:[email protected]] On Behalf Of Morgan Little Sent: Wednesday, November 4, 2015 11:05 AM To: [email protected] Subject: [mssms] SCCM 2012 Software Installation Collection Good Morning All, I have had no luck with finding any articles/posts online regarding an issue we are experiencing with our SCCM 2012 R2 SP1 CU1 environment and Software Installation Collection. We leverage our Application Catalog heavily in this environment and have permissions to which applications are available/displayed to the IT individuals. We have noticed that there is some "caching" from this user collection and workstation from application catalog deployments which has been causing some issues with older versions of products installing. Here is an example: 1. Helpdesk tech installs the Citrix Receiver 4.2 on his laptop via that Application Catalog. 2. Engineering releases a Citrix Receiver 4.3 to all of the IT Support group for testing but needs to keep the 4.2 version active in the Application Catalog since this is the enterprise approved version. 3. Helpdesk tech's laptop checks in with the SCCM Console and begins to reinstall the 4.2 version even though the only deployment of the product is the User Collection as Available. The odd thing about the caching is that even after deleting and recreating the deployment to the User Collection, we are seeing that same symptoms. Has anyone encountered the same scenario or would have any suggestions on how to resolve this? Thanks! Morgan Little IT Engineer * * * * * * * * * * * NOTICE: This e-mail and any attachments contain confidential information that may be legally privileged. If you are not the intended recipient, you must not review, retransmit, print, copy, use or disseminate it. Please immediately notify us by return e-mail and delete it. If this e-mail contains a forwarded e-mail or is a reply to a prior email, the contents may not have been produced by the sender and therefore we are not responsible for its contents. This notice is automatically appended to each e-mail. It is the recipient's responsibility to take measures to ensure that this e-mail is virus free, and no responsibility is accepted by Greystone for any loss or damage arising in any way from its use. * * * * * * * * * * *
