+1 This is exactly what the Detection Method is designed to do in the Application model: detect whether the Deployment Method is already installed on the workstation.
-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 elsalvoz Sent: Wednesday, February 19, 2014 6:31 PM To: [email protected] Subject: Re: [mssms] SCCM 2007 to SCCM 2012 moving from Package Model to Application You certainly can do that but why not put some logic into the apps and check whether the application is already installed in the detection method and run it or don't run it based on that? that will be useful now and you can use it in the future as well. On Wed, Feb 19, 2014 at 1:19 PM, Boseman, Marcia H - Raleigh, NC <[email protected]<mailto:[email protected]>> wrote: We want to take our existing packages from SCCM 2007 and move them to the application model in SCCM 2012 so we do not have to carry over all of our collections. Has anyone created a requirement as part of the package model to check for the packageID to see if it installed on a machine? I was thinking of using the registry to check this information. Does anyone have any suggestions? ________________________________ 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>>
