Terminal Services on Win2k Pro. It is possible.
Yeah, with XP out, probably a bit late for most, but it can be done nonetheless. Also, no direct console access, but you do get to use console plus 2 remote connections. D0sfreak, you have mail with a list of the files and the.
Yeah, with XP out, probably a bit late for most, but it can be done nonetheless. Also, no direct console access, but you do get to use console plus 2 remote connections.
D0sfreak, you have mail with a list of the files and the .reg file too.
I am unable to host the actual files right now and the lists of the files themselves are quite long. However, I'm sure someone will help me out with that.
The whole of it weighs in about 7MB, though can be made smaller if I care to wade through it to eliminate some redundancy.
Here are some basics of what is required:
There are 124 files that I manually copied into subdirectories under the WINNT folder.
At that point, I go to the control panel and install windows components and select terminal services (I did not bother with client files).
It looks to install some files from the Windows CD, I have copied 110 files from the CD for this, some of them are duplicates from the files I have already manually copied.
After the installation and before rebooting, I go to regedt32 and give my account full control of the HKLM\System\CurrentControlSet\Enum\Root key, you can remove this later, and then run a 36KB .reg file.
At this point, I rebooted, I was trying to see if I could get around messing with that product option key, but alas this was not meant to be.
So, using the backup software that comes with Win2k, I created a repair disk and chose to also copy the registry data. This will reside in the \winnt\repair\regback directory. If you use regedt32 and load the system hive from this directory, you can drill down to HKLM\System\ControlSet001\ProductOptions\ProductSuite key and you can type in Terminal Server.
From here it is a quick reboot into the recovery console, copy the system file from \winnt\repair\regback to \winnt\system32\config and reboot.
At this point, you now have terminal services installed in remote admin mode.
D0sfreak, you have mail with a list of the files and the .reg file too.
I am unable to host the actual files right now and the lists of the files themselves are quite long. However, I'm sure someone will help me out with that.
The whole of it weighs in about 7MB, though can be made smaller if I care to wade through it to eliminate some redundancy.
Here are some basics of what is required:
There are 124 files that I manually copied into subdirectories under the WINNT folder.
At that point, I go to the control panel and install windows components and select terminal services (I did not bother with client files).
It looks to install some files from the Windows CD, I have copied 110 files from the CD for this, some of them are duplicates from the files I have already manually copied.
After the installation and before rebooting, I go to regedt32 and give my account full control of the HKLM\System\CurrentControlSet\Enum\Root key, you can remove this later, and then run a 36KB .reg file.
At this point, I rebooted, I was trying to see if I could get around messing with that product option key, but alas this was not meant to be.
So, using the backup software that comes with Win2k, I created a repair disk and chose to also copy the registry data. This will reside in the \winnt\repair\regback directory. If you use regedt32 and load the system hive from this directory, you can drill down to HKLM\System\ControlSet001\ProductOptions\ProductSuite key and you can type in Terminal Server.
From here it is a quick reboot into the recovery console, copy the system file from \winnt\repair\regback to \winnt\system32\config and reboot.
At this point, you now have terminal services installed in remote admin mode.
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Originally posted by Alec§taar:
Quote:Must have been ALOT of work/research/testing on his end to make it happen
It was. I can't remember if I started it or he did since it was so long ago. All I really remember is we were working on it a looooonng time ago back at Ars and then I gave up because I was busy doing other things and then moving and taking on other projects. Imagine my suprise when he posted this topic earlier this year and that he actually remembered me. WOW! HE ACTUALLY DID IT! Then he gets a ton of postings on "Why would someone do this" or the obvious "You can't do that because of legal reasons....so why bother?". It's sad that overall the modification of Windows OS's by enthusiasts has significantly decreased ever since the introduction of Windows 95....not because the need is no longer there...more because of a "Why bother?" attitude.
Quote:Must have been ALOT of work/research/testing on his end to make it happen
It was. I can't remember if I started it or he did since it was so long ago. All I really remember is we were working on it a looooonng time ago back at Ars and then I gave up because I was busy doing other things and then moving and taking on other projects. Imagine my suprise when he posted this topic earlier this year and that he actually remembered me. WOW! HE ACTUALLY DID IT! Then he gets a ton of postings on "Why would someone do this" or the obvious "You can't do that because of legal reasons....so why bother?". It's sad that overall the modification of Windows OS's by enthusiasts has significantly decreased ever since the introduction of Windows 95....not because the need is no longer there...more because of a "Why bother?" attitude.
