Category: App-V

Unable to start app-v client in Windows 10 (build 1603)?

Working on testing app-v packages using Flexera AdminStudio test machine facility (quite nifty actually) and by default was picking up errors using the App-v launcher relating to the app-v client service not being started. Manually starting the service didn’t bring any joy (another error with a -214 code).

Fix for this was simple enough in the end, seems even more than ever powershell needs to be invoked for more and more activities and this is no different. To enable simply go into powershell and type enable-appv like so and it will start up and set the service to automatic and your good to go

Enabling logging for troubleshooting app-v issues in your citrix environment

When troubleshooting App-v issues in your citrix environment one of the first usual port of calls will be to enabling logging.

To enable Studio and VDA logs used for App-V, you must have administrator privileges. You will also need a text editor such as Notepad.

To enable the Citrix Studio logs:

  1. Create the folder C:\AppvLogs.
  2. Navigate to C:\ProgramFiles\Citrix\StudioAppVIntegration\SnapIn\Citrix.Appv.Admin.V1. Open CtxAppvCommon.dll.config in a text editor and uncomment the line: <add key =”LogFileName” value=”C:\AppvLogs\log.txt”/>
  3. Restart the Broker service to start logging.

To enable VDA logs:

  1. Create the folder C:\AppvLogs.
  2. Go to C:\ProgramFiles\Citrix\ Virtual Desktop Agent. Open CtxAppvCommon.dll.config in a text editor and uncomment the following line: <add key =”LogFileName” value=”C:\AppvLogs\log.txt”/>
  3. Uncomment the line and set the value field to 1: <add key =”EnableLauncherLogs” value=”1″/>
  4. Restart the machine and logging should be working

App-v tip : how to easily flush app-v cache

One command that is handy to know when hitting app-v issues is the ability to flush the app-v cache – below are the steps necessary to achieve this task:

  1. On your Windows 8.x machine, log in with any account that has local administrator permissions.
  2. Start | run | cmd.exe | powershell.exe and  enter the following commands:
    Set-ExecutionPolicy RemoteSigned –Force
    Import-Module AppvClient
    Get-AppvClientPackage –All | Remove-AppvClientPackage
    Set-ExecutionPolicy Default –Force
    

    So you’ll see from above first and last lines of the commands allow scripting to run within PowerShell and then set the scripting security settings back to their default. The second line imports the App-V commands into the PowerShell session and the third line retrieves a list of all of the App-V packages and then pipes them into a command to remove them from the client.

  3. To check command worked, examine the size of the C:\ProgramData\App-V folder; it should be nearly empty with only icons and shortcuts remaining for the packages that have otherwise been cleared.

App-V troubleshooting tip: hitting issues with app-v apps in a citrix environment?

Can be a bit of challenge for app-v newbies when troubleshooting issues relating to app-v particularly if using them in a SCCM/App-V setup in a citrix environment as there is a number of moving parts at play.

One simple tip to help you encountering issues relating to app-v launches is to open up the level of event logging on the citrix server relating to app-v events as generally the defaults are never enough to give an adequate picture of what is going on.

 

To do:

i) Logon to the citrix server encountering the issue (preferably admin level access)

ii) go into the event viewer (eventvwr.exe)

iii) Click on View | Show Analytic and Debug Logs

iv) Click on Applications and Services Logs then on left-hand pane and Microsoft | AppV 

v) Under there generally i pick logs under Client and Streaming VFS – if you click into the folders and right-click the appropriate log and choose Enable log you should start getting more information back regards the cause of the errors

iv) appv

Image prep best practice: Flush your app-v client cache prior to seal

Flushing the App-V client cache

When creating a base operating  image for deployment to computers and you are including the App-V client might inadvertently launch an App-V application by mistake before you’ve completed capturing the image), you might find that the package is included in the capture and thus bloats the image unnecessarily. By flushing the App-V client cache before capturing, you can ensure that no packages are included in the image.

Prep step

Install your App-V client installed on a Windows 8.1/10 PC.

How to do

The following list shows you the high-level steps involved in this recipe and the tasks required to complete the recipe (all of the actions in this recipe will take place on the Windows 8.1/10 client):

  • Log in as an Administrator level id and flush the App-V Client Cache

To implement this do the following:

  1. On your Windows 8.1/10 client, log in with an account that has local administrator permissions.
  2. Launch an admin-level PowerShell session and enter the following commands:
    Set-ExecutionPolicy RemoteSigned –Force
    Import-Module AppvClient
    Get-AppvClientPackage –All | Remove-AppvClientPackage
    Set-ExecutionPolicy Default –Force
    

    Here, the first and last lines of the commands allow scripting to run within PowerShell and then set the scripting security settings back to their default. The second line imports the App-V commands into the PowerShell session and the third line retrieves a list of all of the App-V packages and then pipes them into a command to remove them from the client.

  3. To verify command ran successful, check the size of the C:\ProgramData\App-V folder; it should be nearly empty with only icons and shortcuts remaining for the packages that have otherwise been flushed out

App-v 5.x and citrix profile management – don’t forget them exclusions!

tripped me up this one recently. Had an issue whereby we have a “follow the user” model in place where users can still have made available to them applications delivered to them via SCCM user collection when they logon to a citrix published desktop environment.

Noticed over time that more and more users complained of “missing” applications in their Software Center instance.

Turns out we had a folder recommended for exclusion as per :

http://support.citrix.com/proddocs/topic/user-profile-manager-5-x/upm-using-with-app-v.html

not included in the exclusions list.

AppData\Roaming\Microsoft\AppV\Client\Catalog

Interestingly was a while since we had updated the exclusions but would pretty sure this folder was an addition not first set with the original exclusions list (as had the other exclusions already in place)

Once the above folder was cleaned out of the users UPM profile was good to go