Failure to update domain policy Impersonate a client after authenication
- From: Eddie <eddie.doey@xxxxxxxxxxxxxxxxxxx>
- Date: 22 May 2007 00:43:10 -0700
I made a mistake and messed up a group policy on our domain. Having
changed the policy "Impersonate a client after authenication", its
screwed up the domain controller (i missed off service). It was
changed very quickly after going through the process of changing the
RPC service identity, resetting the policy and several reboots. The
active directory looks rights, but sometimes clients pick up the old
policy and can't shake it. I just added a new machine to the domain
and on its second reboot it picked up the rogue policy. I have no idea
where is can still be picking it up from. its frustrating to say the
least. I thought it had something to do with cached credentials, but
it happened on a new machine.
gpupdate /force was run, but on the next reboot it was back. its
driving me a little crazy :)
We have a single domain with three AD servers.
.
- Follow-Ups:
- Re: Failure to update domain policy Impersonate a client after authenication
- From: Roger Abell [MVP]
- Re: Failure to update domain policy Impersonate a client after authenication
- Prev by Date: Re: which ip scheme i have to prefer?
- Next by Date: Re: Security Hardening
- Previous by thread: IEEE 802.1x authentication for domain user accounts only
- Next by thread: Re: Failure to update domain policy Impersonate a client after authenication
- Index(es):
Relevant Pages
|
