It still requires device CALs (as all Windows servers do). TL DR: Windows Server 2000 Terminal Services does not require user CALs. More importantly this is 18 year old software, that hasn't received any security updates not for 8 years Probably won't work but I enjoy taking the longshot now and then.įirstly Windows Server 2000 Terminal Services does require CALs
I've used it to serve ancient programs to Windows 7 machines in the past but I've never tried it with Windows 10. If you could somehow (legitimately) get your hands on a copy you could run it in a virtual environment and provide access to the dos program through RDS. That's how I would approach a project like this anyway.Įxtreme longshot, but Windows Terminal Server 2000 doesn't require user CALs and can run old programs like this. Otherwise, if they would be throwing older physical PC's out to make way for newer PC's running Windows 10, then perhaps you could rescue some of these and install either the version of MS-DOS or Free DOS onto them and have them dedicated for this purpose.
However, if multiple users require access to the environment and program, then perhaps look at running this environment on a centralised server dedicated to virtual machines, such as a HyperV server or a VMWare server. If you would like more networking features and long file name support, then look at Free DOS. That way, when redirecting ports from the virtual machine COM1 = COM1 and LPT1 = LPT1 on the host etc. This would allow for redirection over to USB or to IP for disk drives and printing. You may also need to set up virtual serial and parallel ports on the host PC (there are both free and paid for software to achieve this). If you have a copy of the original DOS operating system, I would install that in the virtual machine. Virtualisation on a single PC would be a way to go if only one single user needs access to that program and you can trust them not to tinker. I think it depends on what the program is and what you are trying to achieve.
0 kommentar(er)
