If you`re from the old school and still use the command prompt regularly, then this tip is for you. You can create a new right-click option to open a command prompt window from the directory you`re currently working in. Open your Registry using RegEdit (not RegEdit32), and find the key HKEY_CLASSES_ROOT\Directory\shell. Create a new sub key called "CommandPrompt" as in HKEY_CLASSES_ROOT\Directory\shell\CommandPrompt.
Change the value of default within the key to equal the text you would like on the right-click menu, for example `Open Command Prompt....` Create another new subkey under the key you just created, and name this subkey "command" as in
Change the value of default within this key depending on your OS to equal either:
command.com /k cd "%1"
cmd.exe /k cd "%1"
Now right-click a folder, and the new option of "Open Command Prompt..." should be available.
This information can be found in MS KB article Q171406
Open up regedt32 and set up a registry key as follows:
Add the key "DontUseUNC" as a DWORD value and give it a value of 1.
This should fix your problem.
Of course, this needs to be performed for all users. You can use a utility called reg.exe with the "add" command to add the key in the usrlogon.cmd logon script.
I recommend that you reboot your server daily or at least weekly. •Terminal Server comes with a command-line tool called TSSHUTDN on TS 2000 and SHUTDOWN on TSE 4.0. This command can be used in conjunction with the Scheduler Service and the AT command to schedule an automatic shutdown and restart of your Terminal Servers.
at 23:00 /every:M,T,W,Th,F,S,Su "tsshutdn /reboot"
at 23:00 /every:M,T,W,Th,F,S,Su “shutdown /reboot"
This would reboot the server every day at 11:00 PM
1. The PATH variable is too long or has an entry pointing to the WINDOWS or WINDOW/SYSTEM directories of a Windows 3.x or Windows 95 installation. This would be in either Control Panel / System / Environment or the AUTOEXEC.BAT. See tip 021.
2. The COMMAND.COM used by Windows NT is missing, damaged or replaced by another version. Repair System files and re-apply your latest Service Pack.
3. The VER.DLL file in the %systemroot%\system or %systemroot%\system32 directories is corrupted or replaced by an invalid version.
4. SHARE.EXE (or VSHARE) is being loaded in an %systemroot%\system32\AUTOEXEC.NT.
5. Insufficent environment space, see tip 047.
6. Check %systemroot%\system32\CONFIG.NT, here is mine:
shell=%systemroot%\system32\command.com /p /e:4096
7. Corruption of the WOW sub-system files. Repair System files and re-apply your latest Service Pack.
8. Make sure the following files are from your latest SP or NT CD, whichever is later:
NOTE: Ver.dll should be in both %SystemRoot% and %SystemRoot%\System32.
This tip comes from http://www.jsiinc.com/tip2200/rh2212.htm To remove the Internet Explorer icon from your Terminal Server desktop, start the registry editor from the Terminal Server console. Delete the following key:
NOTE: Deleting the above key will also work on any Windows NT 4.0 platform.
This tip comes from http://www.jsiinc.com
When a Terminal Server client abnormally (power failure, network failure, etc..)
loses their connection to the Terminal Server, their session may not be marked
as disconnected. When the client logs on again, a new session is created, leaving
the origonal session active, consuming resources.
To fix this problem, apply the latest Terminal Server Service Pack.
Then use Regedt32 to navigate to:
On the Edit menu, Add Value name KeepAliveEnable as a type REG_DWORD.
Set the data value to 1. The default is 0.
Use the Connection Configuration tool to double-click rdp-tcp, and click Advanced.
Locate the On a broken or timed-out connection, connect action the session line. Then:
Clear the Inherit User Config check box.
With these settings, KeepAliveEnable will use Carrier Loss Detection,
polling each client every (KeepAvileInterval / #sessions), to disconnect the client session.