Fix RDS Certificate Showing as Untrusted After Renewal

migrated · remote-access certificaterds

Generated by docuprocessor (prompt article/v3) · 2026-04-22 02:51

Source thread

thread_id: spaces/AAAA05BdS6s/threads/2K1R-hLg3yo · 2 msgs · first 2024-01-15 · participants: Tech A

Tech A 2024-01-15 17:12

Renewed RDS certificate comes up as untrusted. Any thoughts about it?

image/png image.png

**Deployment Properties – Configure the Deployment (Windows Server RDS)** The "Manage Certificates" screen shows four Role Services — **RD Connection Broker - Enable Single Sign On**, **RD Connection Broker - Publishing**, **RD Web Access**, and **RD Gateway** — all with a **Level: Untrusted** and **Status: OK**. The current deployment certificate level is displayed as **Untrusted**, with the subject name listed as **CN=RDS-Certificate2024.p[truncated]**. All four "Untrusted" level entries are circled in red, indicating they are the focus of attention.

Tech A 2024-01-15 18:59

i created certificate incorrectly, forgot to add fqdn of the server. After re-issueing the correct certificate, everything is working fine.

---
title: "Fix RDS Certificate Showing as Untrusted After Renewal"
category: network
tags: ["certificate", "rds"]
source_thread_id: "spaces/AAAA05BdS6s/threads/2K1R-hLg3yo"
source_space: "spaces/AAAA05BdS6s"
generated_at: "2026-04-22T02:51:24"
participants: ["Tech A"]
---

# Fix RDS Certificate Showing as Untrusted After Renewal

## Problem
After renewing an RDS certificate, all four Role Services (RD Connection Broker - Enable Single Sign On, RD Connection Broker - Publishing, RD Web Access, and RD Gateway) showed "Level: Untrusted" status in the Windows Server RDS Deployment Properties configuration screen, despite having "Status: OK". The deployment certificate level displayed as "Untrusted" with the subject name showing as "CN=RDS-Certificate2024.p[truncated]".

## Resolution
1. Verify that the certificate includes the FQDN (Fully Qualified Domain Name) of the server in the certificate subject or Subject Alternative Name (SAN) field
2. If the FQDN is missing, re-issue the certificate with the correct server FQDN included
3. Install the corrected certificate to resolve the untrusted status

The root cause was creating the certificate without including the server's FQDN, which caused the trust validation to fail even though the certificate was otherwise valid.

## References
- Source discussion: `spaces/AAAA05BdS6s/threads/2K1R-hLg3yo`
- Attachments: - ![image.png](../attachments/2K1R-hLg3yo.2K1R-hLg3yo/image.png) — **Deployment Properties – Configure the Deployment (Windows Server RDS)**

The "Manage Certificates" screen shows four Role Services — **RD Connection Broker - Enable Single Sign On**, **RD Connection Broker - Publishing**, **RD Web Access**, and **RD Gateway** — all with a **Level: Untrusted** and **Status: OK**. The current deployment certificate level is displayed as **Untrusted**, with the subject name listed as **CN=RDS-Certificate2024.p[truncated]**. All four "Untrusted" level entries are circled in red, indicating they are the focus of attention.

Generated article

migrated Migrated 2026-04-22 02:54 · view on WikiJS.