Session and Application Management

Module: Monitor and Maintain Azure Virtual Desktop (AVD)

Lesson: Session and Application Management

Introduction: Why Session and Application Management Matters

In the world of Azure Virtual Desktop (AVD), the user experience is defined by the responsiveness of the session and the availability of the applications assigned to them. When users log into a virtual desktop, they expect a workstation-like experience, regardless of whether they are working from home, an office, or on the move. As an administrator, your primary role is to ensure these sessions remain healthy and that applications launch without errors or latency. Effective session and application management is not just about keeping the lights on; it is about proactive troubleshooting, resource optimization, and ensuring that the underlying infrastructure is balanced to meet fluctuating user demands.

If sessions become unresponsive or applications fail to initialize, productivity grinds to a halt. In a multi-session environment, one user running a memory-intensive task can negatively impact twenty other users on the same host. By mastering session and application management, you gain the ability to identify these "noisy neighbors," manage session states effectively, and automate the resolution of common user complaints. This lesson covers the practical mechanics of managing these sessions, monitoring application health, and maintaining a high-performance environment.

Understanding the Lifecycle of an AVD Session

An AVD session begins when a user initiates a connection through the AVD client. Behind the scenes, the AVD service broker evaluates the user’s assignment, checks the health of the available hosts in the host pool, and directs the user to an appropriate virtual machine. Understanding this lifecycle is critical for troubleshooting connection failures.

1. Authentication and Redirection: The user authenticates against Microsoft Entra ID (formerly Azure AD). The AVD service determines which host pool the user is assigned to and identifies an available session host.
2. Session Establishment: The RDP (Remote Desktop Protocol) connection is established. This involves loading the user profile (often using FSLogix) and initializing the shell.
3. Active State: The user interacts with applications. During this phase, performance counters and telemetry data are sent to Azure Monitor.
4. Disconnection: The user closes the client or loses network connectivity. The session enters a "disconnected" state, where the process remains running on the host but the user interface is hidden.
5. Logoff: The session is terminated, processes are killed, and the user profile is detached from the host.

Callout: Disconnected vs. Idle Sessions It is vital to distinguish between a disconnected session and an idle session. A disconnected session occurs when the user actively closes their client or loses network access, leaving the session active on the server. An idle session occurs when the user is logged in, but has not provided keyboard or mouse input for a set period. Administrators should implement policies to automatically log off disconnected sessions to free up system resources, but exercise caution with idle sessions to avoid disrupting active work that might be running in the background.

Monitoring Session Health and Performance

To effectively manage sessions, you must rely on data. Azure Monitor for AVD provides the primary dashboard for viewing the health of your environment. You can see real-time data regarding session counts, average round-trip time (RTT), and input delay.

Identifying High Latency

Round-trip time (RTT) is the most important metric for user experience. If a user complains that their mouse movement feels "laggy," the RTT metric is your first point of investigation. Generally, an RTT under 100ms is considered acceptable for most office applications, while anything above 200ms will result in noticeable performance degradation.

• Network Bottlenecks: High RTT is often caused by the distance between the user’s location and the Azure datacenter.
• Host Resource Exhaustion: If the CPU or RAM on the session host is pegged at 100%, the host will struggle to encode the RDP stream, leading to high latency even if the network connection is excellent.

Tracking Input Delay

Input delay measures the time elapsed between a user action (like a mouse click) and the system processing that action. High input delay is a direct indicator of CPU contention. When multiple users are competing for the same physical CPU cores on a multi-session host, the system queues tasks, causing this delay to spike.

Practical Management of User Sessions

When a user reports an issue, you may need to intervene directly. The most common actions include shadowing a session, resetting a session, or forcing a logoff.

Using PowerShell for Session Management

PowerShell is the most efficient way to manage sessions, especially when you need to perform bulk operations across multiple hosts. Ensure you have the Az.DesktopVirtualization module installed.

# Get all active sessions in a specific host pool
Get-AzWvdUserSession -ResourceGroupName "MyResourceGroup" -HostPoolName "MyHostPool"

# Disconnect a specific user session to force a refresh
Invoke-AzWvdUserSessionDisconnect -ResourceGroupName "MyResourceGroup" -HostPoolName "MyHostPool" -SessionHostName "sh-01.contoso.com" -Id "1"

# Forcefully log off a user session
Invoke-AzWvdUserSessionLogoff -ResourceGroupName "MyResourceGroup" -HostPoolName "MyHostPool" -SessionHostName "sh-01.contoso.com" -Id "1"

