Group Policy IPv6 FYI

[Aaron E.]

Scratch the locking policy idea, doesn't seem to be that either.. I 
might have thought it moved servers but in reality it is still only on 
one server.. I might have to chalk this one up to a faulty windows 
install,, I have removed and added and removed and added group plicy 
editer and same to and from the domain a few times.. along with terminal 
services..  I might just need to see how a fresh installation reacts and 
get rid of the faulty box.. Ill let you know..

On 03/04/2011 11:38 AM, Aaron E. wrote:
> Actually I was wrong... If I open group policy on one server it seems to
> lock up the policy and I can then no longer edit it from another server
> using the group policy editer.. The following error is what I recieve
> when I try to gpupdate /force
>
> This will rotate servers.. It seems to be whatever server access's the
> policy first locks it.. Anyone see this?
>
> samba4 alpha14
> windows 2008 temrinal server
>
> Updating Policy...
>
> User policy could not be updated successfully. The following errors were
> encount
> ered:
>
> The processing of Group Policy failed. Windows attempted to read the
> file
> \\example.com\sysvol\example.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F
>
> 9}\gpt.ini from a domain controller and was not successful. Group Policy
> setting
> s may not be applied until this event is resolved. This issue may be
> transient a
> nd could be caused by one or more of the following:
> a) Name Resolution/Network Connectivity to the current domain controller.
> b) File Replication Service Latency (a file created on another domain
> controller
> has not replicated to the current domain controller).
> c) The Distributed File System (DFS) client has been disabled.
> Computer policy could not be updated successfully. The following errors
> were enc
> ountered:
>
> The processing of Group Policy failed. Windows attempted to read the
> file
> \\example.com\sysvol\example.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F
>
> 9}\gpt.ini from a domain controller and was not successful. Group Policy
> setting
> s may not be applied until this event is resolved. This issue may be
> transient a
> nd could be caused by one or more of the following:
> a) Name Resolution/Network Connectivity to the current domain controller.
> b) File Replication Service Latency (a file created on another domain
> controller
> has not replicated to the current domain controller).
> c) The Distributed File System (DFS) client has been disabled.
>
> To diagnose the failure, review the event log or invoke gpmc.msc to
> access infor
> mation about Group Policy results.
>
>
> On 03/04/2011 11:18 AM, Aaron E. wrote:
>> Hello all, this is just an FYI on my findings.. to help someone that
>> runs into the similar issues...
>>
>> I was not able to edit the policies or gpupdate /force from one of my
>> windows test servers connected to a S4 domain.. I fought with this for a
>> long while. The logs were giving no different information from a working
>> system to the not working system.. The error stated it could not read
>> the Policy due to permissions network settings or dns...
>>
>> Once I looked into it I had disabled IPv6 on the windows network
>> connection setting. I enabled this and all started working.. I am not
>> running IPv6 so not sure what the problem was..
>>
>>
>>
>
>