We have a startup script applied to a set of laptops via group policy which is used to copy a start menu structure from the network to the local machine. It deletes the contents of the current start menu structure on the local machine and then copies the start menu from the network.
The problem that we are having is that the startup script does not run at startup and I am thinking that this is because the wireless connection is not connecting quickly enough and so the startup scripts are being skipped. Am I right with this assumption? Also, we use WPA-PSK not RADIUS.
My question is, is there anyway of getting the laptops to wait for a network connection so that the startup scripts are executed as appropriate.
Thanks in advance,
Last edited by J_Worth; 4th August 2012 at 12:17 AM.
You could try enabling the policy called
"Always wait for the network at computer startup and logon"
You will find it in Computer Policy -- Admin Templates -- System -- Logon
What make/model are the laptops and wireless card?
There are currently 1 users browsing this thread. (0 members and 1 guests)