Well, let me start this off by saying that hopefully I'm doing something wrong...
What I'm looking to achieve is to Install some App-V sequenced applications to some users Primary Devices before the user logs in, but to also have these applications be usable by anyone and everyone that might come along later and use this same computer.
That's all easy enough with regular applications in SCCM, but I'm running into issues doing this with App-V applications.
I've noticed that if I just make an App-V application "Available" to a user and they go to the Application Catalog and install it, then what I get is an application that installs into the profile specific AppData directory and then that application
is not available to anyone else on that machine.
If I deploy an Application and target the computer instead, then the same App-V application will install into the ProgramData directory and everyone that comes along can use this application (this is fine, but I really want to target users and not computers).
So what I tried next was to Deploy the application to a user and make it a "Required" application and to also set it to "pre-deploy" to the users primary device as seen in the image below.
![]()
However, when I do this...what I'm seeing now is that the application installs in BOTH locations. If the user has never logged in, the application will install in only the ProgramData directory which makes it available to the machine. Then when they
do login, SCCM decides that it also needs to isntall the application to the user...and it does (giving them double desktop icons). Or if they are logged in when the install happens then it goes ahead and installs to both locations at the same time (again with
double desktop icons).
So...how do I resolve this?
As stated, I want the app on the machine, but only once and I prefer to target users. Can this be done with an App-V application?
Mike...