change the app to restart required. - deployment type properties #2 is because it does not actually finish until a user logs on
On Fri, May 23, 2014 at 4:22 PM, Patridge, Joseph <[email protected]>wrote: > *Hi – * > > > > We’re trying to do a software deployment in SCCM 2012 that requires > running two executables, each of which requires a restart IMMEDIATELY after > it completes. We want to configure it with an installation deadline, but > give the users the option to run it manually prior to the deadline. > > > > We have tried two methods, both of which pose challenges: > > 1) We tried running a task sequence, which makes the reboot portion > much easier, but even though the task sequence itself contains reboots, the > user notification indicates that a start is not required. Anyone know a way > around this? > > > > > > 2) Then we tried daisy-chaining the two applications together in an > advertisement. But we discovered that even though both applications are set > to run ‘whether or not a user is logged in’, if you run the first one while > logged in, and then the reboot completes, the 2nd portion won’t complete > until the same user logs back on. We would hope that it would run once it > gets back to the Windows logon screen. Anyone have any experience with > that? Is it because the first package ran with a user logged in, that the 2 > nd is expecting to run in the same context? > > > > Thanks, Joe > > > --------------------------------------------------------------------- > CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, > is for the sole use of the intended recipient(s) and may contain > confidential > or legally privileged information. Any unauthorized review, use, disclosure > or distribution is prohibited. If you are not the intended recipient, > please > contact the sender by reply e-mail and destroy all copies of this original > message. > > --------------------------------------------------------------------- > >
