In Previous post ,we have seen Installation of Microsoft Application Virtulisation (4.6) Desktop Client
In this Post ,We will see how to Configure settings of App-V Desktop Client and its Basic Troubleshooting Steps:
If you want to change the settings that are specified at the time of installation of App-V client Or any customization do be done,you can do that Via Management Console(SftCMC) which is located in C:\Program Files (x86)\Microsoft Application Virtualization Client.
Click Start | Administrative Tools | Application Virtualization Client
click on Properties .
General Tab : If you want to record only error or warning messages,you can select it from Drop down “Log level” and the path of the log file(sftlog.txt) and other Settings as well. Take a look at Global Data Directory which is used to store all users data.You should see the default App V Application published into that.
Interface Tab: How do you want to show the notification Icon(app-V) on the system tray and how long do you want to display the error messages on the system tray icon.
Next is File System Tab: about client cache Configuration settings
Connectivity Tab: If you want to make the client to work in offline mode,you can check “Work Offline”. For more info “How to Work Offline or Online with Application Virtualization” : http://technet.microsoft.com/en-gb/library/cc817097.aspx
Permissions Tab :
Next is Applications:This list all the applications with status(running ,Not running) and what is the package status. Since the default application is not in Use, it says Not running.
The below shows the status of default application in running Mode.
If you want to know ,from where the application is loaded,application URL , Package ID,Version and what is the size of the package , Right click on the Default package ,go to properties.
If you want to set the publishing server or to change the existing one and set the refresh interval time for loading the applications etc ,Click on publishing server and go to properties.
The Above all settings also can be applied to group of computers Via Group Policy Object by importing ADM Template. Read the Document from http://download.microsoft.com/download/F/7/8/F784A197-73BE-48FF-83DA-4102C05A6D44/App-V_ADM_Template.docx
You can also Configure the App-V Client Registry Settings by Using the Command Line .Read more from http://technet.microsoft.com/en-gb/library/cc843710.aspx
Below is the Log file from my Windows 7 Desktop Client :
If you see any other errors ,please post it on the Forums.
Troubleshooting Tips :
Common Errors on the Microsoft Application Virtualization Client
The following sections list the most common errors encountered with Microsoft Application Virtualization
Desktop Client and the most common solutions to those errors.
1.When you attempt to refresh the server you get an error that says, "The client failed to download..." and "The server could not authorize you to access the requested data..."
2.The application shortcut is not on the Microsoft Application Virtualization Client desktop.
3.The application did not stream to the Microsoft Application Virtualization Client. If the application fails to stream you see the "Launch Failed" error message above the notification area.
1. The user account used to log on to the Microsoft Application Virtualization Client is not a member of the Microsoft Application Virtualization Users group or is not a domain user account.
2. The .sft, .ico, and/or .osd files are not in the Microsoft Application Virtualization Management Server “content” folder. Copy these file to C:\Program Files\Microsoft Application Virtualization\Microsoft Application Virtualization Server\Application Virtualization Server\content.
3.There are typing errors in the .osd and .ico paths in the application record in Microsoft Application Virtualization Management Console.
4. The Microsoft Application Virtualization Client cannot access the “content” directory on the Microsoft Application Virtualization server. Check the permissions settings on the content share.
5. The Microsoft Application Virtualization Client cannot access the Microsoft Application Virtualization Management Server. Check network settings, cabling and firewall exceptions for the server services.
6. The “content” folder on the Microsoft Application Virtualization Management Server is not set to share or to be shared with everyone who has read access.
7.The Microsoft Application Virtualization Client is not a member of the domain.
8.The user lacks necessary permissions to access the application. Reread and follow the procedure regarding importing .osd files, paying close attention to setting the access group.
9.The operating system of the Microsoft Application Virtualization Client computer is not listed in the .osd file of the application.
If none of the above appears to be the cause of the problem, check the Microsoft Application Virtualization Client log (Sftlog.txt) in Desktop Client for errors. The file can be found here:
-->C:\Documents and Settings\All Users\Application Data\Microsoft\Application Virtualization Client: Windows XP, Windows Server 2003
-->C:\ProgramData\Microsoft\Application Virtualization Client: Windows 7, Windows Server 2008
Application Virtualization Server :http://technet.microsoft.com/en-gb/library/cc817208.aspx
Application Virtualization Client: http://technet.microsoft.com/en-gb/library/cc817162.aspx
Application Virtualization Sequencer : http://technet.microsoft.com/en-gb/library/cc817192.aspx
Troubleshooting Information for the Application Virtualization Client: http://technet.microsoft.com/en-gb/library/cc843669.aspx
May I suggest that you add the firewall ports that need to be opened for the client to communicate with the server? Windows 2008 R2 brings the firewall turned on by default, so if someone follows your documentation, they'll soon find out that clients do not 'talk' to the server due to the firewall on the server.
If it is Windows Firewall,you can either Disable it Via Group policies to disable the firewall.
If there is something issue with client to communicate with management server over ports like HTTP,RTSP,RTSPS or HTTPS,you should really look at them if they are opened or not or contact network administrator.
Default ports for each protocol type:
Please read for more information on How to troubleshoot applications failing to stream from an App-V management server
and Troubleshooting Common RTSPS Issues with App-V