Failed to save remote desktop extension

Hi, the error "osFamily '4' cannot be used" means that Windows Server 2012 R2 (Guest OS Family 4) has been retired, since February 2025, Azure blocks new extensions (like RDP) on services still using it.

What to do:

-Switch to a supported OS family: 5 (WS2016), 6 (WS2019), or 7 (WS2022).

-Update your .cscfg file to: <ServiceConfiguration osFamily="7" osVersion="*">.

-Redeploy the service (e.g. via az cloud-service update).

-Re-enable Remote Desktop via Portal - Remote Desktop - Add.

Hi Azure BIG,

The error you're encountering: "The osFamily '4' cannot be used. Provide a valid osFamily..."is directly related to the retirement of Guest OS Family 4 in Azure Cloud Services (Extended Support).

 As per official Microsoft documentation, Guest OS Families 2, 3, and 4 are retired or in retirement phase:

 To resolve this issue, you need to migrate your cloud services to a supported OS family, such as Guest OS Family 6 (Windows Server 2019) or Family 7 (Windows Server 2022).

 Steps : 

 1.Check Your Current Configuration Open your .cscfg (Service Configuration) or Azure portal:

<ServiceConfiguration osFamily="4" osVersion="*">

2.Update to Supported OS Family Replace osFamily="4" with osFamily="6" or 7 in your .cscfg:  

<ServiceConfiguration osFamily="6" osVersion="*">

3.Rebuild & Redeploy Your Cloud Service

 Rebuild with Visual Studio 2019+ or compatible SDK (2.9.6+).

 Make sure your app targets a compatible .NET version (4.7.2+ for Family 6, or 4.8+ for Family 7).

 Redeploy to Azure.

 4.Then Reapply the RDP Extension

 Once the service is running on a supported family, go back to the Azure Portal or use PowerShell to reconfigure RDP.

Thanks for the feedback. I was not aware that the OS got blocked out due to retirement. This is going to be interesting since we no longer have developers. Is there any other way as a workaround?

Hi Azure BIG,

You can’t avoid the retirement of Guest-OS family 4 just by reapplying the RDP extension because it won’t work on any cloud service still using OS Family 4. But don’t worry, you can still access your VM to fix things or get your files with these simple workarounds:

 How to Access Your VM When RDP Isn’t Working

1. Use Azure Serial Console

• This is a way to connect directly to your VM’s command line, even if RDP isn't working or you can’t install the RDP extension.
• What you need:
  • Boot diagnostics turned on for your VM.
  • Azure VM Agent installed (you already have this if RDP was working before).
• What you can do when connected:
  • Look at or save important log files.
  • Create a new local admin user and set a password.
  • Change firewall or RDP settings so you can use RDP later on a supported OS.

Supported document: https://learn.microsoft.com/en-us/azure/virtual-machines/troubleshooting/serial-console-windows

2. Attach the OS Disk to a Rescue VM

• Detach the OS disk from the problem VM.
• Attach it to another temporary Windows VM that is running a supported OS.
• Access the disk from that rescue VM and copy off any important files like logs or configurations.
• After you finish, you can either reattach the disk to your original VM or use it to create a new VM.

Supported document: https://learn.microsoft.com/en-us/azure/virtual-machines/windows/manage-disks#attach-a-disk-to-a-windows-vm

3. Use Azure Bastion (If Available)

• Azure Bastion lets you open an RDP session securely through the Azure Portal without needing the RDP extension installed on the VM.
• It works even if RDP service on the VM isn’t set up correctly, as long as the network rules allow it and the Azure VM Agent is installed.

Supported document: https://learn.microsoft.com/en-us/azure/bastion/bastion-overview

 Recommended Steps to Avoid in future

• As soon as possible, use the Serial Console to create a new admin user and back up any important data.
• Plan to move your cloud service to a newer, supported Guest OS family like 5, 6, or 7.
• If you can’t redeploy your cloud service yourself right now, consider using normal IaaS virtual machines for your long-term needs until your team can help with the migration.