Microsoft Application Virtualization Client

Version: 4
Views: 4.7k  |  Created: 10/27/2008

Average Rating: 0
Application Virtualization Client has 1 inventory records, 6 Questions, 2 Blogs and 8 links. Please help add to this by sharing more!

Deployment Tips (10)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 1 / 5 (Very Easy) based on 2 ratings
Most Commonly Reported Deployment Method
Vendor Provided Command Line (switch driven)
or cancel
7
Command Line
The correct command line to make the installation silent including all pre-requisites is:
setup.exe /s /v"/quiet /norestart /qn"0\"\"

Applies to the desktop client and the TS client.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
4
Note
Setup.exe checks for and installs any pre-requisites, but if you just want to use the .msi, then you have to install the following:

Microsoft Visual C++ 2005 SP1 Redistributable Package (x86):
http://go.microsoft.com/fwlink/?LinkId=119961.

Microsoft Core XML Services (MSXML) 6.0 SP1 (x86):
http://go.microsoft.com/fwlink/?LinkId=63266.

Microsoft Application Error Reporting:
The install program for this software is included in the Support folder in the self-extracting archive file.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
4
Note
If you want to preinstall the Application Error Reporting prerequisite, you can install this by running dw20shared.msi installer from the client\Support\Watson directory, but the install will fail with a 1603 Windows Installer error if you don't specify the GUID of the application requesting the installation on the command-line. Apparently this is a new feature of the latest AER client.

We pre-installed AER using the following command-line:

start /wait msiexec /i "\\servername\installshare\Microsoft Apps\Desktop Optimization Pack for Software Assurance\2008 R2\Microsoft Application Virtualization CU1\client\Support\Watson\dw20shared.msi" APPGUID={FE495DBC-6D42-4698-B61F-86E655E0796D} ALLUSERS=2 /QN REBOOT=ReallySuppress /LiV %temp%\dw20shared.log
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
2
Virtualization

KIll the browser window after it launches another browser window in IE using the following vbscript:

----------------------------------------------------------------------------

Set oShell = CreateObject("WScript.Shell")
If oShell.AppActivate("type the IE window title you want to close here") Then
WScript.Sleep 500
oShell.SendKeys "%{F4}"
End If

----------------------------------------------------------------------------

 

place the path of the vbscript in the OSD file in the following XML tag:

DEPENDENCY> <SCRIPT EVENT="LAUNCH" TIMING="POST" PROTECT="TRUE" WAIT="TRUE"> <SCRIPTBODY>

type the name or path to the script here eg. killtask.vbs </SCRIPTBODY> </SCRIPT> </DEPENDENCY>

After you launch the appv package, the vbs script will kick in and kill the browser window you defined in the vbscript.

Job done :)

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
1
Command Line
To install the Application Virtualization Client by Using Setup.msi:

msiexec.exe /i "setup.msi" SWICACHESIZE="1024" SWIPUBSVRDISPLAY="Production System" SWIPUBSVRTYPE="HTTP /secure" SWIPUBSVRHOST="PRODSYS" SWIPUBSVRPORT="443" SWIPUBSVRPATH="/AppVirt/appsntype.xml" SWIPUBSVRREFRESH="on" SWISKIPDATASETTINGS="false" SWIGLOBALDATA="D:\AppVirt\Global" SWIUSERDATA="^%HomeDrive^%\Windows\Application Virtualization Client" SWIFSDRIVE="S" /q

Application Virtualization Client Installer Command-Line Parameters documented here:

http://technet.microsoft.com/en-us/library/cc843737.aspx
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
1
Note
I try to deploy as much as I can using MSIs and AD
As stated above, the setup.msi won’t install the prerequisites if they don’t already exist and will just fail. Setup.exe with the options works well, but takes it out of easy control of AD. To deploy fully with AD this worked a charm for me. What we need to do this is the following 8 files:

dw20shared.msi
dw20shared.mst
setup.msi
setup.mst
vc_red.cab
vc_red.msi
vcredis1.cab
vcredist.msi

