Windows Server 2019 RDC

[xrobwx71]

Do any of you have any experience setting up RDP/C in Server 2019?

I bought a brand new server with 2019 installed. I am currently on Windows Server 2008 R2. Setting up RDC in 2008 was simple. There are lots of changes in Server 2019.

What I have. The server runs the point of sale software. I have 3 thin clients that need a separate terminal session to the server to use the POS software.

As I said, the setup in Server 2008 was simple, you simply create 3 users with credentials and remote into each with RDC. This is all local, no remote offsite connections needed. I use Splashtop for that.

In Server 2019, according to multiple MS tutorials, seems to require Active Directory and Domains in which I have never used and had zero experience with.

What I've accomplished so far.
Setting up Active Directory with a domain. (local)
Setting up RPD gateway and licensing server(local)
Installed RDP license per device.
Created a group, created devices in said group.
_________________________________________________________________________

What I've not accomplished:
Getting the damn thin clients to connect with separate sessions to the created devices. I can connect from the thin clients using RDC to the built-in Admin, with its credentials on Server 2019.

I have followed many tutorials from MS to get this far.

Thanks,
Rob

 

[xrobwx71]

Got it!! Eureka! <much fanfare, the crowd goes wild>

1. I had to create each COMPUTER in Active Directory
2. I had to add the computers to a GROUP, I left it the default  DOMAIN USER GROUP
3. I had to create a USER for each COMPUTER and set their passwords and toggle their access to the network.
4.In one of the tutorials I was supposed to change some settings in Windows Firewall Inbound rules but they were automatically done in my version.
5. Using Remote Desktop Connection, I had to connect to each COMPUTER via the IP address of the Main Server with the USER's name and password!

[HR][/HR]

This seems easy and I'm sure it is for a trained network admin in which I am not. This took lots of hair pulling, trial, and error.

I had to get this done by this coming Tuesday as the POS Software tech was going to logon to finalize the data and SQL migration. Wednesday we should go live with the new system!

This Xeon processor and the SSD's are blazing compared to the old system.

The old Server -

Spoiler

Computer: DELL PowerEdge T320
CPU: Intel Xeon E5-2430 (Sandy Bridge-EN, C2)
2200 MHz (22.00x100.0) @ 1200 MHz (12.00x100.0)
Motherboard: DELL 0W7H8C
BIOS: 1.6.7, 08/30/2013
Chipset: Intel C600/X79 (Patsburg)
Memory: 49152 MBytes @ 666 MHz, 9-9-9-24
Graphics: Matrox G200eR2 Video Adapter [DELL]
Matrox MGA-G200eR2, 16 MB SDRAM
Drive: TOSHIBA MG03ACA200, 1953.5 GB, Serial ATA 3Gb/s @ 3Gb/s
Drive: HL-DT-ST DVD+-RW GHA2N, DVD+R DL
Drive: ATA TOSHIBA MG03ACA2, Disk drive
Drive: DELL PERC H310, Disk drive
Drive: RAID DummyDevice, Unknown or none
Network: Broadcom BCM5720 NetXtreme PCI-E Gigabit Ethernet Controller
Network: Broadcom BCM5720 NetXtreme PCI-E Gigabit Ethernet Controller
OS: Microsoft Windows Server 2008 R2 Standard (x64) Build 7601

---

The new Server:

Spoiler

Puget Systems C246M-WU4
CPU: Intel Xeon E-2288G (Coffee Lake-E, R0)
3700 MHz (37.00x100.0) @ 4587 MHz (46.00x99.7)
Motherboard: GIGABYTE C246M-WU4-CF
BIOS: F3, 06/05/2019
Chipset: Intel C246 (Cannon Lake-H)
Memory: 32768 MBytes @ 1330 MHz, 19-19-19-43
- 16384 MB PC21300 DDR4 SDRAM - Kingston 9965745-002.A00G
- 16384 MB PC21300 DDR4 SDRAM - Kingston 9965745-002.A00G
Graphics: Intel UHD Graphics P630 (Coffee Lake-S WS GT2) [GIGABYTE]
Intel UHD Graphics P630, 1024 MB
Drive: Samsung SSD 860 EVO 2TB, 1953.5 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: WDC WD80EFAX-68KNBN0, 7814.0 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: Samsung SSD 970 PRO 1TB, 1000.2 GB, NVMe
Sound: Intel Cannon Lake-H/S - cAVS (Audio, Voice, Speech) [B0]
Network: Intel Ethernet Connection I219-LM
Network: Intel I210AT Copper (Springville) Network Adapter
OS: Microsoft Windows Server 2019 Standard (x64) Build 17763.1518 (1809/RS5)