login vsi company logo login vsi company logo 250x40

 

Get the best possible VDI performance, density and availability with Login VSI
Our Solutions

Warning

JUser: :_load: Unable to load user with ID: 19633

App-V 4.x and 5.x Integration with Login VSI

App-V 4.x and 5.x Integration with Login VSI

Login VSI supports application virtualization, but how do you integrate App-V within a workload? Depending on which applications are virtualized it is possible to run the medium workload without any modifications. When every application is virtualized some modifications are required. Because Login VSI v4 has a simple workload language, App-V can be easily integrated. In this blog post I will explain the App-V 4.x & 5.x integration with Login VSI 4.0.

General configuration

Because Login VSI uses file type association it is easy to integrate App-V in a workload. To run the medium workload without any modifications Microsoft Outlook, Microsoft Word and Adobe Flash cannot be virtualized. When all application are virtualized the workload needs to be modified. In this case we will create a workload where every application is virtualized

Please note: With App-V 4.x the basephase cannot be used because Microsoft Word is started directly during the basephase.

First we need to do some configurations in the Login VSI Management Console. To prevent the Freemind file type association be overwritten we need to configure to not set the file type association during the preparation. Open the Login VSI Management Console and go to the workload settings section.

login vsi management console uncheck set freemind fta

Uncheck “Set Freemind FTA” setting.

I recommend to set Log application start times because this can provide interesting information. When this option is enabled Login VSI will collect the application start time of each application. This can help to get a better understanding about the virtualized applications.

login vsi management console check log application start times

Check “Log application start times” setting.

App-V 4.x workload

For App-V 4.x we can use the SFTTRAY.exe to start the applications. Within the workload we use the App_Start command to start the virtual package. Different segments needs to be modified in the workload. We will start in the prepare segment.

First we need to make sure Microsoft Outlook has a profile configured. Because this is within a virtual package we need to inject the registry setting within the virtual bubble. This can be done by the following command:

SFTTRAY.exe /exe reg.exe /Launch "Microsoft Outlook 2010" add HKEY_CURRENT_USER\Software\Microsoft\Office\%VSI_Office_Version%.0\Outlook\Setup /v importPRF /t REG_SZ /d %TMP%\VSI\Runtime\Outlook.prf

Replace the ImportPRF VSI_RegWrite with the following workload command:

VSI_ShellExecute("Workload", "SFTTRAY.exe",  "/exe reg.exe /Launch "Microsoft Outlook 2010" add HKEY_CURRENT_USER\Software\Microsoft\Office\%VSI_Office_Version%.0\Outlook\Setup /v importPRF /t REG_SZ /d %TMP%\VSI\Runtime\Outlook.prf")

For Microsoft Powerpoint the hardware acceleration is disabled. If this is not set within the virtual package this can be done within the prepare segment. The clean command is as followed:

SFTTRAY.exe /exe reg.exe /Launch "Microsoft PowerPoint 2010" add HKEY_CURRENT_USER\Software\Microsoft\Office\%VSI_Office_Version%.0\Powerpoint\Option /v DisableHardwareNotification /t REG_DWORD /d 1

Replace the VSI_RegWrite with the following workload command:

VSI_ShellExecute("Workload", "SFTTRAY.exe",  "/exe reg.exe /Launch "Microsoft PowerPoint 2010" add HKEY_CURRENT_USER\Software\Microsoft\Office\%VSI_Office_Version%.0\Powerpoint\Option /v DisableHardwareNotification /t REG_DWORD /d 1")

During the prepare phase Microsoft Word will be started and closed. To make sure the virtual package is used we need to replace the App_Start command with the following workload command:

App_Start("WordPrepare", "C:\Program Files\Microsoft Application Virtualization Client", "SFTTRAY.exe", "Title", "Word", "", "/Launch "Microsoft Word 2010"")

Within the prepare segment there are some registry tweaks to let the workload run smoothly. In my case it was not required to include all registry tweaks within the virtual packages. If you experience issues within some Office applications you probably need to modify the following two sections:

“Prevent excel book is windowed” & “Deleting Office auto-repair documents”

Now that we have finished the prepare segment we can edit the other segments. During the workload there are two applications that are not started by the file type association, Microsoft Outlook and Internet Explorer including Adobe Flash. We need to make sure these applications are started by the SFTTRAY.

Within segment 1 we need to start Microsoft Outlook. Replace the current App_Start with the following workload command:

App_Start("Outlook", "C:\Program Files\Microsoft Application Virtualization Client", "SFTTRAY.exe", "Title", "lang:Outlook:lang", "", '/Launch "Microsoft Outlook 2010"')

Within segment 4 we need to start Internet Explorer with Adobe Flash. Replace the current Web_Start with the following workload command:

App_Start("IE5", "C:\Program Files\Microsoft Application Virtualization Client", "SFTTRAY.exe", "Title", "Login VSI Flash Game", "", "/Launch "Internet Explorer" %VSI_WebLocation%\FlashGame\index.html")

Save the workload file and the App-V workload can be used including the virtual applications.

App-V 5.x workload

For App-V 5.x we can directly start the applications. Within the workload we use the App_Start command to start the virtual package. Different segments need to be modified in the workload. We will start in the prepare segment.

First we need to make sure Microsoft Outlook has a profile configured. Because this is within a virtual package we need to inject the registry setting within the virtual bubble. This can be done by the following command:

reg.exe /AppVVE:AE2439BA-A9CF-4220-A7F0-BBB378A29EDD_04244DE7-A338-4944-8CF0-2013926DCB59 add HKEY_CURRENT_USER\Software\Microsoft\Office\%VSI_Office_Version%.0\Outlook\Setup /v importPRF /t REG_SZ /d %TMP%\VSI\Runtime\Outlook.prf

