Can anyone tell me why every time a new user profile is created on a/my laptop I have to run the Dell wireless setup again? We will be rolling out a AD deployment and when a new station gets imported into the domain, naturally it will create a new profile. Does this mean I have to touch every machine again?
Any help would be greatly appreciated.
THX!!!
OS is Win XP SP2. I think the wireless config has a problem working over multiple user profiles. regardless if the new user has admin rights.
Windows 2000 Pro?
Windows XP Professional?
Windows 2003 server (for the Domain)?
I do not know. Any notebook computer we have connected is, I believe, the Home edition.
By any chance, is the notebook running Windows Media Edition?
This is an issue I'm finding as well (Dell D810, 1370 card, WinXP Pro, SP2, + relevant security bulletin patches). Initially, I thought it was because I was attempting to launch bcmwlcpl.cpl under elevated privies (we have a program that'll send keys to the GUI, so a user can have their card auto-configured for them), but I'm now thinking it's linked to the fact that I'm shutting down wzcsvc (the cheaky, but easy, way to disallow Windows from trying to manage the wireless devices).
While this doesn't answer your question... it may contribute to your thoughts, or others, that may be trying to work this out.
Message Edited by squidlyman on 06-29-200603:15 PM
I also think the problem lies w/ wireless zero configuration. The service is disabled when you run the setup for the dell wireless. Just out of curiosity what program do you guys use for auto config of the wireless card?
It may be useful to say
why we're using a "Send Keys" method. We have these kiosk-mode machines, and wish to have them commonly configured. In going to a LEAP-enabled wireless environment, a userID and userPW is required. We have opted for a single/generic credential set for all of these devices, but at the same time, we obviously don't wish to publish what these credentials are. Thanks to Dell, we don't have command-line/programmatic access to manage the NIC, so we have to do the following...
Launch the utility under elevated privileges, and then send keys to the utility (including the credentials). We use a compiled Winbatch script for this, which allows us to "embed" the credentials so that techs and users can not see them.
This worked just dandy for the 1350's, but the 1370's are causing this semi-random problem (along with minor (read: annoying) changes in the utility's GUI), which we're still trying to work around.
This environment is not running within AD... but still keys off an NT domain. We're moving to AD down the road.
Message Edited by squidlyman on 07-04-200609:46 AM
tonyjortiz
5 Posts
0
May 23rd, 2006 15:00
BBraxton
2 Intern
•
2K Posts
0
May 23rd, 2006 15:00
Windows XP Professional?
Windows 2003 server (for the Domain)?
I do not know. Any notebook computer we have connected is, I believe, the Home edition.
By any chance, is the notebook running Windows Media Edition?
squidlyman
2 Posts
0
June 29th, 2006 19:00
While this doesn't answer your question... it may contribute to your thoughts, or others, that may be trying to work this out.
Message Edited by squidlyman on 06-29-200603:15 PM
tonyjortiz
5 Posts
0
June 29th, 2006 19:00
Thanks for the reply.....
I also think the problem lies w/ wireless zero configuration. The service is disabled when you run the setup for the dell wireless. Just out of curiosity what program do you guys use for auto config of the wireless card?
are you running an AD environment?
squidlyman
2 Posts
0
June 29th, 2006 19:00
Launch the utility under elevated privileges, and then send keys to the utility (including the credentials). We use a compiled Winbatch script for this, which allows us to "embed" the credentials so that techs and users can not see them.
This worked just dandy for the 1350's, but the 1370's are causing this semi-random problem (along with minor (read: annoying) changes in the utility's GUI), which we're still trying to work around.
This environment is not running within AD... but still keys off an NT domain. We're moving to AD down the road.
Message Edited by squidlyman on 07-04-200609:46 AM