The second most exciting feature (to me) is the support for packages sequenced with 4.5 to be played on 4.6 clients (even the x64 client!).  The problem I had this morning, though, was there are a ton of blogs touting this support, but no one bothered to publish how.  For instance, from The App-V Team Blog:

All your pre-4.6 packages are valid and can continue to be used on the 4.6 client – just modify the OSD file to include the OS values for the 32 and/or 64-bit platform as target, as appropriate.

So, it can be done, but how do I include support for Windows 7 x64 clients in the OSD?  Like this:

Your current OSD files have a section that includes something similar to the following:

<OS VALUE=”WinXP”/>
<OS VALUE=”Win7″/>

This indicates that the package is available for all Windows XP and Windows 7 clients (32-bit of course, because version 4.5 does not support 64-bit).  So, add the following to your OSD file under the last “OS VALUE” entry to enable support for Windows 7 x64:

<OS VALUE=”Win764″/>

And here’s a list of all the available target operating systems:

<OS VALUE=”Win2003TS”/>
<OS VALUE=”Win2003TS64″/>
<OS VALUE=”Win2008R2TS64″/>
<OS VALUE=”Win2008TS”/>
<OS VALUE=”Win2008TS64″/>
<OS VALUE=”Win7″/>
<OS VALUE=”Win764″/>
<OS VALUE=”WinVista”/>
<OS VALUE=”WinVista64″/>
<OS VALUE=”WinXP”/>
<OS VALUE=”WinXP64″/>

Generally, the App-V Client refreshes the applications published to a user at log on.  This, of course, means valuable seconds/minutes are wasted waiting for the machine to log off and back on.  So, of course, there is a way to manually refresh the published applications via the App-V Client Console.

As any good administrator does (yeah, right), they do not set themselves as a local administrator for the machine they are using.  In order to access some of the “administrative-y” features of the App-V Client Console (such as the option to delete an application from the client), one must “Run as Administrator” – assuming they aren’t a local administrator.

Here’s the kicker: if you’ve opened the console as an administrator (using “Run as…”) and refresh the published applications, you’ll be updating it based on the user’s credentials you’ve provided.  If you’re running the console under the logged in user’s credentials, you’ll be updating the applications based on the applications published to that user.

I’ll admit this does sound like an obvious conclusion, but for those of us who choose not to be local administrators it seems a bit confusing.  Just remember: the console updates based on user – not machine (because the applications are published based on a user and not a computer account).