Please note the packageGUID and versionGUID are unique for each package. To get the packageGUID and versionGUID run the following command in powershell:

Get-AppvClientPackage

More information can be found here.

To make sure the workload can execute this, replace the action with the following workload command:

VSI_ShellExecute("Workload", "reg.exe",  "/AppVVE:AE2439BA-A9CF-4220-A7F0-BBB378A29EDD_04244DE7-A338-4944-8CF0-2013926DCB59 add HKEY_CURRENT_USER\Software\Microsoft\Office\%VSI_Office_Version%.0\Outlook\Setup /v importPRF /t REG_SZ /d %TMP%\VSI\Runtime\Outlook.prf")

For Microsoft Powerpoint the hardware acceleration is disabled. If this is not set within the virtual package this can be done within the prepare segment. The clean command is as followed:

reg.exe /AppVVE:AE2439BA-A9CF-4220-A7F0-BBB378A29EDD_04244DE7-A338-4944-8CF0-2013926DCB59 add HKEY_CURRENT_USER\Software\Microsoft\Office\%VSI_Office_Version%.0\Powerpoint\Options /v DisableHardwareNotification /t REG_DWORD /d 1

Replace the VSI_RegWrite with the following workload command:

VSI_ShellExecute("Workload", "reg.exe",  "/AppVVE:AE2439BA-A9CF-4220-A7F0-BBB378A29EDD_04244DE7-A338-4944-8CF0-2013926DCB59 add HKEY_CURRENT_USER\Software\Microsoft\Office\%VSI_Office_Version%.0\Powerpoint\Options /v DisableHardwareNotification /t REG_DWORD /d 1")

Within the prepare segment there are some registry tweaks to let the workload run smoothly. In my case it was not required to include all registry tweaks within the virtual packages. If you experience issues within some Office applications you probably need to modified the following two sections:

“Prevent excel book is windowed” & “Deleting Office auto-repair documents”

Now that we have finished the prepare segment we can edit the workload segments. During the workload there are two applications that are not started by the file type association, Microsoft Outlook and Internet Explorer including Adobe Flash. We need to make sure these applications are started within the package root directory.

Within segment 1 we need to start Microsoft Outlook. Replace the current App_Start with the following workload command:

App_Start("Outlook", "%ALLUSERSPROFILE%\Microsoft\AppV\Client\Integration\7AFDB884-2ED9-44A1-A69F-0D6206945C55\Root\Office14\", "Outlook.exe", "Title", "lang:Outlook:lang")

Within segment 4 we need to start Internet Explorer with Adobe Flash. Replace the current Web_Start with the following workload command:

App_Start("IE5", "C:\Program Files\Internet Explorer\", "iexplore.exe", "Title", "Login VSI", "", "/appvve:9DD1E58B-5FED-4EA7-A9C3-7520D1E76989_E9D056E8-7304-42E8-97B6-E52683B8156B %VSI_WebLocation%\FlashGame\index.html")

Save the workload file and the App-V workload can be used including the virtual applications.

Conclusion

With Login VSI it is simple to integrate Microsoft App-V or any other virtualization technique within a workload. When Microsoft Outlook, Microsoft Word and Adobe Flash are not virtualized you can even run the official medium workload. You just have to make sure the file type association for the virtual applications are set correctly.

The complete example workload file can be found here: App-V 4.x & App-V 5.x.

This blog was originally published on Logit Blog.

About the author

Tags: How-to, Login VSI, Microsoft, Application Virtualization

Popular Blogs

Login VSI Blog Article - Microsoft Windows 10 Default FTA Associations - Teaser Image

Windows 10 Default File Type Associations and Login VSI

When Login VSI 4.1 was released, the majority of desktops were running Windows 7 and life was easy. We’d set the default filetype for an application and it would simply work. Continue Reading
Login VSI - Press Release - IGEL - Login VSI Partner to Optimize End User Computing Experience Image

[Press Release] IGEL Partners with Login VSI to Optimize the End User Computing Experience

Login PI enables organizations to better protect the performance and availability of their IGEL OS-powered virtual desktop environments Continue Reading
Login VSI - Blog - Login PI Blog Teaser Image - Windows Virtual Desktop: How To Monitor User Experience With Login PI

Windows Virtual Desktop – How to Monitor User Experience?

Microsoft has just announced the public preview of their new Windows Virtual Desktop (WVD) offering at Microsoft Ignite on Tour in Amsterdam today. For those of you who’ve not followed the rumors or the private beta, here’s the outline... Continue Reading
Login VSI Blog - Teaser Image - A Practical Guide to VDI Change Management - Part 1

A Practical Guide to VDI Change Management

Part 1: IT Change Management in general The first in an 8-part series, this practical guide to VDI Change Management will guide you through the transformation of the IT department from a back-end function into a core competency for every modern organization. Continue Reading
Investigating Online Application Performance with Login PI

Investigating Online Application Performance with Login PI

As many companies do, we use a CRM system. Recently, I have been getting complaints about our cloud CRM system, Microsoft Dynamics, being slow. I tried to investigate this by shadowing one of our users to see what was wrong. Continue Reading
Login VSI Blog - How-To Update, Protect Against RIDL, Fallout MDS Vulnerability

How-To: Update, Protect Against RIDL, Fallout MDS Vulnerability

RIDL & Fallout MDS vulnerabilities, impact on VDI performance & actions to take. FAQs we’re receiving & updates on performance tests executed to patch flaws Intel calls “Microarchitectural Data Sampling (M.D.S.)” aka: Rogue In-Flight Data Load (RIDL), Fallout, ZombieLoad & Store-to-Leak Forwarding. Continue Reading
Cookie Settings