Run the downloaded setup.exe, and before installing browse to the temp folder to dig out the files we need (In Windows 7 it’s at C:\Users\<user>\AppData\Local\Temp\{271C7EDF-9A56-4745-BB2C-C1BE3B1F0E36}

Setup.msi you probably already have as part of the download, we need to build a response file for that later, but you can copy that to your distribution point.
There will also be 3 folders with their own GUID label, in each you will find one of dw20shared.msi, vcredist2005_x86.exe and vcredist_x86.exe.

copy these 3 files to c:\AppV
Open command prompt and run the following commands from that directory:
vcredist_x86.exe /c (it will extract to a folder in root of C called 085b85a0ec37c07c43). Copy the resulting vc_red.cab and vc_red.msi to your distribution point.

vcredist2005_x86.exe /c (it will ask you for a location to extract, pick your c:\AppV folder and it will extract a file called vcredi~3.exe)
run the vcredi~3.exe /c command and pick the same location. Now copy the 2 resulting files vcredist1.cab and vcredist.msi to your distribution point.

I use AdminStudio, but use whatever package you have (ORCA?) to create an .mst to customise dw20shared.msi to include the property APPGUID={ 9E9D30B2-2065-4FDE-B756-8F1A6EABAFC3}. Copy both of these to your distribution point.

Create a response .mst file for setup.msi with all your own server details.

Go to AD and create a software distribution policy. Add the 3 prerequisite MSIs (don’t forget the .mst for dw20shared) and finally the setup.msi (with the setup.mst). AD will deploy them in the order you add them, no restarts required. Bingo!
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
1
Note
The user permissions for the App-V client can also be set by properties. They can be set by the following:

PERM_ADDAPP #0
PERM_CHANGECACHESIZE #0
PERM_CHANGEFSDRIVE #0
PERM_CHANGELOGSETTINGS #0
PERM_CHANGEREFRESHSETTINGS #0
PERM_CLEARAPP #1
PERM_DELETEAPP #0
PERM_IMPORTAPP #0
PERM_LOADAPP_TS #0
PERM_LOADAPP_WD #1
PERM_LOCKAPP_TS #0
PERM_LOCKAPP_WD #1
PERM_MANAGESERVERS #0
PERM_MANAGETYPES_TS #0
PERM_MANAGETYPES_WD #1
PERM_PUBLISHSHORTCUTS #0
PERM_REFRESHSERVER_TS #0
PERM_REFRESHSERVER_WD #1
PERM_REPAIRAPP #1
PERM_TOGGLEOFFLINEMODE_TS #0
PERM_TOGGLEOFFLINEMODE_WD #1
PERM_UNLOADAPP #0
PERM_UPDATEOSDFILE #0
PERM_VIEWALLAPPLICATIONS #0
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
1
Note
I try to deploy as much as I can using MSIs and AD
As stated above, the setup.msi won’t install the prerequisites if they don’t already exist and will just fail. Setup.exe with the options works well, but takes it out of easy control of AD. To deploy fully with AD this worked a charm for me. What we need to do this is the following 8 files:

dw20shared.msi
dw20shared.mst
setup.msi
setup.mst
vc_red.cab
vc_red.msi
vcredis1.cab
vcredist.msi

Run the downloaded setup.exe, and before installing browse to the temp folder to dig out the files we need (In Windows 7 it’s at C:\Users\<user>\AppData\Local\Temp\{271C7EDF-9A56-4745-BB2C-C1BE3B1F0E36}

Setup.msi you probably already have as part of the download, we need to build a response file for that later, but you can copy that to your distribution point.
There will also be 3 folders with their own GUID label, in each you will find one of dw20shared.msi, vcredist2005_x86.exe and vcredist_x86.exe.

copy these 3 files to c:\AppV
Open command prompt and run the following commands from that directory:
vcredist_x86.exe /c (it will extract to a folder in root of C called 085b85a0ec37c07c43). Copy the resulting vc_red.cab and vc_red.msi to your distribution point.

vcredist2005_x86.exe /c (it will ask you for a location to extract, pick your c:\AppV folder and it will extract a file called vcredi~3.exe)
run the vcredi~3.exe /c command and pick the same location. Now copy the 2 resulting files vcredist1.cab and vcredist.msi to your distribution point.

I use AdminStudio, but use whatever package you have (ORCA?) to create an .mst to customise dw20shared.msi to include the property APPGUID={ 9E9D30B2-2065-4FDE-B756-8F1A6EABAFC3}. Copy both of these to your distribution point.

Create a response .mst file for setup.msi with all your own server details.

Go to AD and create a software distribution policy. Add the 3 prerequisite MSIs (don’t forget the .mst for dw20shared) and finally the setup.msi (with the setup.mst). AD will deploy them in the order you add them, no restarts required. Bingo!
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
0
Note
We wanted to allow the Service Desk to launch the Application Virtualization MMC (sftcmc.msc) in the context of the user, but we have restricted mmc snap-ins to those that we specifically allow. Therefore I edited Appvirt.adm file and these changes might be useful for others.

Add this section just before [Strings]:

CLASS USER

CATEGORY "Windows Components"

CATEGORY "Microsoft Management Console"

CATEGORY "Restricted/Permitted snap-ins"

KEYNAME "Software\Policies\Microsoft\MMC\{F7E7A18B-F9AA-45C7-A234-CE2082268844}"

POLICY "Application Virtualization"
EXPLAIN !!MMC_Restrict_Explain
VALUENAME "Restrict_Run"
VALUEON NUMERIC 0
VALUEOFF NUMERIC 1
END POLICY
END CATEGORY

END CATEGORY

END CATEGORY

Add this section at the very end.

MMC_Restrict_Explain="Permits or prohibits use of this snap-in.\n\nIf you enable this setting, the snap-in is permitted. If you disable the setting, the snap-in is prohibited.\n\nIf this setting is not configured, the setting of the "Restrict users to the explicitly permitted list of snap-ins" setting determines whether this snap-in is permitted or prohibited.\n\n-- If "Restrict users to the explicitly permitted list of snap-ins" is enabled, users cannot use any snap-in except those explicitly permitted.\n\n To explicitly permit use of this snap-in, enable this setting. If this setting is not configured (or disabled), this snap-in is prohibited.\n\n-- If "Restrict users to the explicitly permitted list of snap-ins" is disabled or not configured, users can use any snap-in except those explicitly prohibited.\n\n To explicitly prohibit use of this snap-in, disable this setting. If this setting is not configured (or enabled), the snap-in is permitted.\n\nWhen a snap-in is prohibited, it does not appear in the Add/Remove Snap-in window in MMC. Also, when a user opens a console file that includes a prohibited snap-in, the console file opens, but the prohibited snap-in does not appear."
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
0
Command Line
Command line option for those who would like to perform a silent install of the new AppV Client v4.6 SP1 in standalone mode without reboot.

Note: The following option will work with setup.exe only and not with the MSI file.


AppV Client v4.6SP1 Standalone installation
----------------------------------------------------------

For Silent installation: Copy the following to a notepad and rename the file to ".cmd"


AppVClient_4.6SP1_Setup.exe /s /v"/qn SWICACHESIZE=\"12144\" SWISKIPDATASETTINGS=\"false\" SWIGLOBALDATA=\"C:\AppVirt\Global\" SWIUSERDATA=\"^%APPDATA^%\" SWIFSDRIVE=\"Q:\" REQUIREAUTHORIZATIONIFCACHED=\"0\" ALLOWINDEPENDENTSTREAMING=\"1\" AUTOLOADONLAUNCH=\"0\" AUTOLOADONLOGIN=\"0\" /norestart /l*vx! AppVClient_4.6SP1_Setup_Install.log"

----------------------------------------------------------
For Silent Uninstallation: Copy the following to a notepad and rename the file to ".cmd"


AppVClient_4.6SP1_Setup.exe /s /x /v"/qn /norestart /l*vx! AppVClient_4.6SP1_Setup_Uninstall.log"
----------------------------------------------------------
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

Application Virtualization Client

Version

4

Questions & Answers (6)

Questions & Answers related to Microsoft Application Virtualization Client

Blogs (2)

Blog posts related to Microsoft Application Virtualization Client

Reviews (0)

Reviews related to Microsoft Application Virtualization Client