GLADIATOR@MSFT

Adventures in Desktop, Application, and User State Virtualization

Important Note for App-V 4.6 Users Upgrading to Windows 8.1

Important Note for App-V 4.6 Users Upgrading to Windows 8.1

  • Comments 5
  • Likes

If you have not already heard, today MDOP (Microsoft Desktop Optimization Pack) 2013 R2 became generally available for download to our MDOP customers. More information can be found here:

http://blogs.windows.com/windows/b/business/archive/2013/12/02/mdop-2013-r2-now-available.aspx

and

http://blogs.windows.com/windows/b/springboard/archive/2013/12/02/announcing-mdop-2013-r2.aspx

This latest incarnation of MDOP includes the release of:

  • Application Virtualization (App-V) 5.0 SP2 and the virtualization of Office 2013
  • Application Virtualization (App-V) 4.6 SP3
  • User Experience Virtualization (UE-V) 2.0
  • Microsoft BitLocker Administration and Monitoring (MBAM) 2.0 SP1, which also offers multi-language support.
  • Diagnostics and Recovery Toolset (DaRT) 8.1
  • Advanced Policy Group Management (APGM) 4.0 SP2

Primary release pillars for MDOP 2013 R2 revolve around support for Windows 8.1.

If you are still using App-V 4.6 on Windows 7 (either 4.6 SP1 or SP2) or Windows 8 (4.6 SP2) you may also be aware that the installation of Windows 8.1 will be blocked if it detects the presence of any version of App-V 4.x. This will also include 4.6 SP3 if you decide to go ahead and pre-install SP3 prior to the upgrade to 8.1. This relates to the
operating-specific drivers that are used by App-V 4.6. If you are planning to use Windows 8.1 with App-V 4.6 SP3, you will need to first remove any installations of App-V 4.6. Then you can upgrade/install Windows 8.1. Once Windows 8.1 is installed, you can install App-V 4.6 SP3. Please note this approach only applies to App-V 4.6 and not App-V 5.0.

While the App-V Client settings and user application settings will be retained with the uninstallation/reinstallation approach, the App-V 4.6 cache will be reset so applications will have to be re-delivered (re-streamed, pre-cached, re-advertised, etc.) Normally to avoid having to do this in the past, administrators would simply do in-place upgrades. This one-time exception does not allow for this and will require likely adjustments if you have users currently using virtual applications with 4.6 and will be upgrading to Windows 8.1 from Windows 7 or Windows 8.

 

Comments
  • Just curious...you refer to some service packs that AFAIK do not (yet) exist:  Windows 7 SP2 and Windows 8 SP2.  What gives? Is SP2 for Windows 7 and 8 released?

  • @Robbie, after reading it again, I noticed exactly what confused you and I believed I corrected it.

  • Hi, We have a banking client that has DOS-based banking system. Can we use App-V on Windows 8.1 to be able to use the application? Can we use Med-V instead.

  • In most cases, App-V will NOT resolve application compatibility issues for Windows 8.1. I am assuming you cannot run this application natively or we have a bitness issue (16/64). Since MED-V is EOL and does not run on Windows 8.1, my advise (outside of app upgrade/migration) would be to look at Hosting Client Hyper-V (assuming the application runs on a recent OS like Windows 7 32-bit.)

  • @emansky; I have done this with success in the past, here at the University we have several 16-bit applications running on 64-bit Windows through App-V. There are two approaches I have used:

    1. DOS Software; Pack an installation of DosBox with the application.
    2. Windows Software; Pack DosBox, Windows 3.1x, and then the application.

    Of course, every app has it's quirks you'll need to figure out, but with some tinkering, this approach has helped us with these kind of issues, where upgrading to a new version is not possible.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment