Guest Daryl Posted September 6, 2008 Posted September 6, 2008 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?
Recommended Posts