Posted September 6, 200816 yr The issue is in detail as explained it http://support.microsoft.com/kb/319440. In the CAUSE paragraph: "This behavior may occur if the client is unable to use opportunistic locking when the client is downloading the policy. " If opportunistic locking is disabled on the client end would this be the same as "The client is unable to use opportunistic locking?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.