Select the product you need help with

How To Enable Debug Logging in Microsoft User Experience Virtualization (UE-V)

Article ID: 2782997 - View products that this article applies to.

Summary

This article describes how to enable debug logging for the Microsoft User Experience Virtualization (UE-V) agent. This is useful in troubleshooting issues where settings or files are not replicating as expected. Typically, this process is ran on at least two different client machines to test replication.

Back to the top | Give Feedback

More Information

First, identify the scenario you wish to trace. The two main variations for UE-V are tracing applications and tracing desktop settings. User application traces can be collected when an executable is launched; desktop settings must be recorded during logoff and subsequent logoff.

Traces collect data for all users logged in to a computer. If you wish to record a trace for a non-administrator account, you will need to either log in to a second desktop session (in the case of a Terminal Server, for example), or else launch a command prompt in the context of a member of the machine's local Administrators group by holding down the shift key and right-clicking on a shortcut to a Command Prompt. In addition, these commands must be ran in an elevated token.

Scenario 1: Tracing an Application

Log on to the computer as a member of the local administrators group.
Launch an elevated command prompt by right-clicking on a shortcut to Command Prompt and selecting Run as administrator.
Create the trace definition by running these two commands in the elevated Command Prompt window:

logman create trace UEV -P "Microsoft-User Experience Virtualization-App Agent" -ow -o uevtrace.etl

logman update UEV -P "Microsoft-User Experience Virtualization-Agent Driver"

Start the trace by typing the command logman start UEV
Close any running instances of the application you are investigating, then launch the application.
Reproduce the issue you are investigating, then close the application.
Stop the trace by typing logman stop UEV
Delete the trace definition by typing logman delete UEV
Decode the trace by typing the command netsh trace convert uevtrace_000001.etl DUMP=TXT

Note: The first trace you take will be named uevtrace_000001.etl by default. Edit the command above if you take multiple traces to reflect the name of the ETL file.

Scenario 2: Tracing a Desktop Settings Issue

Log on to the computer as a member of the local administrators group.
Launch an elevated command prompt by right-clicking on a shortcut to Command Prompt and selecting Run as administrator.
Create the trace definition by running these two commands in the elevated Command Prompt window:

logman create trace UEV -P "Microsoft-User Experience Virtualization-App Agent" -ow -o uevtrace.etl

logman update UEV -P "Microsoft-User Experience Virtualization-Agent Driver"

Start the trace by typing the command logman start UEV
Reproduce the issue you are investigating, then log off.
Log back on to the server.
Launch an elevated command prompt by right-clicking on a shortcut to Command Prompt and selecting Run as administrator.
Stop the trace by typing logman stop UEV
Delete the trace definition by typing logman delete UEV
Decode the trace by typing the command netsh trace convert uevtrace_000001.etl DUMP=TXT

Note: The first trace you take will be named uevtrace_000001.etl by default. Edit the command above if you take multiple traces to reflect the name of the ETL file.

Alternate Method: Event Viewer Logging

If you wish to use Event Viewer rather than text file logging, use the steps below.

Log on to the computer as a member of the local administrators group.
Launch Event Viewer.
Select View\Show Analytic and Debug Logs.
Navigate to Event Viewer (Local)\Applications and Service Logs\Microsoft\User Experience Virtualization\App Agent.
Right-click on Debug under App Agent and select Enable Log.
Select OK when presented with the "Analytic and Debug logs may lose events when they are enabled. Do you want to enable this log?" dialog.
Reproduce your issue.
Right click Debug and select Refresh.
Right click Debug and select Disable Log.

Back to the top | Give Feedback

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Back to the top | Give Feedback