Warning: Forceful Logoff Risks Always attempt to communicate with the user before using Invoke-AzWvdUserSessionLogoff. Forcing a logoff will terminate all running processes instantly, which may result in data loss if the user has unsaved documents. Use the "Send-Message" functionality or direct communication channels to warn the user before taking action.

Application Management: Delivery and Troubleshooting

In AVD, applications are delivered either via full desktop experience or via RemoteApp. RemoteApp is often preferred for specific business applications because it integrates the application seamlessly into the user’s local desktop, making it feel like a native app.

Publishing RemoteApps

When publishing an application, you must ensure the executable is present on the session host image. If you are using a pooled host pool, every host in that pool must have the same application installed in the same directory path.

1. Navigate to the AVD workspace in the Azure Portal.
2. Select Application Groups.
3. Click on the group and select Applications.
4. Click Add and provide the path to the executable.

Troubleshooting Application Failures

If an application fails to launch, the issue usually falls into one of three categories:

• Missing Dependencies: The application requires a runtime (e.g., .NET Framework, C++ Redistributable) that is not installed on the golden image.
• Permission Issues: The application attempts to write to a protected system folder, but the user does not have the necessary permissions.
• Profile Conflicts: The user's FSLogix profile may contain corrupted settings or cache files from a previous session that interfere with the application launch.

Tip: Use Process Monitor (ProcMon) When an application fails to launch, Sysinternals Process Monitor is your best friend. Filter by the process name and look for "NAME NOT FOUND" or "ACCESS DENIED" results. This will tell you exactly which file or registry key the application is trying to access but failing to find.

Best Practices for Session and Application Management

To maintain a healthy AVD environment, you should adhere to established industry standards. These practices minimize the need for reactive troubleshooting and ensure a consistent experience.

1. Implement FSLogix Profile Containers

FSLogix is essential for AVD. It redirects user profiles to a VHD(x) file stored on a file share (like Azure Files). This ensures that user settings, application data, and Outlook caches follow the user from one session host to another, significantly reducing login times and profile corruption.

2. Optimize Session Host Images

Keep your golden images lean. Unnecessary background services, pre-installed bloatware, and heavy antivirus scanning can all contribute to session lag. Use the "Virtual Desktop Optimization Tool" provided by Microsoft to disable unnecessary Windows services that are not required in a virtualized environment.

3. Use Scaling Plans

A scaling plan allows you to automatically turn on or shut down session hosts based on a schedule or usage metrics. This prevents "session sprawl," where users are spread thinly across too many machines, and ensures that you aren't paying for compute resources that aren't being utilized.

4. Monitor User Experience with Log Analytics

Enable diagnostic settings to send AVD logs to a Log Analytics workspace. Create custom workbooks to track common errors such as "Connection Failed" or "App Launch Timeout." Having this data visualized allows you to spot trends, such as a specific host repeatedly failing to accept connections.

Common Pitfalls and How to Avoid Them

Even experienced administrators can fall into traps when managing AVD. Below are common mistakes and strategies to avoid them.

• Ignoring Update Cycles: Failing to update the golden image regularly means that applications become outdated and security vulnerabilities accumulate. Solution: Establish a monthly "Patch Tuesday" cycle where you update your base image, test applications, and redeploy.
• Over-Provisioning Hosts: Creating too many hosts leads to increased costs and difficulty in managing session density. Solution: Use performance counters to monitor actual usage before adding more capacity.
• Inconsistent Application Paths: Installing an app in C:\Program Files on one host and D:\Apps on another will break RemoteApp functionality. Solution: Use a deployment tool (like SCCM, Intune, or a simple PowerShell script) to ensure consistency across all hosts in a pool.
• Neglecting User Communication: Silently resetting sessions or rebooting hosts causes frustration. Solution: Always notify users of maintenance windows or potential service disruptions via email or a dashboard notification.

Comparison: Personal vs. Pooled Desktops

Callout: When to use Personal Desktops While pooled desktops are the standard for cost efficiency, personal desktops are necessary for users who require administrative rights to install their own software or who have specialized hardware requirements that cannot be easily replicated in a shared environment. Always evaluate the specific needs of the user persona before assigning a desktop type.

Advanced Troubleshooting: The "Ghost" Session

Occasionally, you may encounter a "ghost" session—a scenario where the AVD service believes a user is logged in, but the session host shows no active process. This usually happens when the RDP connection drops but the session cleanup process fails to complete.

