The D-spot

Microsoft’s application virtualization solution has reached version 4.6 some weeks ago. The most important thing about version 4.6 is support for 64 bit. The Server parts could run on x64 operating systems, but it was impossible to install the AppV client on x64 operating systems. Time to upgrade!

As the client needs to be updated first, I will cover the client upgrade process only. (Client first, server next, sequencer last). Good to know that only the client and the sequencer are updated to version 4.6. No need to update your Management server as version 4.5.2.17140 is still the latest and greatest.

AppV has some Prerequisites, I will install them first. Then I will install the AppV client itself, using some command line parameters and a registry file import for applying custom settings.

Prerequisites

Application error reporting

msiexec /I SOURCE_PATH\dw20shared.msi /QN APPGUID={4C1CE627-6B28-436E-BD12-3A881065FB20} REBOOT=REALLYSUPPRESS ALLUSERS=1

Visual C++ 2005 runtime

SOURCE_PATH\vcredist2005_x86.exe /Q:A /c:”VCREDI~3.exe /Q:A /C:”"MSIEXEC /I VCREDIST.MSI /QN “”"

Visual C++ 2008 runtime

msiexec /i SOURCE_PATH\vc2008\vc_red.msi /qn /l*v “LOGFILE_PATH\vc2008runtime.log”

AppV 4.6 Client with command line parameters

Because storage is expensive, we have a different cache policy for virtual machines. Cache size on virtual systems don’t have to be as enormous as on physical machines. Not only the cache size is reduced in virtual machines, also the AutoLoad features are disabled via the MSI command line parameters.

To identify virtual machines I query on the computer name. As we use specific names for our VM’s, this should be a piece of cake!

We do an architecture check in a batch file. So I have two code blocks, one for x64 and another for x86 operating systems. Only the paths are different, so I will post only one.

AppV Client Installation

Echo install AppV x64 Client

rem Virtual Machine check
Echo %computername% | findstr /i “ISOPC99 VPC” >NUL && (
    Echo Installing AppV x64 client for Virtual Machines
    msiexec /i “SOURCE_PATH\x64\setup.msi” SWICACHESIZE=”4096″ autoloadTriggers=0 AutoLoadTarget=0 AutoLoadonLaunch=0 AutoLoadonRefresh=0 AutoLoadonLogin=0 SWIDCSDISPLAY=”Company Streaming Server” SWIDCSTYPE=”RTSP” SWIDCSHOST=”appvserver.domain.local” SWIDCSPORT=”554″ SWIDCSREFRESH=”on” SWIGLOBALDATA=”C:\Program Files\Microsoft Application Virtualization Client\GLOBAL\” SWISOFTGRIDDRIVE=”Q” /q REBOOT=REALLYSUPPRESS /l*v “LOGFILE_PATH\appv46.log”
    ) || ( 
   Echo Installing AppV x64 client for Physical Machines
    msiexec /i “SOURCE_PATH\Source\x64\setup.msi” MinFreeSpaceMB=”6000″ SWIDCSDISPLAY=”Company Streaming Server” SWIDCSTYPE=”RTSP” SWIDCSHOST=”appvserver.domain.local” SWIDCSPORT=”554″ SWIDCSREFRESH=”on” SWIGLOBALDATA=”C:\Program Files\Microsoft Application Virtualization Client\GLOBAL\” SWISOFTGRIDDRIVE=”Q” /q REBOOT=REALLYSUPPRESS /l*v “LOGFILE_PATH\appv46.log”
    )

Echo Import Regkeys
regedit /s SOURCE_PATH\appv64_v2.reg

The registry file that is imported in the last line specify the sftlog.txt log file location, and some other tweaks, have a look:

Registry import (x86)

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration]
“SystemEventLogLevel”=dword:00000004
“LogFileName”=”C:\\PATH_OF_YOUR_CHOICE\\sftlog.txt”
“UserDataDirectory”=”%APPDATA%”
“ApplicationSourceRoot”=”RTSP://server.domain.local:554″
“LaunchRecordMask”=dword:005a0000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\DC Servers\Company Streaming Server]
“Period”=dword:00000000
“Refresh”=dword:00000001
“Reporting”=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\AppFS]
“UnloadLeastRecentlyUsed”=dword:00000001
“MinPackageAge”=dword:00000001

Registry import (x64)

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\Configuration]
“SystemEventLogLevel”=dword:00000004
“LogFileName”=”C:\\PATH_OF_YOUR_CHOICE\\sftlog.txt”
“UserDataDirectory”=”%APPDATA%”
“ApplicationSourceRoot”=”RTSP://server.domain.local:554″
“LaunchRecordMask”=dword:005a0000

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\DC Servers\Company Streaming Server]
“Period”=dword:00000000
“Refresh”=dword:00000001
“Reporting”=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\Client\AppFS]
“UnloadLeastRecentlyUsed”=dword:00000001
“MinPackageAge”=dword:00000001

That’s it.

When the SQL Server is on the same machine as the App-V Management Server (formerly known as the VAS Server), the App-V Management Server Service doesn’t start after a reboot.

Solve this by adding the MSSQLSERVER as dependency to App-V service in the registry. (Use MSSQL$SQLEXPRESS when using SQL Server Express edition).

To finalize, add a DWORD named ‘DelayedAutostart’ with value 1.

Reboot the server, the Application Virtualization Management Server service should start (with a slight delay).

When troubleshooting App-V applications looking into the bubble can ease your work.
Sneaking into the bubble gives you information about which files are stored local and which virtual.  This way you know what files actually will be used by the application.  You can modify some configuration files without resequencing the whole application.

There are some ways to view inside the virtual Softgrid / App-V bubble.

1. First method is a PRE LAUNCH script in the OSD file that would launch a Command Prompt window inside the bubble

Editing the .OSD file, inside the <DEPENDENCY> tag add:

<SCRIPT EVENT="LAUNCH" TIMING="PRE" PROTECT="TRUE" WAIT="TRUE" TIMEOUT="">
<HREF>cmd.exe</HREF>
</SCRIPT>

Launching the OSD file will present you a DOS BOX inside the bubble.  With this box you can do anything.  Browsing the Q: drive, starting regedit, changing config/ini files, map a drive, copy some files ..

2. Second way by using sfttray

• sftmime /query obj:app /short -> gives you a list of all Softgrid applications on your client

• sfttray /EXE cmd.exe /launch “Notepad++ 5.4.2″ -> launches a command prompt in the bubble

3. Third method using SFT Explorer

With SFT Explorer you can look inside the SFT file without ever having to load it. You can see files and registry keys would look like if the App-V application was loaded on the target machine. It only supports viewing in the SFT file, you cannot make any changes.