I set this up for a previous employers. We set a global condition as a requirement on the deployment type that checked if a user was logged on. If one was on, they got the user deployment type. If one wasn't on, they got the system deployment type.
The problem with doing it like this is if you set up a deployment type to run interactive with the user, you will no longer be able to add the app to a task sequence. So they did this to avoid duplicating apps, but had to duplicate apps when they started building OSD in 2012; one OSD app and one deployment app. On Thu, Jun 5, 2014 at 11:20 AM, Mitch Beck <[email protected]> wrote: > Hey Guys! > > > > Is it possible to have one Application-Model package setup with two > deployment types: > > > > 1. Two Deployment Type Differences: > > a. Runs whether or not a user is logged on > > b. Runs only when no user is logged on > > > > 2. Two deployments: > > 1. Deployment 1: Make Available to a user collection > > a. Deployment type: Runs *whether or not a user is logged on* > > 2. Deployment 2: Make Required for device collection > > a. Deployment type: Runs only *when no user is logged on* > > > > Is this possible or do I need to setup two separate App-Model packages for > this to work? Currently I have been setting up two separate Applications > (Screenshot below). > > > > Thanks, > > > > *Mitch* > > > > *Circular 230 Notice:* In accordance with Treasury Regulations we notify > you that any tax advice given herein (or in any attachments) is not > intended or written to be used, and cannot be used by any taxpayer, for the > purpose of (i) avoiding tax penalties or (ii) promoting, marketing or > recommending to another party any transaction or matter addressed herein > (or in any attachments). > > *Attention:* This message is sent by a law firm and may contain > information that is privileged or confidential. If you received this > transmission in error, please notify the sender by reply e-mail and delete > the message and any attachments. > >
