When you say it’s not enforcing the supersedence, what exactly are you seeing?  
Did you specify the Deployment Type to replace and tell it to Uninstall?

-Phil
_________________________________________________________________
Phil Schwan | Technical Architect, Enterprise Windows Services
Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 
48075
Lync: 312.756.1626  Mobile: 419.262.5133
www.projectleadership.net<http://www.projectleadership.net/>
[Description: Description: Description: Arrow email]Lead with Strategy. 
Leverage Technology. Deliver Results.
[linkedin_logo-19x20]<http://www.linkedin.com/in/philschwan>[Twitter-Logo1-20x20]<https://twitter.com/philschwan>
 [wordpress-logo3] <http://myitforum.com/myitforumwp/author/philschwan>





From: [email protected] [mailto:[email protected]] On 
Behalf Of Matt Wilkinson
Sent: Thursday, April 17, 2014 10:38 AM
To: [email protected]
Subject: [mssms] Supercedence with Avalible appplications targeted at users.

Hi
I have a custom script that is deployed as an application. Its available on the 
software catalog to a user collection. I want to supersede this application 
with a newer version. The sccm client doesn’t seem to enforce the supersedence 
where the application is already installed.

Does anybody have any experience of this? We supersede required applications 
with no issue.

_____________________________________________________________________
This email has been scanned by the MessageLabs Email Security System on behalf
of Leeds College of Building.
For more information please visit http://www.symanteccloud.com
_____________________________________________________________________

________________________________

PRIVILEGED AND CONFIDENTIAL. This email and any files transmitted with it are 
privileged and confidential and intended solely for the use of the individual 
or entity to whom they are addressed. If you have received this email in error 
please notify the sender. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail or any of its attachments.


<<inline: image001.jpg>>

<<inline: image002.jpg>>

<<inline: image003.jpg>>

<<inline: image004.jpg>>

Reply via email to