Due to hardware reqs we're tossing the idea at work to replace the Microsoft termserv with Linux. Due to the userbase being all windows fans we'd need a full on GUI and i've been prodded towards Mint. Good idea or bad?
I've happily set up a remote kunbuntu for my workspace previously, but accomodating multiple complete linux neophytes is giving me a bit of pause.
Bit more info: The current termserv is a debloated win10 machine with the multisession registry edit. However, it's on an R515 with proxmox (and running extremely well). Due to partner network requirements, we can't run depreciated software, and the box won't support win11, and frankly, I sat the boss down and asked him if he wanted to be microsoft's bitch for the forseeable future and junk serviceable hardware. He's absolutely up to getting on a linux ecosystem, but the graphical desktop environment is non-negotiable on his end.
If you need all GUI tools on a server you might want to try OpenSUSE Leap, it has full GUI (Yast2-GUI-GTK) tools for administering network, Firewalld, services, users, shares, LDAP, filesystem snapshots. Also has AutoYast for saving off server and software config and redeploying on another server.
YAST software also lets you select packages to install with check boxes, and other click options to lock/hold a package, upgrade, delete etc. While seeing the versions as radio buttons that can be selected. Takes all commandline work out of the equation.
terminal server as in individual user logins to a desktop environment for internet access. So locked down, RDP access (using XRDP at the moment on a test proxmox image)
Ah, i skimmed over termserver the first time. Both Mint and Zorin are very Windows like. And Zorin is developing GRID, when released is supposed to be a deploy / management tool for IT caring that is caring for multi client installs.
Due to the userbase being all windows fans we'd need a full on GUI and i've been prodded towards Mint. Good idea or bad?
That is completely up to what their requirements are (which applications they use, workflow etc) and what your users are like. Some users are extremely resistant to change - and have connections to people in high places - so you'll need to think about how to handle them. Like back in my helpdesk days, we had a bunch of VIP users and admin staff oppose the upgrade to Office 2007 (from XP/2003), mainly due to its new ribbion interface, and also incompatibility with some of their custom macros etc. We were midway thru the rollout and ended up completely halting the upgrades due to the fuss they kicked up. Office XP/2003 was already way out of support, but they didn't care or listen.
Company owner is 10000% on board because cheap so the only complications will be getting some win-specific software (download clients mostly) to run on the emu
terminal server to provide internet access for multiple users.
More in depth:
Workplace infrastructure is being dragged kicking and screaming into the 21st century. Part of this is to separate production from internet entirely (we work in cinema distribution) , so existing prod workstation VLAN is being blocked off, but staff still need some internet access for downloading content from studios, email, Aspera access, other bits and bobs. So the terminal server will provide this access. The users are all completely unfamiliar with linux, so the Mint GUI has been suggested as a good substitute.
Given most production machines are MS, and again for user comfort, looking to set up xRDP access for multiple users to this mint instance. From what Ive been reading up MATE is the best distro to use for what I'm planning. Not going to be hellishly high load, probably mostly email and browsing as I'm already looking to DMZ dedicated content reception servers (this place is a mess I've got my work cut out for me...)
Could you just give them limited access to the internet? Or maybe just setup a network share. What you are describing sounds overly complex. Maybe I'm just being pessimistic but what your describing sounds like a support nightmare
Honestly, Linux very much not as polished as Windows when it comes to a multiuser terminal server.
With that being said you need to look at xrdp and X. Make sure you lock down security and configure your desktop.
Honestly I would not use something with a preinstalled desktop. Start with a base image and then install the basic desktop and apps you need. You can always use custom configs to make the desktop look like whatever you want.
I'm all for Linux but terminal services is not a common use case.
I tried KASM and it seems to be solid.
Update: On further investigation Kasm requires you sign the EULA and is not free of cost or freedom.
You can make KDE Plasma look like a dead ringer for Windows. This might make user acceptance easier.
I'd look at KasmWeb for VDI. You can make instances ephemeral or keep them persistent, and you can also hook actual desktops via the VDI as RDP sessions. I have also set up a docker instance of a Windows session via Dockur and exposed it via Kasm