Windows 2000 Pro Slipstreamed SP3 Windows 2000 Server Slipstreamed SP3 Purpose: To install Terminal Services Server on a Windows 2000 Professional machine. SYSOC.INF Add TerminalServices Under IndexSrv: IndexSrv_System = setupqry.dll,IndexSrv,setupqry.inf,,7 TerminalServices=TsOc.dll, HydraOc, TsOc.inf,,2 After doing this and going back into Add/Remove programs it complained about the missing TSOC.INF. So I copied TSOC.INF to the INF directory in PRO. Going into Add/Remove again it complained about TSOC.DLL Copied TSOC.DLL from 2K Server System32 Setup to PRO System32 Setup Going back into Add/Remove Programs and the menu's work! I have a feeling you are missing necessary hardware drivers that Windows will need to access to get it running.

This file infector arrives on a system as a file dropped by other malware or as a file downloaded unknowingly by users when visiting malicious sites. Tscupgrd.exe; tsdiscon.exe; tskill.exe; tsprof.exe; tsshutdn.exe; twunk_16.exe; twunk_32.exe; typeperf.exe; unlodctr.exe; unsecapp.exe; uploadm.exe; upnpcont.exe; ups.exe.

Not regular drivers mind you but pseudo drivers that are hidden from view normally in the Device Manager. In the WIndows XP device manager you can click the 'View' menu and then click 'Show Hidden Devices' and all of a sudden a bunch of crazy things appear. I bet at least one of those is a Term Serv redirector or at the very least something that interacts with the services and makes things work. I have a feeling what you are trying is impossible.

Roland Print Server Net Tool. I have all of those drivers installed. That was easy and is documented up above. Here's my latest: Found LEGACY_TERMSERVICE registry entry. Exported from SERVER.

Modify [HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Enum Root permissions to allow access and then imported registry. Also found that RDPR in Root was different from server.

Exported Server and imported into PRO Also exported TERMDD LEGACY. All the files are there it just seems to be registry entries that are the problem. I'm thinking that its the enumeration between the service and the LEGACY entries but I'm not too knowledgeable in this area.

As far as I can tell they match up but it's still not working. I even misconfigured one of them and the Terminal Services Service provided a different error message about misconfigured registry settings so I know that it's parsing those entries. Mabye it's a GUID setting that needs to reference the Terminal Server Device Redirector or RPDR.SYS? Sorry, but netmeeting sucks. Yep, this error: 'Configuration Manager: The specified device instance handle does not correspond to a present device'. Is caused by misconfigured registry entries.

I think when I exported the registry entries from Server that I did not reboot after installing TS. I just re-exported all the registry entries and reinported them and now I can click on the service without errors.unfortuately the service is still in the 'Starting' State. Just checked all the dependencies and everything checks out. Missing RDPWD.SYS. COpied from SERVER SYSTEM32 DRIVERS to PRO SYSTEM32 DRIVERS SERVICES RDPDD RDPWD RDPDR TERMDD TERMSERVICE ENUM ROOT LEGACY_TERMDD LEGACY_TERMSERVICE LEGACY_RDPWD CurrentControlSet Control Terminal Server Exported All Services and Enum Root Entries. Imported into PRO Rebooted PRO Service still hung on Starting. Anyone know hot to debug a service?

Opmanager License File Crack there. My guess is that if it could be done - someone would have already done it by now, because it certainly would be helpful. Windows 2000 has been available for over 3 years now. Its probably not possible. Quote: Terminal services provides many benefits that netmeeting does not.

Your suggestion may quite possibly have been declined without having been tried. I understand that, but if you are just trying to remotely connect to a computer to help a user solve a problem or something, it works quite well. Quote: Originally posted by dfedders: My guess is that if it could be done - someone would have already done it by now, because it certainly would be helpful. That's the spirit. If it hadn't been for me then WMP7 wouldn't have been ported to 2K.nor would the Boot Disk script for NT4/2K/XP been made. (Although useless for NT4 as of yet since I haven't finished my NT4 slipstream project yet.and as for the Boot Disk script Zarquon would have got pissed off enough to do it eventually anyway. ) The problem is that people think things cannot be done.which is why they aren't.

Quote: Originally posted by stevestrike: quote: Originally posted by DosFreak: Windows 2000 Pro Slipstreamed SP3 Windows 2000 Server Slipstreamed SP3 Purpose: To install Terminal Services Server on a Windows 2000 Professional machine. That sounds like a goal to me, so what's the purpose? I mean, why do you want to do this?