Kill RDP session for Dentrix RemoteApp when user connects from different location

draft · remote-access dentrixrdpremoteapp

Generated by docuprocessor (prompt article/v3) · 2026-04-22 12:44

Source thread

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

Tech A 2024-11-14 15:38

@all where can we kill the session for ELFAR MANAGEMENT CC6? they are having problems with dentrix remote app on Livingstong location but I don't see any TS SVR for that location.

Tech A 2024-11-14 15:39

NVM, I can see the session is in Hackensack TS SVR

Tech B 2024-11-14 15:40

So management is now in the livingston location that is why the dentrix liv is local dentrix db. yeah so kiill session from Hack TS...

---
title: "Kill RDP session for Dentrix RemoteApp when user connects from different location"
category: remote-access
tags: ["dentrix", "rdp", "remoteapp"]
source_thread_id: "spaces/AAAA05BdS6s/threads/iPqotmXbvBM"
source_space: "spaces/AAAA05BdS6s"
generated_at: "2026-04-22T12:44:33"
participants: ["Tech A", "Tech B"]
---

# Kill RDP session for Dentrix RemoteApp when user connects from different location

## Problem
A management user was having problems with Dentrix RemoteApp at the Livingston location. The user's active RDP session was running on the Hackensack terminal server, but they were now physically at a different location trying to connect to the local Dentrix database.

## Resolution
1. Identify which terminal server is hosting the user's active session by checking all relevant terminal servers for the location
2. Kill the existing RDP session from the terminal server where it's currently running (in this case, the Hackensack terminal server)
3. This allows the user to establish a new session connecting to the appropriate local Dentrix database for their current location

## References
- Source discussion: `spaces/AAAA05BdS6s/threads/iPqotmXbvBM`

Generated article

draft