M365Con 2027 – conférence en ligne gratuite · 11–22 Jan 2027 · 120 sessions m365con.net

Azure Virtual Desktop agent

Concept

L'agent Azure Virtual Desktop connecte les hôtes de session au service Azure Virtual Desktop et sert d'intermédiaire entre le service et la machine virtuelle. Les nouvelles versions s'installent automatiquement et se déploient progressivement, d'abord dans les environnements de validation.

Courte description rédigée avec l'IA à partir des informations de cette page. Tu peux l'améliorer avec le bouton de modification ci-dessous.

✦ CONCEPTAzure Virtual DesktopagentM365.FM
Image de titre : agent Azure Virtual Desktop (concept)

Relations

Azure Virtual Desktop agent relève du thème plus large Session host (Azure Virtual Desktop). Azure Virtual Desktop agent a un lien étroit avec Azure Virtual Desktop, Host pool (Azure Virtual Desktop) et Scheduled agent updates (Azure Virtual Desktop).

Description

The Azure Virtual Desktop agent links session hosts with the Azure Virtual Desktop service. Microsoft Learn describes it as the intermediate communicator between the service and the virtual machines, which enables connectivity. It runs together with the agent bootloader, the executable that loads the agent, the side-by-side stack, which users need to establish secure reverse server-to-client connections, and the Geneva Monitoring agent, which monitors the health of the agent. Learn calls the agent, the side-by-side stack and the Geneva Monitoring agent essential for end-to-end connectivity.

VMs that you create through the Azure portal or the Azure Marketplace get the agent and bootloader automatically. With PowerShell you download and install the MSI files yourself. Once the agent is installed, it installs the side-by-side stack and the Geneva Monitoring agent. The required URLs must be reachable for installation and for using the service. A registration key authorizes the VM to join a host pool; Learn's troubleshooting article says it must be valid for at least one hour and at most 27 days.

New agent versions install automatically and roll out progressively to session hosts, a process Learn calls flighting. Validation environments receive updates first and more often than production, and not every validation version reaches production. Learn says a rollout can take several weeks across all environments. The Scheduled Agent Updates feature can defer updates to a maintenance window. In the host status, Upgrading and Upgrade Failed refer to the agent update, and a failed update is logged with event ID 3277 in the Application log.

TypeConcept
TypeTerm
Aussi appeléAVD Agent
DocumentationAzure Virtual Desktop agent – Microsoft Learn learn.microsoft.com
Carte des relations de l'agent Azure Virtual Desktop : sujets liés

Sujets liés en bref

Sujets liés à Azure Virtual Desktop agent, chacun expliqué en bref :

Toutes les relations d’Azure Virtual Desktop agent, classées par type de relation :

Broader topic

Thèmes plus larges d’Azure Virtual Desktop agent :

Related to

Les 3 sujets liés à Azure Virtual Desktop agent :

Glossaire

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts et entreprises pour ce sujet

Personne n'a encore indiqué ce sujet. Ajoutez-le à votre profil.

Sources

Maintenu par Mirko Peters (Microsoft MVP) · Dernière mise à jour: