Re: Wireless laptops and Group Policy

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Steven L Umbach (n9rou_at_nospam-comcast.net)
Date: 02/21/05 

Date: Sun, 20 Feb 2005 20:26:40 -0600

There was recently a long discussion about such in the
win2000.public.networking newsgroup if you want to check the posts there and
also you may want to post in the Microsoft.public.networking.wireless. What
more than likely is happening is that users are being logged on with cached
credentials and then when the network becomes available they are then being
authenticated to the domain, but too late to have initial logon Group Policy
applied to them and of course that is the only time that logon/startup
scripts will be applied. You could try to disable logging on with cached
credentials to see if that makes a difference [try one computer for a test]
. That can be done in the appropriate security policy such as at the
domain/OU/local level. For example for Local Security Policy go to security
settings/local policies/security options and for the option number of
previous logons to cache - set to zero. However if it takes too long for the
wireless network to respond the user may get a message that they can not
logon because a domain controller can not be contacted. --- Steve

"Daniel" <Daniel@discussions.microsoft.com> wrote in message
news:8B60CB19-85CC-4345-8F73-0DDD78F1BEF8@microsoft.com...
>I have Win2k Pro laptops connecting to Win 2k3 server via a Netgear WG302
> wireless access point. When the users logon they are not getting the Group
> Policies applied and batch files are not executing. If I connect the wired
> they all works ok. Can anyone tell me why and how to fix?

Relevant Pages

  • Re: Wireless laptops and Group Policy
    ... wireless network is not being enabled in time for a domain logon. ... would not receive initial logon Group Policy. ... That can be done in the appropriate security policy such as at the ...
    (microsoft.public.windows.server.networking)
  • Failed Logon Attempts
    ... to domain set a domain security policy ... lockout policies>>set account lockout threshold>> to 4 ... our servers for failed logon attempts. ... user 'joeblow' on workstation 'jowblowspc' between ...
    (microsoft.public.security)
  • Re: logon from the server machine !
    ... The default Domain Controller policy in Windows Server 2003 does not allow ... Security Policy setting. ... Policies/User Rights Assignment - and add the user to the Allow Local Logon ...
    (microsoft.public.windows.server.general)
  • Re: Firewall and Security
    ... the Domain Controller Security Policy (on the server under Administrative ... >>and regular logon failure, account management success ...
    (microsoft.public.windows.server.sbs)
  • Re: Firewall and Security
    ... the Domain Controller Security Policy (on the server under Administrative ... >>and regular logon failure, account management success ...
    (microsoft.public.windows.server.sbs)