Hi,

We are using SCCM 2012 R2 CU4

Wanted to know if there are implications, risks or settings to take while moving from a device based deployment model to user based deployment model. Currently all our deployments are targeted to devices and we wanted to explore the option of deploying to users. That way even if user logs into a different machine required applications get installed.

We use Task Sequence model for deploying most of the custom software and application/package model for other standard software

I know that choosing Install for user in the Application Deployment type settings works differently for different software.

I just want to know if we need to consider anything before applying this approach to the production users

• Edited by MicroDex 18 hours 14 minutes ago

Are you going to be deploying packages/programs or are you using the application model? The differences between deploying to devices vs. users are not all that great but there are things to keep in mind such as:

* Do you have the application catalog configured?

* How deployments show up in software center vs. application catalog (see here: http://blogs.technet.com/b/configmgrteam/archive/2012/03/31/introducing-the-application-catalog-and-software-center-in-system-center-2012-configuration-manager.aspx)

* User device affinity - are you going to have requirements to only deploy on a user's primary device?

Jeff

I know that choosing Install for user in the Application Deployment type settings works differently for different software.

Installing as user is completely different than targeting users with your deployments; the later in no way implies the former. The later is simply controlling on what systems the installer will be run. The former changes how the installer is run and should not be done unless you know the installer and application it installs supports per user installations as many do not. Servicing per-user installations is also more difficult as is inventorying them.

Test, test, test before you use a per-user installation.

As mentioned though, this does not preclude you from targeting users with your deployments. Doing this is still perfectly applicable with per-system installations. Of course, every user on that system will now access to the application installed. App-V is one possible solution to this dilemma as it can make any application a per-user application.

Also, neither per-user installations or user targeting works with task sequences.