AppV 4.6 Migrations to AppV 5 – real world experience.

  • Client Issues –

Clients need a minimum of AppV 4.6 sp2 –

AppV 4.6 is on SP3 HOTFIX X – But it is debatable if SP3 (support for windows 8) and hot fixes are needed

Lots of pain automating deployments –

I’ve had windows installer corruption – still looking into this.

  • AppV Client Installation

4.6 RTM

4.6 SP2 – Requires REBOOT

4.6 SP3 – Requires REBOOT

5.0 RTM –

  • Powershell – Requires REBOOT
  • DOTNET 4.5
  • KBxxx

5.0 SP2 – Requires REBOOT

5.0 SP2 Hot fix 4 – Requires REBOOT

As far as the conversation about deploying AppV 5SP2 hotfix 4 –

Within VDi

http://www.loginconsultants.com/en/about/blog/all/item/first-results-app-v-5-sp2-hotfix-4

Great Blog about VFS functionality

http://blogs.technet.com/b/gladiatormsft/archive/2014/05/24/app-v-5-on-sequencing-using-tokenized-paths-pvad-s-vfs-and-vfs-write-mode.aspx

Do your research – TEST – and decide for yourself.

For me – re converting 4.6 apps within a 5.0 SP2 HF4 sequencer – FIXED a lot of converted app issues

  • Client interface

AppV 5 SP2 NO interface by default

Can be deployed via

  • MSI
  • AppV Console/SCCM

  • Client Migration issues

Shortcuts – converted apps from 4.6 – shortcut location is NOT retained

Ways to mod the location of the converted shortcut

  • Edit converted package and re point shortcut
  • Edit XML to repoint shortcut
  • Use appvve:

C:\Windows\System32\xyz.exe "%LOCALAPPDATA%\Microsoft\AppV\Client\Integration\%PKGGUID%\Root\xyz.hta" /appvve:\%PKGGUID%_%PKGIDGUID%

User doesn’t have AppV 5 Client – THIS has been my biggest PITA – because

  • Client doesn’t have 4.6sp2/3
  • Client doesn’t have powershell
  • User hasn’t closed appv 4.6 apps

Removing 4.6 apps WILL NOT delete a copied version of the 4.6 shortcut – so PLAN to create a script to delete the orphaned shortcut

Part 2 of this blog will consist of detailed migration steps-

the migration process – step by step going from AppV 4.6 (console) to SCCM 2012