Good question, I haven't thought about this before. If using Application Method you'd probably have to use Detection Method for Version => xxx.xx Otherwise, standard Package deployment would work.
On Tue, Jan 23, 2018 at 12:23 PM, Heaton, Joseph@Wildlife < [email protected]> wrote: > I think the only way it would go back and forth, is if you select “Always > rerun”. I typically select “rerun upon failure”, or something to that > effect. > > > > So, deploy the base app with SCCM, then import and upgrade/patch using the > SCUP import. > > > > *From:* [email protected] [mailto:listsadmin@lists. > myitforum.com] *On Behalf Of *Chris Carbone > *Sent:* Tuesday, January 23, 2018 9:15 AM > *To:* '[email protected]' <[email protected]> > *Subject:* [mssms] Questions around deploying with SCCM/SCUP > > > > Hello All, > > > > This is probably a goofy question but wanted to see how others are > handling this. We recently purchased PatchMyPC licenses to leverage > patching 3rd party applications. I was not aware that this will only update > existing installed applications and you cannot use it for pushing software > to machines that never had the software installed. > > > > How is everyone handling I guess the, “base” version of your applications > in SCCM? Do you just update the detection method to include the newest > build from SCUP so it will always show as compliant in software center? Or > do you update the base version every so often? I guess if you are not > careful and push out the base application and leave it out there, then down > the road also push out a newer update with the SCUP version, the machine > will go back and forth installing the old one and newer one. > > > > I also have a couple steps in my TS to install applications during OSD and > I guess with SCUP when it imports into SCCM, shows up as a software update. > I know how software updates and task sequences do not work all that great. > Are you also not using SCUP/PatchMyPC for OSD applications? Or found a > dependable way to do this? > > > > Thanks in advance! > > > > Chris > > This electronic mail transmission may contain confidential information > intended only for the use of the individual(s) identified as addressee(s). > If you are not the intended recipient, you are hereby notified that any > disclosure, copying, distribution or the taking of any action in reliance > on the contents of this electronic mail transmission is strictly > prohibited. If you have received this transmission in error, please notify > me by telephone immediately. > > > >
