You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> RHEL/Oracle Linux 6.10 is the only RHEL/OL 6 version with ELS support available, [the extended maintenance ends on 06/30/2024](https://access.redhat.com/support/policy/updates/errata)
Copy file name to clipboardExpand all lines: articles/virtual-machines/extensions/agent-windows.md
+28-12Lines changed: 28 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,34 @@ The Microsoft Azure Virtual Machine Agent (VM Agent) is a secure, lightweight pr
15
15
16
16
This article details installation and detection of the Azure Virtual Machine Agent.
17
17
18
+
## Prerequisites
19
+
20
+
### **Windows OS’ Supported**
21
+
|**Windows OS**|**x64**|
22
+
|:----|:----:|
23
+
| Windows 10 | Supported |
24
+
| Windows 11 | Supported |
25
+
| Windows Server 2008 SP2 | Supported |
26
+
| Windows Server 2008 R2 | Supported |
27
+
| Windows Server 2012 | Supported |
28
+
| Windows Server 2012 R2 | Supported |
29
+
| Windows Server 2016 | Supported |
30
+
| Windows Server 2016 Core | Supported |
31
+
| Windows Server 2019 | Supported |
32
+
| Windows Server 2019 Core | Supported |
33
+
| Windows Server 2022 | Supported |
34
+
| Windows Server 2022 Core | Supported |
35
+
36
+
37
+
> [!IMPORTANT]
38
+
> - The Windows VM Agent needs at least Windows Server 2008 SP2 (64-bit) to run, with the .NET Framework 4.0. See [Minimum version support for virtual machine agents in Azure](https://support.microsoft.com/help/4049215/extensions-and-virtual-machine-agent-minimum-version-support).
39
+
>
40
+
> - Ensure your VM has access to IP address 168.63.129.16. For more information, see [What is IP address 168.63.129.16](../../virtual-network/what-is-ip-address-168-63-129-16.md).
41
+
>
42
+
> - Ensure that DHCP is enabled inside the guest VM. This is required to get the host or fabric address from DHCP for the IaaS VM Agent and extensions to work. If you need a static private IP, you should configure it through the Azure portal or PowerShell, and make sure the DHCP option inside the VM is enabled. [Learn more](../../virtual-network/ip-services/virtual-networks-static-private-ip-arm-ps.md) about setting up a static IP address with PowerShell.
43
+
>
44
+
> - Running the VM Agent in a "Nested Virtualization" VM might lead to unpredictable behavior, hence it's not supported in that Dev/Test scenario.
- The Windows VM Agent needs at least Windows Server 2008 SP2 (64-bit) to run, with the .NET Framework 4.0. See [Minimum version support for virtual machine agents in Azure](https://support.microsoft.com/help/4049215/extensions-and-virtual-machine-agent-minimum-version-support).
69
-
70
-
- Ensure your VM has access to IP address 168.63.129.16. For more information, see [What is IP address 168.63.129.16](../../virtual-network/what-is-ip-address-168-63-129-16.md).
71
-
72
-
- Ensure that DHCP is enabled inside the guest VM. This is required to get the host or fabric address from DHCP for the IaaS VM Agent and extensions to work. If you need a static private IP, you should configure it through the Azure portal or PowerShell, and make sure the DHCP option inside the VM is enabled. [Learn more](../../virtual-network/ip-services/virtual-networks-static-private-ip-arm-ps.md) about setting up a static IP address with PowerShell.
73
-
74
-
- Running the VM Agent in a "Nested Virtualization" VM might lead to unpredictable behavior, hence it's not supported in that Dev/Test scenario.
0 commit comments