1. Check the Host: Log into the session host as an administrator and check the Task Manager for the user's processes (e.g., explorer.exe).
2. Check the WVD Agent: Sometimes the AVD Agent service on the host gets stuck. Restarting the Remote Desktop Services and WVD Agent services can often force the host to report the correct status to the broker.
3. Use qwinsta and rwinsta: These legacy Windows commands are still highly effective. qwinsta lists sessions on the local host, and rwinsta can be used to reset a hung session that PowerShell might miss.

Step-by-Step: Setting Up Automated Session Cleanup

To prevent sessions from lingering and consuming resources, you should configure Group Policy Objects (GPOs) to handle idle and disconnected sessions.

1. Open Group Policy Management: Create a new GPO linked to the Organizational Unit (OU) containing your session hosts.
2. Navigate to Policy Settings: Go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits.
3. Configure Limits:
   • Set time limit for active but idle Remote Desktop Services sessions: Set this to a reasonable limit, such as 2 hours.
   • Set time limit for disconnected sessions: Set this to 1 hour. This ensures that if a user forgets to log off, the session is purged shortly after.
4. Enforce Policy: Run gpupdate /force on your session hosts to apply these settings immediately.

This approach is superior to manual intervention because it creates a predictable environment where resources are reclaimed automatically, reducing the administrative burden on your team.

Monitoring Application Performance with Performance Counters

Beyond the basic metrics provided by the AVD dashboard, you can collect granular data using performance counters. For instance, monitoring Terminal Services counters can reveal how many sessions are active and how much memory each session is consuming.

To capture this, configure your Log Analytics agent on the session hosts to collect the following counters:

• Terminal Services\Active Sessions
• Terminal Services\Inactive Sessions
• Memory\Available MBytes
• Processor(_Total)\% Processor Time

By correlating this data with user complaints, you can identify if a specific application or time of day is causing system-wide performance dips. For example, if you see a spike in Processor(_Total)\% Processor Time every Monday morning, you might identify that a scheduled antivirus scan or a login script is overwhelming the CPU when everyone logs in simultaneously.

Managing FSLogix Profiles

FSLogix is the backbone of session management in AVD. If the profile container fails to mount, the user will receive a temporary profile, and all their personalized settings (desktop icons, browser bookmarks, Outlook signatures) will be missing.

• Check the File Share: Ensure that the permissions on the Azure Files share are correct. The computer accounts of the session hosts must have "Creator Owner" and "Contributor" access to the share.
• Review Logs: FSLogix logs are located at C:\ProgramData\FSLogix\Logs. If a user reports a profile issue, check the Profile folder for errors like "Access Denied" or "Disk Full."
• Profile Compaction: Over time, VHD(x) files grow in size even if the user deletes files. Use the frx command-line tool to compact these files periodically to save storage space and improve performance.

Summary and Key Takeaways

Managing sessions and applications in AVD is a balance of monitoring, automation, and proactive maintenance. By focusing on the health of the connection and the consistency of the application environment, you ensure that the virtual desktop remains a reliable tool for your users.

Key Takeaways:

1. Proactive Monitoring: Always keep an eye on RTT and Input Delay. These are your leading indicators of a poor user experience. Never wait for a user to complain before investigating performance spikes.
2. Automation is Essential: Use scaling plans to manage host capacity and Group Policy to manage session timeouts. Manual management is not scalable and leads to inconsistent results.
3. Standardize Everything: Whether it is your golden image, your application installation paths, or your FSLogix settings, consistency is the key to stability. Any deviation between hosts in a pool will eventually cause an issue for a user.
4. Prioritize FSLogix: Your profile management strategy is just as important as your host management strategy. A failing profile container will make even the fastest server feel broken to the user.
5. Effective Tooling: Familiarize yourself with the full suite of tools, including Azure Monitor, PowerShell, and Sysinternals. Knowing which tool to use for a specific problem will save you hours of troubleshooting time.
6. Communication: When you must intervene in a session, always prioritize clear communication with the affected user. A well-informed user is far more forgiving of technical issues than one who is suddenly booted from their work.
7. Continual Review: The environment will change as users add new applications or as your organization grows. Review your performance data quarterly to ensure that your host sizing and scaling plans still meet the demands of the business.

By applying these principles, you move from a reactive state of "fixing broken sessions" to a strategic state of "optimizing user productivity," which is the ultimate goal of any AVD administrator. Always document your findings during troubleshooting; a resolved issue today is a reference point for a faster resolution tomorrow.