myITforum and Windows IT Pro Forums

 CM12 "Rerun behavior" equivalent??

Author Message

  • Total Posts : 99
  • Scores: 2
  • Reward points : 53470
  • Joined: 10/25/2007
  • Status: offline
CM12 "Rerun behavior" equivalent?? Thursday, July 24, 2014 11:36 AM (permalink)
Hello all,
When using CM12 applications, I am no longer seeing rerun behavior (always rerun, rerun only if failed etc).  Based on sample situation below, please offer suggestions....
In CM07 we have several applications where part of the package (sometimes data content, other times the exe itself) is updated on a weekly basis.  we would simply overwrite the SCCM source content, set the DPs to update on a schedule and the advert to also reoccur on a schedule (usually 24 hours after the DP schedule).  The Program was set as "Always rerun" to ensure the endpoints would always receive the newest content.  This worked great for years in SMS 2003 and a couple iterations of CM07. 
The only piece of the above I cannot find in CM12 is the program "Always rerun".  Has this been taken away?  Is there an equivalent replacement?  do we have to set a detection method in a silly manner like, "if the sky is blue, rerun this advert"?  Prefering not to go the route of traditional package b/c these may just disappear altogether at some point. :) 
Suggestions please?? 
Thank you
<message edited by Darren on Thursday, July 24, 2014 1:02 PM>

    • Total Posts : 1438
    • Scores: 131
    • Reward points : 71080
    • Joined: 3/24/2005
    • Location: San Antonio, TX
    • Status: offline
    Re:CM12 "Rerun behavior" equivalent?? Thursday, July 24, 2014 7:06 PM (permalink)
    That's correct. This is because applications are enforced differently on client systems. Similar to updates, applications define a desired state for that application if it is required: either installed or uninstalled. The client agent then goes about enforcing that state starting at the deadline time specified in the deployment. Then, every time the deployment evaluation cycle runs, the client will ensure that state is still enforced (based upon the detection logic) and if not enforce it. This is an intent based system where you simply define what you want to happen and then ConfigMgr does it. The key here is that Applications are called "Applications" for a reason: they are meant to install applications because that's really the only time this intent based model makes sense.
    For recurring tasks like scripts or what you have defined above that do not truly have anything to do with the state of the target system, packages and programs are still the primary method to use. Packages and programs are not going anywhere -- not sure how you came to that conclusion -- they are still very much needed for these scenarios.
    Configuration Manager MVP
    My Blog
    Twitter @JasonSandys

      • Total Posts : 99
      • Scores: 2
      • Reward points : 53470
      • Joined: 10/25/2007
      • Status: offline
      Re:CM12 "Rerun behavior" equivalent?? Thursday, July 24, 2014 7:31 PM (permalink)
      Thanks for taking your time to respond. 
      Didn't mean "packages going away as a conclusion", just was thinking it a possibility that applications was the way of the future and packages might go away.  Just don't want to get stuck using a method which may disappear.  ;)
      Have a great week!
        Online Bookmarks Sharing: Share/Bookmark

        Jump to:

        Current active users

        There are 0 members and 1 guests.

        Icon Legend and Permission

        • New Messages
        • No New Messages
        • Hot Topic w/ New Messages
        • Hot Topic w/o New Messages
        • Locked w/ New Messages
        • Locked w/o New Messages
        • Read Message
        • Post New Thread
        • Reply to message
        • Post New Poll
        • Submit Vote
        • Post reward post
        • Delete my own posts
        • Delete my own threads
        • Rate post

        2000-2018 ASPPlayground.NET Forum Version 3.9