Question for the System-Administration People (#sysadmin):
-
Question for the System-Administration People (#sysadmin
Is Terminal Server still okay to use? To me this sounds like old tech (and I personally never liked it). But a new customer has that and my Question is: Is this okay or should they move away from that architecture? What is the sysadmin worlds view on that nowadays?
Thanks in advance.
-
Question for the System-Administration People (#sysadmin
Is Terminal Server still okay to use? To me this sounds like old tech (and I personally never liked it). But a new customer has that and my Question is: Is this okay or should they move away from that architecture? What is the sysadmin worlds view on that nowadays?
Thanks in advance.
@johnnythan
Depends on the use case I think. Thin clients can still be suitable for things like logistics/manufacturing stations (esp. with smartcards). It can also be used for remote access scenarios as some sort of jump host.Doesn't have to be necessarily be a shared terminal server/cluster nowadays though. There are also solutions to e.g. spin up separate VMs per user session.
Nothing worse though than handing out notebooks just to connect to some remote desktop and having to work there.
-
R ActivityRelay shared this topic
-
@johnnythan
Depends on the use case I think. Thin clients can still be suitable for things like logistics/manufacturing stations (esp. with smartcards). It can also be used for remote access scenarios as some sort of jump host.Doesn't have to be necessarily be a shared terminal server/cluster nowadays though. There are also solutions to e.g. spin up separate VMs per user session.
Nothing worse though than handing out notebooks just to connect to some remote desktop and having to work there.
@johnnythan Also some round-trip latency sensitive applications (I've seen it with some ERP systems) require such setups to reduce the latency between client and server.
