Closed this one the other day because I thought I had a fix. Please see below:
“This is going to be a tough one, I think.
I’ve got term services set up on my Win2k server, and am currently testing it for deployment to our remote sites. This is really my first dabble with term services, so I’m a complete newbie.
Anyhoo…Myself and the other IT person here are able to log into the term server using the client with no problem. We are both Administrators. However, when trying to log into the term server using one of my user’s logons, I get “The local policy of this system does not allow you to log in interactively”.
I’ve looked at my local policy on the server, and nothing stands out. To be certain, I added “Terminal Server Users” to the “Log onto this machine locally” policy on the server. I have also verified that the user(s) in question have “Allow Terminal Server login” checked in their user profile in AD.
This is a sticky one.
Any thoughts? ”
Update: I found I had not activated my license server within the 90 grace period before slipping back into Remote Admin mode. So, I activated my server with a 10 cal license pack for Term Services. I did have the term services licensing component installed on my main term server, however I removed it upon activation of my license server. I added a DefaultLicenseServer key to the registry of the term server that points to my login server, and reinstalled Term Services to force it back into Application Server mode. The licensing server piece is installed on a domain controller (not the FSMO).
This is still not working…giving the same error as before “The local security policy of this system does not allow you to login interactively”.
Something else of note: My test users do not have a term services profile set up, or a home directory (don’t know if that makes a difference or not).
At this point, I’m stumped.
Any info would be greatly appreciated.
Dennis Jones