Re: What's happening ? Group Policy problem

Tech-Archive recommends: Fix windows errors by optimizing your registry




"abuck" <abuck@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B1424091-78BF-410E-9E62-32FE6BB0730B@xxxxxxxxxxxxxxxx
Ok, i'm pretty new to active directory but I'm doing some test and found
something that is very strange.

I have a client machine (windows XP) as well as a windows 2003 server
(Domain controller) and I have added my client machine in the domain. I
have
added a group policy in the domain controller which has the authenticated
user has the security filtering.

Let's say that I define the change system clock policy in computer
configuration, windows settings, security settings, local policies, user
rights to be no one.

It is doing the good behaviour when i'm logging to my domain in my client
machine (I can't change the system clock) but the problem is even if i'm
connecting LOCALY to my client machine, i STILL can't change my system
clock.

What do you mean? With a LOCAL account defined on the client
computer?

(Domain) Group Policies have no control over non-Domain users --
except by controlling the machine itself.

User policies affect domain users -- Computer Policies affect domain
computers.

BUT the domain policy still affects that domain machine as a computer
which MAY restrict what a user can do.

It's seems that the domain group policy override my client pc when i'm
logging localy.

How come ? How can we explain that ? any info on that is very much
appreciated.

--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)


.



Relevant Pages

  • Re: DNS-AD integration
    ... When a new non domain client machine first try to join to domain, ... the DNS will direct it to use the live domain controller for authenication? ... I have also set up AD-integrated DNS in both of these servers. ... It will use DNS Round Robin to resolve it. ...
    (microsoft.public.windows.server.dns)
  • Re: XP Longon and time mismatch with domain controller
    ... > I have XP professional client machines with SP1 working ... Every time I login from XP client machine to ... > domain controller machine time changes to 6 hours ahead. ... > as "Machine time is different from the network time ...
    (microsoft.public.windowsxp.network_web)
  • Problem in acessing the network
    ... I also had a similar problem, with member server ... "No Windows NT or Windows 2000 Domain Controller is available for ... Domain Controller: ... > servers that exhibit the behaviour and an affected client machine and post ...
    (microsoft.public.windows.server.networking)
  • RE: NSLookup failure in DNS
    ... Also DHCP is showing as not running when I do ipconfig/all on the ... Server/Active Directory Domain Controller. ... However I am able to log in if I remove the network connection. ... once I am logged into a client Machine. ...
    (microsoft.public.windows.server.dns)
  • XP Longon and time mismatch with domain controller
    ... domain controller machine time changes to 6 hours ahead. ... If I forcefully change the time on client machine to match ... as "Machine time is different from the network time ... sets 6 to 8 hour ahead time and logon will be successful. ...
    (microsoft.public.windowsxp.network_web)