Fix RemoteApp connections showing no resources despite successful authentication

draft · remote-access rdpremoteappauthentication

Generated by docuprocessor (prompt article/v3) · 2026-04-22 13:38

Source thread

thread_id: spaces/AAAA05BdS6s/threads/DHV32bPd0mI · 14 msgs · first 2024-11-25 · participants: Tech ATech B

Tech A 2024-11-25 17:42

Hey Guys, question, I am working on a ticket for ELFAR Livingston, trying to add the RDP app, on the Billing PC, I was able to install the Certificates for the three locations, added the IP's and SVR to the Hosts file in c:\Windows\System32\Drivers\etc\hosts and also checked the configuration for another location that has the apps added, these supposed to be the URLs: https://svr-ts1.dental.local/rdweb/feed/webfeed.aspx https://svr-ts2.dental.local/rdweb/feed/webfeed.aspx https://svr-ts.genuinesmiles.local/rdweb/feed/webfeed.aspx I added the URL's with no problem but only the TS2 for Jersey city recognized the remote apps, the other locations shows with no Resource added, is there any additional configuration that I am missing?

image/png image.png

The screenshot shows the **RemoteApp and Desktop Connections** panel in Windows, listing three workplace connections: **Work Resources**, **Work Resources (1)**, and **Work Resources (2)**. Work Resources (1) is highlighted with a red annotation and contains **4 programs and 0 desktops** with a "View resources" link visible; the other two connections show **0 programs and 0 desktops**. All three connections show a **"Not connected"** status with **"Update successful"** indicators, and all were created on **Saturday, November 23, 2024**, with most recent updates between **12:09 PM and 12:15 PM**.

Tech A 2024-11-25 20:22

👀 @all

Tech B 2024-11-25 20:34

Did you try “view details” > update now?

Tech A 2024-11-25 20:34

I think I did, let me try again.

Tech B 2024-11-25 20:35

Also which user account was used to authenticate to remote apps, that could matter as well

Tech A 2024-11-25 20:37

I did it with the admin account, same as the one that is working, otherwise I am assuming it wouldn't allow me to authenticate if it was a wrong user, right?

Tech B 2024-11-25 20:39

Remote apps on the server side is assigned to specific group/users, you should authenticate with account that’s part of it

Tech A 2024-11-25 20:39

right, I was thinking that, I checked on the server that was assigned to an specific user group with a domain, but didn't think it was the case.

Tech B 2024-11-25 20:41

If I remember correctly their offices are on different domains, so you may need to create a user and add to group if doesn’t already exist

Tech A 2024-11-25 20:43

Jersey City is the one that is working good, which has Dental\Domain, and Kearney is showing as GeuineSmiles\RemoteUsers within the Server Manager Remote DesktioConnections

Tech A 2024-11-25 20:45

(no text)

image/png image.png

**Server Manager — Remote Desktop Services — QuickSessionCollection** The collection is configured as a **Session** type assigned to **DENTAL\Domain Users**, with four published RemoteApp programs: **AppLauncher**, **Appointments (Apptbook)**, **ClaimListener**, and **explorer**, all visible in RD Web Access. The Connections panel on the right shows **17 total sessions** on **SVR-TS2.DENTAL.LOCAL** as of 11/23/2024 12:52:14 PM, with **DENTAL\staff** currently highlighted in an **Active** state, while multiple other users (cc1–cc6, billing1–6, operation, Administrator) show a mix of **Active** and **Disconnected** session states.

Tech A 2024-11-25 20:46

(no text)

image/png image.png

**Windows Server Manager – Remote Desktop Services Collection Configuration** The screenshot shows the **REMOTE** collection properties in Windows Server Manager under Remote Desktop Services. The Collection Type is **Session**, Resources are set to **RemoteApp Programs**, and the User Group is **GENUINESMILES\RemoteUsers** (underlined in red). Four RemoteApp programs are published and visible in RD Web Access: **Appointments** (alias: Apptbook), **ClaimListener** (alias: ClaimListener), **Explorer Kearny** (alias: explorer), and **Timeclock Kearny** (alias: AppLauncher), last refreshed **11/23/2024 at 12:36:44 PM**.

Tech B 2024-11-25 20:48

