M365Con 2027 – כנס אונליין חינמי · 11–22 Jan 2027 · 120 sessions m365con.net

Azure Virtual Desktop agent

Concept

ה-agent של Azure Virtual Desktop מחבר בין session hosts לבין שירות Azure Virtual Desktop, ומשמש כמתווך בין השירות לבין המכונה הווירטואלית. גרסאות חדשות מותקנות אוטומטית ומופצות בהדרגה, תחילה דרך סביבות אימות.

Short description written with AI from the facts on this page. You can improve it with the edit button below.

✦ CONCEPTAzure Virtual DesktopagentM365.FM
Title graphic: Azure Virtual Desktop agent (Concept)

קשרים

הנושא הרחב של Azure Virtual Desktop agent: Session host (Azure Virtual Desktop). נושאים הקשורים קשר הדוק ל-Azure Virtual Desktop agent: Azure Virtual Desktop, Host pool (Azure Virtual Desktop) ו-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
KindTerm
Also known asAVD Agent
DocumentationAzure Virtual Desktop agent – Microsoft Learn learn.microsoft.com
Relationship map of Azure Virtual Desktop agent: linked topics

נושאים קשורים בקצרה

נושאים הקשורים ל-Azure Virtual Desktop agent, כל אחד עם הסבר קצר:

כל הקשרים של Azure Virtual Desktop agent, מקובצים לפי סוג הקשר:

Broader topic

הנושאים הרחבים של Azure Virtual Desktop agent:

Related to

Azure Virtual Desktop agent: כל הנושאים הקשורים (3):

Glossary

Community wiki

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

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: