Re: Local System Log on

Hi
I belive that you have to add the created useraccount to the "allow log on
locally" parameter.

You can find it under Administrative tools -> Domain Controller Security
policy ->Local policies -> Allow log on locally


"BJ" <BJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:838185FC-172B-45C8-86C7-DE1DE8A96592@xxxxxxxxxxxxxxxx
I have a Windows 2003 Server configured with Active Directory. But I want
to
be log on to the server locally without using the Administrator account.
SO I
went into Active Directory Users & Computers, created an account and
attempted to log in to it. But when I log off and attempt to log in with
the
account I created, it shows the following message:

"To log on to this remote computer, you must be granted the "Allow log on
through Terminal Services" right. By default, members of the Remote
Desktop
Users group have this right. If you are not a member of the Remote Desktop
Users group , or another group that has this right, or if the Remote
Desktop
Users group does not have this right, you must be granted this right,
manually."

Bottomline is, I cannot log in with the account I created. I do not want
this account to have administrative privileges. I noticed that when I
logged
in with an account with administrative privileges, I had no issues. But I
could not do the same with an account ordinary "user rights".

This computer does not run Terminal Services, even though the service is
installed and currently running. And no other Remote Access services are
actively running, per se. So I find it hard to understand why I cannot use
this.

I look forward to your assistance in helping me resolve this.

Regards



.

Relevant Pages

  • Re: Performance monitor on a remote computer
    ... In the right pane of the subsequent two pane window, ... that is selected is "Local System Account". ... log counters on the remote machine. ... >> I am logged into both machines as an administrator. ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: No login & no accounts- XP Home
    ... > Why you should not run your computer as an administrator: ... > reformat your hard drive, delete all your files, create a new user account ... > You should add yourself to the Users or Power Users group. ... > you can perform routine tasks and you can also install programs, ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Firewall
    ... > a couple hours away in a remote office. ... > can log onto the comuputer locally is the administrator. ... > understand why no other account was created with more access than the ... If it is the built-in Windows SP2 firewall, ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Logon failure on disabled Administrator account
    ... A workaround is to remote into your "home" system (that has the allowed IP ... Les Connor [SBS Community Member - SBS MVP] ... another account for administrator tasks. ... because someone periodically tries to brute force the account. ...
    (microsoft.public.windows.server.sbs)
  • Re: Block remote access for the default domain administrator
    ... remote administration and then block remote access for the default domain ... The strong password set on the Administrator account should be sufficient but he feels remote administration would be more secure using an account with a different name and strong password as well. ... Neither the loss of remote admin facilities nor having the server cracked is particularly desirable, but I know which I'd prefer. ...
    (microsoft.public.windows.server.sbs)