Re: Terminal Server Log on Problem with New Ad 2003

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Venkat (anonymous_at_discussions.microsoft.com)
Date: 05/31/04 

Date: Mon, 31 May 2004 03:16:07 -0700

U can also see the following option in the secpol.msc
1.Allow log on through Terminal service in this add the
users or groups which u want to log on locally
2. go to doami controlled policy and domain security
policy check for the same there also.

Do the same process there also.\

Rgds,
Venkat
>-----Original Message-----
>Have you checked for "deny logon locally in the default
DC policy? Make
>sure that Deny logon locally has not been set. Run
secpol.msc on the DC to
>see the local policy. Check to see what the effective
setting is. If the
>effective setting does not allow the group to logon
locally then there must
>be another policy defined that is preventing this.
Running GPresult.exe may
>be helpful to determine what policies are being applied
to the server. It
>seems that the logon locally setting is defined in a
different policy and
>you will need to determine where.
>
>--
>--
>Tim Hines, MCSE, MCSA
> Windows 2000 Directory Services
>
>=====================================================
>When responding to posts, please "Reply to Group" via
>your newsreader so that others may learn and benefit
>from your issue.
>=====================================================
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>
>"Tom" <anonymous@discussions.microsoft.com> wrote in
message
>news:1452601c444dc$2d64a140$a301280a@phx.gbl...
>> Hello Everyone.
>> Finally we mugrated to Ad 2003 and i was able to setup
the
>> basic GPO(First time)but i am getting a problem for
>> terminal server option, when i try to log on the AD
server
>> (main domain controller and including all the server) i
>> get the below error.
>> ""The Local policy of this system does not permit you
log
>> on interactively""
>> Even i went back and took off the settings for domain
>> controller security policy and uncheck that no policy
>> defined for log on intercatively for both server. but
>> still i am getting these errors. Can any one help?
>> Thanks
>>
>>
>
>
>.
>

Relevant Pages

  • RE: Policy for Terminal Service not visible
    ... The settings for Terminal Service and other 2003-specific components are ... The easiest way around this is to copy the system.adm file from a server ... In your Group Policy Object Editor, ...
    (microsoft.public.windows.group_policy)
  • Re: How to allow users to create groups and shares
    ... Add the user/group to the Computer configuration, windows settings, security settings, Local policies, "Allow logon locally" in the Default domain controllers policy and on a existing or new created policy for the member servers. ... Filtering: Not Applied ... check with GPMC on the server or from a client the policy settings. ...
    (microsoft.public.windows.server.active_directory)
  • Domain Controller Security Policy errors
    ... Security Policy or the Domain Controller Security Policy. ... The DC is also a print and file server. ... The domain controller for Group Policy operations is not available. ...
    (microsoft.public.win2000.active_directory)
  • RE: Cant set Local Security policies. They fail to save
    ... predefined Security Template on SBS 2003 to restore security groups ... run "gpupdate.exe /force" under command prompt to force the policy ... reboot the Server to test. ... and then logon to client computer to test if user can save system logs. ...
    (microsoft.public.windows.server.sbs)
  • Re: Move W2K3 server to its own OU seperate from SBS (MyBusiness) OU
    ... OU and move the member server to so that it does not inherit it's GPO from ... policies from inheriting the default domain policies of the SBS ... section of the default domain policy. ... In direct answer to your question, you would need to filter this ...
    (microsoft.public.windows.server.sbs)