Resolve Doc Center freezing by disabling problematic RDS server connections
draft ยท remote-access rdssession-managementdoc-center
Generated by docuprocessor
(prompt article/v3)
ยท 2026-04-22 10:21
Source thread
thread_id: spaces/AAAA05BdS6s/threads/jDFVovQ0nak
· 12 msgs
· first 2024-08-27
· participants: Tech ATech BTech C
Tech A
2024-08-27 15:30
Guys, trying to help aveu-fd02 with a doc center task when I end the task and launch it again it keeps freezing, I tried to sign off the computer to see if it would connect to a different RDS but it kept connecting to the same one, any ideas on what's happening here? yesterday some offices had the same issue with doc center
video/x-matroska
2024-08-27 10-26-11.mkv
Tech B
2024-08-27 15:33
Maybe related to what @Albert Khaydatov is looking into on their GW server?
Tech C
2024-08-27 15:34
@Vladimir Sobko you can log in to the gateway and check, i couldn't find it and got another call now.
Tech A
2024-08-27 16:04
Teaneck reporting the same issue with Doc Center, not opening and laggy - ๐
image/png
image.png
**Visible on-screen ticket/task notification:**
- **Task #131382**: "Cristy, FD05-07; issues with doc center not opening and lagging (Ticket)"
- **Company**: Pediatric Dentistry of Teaneck โ PDS
- **Contact**: Luz (HQRC Teaneck)
- **Time indicators**: "Since last comment: 0 min," "In stage: 0 min," "Since creation: 0 min"
This appears to be a helpdesk or CRM task pop-up notification with a newly created ticket (all timers at 0 min), referencing a software issue with a "doc center" application on a workstation designated **FD05-07**.
Tech B
2024-08-27 16:06
Well issue with gw01 was just fixed - see if you can sign the user off from the server and have them log back in , see if it connects to different server now
Tech A
2024-08-27 16:07
On it, I'll try and I'll let you know
Tech A
2024-08-27 16:15
Well, I tried to sign her off like 5 times, and she's still getting connected to the RDS01 it doesn't want to put her on another RDS
Tech A
2024-08-27 16:22
Guys, the users on aveu and teaneck which are having the issues with doc center they are all in RDS01 - no matter how many times I try to disconnect them, it stills route them to the same RDS, any idea on what else can I do?
image/png
image.png
The image shows two lines of text displaying server/domain information: **RDS01.pdsmgmt.local** mapped to **PDSMGMT\TEA-FD07**, and **RDS01.pdsmgmt.local** mapped to **PDSMGMT\TEA-FD05**. Both entries reference the same RDS (Remote Desktop Services) server hostname but associate it with two different user or device accounts within the PDSMGMT domain. Text appears in a list or log format, possibly from a session management or Remote Desktop Services console.
Tech A
2024-08-27 16:22
(no text)
image/png
image.png
The image shows a Windows Remote Desktop or system status bar displaying the text **"RDS01.pdsmgmt.local | PDSMGMT\AVEU-FD02"**, indicating a remote desktop session connected to server **RDS01.pdsmgmt.local** under the domain/user context **PDSMGMT\AVEU-FD02**. The bar has a blue background with white text, consistent with a Remote Desktop Connection title bar or session indicator.
Tech B
2024-08-27 16:23
Maybe that rds01 server needs to be rebooted if its multiple users with the same issue
Tech B
2024-08-27 16:24
I know theres a way to prevent new connections to a specific rds server - the user can bypass that problematic server in the meantime , that might at least get them connected and working
Tech A
2024-08-27 16:27
Good idea - I'm doing that to see if I can get them up and running and after that I'll try and restart the server
image/png
image.png
**HOST SERVERS panel** (Last refreshed 8/27/2024 12:25:20 PM | All servers | 8 total)
One server is listed and highlighted in blue: **RDS01**, Type: **RD Session Host**, Virtual Desktops: **N/A**, Allow New Connections: **False**.
No error codes are visible, but the "Allow New Connections" value of **False** indicates this server is currently configured to reject new incoming connections.
Generated article
draft