Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED Difference between Install for system, install for user , deploy to user collection deploy to device collection

  • Thread starter Thread starter micdam
  • Start date Start date
  • Replies Replies 5
  • Views Views 19K

micdam

Well-Known Member
Messages
99
Reaction score
1
Points
8
Hi,
can someone explain me the Difference between creating an application with "Install for system", "install for user" value for Installation behaviour property and "deploy to user collection" vs "deploy to device collection" with this type of installation debhaviour
 
below is the difference for install for user and system/device
  • Install for user: The client only installs the application for the user to whom you deploy the application.
  • Install for system: The client installs the application only once. It's available to all users.
  • Install for system if resource is device; otherwise, install for user: If you deploy the application to a device, the client installs it for all users. If you deploy the application to a user, the client only installs it for that user.
 
You'll almost always want to install as system. In my experience, you only want to install as user when the application being deployed only installs to the logged on user's profile and not system-wide. For example, AppX installed under Susan's profile will appear invisible to Caren's profile. If AppX was deployed as system, it would be invisible to all logged on users.
 
below is the difference for install for user and system/device
  • Install for user: The client only installs the application for the user to whom you deploy the application.
  • Install for system: The client installs the application only once. It's available to all users.
  • Install for system if resource is device; otherwise, install for user: If you deploy the application to a device, the client installs it for all users. If you deploy the application to a user, the client only installs it for that user.
[/QUOTE[/QUO
You'll almost always want to install as system. In my experience, you only want to install as user when the application being deployed only installs to the logged on user's profile and not system-wide. For example, AppX installed under Susan's profile will appear invisible to Caren's profile. If AppX was deployed as system, it would be invisible to all logged on users.

But if i create appx with "installation behavour" property set to "Install to system" and deploy it to a user collectin that contains Susan the result is that after the application has been installed by the user Susan (software center) if caren logs to the same device the application is available also for caren. Is it Right?
 
Yes, it does not matter if you deploy to user or device collection. It matters how the app installs and if it requires to run with specific permissions or only installs to the logged on profile and not globally (unusual). Typically an app will be installed globally to the system and be available to all users of the system regardless of how it was deployed.
 
Yes, it does not matter if you deploy to user or device collection. It matters how the app installs and if it requires to run with specific permissions or only installs to the logged on profile and not globally (unusual). Typically an app will be installed globally to the system and be available to all users of the system regardless of how it was deployed.
Thankyou
 

Forum statistics

Threads
7,187
Messages
28,058
Members
18,330
Latest member
curtsmith
Back
Top