1. Remove non working connections 2. Check users/groups on server side 3. Create or assign required user to group that’s in server manager > RDS 4. Reconnect to remote apps on the client side using the account from above steps (use domain\username format) 5. Check if works

Tech A 2024-11-25 21:13

looks like that was the problem, the admin user that I was using to authenticate wasn't within the group that the RemoteApp were assigned to. Thank you.

---
title: "Fix RemoteApp connections showing no resources despite successful authentication"
category: remote-access
tags: ["rdp", "remoteapp", "authentication"]
source_thread_id: "spaces/AAAA05BdS6s/threads/DHV32bPd0mI"
source_space: "spaces/AAAA05BdS6s"
generated_at: "2026-04-22T13:38:48"
participants: ["Tech A", "Tech B"]
---

# Fix RemoteApp connections showing no resources despite successful authentication

## Problem

RemoteApp connections authenticate successfully but display "0 programs and 0 desktops" instead of showing published applications. The issue occurs when connecting to Remote Desktop Services feeds across multiple domains, where some connections work correctly while others show no resources despite using the same authentication credentials and following identical setup procedures.

In this case, three RemoteApp feed URLs were configured, but only one (svr-ts2.dental.local) displayed the expected 4 programs, while the other two connections showed no resources available.

## Resolution

1. **Remove the non-working RemoteApp connections** from the client machine
2. **Verify user group assignments on the server side** by checking Server Manager > Remote Desktop Services > Collections to identify which domain groups are assigned to each RemoteApp collection
3. **Ensure the authenticating user account is a member of the correct domain group** that matches the RemoteApp collection assignment (e.g., DENTAL\Domain Users or GENUINESMILES\RemoteUsers)
4. **Create or add the user to the required group** if they are not already a member
5. **Reconnect to the RemoteApp feeds** using an account that belongs to the assigned group, using domain\username format for authentication
6. **Verify the connection shows available programs** after successful authentication

The root cause is typically that RemoteApp collections are assigned to specific domain groups, and authentication with an account outside those groups will succeed but return no published applications.

## References

- Source discussion: `spaces/AAAA05BdS6s/threads/DHV32bPd0mI`
- Attachments:
  - ![image.png](../attachments/DHV32bPd0mI.0hP_R5jIn4A/image.png) — **Server Manager — Remote Desktop Services — QuickSessionCollection**

The collection is configured as a **Session** type assigned to **DENTAL\Domain Users**, with four published RemoteApp programs: **AppLauncher**, **Appointments (Apptbook)**, **ClaimListener**, and **explorer**, all visible in RD Web Access. The Connections panel on the right shows **17 total sessions** on **SVR-TS2.DENTAL.LOCAL** as of 11/23/2024 12:52:14 PM, with **DENTAL\staff** currently highlighted in an **Active** state, while multiple other users (cc1–cc6, billing1–6, operation, Administrator) show a mix of **Active** and **Disconnected** session states.
  - ![image.png](../attachments/DHV32bPd0mI.DEjJIYAo14w/image.png) — **Windows Server Manager – Remote Desktop Services Collection Configuration**

The screenshot shows the **REMOTE** collection properties in Windows Server Manager under Remote Desktop Services. The Collection Type is **Session**, Resources are set to **RemoteApp Programs**, and the User Group is **GENUINESMILES\RemoteUsers** (underlined in red). Four RemoteApp programs are published and visible in RD Web Access: **Appointments** (alias: Apptbook), **ClaimListener** (alias: ClaimListener), **Explorer Kearny** (alias: explorer), and **Timeclock Kearny** (alias: AppLauncher), last refreshed **11/23/2024 at 12:36:44 PM**.
  - ![image.png](../attachments/DHV32bPd0mI.DHV32bPd0mI/image.png) — The screenshot shows the **RemoteApp and Desktop Connections** panel in Windows, listing three workplace connections: **Work Resources**, **Work Resources (1)**, and **Work Resources (2)**. Work Resources (1) is highlighted with a red annotation and contains **4 programs and 0 desktops** with a "View resources" link visible; the other two connections show **0 programs and 0 desktops**. All three connections show a **"Not connected"** status with **"Update successful"** indicators, and all were created on **Saturday, November 23, 2024**, with most recent updates between **12:09 PM and 12:15 PM**.

Generated article

draft