Because the new application model is state-based, a dependency will evaluate to see if it's already installed instead of just running the install regardless as with "Run Another Program First." Much more flexible and dynamic. Plus the 2007 feature doesn't work in a Task Sequence.
-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 Kevin Ray Sent: Wednesday, February 26, 2014 4:31 AM To: mssms Subject: [mssms] Difference between SCCM 2012 and SCCM 2007 in Dependency option - Hi All, I have checked in SCCM 2012 dependency feature it looks to be same , As in SCCM 2007 Child program option... Since 2012 also we need to specify the dependency packge name. What is new in this? ________________________________ 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>>
