Solved

Wireless XP SP2 Clients do not run login script at startup

Posted on 2006-06-12
6
2,494 Views
Last Modified: 2007-12-19
I have a large number of wireless XP SP2 clients to roll out.  They are all running with Dell 1450 wireless adaptors and are integrated in a Windows 2003 Active Directory.  The clients are authenticating via IEEE 802.1x using PEAP.

Clients connect without a problem, but will not run the login script if the user logons on as soon as the login prompt appears.

Group policy is configured to wait for the network : \\Computer configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon = enabled
Group policy is configured to run logon scripts synchronously: \\Computer configuration\Administrative Templates\System\Scripts\Run logon scripts synchronously

Despite auditing the RSOP after logon using GPRESULT, the above two settings are adhered to.

The HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\GpNetworkStartTimeoutPolicyValue has been added and set to 60.

Can anybody provide any assistance in enforcing the login script will run at startup?

0
Comment
Question by:psquance
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
6 Comments
 
LVL 9

Expert Comment

by:dooleydog
ID: 16886742
In GPMC, there is a setting to force a group policy and script to run, even over a slow connection, you might look into that. I cannot remember where off the top of my head.

Good Luck,

0
 

Author Comment

by:psquance
ID: 16886838
The policy is enforced.
When running GPRESULT the connection speed is listed.  All policy audits that I have carried out have not been at low speed.
0
 
LVL 48

Accepted Solution

by:
Jay_Jay70 earned 125 total points
ID: 16890143
maybe try setting it as a startup script instead ofa logon script - you run these within group policy
0
 
LVL 18

Assisted Solution

by:carl_legere
carl_legere earned 125 total points
ID: 16891397
Agree with Jay's suggestion.  I could not get certian wireless cards to work for simple add-to-domain functions (specifically that critical first login after add.)   Some policy prohibits the wifi from connecting early enough for the actual AD connection to build during login.
0

Featured Post

Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Have you ever set up your wireless router at home or in the office to find that you little pop-up bubble in the bottom right-hand corner of Windows read "IP Conflict - One of more computers on the network have been assigned the following IP address"…
Many of us in IT utilize a combination of roaming profiles and folder redirection to ensure user information carries over from one workstation to another; in my environment, it was to enable virtualization without needing a separate desktop for each…
In this video, viewers are given an introduction to using the Windows 10 Snipping Tool, how to quickly locate it when it's needed and also how make it always available with a single click of a mouse button, by pinning it to the Desktop Task Bar. Int…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Suggested Courses
Course of the Month5 days, 21 hours left to enroll

627 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question