App v client not updating
Unlike in SCCM 2007, deleting the deployment of an App-V application is not removing it on the clients.In SCCM 2012 it has to be removed with an uninstall deployment like physical applications.This will take a lot of time to create, as it is much more configuration then the option being used before. That way the Microsoft query mentioned is not needed, way to many clicks for me!Just create an Install and Uninstall collection and deployment per application.Deployment of applications is done on the same collection in this scenario.That way management (adding users to a group) can be done in Active Directory, no need to add users in the Config Mgr console. When deploying an application to a already logged on session, nothing is happening.Please pay attention to the details in the readme about the order of upgrade installation, as this is different from prior releases due to the changes to support the new connection groups.You should upgrade the servers before upgrading ANY clients.
No word on what they were trying to fix, but presumably it was to fix a different virtual service issue reported by a customer.
The msdn download center has been all bonkers so I haven’t gotten the actual bits yet.
In the release, all components of App-V are upgraded. There are MDOP downloads, RDS downloads, and Hosting Provider downloads showing on the site (even if the download button isn’t working. Each app will act differently, but often the when at the client and you launch the virtual app, it will in some way complain that it isn’t installed or configured correctly and refuse to run.
Oh, it was still better than the alternatives, but not necessarily better than App-V 4.6.
At that time, To start with, everything here is based upon a combination of access to pre-release software, plus a review of the release notes.
A user policy refresh must be done first, or just logoff and logon again.