I figured it out.
The machines (Dell Latitude F510's) use an Intel onboard wireless card. The
driver for the card loads a WLANKEEPER service that runs the irritating Intel
software. SO even though I tell Windows to manage the wireless card, the
Intel stuff kicks it offline,
Stopping the WLANKEEPER service and setting it to disabled allows me to
re-enable WZC and lets Windows manage my wireless word.
Woot.
"Matthew Ellis (SD47)" wrote:
> I am having a problem with a set of laptops running Windows XP Pro (w/SP2).
>
> This is all on a wireless connection:
>
> When I log on with the domain administrator account, all is well, however,
> when my regular domain users log in, they are able to authenticate against
> the domain, Active Directory enabled scripts and policies run, folder
> redirections, mapped drives, etc connect, and then the Wireless Zero
> Configuration service appears to stop as they lose their wireless connection.
>
> If I re-enable the service, it works fine until the machine is rebooted.
>
> UPDATE: the service starts fine on the default domain (the domain the
> machines are joined to during RIS) however, the service stops starting (can I
> even say that?) after I rejoin them to a child domain.
>
> Any suggestions?
>
|