Group Policy Not Processed Correctly via Wireless Connection
We have a number of machines that are giving us fits because, from what I can tell, Active
Directory tasks are trying to occur before the WLAN service starts up. For instance, looking in the event log I'll see an error from NETLOGON on system startup. The error says no domain controllers are available, and the reason is that the WLAN-AutoConfig
hasn't started up yet (I can see from the event logs where it starts, and it's not until after the NETLOGON error). The end result is things like computer group membership not being updated correctly, software not deploying correctly, and login scripts not
running.
In our group policies, I've got the option for waiting for the network enabled--so theoretically this shouldn't be happening. Yet it
is...
October 14th, 2010 11:42am
Hi,
Thanks for posting in Microsoft TechNet forums.
The Netlogon service may start before the network is ready, the computer may be unable to locate the logon domain controller. Therefore, event error
is logged. However, after the network is ready, the computer will try again to locate the logon domain controller. In this situation, the operation should be successful.
Your situation may occur to those old computer.
In order to get the laptops to connect faster, you may try decreasing the beacon time interval on the access point. Typically they are set at around 100ms. You might reduce
it in increments of 5 or 10.
You can also try restarting the Net Logon service and force group policy refresh to check.
Best Regards
Magon Liu
TechNet Subscriber Support
in forum. If you have any feedback on our support, please contact
tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
October 15th, 2010 3:42am
Hi,
Thanks for posting in Microsoft TechNet forums.
As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark
it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer
as you wish.
BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other
community members facing similar problems. Thanks for your understanding and efforts.
Best Regards
Magon Liu
TechNet Subscriber Support
in forum. If you have any feedback on our support, please contact
tngfb@microsoft.com
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
October 21st, 2010 1:47am