Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm trying to serve two legacy Windows Applications (one of them are 16bits) in a Linux LTSP University Lab. We never found a real solution for this problem.

But today this is getting insane; at a point of running a modern version of Windows in a localdisk; with XP-Mode just to run those applications.

So I'm looking for ideas/help on how to run it. Wine is not an option; since one of the programs crashes in the save dialog (perhaps because the save dialog is the one from Windows 3.x)

If someone would like to suggest running some virtualization technology, like Xen or Virtualbox we need to embed this in the boot image; since the LTSP Server is based on the "fat clients" style. And, the VM's must be non-persistence and most restrictive possible, since we don't want our alumni installing apps, surving the web, etc on this Windows solution.

Thanks for any help and sorry english mistakes.

share|improve this question
1  
Do you need to make this application multi-user? –  Mark Henderson Apr 8 '13 at 7:35
    
I don't think so. I just need simultaneous use by some users. They should be able to save our documents to a fileserver. The fileserver is a Ubuntu 12.04 LTS or a Debian 6 Squeeze (since they have home directories shared by NFS. I can install Samba if needed or a Windows Server since we have licenses for Windows Servers. –  Vinícius Ferrão Apr 9 '13 at 1:23

1 Answer 1

up vote 0 down vote accepted

I found a solution.

We managed to obtain a legacy copy of Windows NT 4 Terminal Server and deployed it in a virtual machine with one processor and 128MB of RAM. Unfortunately we are unable to serve it using Hyper-V from Windows 2012 Server. Since we don't have any other virtualization technology without cost, we opted to use VMWare Player as a solution, and it worked fine.

With the NT4 TS we can install the legacy 16bits applications and serve it using the RDP4 Protocol to the Linux Client's.

We wrapped the rdesktop program with it's command line arguments in a fancy shell script with an icon. So it's transparent to the user, and the user never knows were the software is running, since only the software is exported through the rdesktop.

Windows NT 4 Terminal Server is old and deprecated, but it's still amazing. This was my first contact with it and I'm really pleased about the solution.

TODO: Try to deploy/migrate the same Windows NT 4 Terminal Server to a KVM+QEMU server. So we can ditch the VMWare Player.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.