Windows 2000 Terminal Server connecting to 2003 License Server
You have a mixed environment with a 2000 Terminal Server and your Domain Controller and License Server is 2003. The problem you have is that the 2000 TS doesn’t see the 2003 License Server. You can connect to it if you manually go to Licensing on the 2000 TS and then select “Connect” and type in the License Server Name, but that of course won’t work if you connect with a Terminal Service Client.
Solution: (this involves editing the registery, so be carefull)
Login to the 2000 Terminal Server and start the registry editor (regedit) and open the following:
HKLMSYSTEMCurrentControlSetServicesTermServiceParameters
and add the followinfg key: (type REG_SZ) DefaultLicenseServer for the value enter the License Server Name (must be resolvable by DNS or WINS).
Terminal Server – You do not have access to logon to this session
When a user try to log on to TS session, they receive the following error message: “You do not have access to logon to this session.” The administartor however can log in without a problem.
Solution:
Set custom Terminal Services connection permissions:
1. Click Start > Programs > Administrative Tools and then Terminal Services Configuration.
2. Open the Connections folder.
3. Right-click the connection (RDP-TCP) and then click Properties.
4. On the Permissions tab, add the group(s) or user that needs access to this connection.
5. Click OK.
Server 2003 – You may not have appropriate permissions to access the file
This is a problem you run into when you want to run an exe file from a Terminal Server Session. You can run the exe from anyone’s desktop, but if you attempt to terminal services into a server, and run it from there, you get the “Windows cannot access the specified device, path, or file” error.
Solution: Remove IE7 Enhanced Security on these workstations from Add/Remove>Windows Components.
Add remove Windows Componenets.
Deselect IE7 Enhanced Security Configuration.