Enabling computer based targeting in App-V 5.0

Share on facebook
Share on twitter
Share on linkedin
Share on reddit
Share on stumbleupon

Happy New Year! I hope you all had a perfect holiday season, I definitely did but now I think it’s time for my first post of 2013….

Now this is something that I have hardly heard anyone really talk about with App-V 5.0; the fact that we can now target machines instead of users when publishing packages when using full infrastructure deployment.

In this post I am going to publish a media player (VLC Player) to my client by targeting the machine not the user.

First thing to do is run the following command after you have added a publishing server to your client:

You will notice there is a GlobalRefreshEnabled and GlobalRefreshOnLogon setting, these two settings control whether we perform a machine wide refresh and also if it is triggered at logon. There are also two other settings below that which can be used to set periodic refreshes also.

So to start machine targeting to we need to run the following command on the client to enable global refresh and to trigger it at logon:

We should now see the new settings have been applied:

set-appvpub

Now in Active Directory Users and Computers we need to create a security group and add our desired computer object into it, I’ve created a group called App-V Computers:

aduac

Next we need to publish the application to the group we just created:

publish

Finally we need to log off and back onto the client to trigger a refresh and we will find we now have VLC Player published:

vlc

If we hit the publishing server URL as a user to will noticed that VLC doesn’t appear in the list of applications, this is of course because the package is published to the machine:

pubserv

One last thing to note is that if you change the global refresh settings back to false the applications published to the machine will remain on the client, even after logging off and back on. We need to unpublish the package on the management server while the settings are still enabled on the client to successfully remove the package.

 

Leave a Reply.

19 thoughts on “Enabling computer based targeting in App-V 5.0”

  1. Followed your article but only packages assigned to the user are being deployed to my client computer.

    The client computer is in the AD group that is assigned to the package, and I have updated the GPO that applies the App-V client configuration. Also I have manually tried updating the App-V client

    Not sure what else to check?

    thanks in advance

    • Can you verify the following:

      – The GlobalRefreshEnabled and GlobalRefreshOnLogon settings are both set to true when doing a Get-AppvPublishingServer.

      – The client has been rebooted after the change

      – The AD group membership has been applied to the client machine

  2. thanks the The GlobalRefreshEnabled and GlobalRefreshOnLogon settings were still set to false, despite the GPO being applied.

    I manually set them and bang it worked. Need to work out why my GPO is not doing this

    thanks for your time

  3. Hi Thamim,

    Do you know if computer based targeting is now enabled for the RDS client also? Full appv infrastructure.

    Thanks

    Kevin

  4. hey Kevin, i followed the steps but the app doesn’t show up on the target computer. do I need to install anything on the target computer….eg another appv client…so it syncs??

    thanks

  5. Hi All, Thanks for your guide, I was able to publish packages globally, but I have a problem, when the package is published globally and I remove the access for certain applications for example excel since I’m streaming office, the client is still able to open excel on his computer, but If I publish to the user instead, he don’t have access to excel. Any clue ?

  6. Do you need to modify any of the properties of the actual package, so that it publishes to the machine? I’ve made the changes on the machine for the GlobalRefreshEnabled and GlobalRefreshOnLogon, added machine to an AD group, but the App does not appear on the server.

  7. I’ve followed the guide and it’s similar to the office 2013 deployment. However I am still not getting it to work automatically.

    I have the machines in a group and assigned the group to the package but I didn’t have it published. Interestingly it is in the cache but not installed(published).

    On the client t I could run publish-appvclientpackage -global -path c:/programdata/appv/guid/guid/package.appv but I need it to be more automated than having to run commands.

    Running Appv 5.0 sp2 hot fix 4

    • Hi, I wouldn’t expect you to be able to run the command you mentioned as the .appv wouldn’t reside in the ProgramData location? Have you ensured GlobalRefresh is both enabled and set to run? Have you made sure your computer has updated its group membership from AD?

  8. Thamim,
    how would we go about getting these to sync on computer startup; NOT on logon? Running this in a VDI environment; I would like to preload the apps on startup; so the only thing syncing on user-logon are user apps.
    Any ideas?

    • Hi,

      The triggers for a global refresh are at logon or any other periodic interval, start-up itself is not an option nor would I recommend this approach. The best approach in VDI would be the ‘pre-bake’ packages into the actual VDI image, so basically deliver your packages into the build itself before it is delivered.

  9. Hi Thamim,
    I am trying to publish App-V packages in VDI environment to non-persistent and RDS desktops and with SCS mode enabled in both. The App-v configurations are applied via GPO and I have enabled both User Refresh and Global refresh options. The App-V apps are published to user groups and not to computer groups. The issue is there is a marked delay in the display of App-V icons in the Standard Desktop although this does not seem to be an issues with RDS desktop.

    Am I missing any App-V configuration in the Standard desktop?
    Regards,
    VS

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.