These posts answer more peoples questions than just the first guy posting it, after all.There is no magic wand that can lock down your Windows Terminal Servers, but there are many built-in tools provided by Microsoft that do a pretty good job. When the built-in tools are not appropriate or sufficient there are many freeware and commercial 3rd party utilities to do the job.īuilt-in tools, settings and lockdown tactics I know the guy gave up, but I found the question useful and wanted to pat him on the back for asking it. Though decent chances for an OS hack is like 20% by my experience. If you change the OS from Pro to Server using a tool or a registry hack, and then install the services from a legit Windows 2000 Server CD I think it has a decent chance of working.
and I've used TweakNT (a more modern version of NTSwitch) to try the same thing for windows 2000 and in the case of windows 2000 the problem is really just the title of the OS. I'm glad the guy asked this question and to add to the answer, I've tried to get Terminal Services running on XP home once, transplanted from XP Pro, and that didn't work. That same RDP client swap was CRUCIAL for having remote desktop client with sound support on windows 2000, in an era when I could not use windows XP for reasons unexplained. Nothing else from Windows 7 worked out that way. For example, I have ripped the remote desktop client from Windows 7 out of Windows 7 and put it into windows XP, for no other reason than to satisfy my curiousity.
We don't all have access to whatever OS we need, when we need it, and sometimes there is some strange rare purpose for doing something abnormal with an OS, like backwards engineering it into doing what it isn't supposed to do. as it is often times possible to take parts from one Microsoft OS and put them in another (regardless of legality). I've tried to do what this guy is trying to do for years. Well, I don't think this is a very stupid question.
0 kommentar(er)
