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
title: Troubleshooting Tool for Linux Guest Agent - VM assist
3
+
description: Provides script-based tool to help diagnose and resolve Azure Guest Agent issues on Azure virtual machines running Linux.
4
+
author: JarrettRenshaw
5
+
ms.author: jarrettr
6
+
manager: dcscontentpm
7
+
ms.date: 10/24/2025
8
+
ms.reviewer: v-jsitser, scotro, v-ryanberg
9
+
ms.service: azure-virtual-machines
10
+
ms.custom: sap:zzzz
11
+
---
12
+
# Troubleshooting Tool for Linux Guest Agent - VM assist
13
+
14
+
**Applies to:**:heavy_check_mark: Linux VMs
15
+
16
+
## Overview
17
+
18
+
The Microsoft Azure Linux VM Agent is a secure, lightweight process that manages virtual machine (VM) interaction with the Azure fabric controller. The Azure Linux VM Agent has a primary role in enabling and running Azure VM extensions. VM extensions enable post-deployment configuration of VMs, such as installing and configuring software. VM extensions also enable recovery features, such as resetting the administrative password of a VM. Without the Azure Linux VM Agent, you can't run VM extensions.
19
+
20
+
## Purpose
21
+
The Linux version of VM assist is composed of bash and Python scripts that are used to detect potential issues that affect the guest agent in a Linux VM. It also examines other issues that are related to the general health of the VM. Output is intended to be viewed in the serial console. It provides pointers to solve well-known issues and certain deviations from best practice that can affect VM availability. The intention is for engineers to provide this script to customers through GitHub. However, it's possible and acceptable that a customer uses the script on their own and provides data through a service request.
22
+
23
+
Because the output of this script is designed to be viewed in a worst-case scenario of the Azure serial console, the information that's displayed is minimal and condensed. Details are provided through online resources that are accessed through a link that's provided in the output. See [VM assist for Linux](https://aka.ms/vmassistlinux).
24
+
25
+
VM assist is delivered in two functional scripts (one in bash and one in python3) plus an optional 'downloader' script.
26
+
27
+
The bash script performs some basic checks and determines whether running the Python script is possible or necessary.
28
+
29
+
## Key features
30
+
31
+
### Bash checks
32
+
33
+
The following checks are run in bash today:
34
+
35
+
- OS family detection
36
+
- Identify the Guest Agent service
37
+
- Identify the path of Python called from the service - this will be used for running the Python script
38
+
- Display the package and package repository for the agent and the Python called from the agent
39
+
- Basic connectivity checks to the wire server and IMDS
40
+
41
+
> If the bash script finds a python2 system the script will exit and display the information it has gathered.
42
+
43
+
### Python analysis
44
+
45
+
If no issues are discovered during the base checks by using bash, the Python script is called to perform a deeper analysis that includes the following tasks:
46
+
47
+
- Find the source (package) for the guest agent executable and the Python passed from bash
48
+
- Optionally check any service or package statuses (this is currently a proof-of-concept inside the script)
49
+
- Only SSH is checked for the PoC
50
+
- Provide source information for all checked files and services
51
+
- Do configuration checks for the Guest Agent
52
+
- Connectivity checks for requirements of the guest agent
53
+
- Basic system configuration and status checks (#Guest best practices)
54
+
55
+
## Prerequisites
56
+
57
+
- The VM must start to the full OS (not emergency or maintenance mode).
58
+
- Root-level access must be available through either sudo or direct login/sudo -i
59
+
60
+
## How to run the tool
61
+
62
+
The VM assist scripting is run initially from the documentation. Subsequently, you can run the bash script directly: `vmassist.sh` as root or by using `sudo`.
63
+
64
+
If you open a support request, please include both of these files to aid the support agent who assists you.
65
+
66
+
## Known issues
67
+
- Don't try to run VM assist on appliances. Appliances don't run on general purpose operating systems, and the guest agent might not run at all.
68
+
- Distributions outside PAYG versions of RedHat or SUSE, or any Ubuntu or Mariner or Azure Linux, might display false positive warnings about repository names. This situation requires a more careful reading because even official repositories might not match strict pattern matching. This condition is true because we don't build cases for all distributions.
69
+
- Ubuntu 24.04 has a different architecture of the SSH service. It might flag the service even if the service is operating well.
title: 'Windows Server 2003 End of Support (EOS) FAQ'
3
+
description: Provides information about Windows Server 2003 End of Support (EOS) FAQ.
4
+
ms.date: 08/26/2025
5
+
ms.reviewer: v-liuamson
6
+
ms.service: azure-virtual-machines
7
+
ms.collection: windows
8
+
ms.custom: sap:VM Admin - Windows (Guest OS)
9
+
---
10
+
# Windows Server 2003 End of Support (EOS) FAQ
11
+
12
+
**Applies to:**:heavy_check_mark: Windows VMs
13
+
14
+
_Original KB number:_ 4010166
15
+
16
+
## Microsoft Windows Server 2003 End of Support (EOS)
17
+
18
+
Microsoft ended extended support for Windows Server 2003 on July 14, 2015. If you are running Windows Server 2003, this may put your applications and business at risk, since there may be no security or software updates. You can still move a Windows Server 2003 VM to Azure and receive assistance in troubleshooting issues that concern running Windows Server 2003 on Azure. However, this support is limited to issues that don't require OS-level troubleshooting or patch.
19
+
20
+
## Frequently asked questions
21
+
22
+
> [!NOTE]
23
+
>The information provided in this section is specific to Windows Server 2003.
24
+
25
+
**When does extended support for Windows Server 2003 end?**
26
+
27
+
Windows Server 2003 extended support ended on July 14, 2015.
28
+
29
+
**Can I run existing Windows Server 2003 instances after the end of extended support?**
30
+
31
+
Yes.
32
+
33
+
**Can I create a new VM from the custom Windows Server 2003 image after the end of extended support?**
34
+
35
+
Yes. You can create a Windows Server 2003 Azure VM from specialized VHD only, not from generalized (Syspreped) VHD.
36
+
37
+
**Can I create a new Windows Server 2003 VM from the Azure Marketplace?**
38
+
39
+
For versions that are earlier than Windows Server 2008 R2, there is no Azure Marketplace support. you must provide your own specialized operating system VHD for new Windows Server 2003 VMs.
40
+
41
+
**Will Microsoft Azure support Windows Server 2003 after July 14, 2015?**
42
+
43
+
The Azure support team continues to offer assistance in troubleshooting issues that concern running Windows Server 2003 on Azure. However, this support is limited to issues that don't require OS-level troubleshooting or patches.
44
+
45
+
**Can I build custom images that contain updates provided by Microsoft through a custom support agreement?**
46
+
47
+
Yes. You can create and upload [specialized VHD](/azure/virtual-machines/windows/create-vm-specialized-portal) only for your own use, including situations in which those images contain updates resulting from a custom support agreement.
48
+
49
+
**Will I be able to import new Windows Server 2003 virtual machines after the end of extended support?**
50
+
51
+
Yes.
52
+
53
+
**How can I migrate specifically the apps from Windows Server 2003?**
54
+
55
+
See [Migrate an enterprise web app to Azure App Service](https://azure.microsoft.com/migration/web-applications/).
56
+
57
+
**If I run Microsoft applications such as SQL Server 2005 on Windows Server 2003, will it be supported after the end of extended support?**
58
+
59
+
Yes. The applications running on Windows Server are supported based on their [lifecycle](https://support.microsoft.com/lifecycle). However, if the application issue requires OS-level troubleshooting or patches, Azure support may not be able to fully resolve the issue.
60
+
61
+
**Does Microsoft support in-place OS upgrades for my Windows Server 2003 instances?**
62
+
No.
63
+
64
+
**Do I need to bring my own Windows Server 2003 license to Azure?**
65
+
66
+
Yes, you will need your own Windows Server 2003 license, and it must be valid. For more information, see [Prioritize Your Windows Server 2003 Migration Plans](https://azure.microsoft.com//blog/be-prepared-for-tomorrows-business-prioritize-your-windows-server-2003-migration-plans/).
67
+
68
+
**Does the Azure VM agent and extensions work in Windows Server 2003?**
69
+
70
+
No. The Azure VM agent and extensions do not support Windows Server 2003.
71
+
72
+
**What is the maximum number of virtual processors that Windows Serve 2003 Azure VM can support?**
73
+
74
+
The maximum supported VM size is two virtual processors. 64-bit OS has been reported to work with a larger number, but this configuration is not officially supported due to limited testing.
75
+
76
+
**Is 32-bit version of Windows Server 2003 supported on Azure?**
77
+
78
+
A: Windows Server 2003 32-bit has the same level of support as 64-bit, but both operating systems are past their end of support date. Microsoft does not support operating systems that are past their [End of Support date](https://support.microsoft.com/lifecycle/search) without a Custom Support Agreement (CSA). However, the Azure infrastructure is supported. See [Microsoft server software support for Microsoft Azure virtual machines](https://support.microsoft.com/help/2721672/microsoft-server-software-support-for-microsoft-azure-virtual-machines) for more information.
79
+
80
+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments