Wireless Only Desktop - Network Starts too late and AD Computer Policies Don't Apply
- From: "Kenny" <None@xxxxxxxx>
- Date: Tue, 8 Nov 2005 08:27:21 -0500
Okay this problem has me pretty mad since I see postings about about it in
many places on the internet but no actual solutions, specifically from
Microsoft. Even though this would seem like a common sense requirement but I
guess Microsoft diasgrees.
I could really use some help with this I'm holding up an entire project
right now.
Anyway to the problem:
I am supposed to deploy 50 new Dell desktops which will be joined to my 2003
domain and strictly use wireless.
When they startup they do not apply computer policies, I see things in the
event viewer such as cannot obtain domain controller name. The wireless
doesn't seem to connect quick enough and/or windows is not waiting long
enough.
Users CAN login who have never been on the machine before so it seems to be
able to find the DC's at that point.
I have played with the local GPO- always wait for network startup, expected
dial up delay, gp delay, winlogon delay and the DHCP media sense reg hack.
Using the previously mentioned it did process the computer gpo's once, by
luck I guess because it never happened again.
Now my boss seems to think who cares as long as users can login. Now number
one I care because it makes my job harder and two I told him I wasn't sure
but if these machines continue to run like this, lets say two months down
the road aren't you going to have the SC screwed up between the computer
account and the DC's?
FYI- These same machines work flawlessly on a wired connection.
Right now I am using a 3com a/b/g pci card but at this point I'll take what
I can get.
My access points are Cisco 1200's, they are broadcasting SSID's and using no
encryption. The AP's are however bouncing the MAC's of of a RADIUS server.
Anyway I am just trying to find a real solution whether it be software,
hardware or both.
As far as hardware goes I definitly need to support 802.11a at a minimum, I
would much prefer PCI (low profile PCI), but USB will do if neccessary. I
would just prefer staying away from USB...had to reconnect USB devices one
too many times :)
.
- Prev by Date: Sysprep 2.0 & XP SP2 - Failed to Update Registry
- Next by Date: Re: XP Pro SP2 OEM won't install...
- Previous by thread: Sysprep 2.0 & XP SP2 - Failed to Update Registry
- Next by thread: Re: XP Pro SP2 OEM won't install...
- Index(es):
Relevant Pages
|
