Software not deploying on Wireless

[Andthomson]

We've got a head scratcher here at the moment.

 

We deploy pretty much all of our software and updates through Group policy and MSI packages, but we've noticed that with some new Lenovo T430 laptops, no group policys are applying when they are on wireless.

Not only software installs/updates, but also startup scripts and proxy settings etc. Logon scripts appear to work fine however!

 

I have checked that the 'Always wait for the network at computer startup and logon' and 'allow processing over a slow connection' is enabled but this does not appear to solve the issue.

 

As soon as we restart with the device plugged into a network cable, all the installs and scripts/updated policies install perfectly.

 

We have never had this issue deploying to wireless devices before so i am thinking it may be something to do with something in these new machines specifically as older ones are still picking things up nicely.

 

If anyone has any ideas I'd be grateful to hear them, got a flash update to rollout and cant be handling 60 staff needing to plug their laptops into a free network socket to pick it up.

 

Ah the joys of the start of the school year!

[sted]

are these xp pcs or 7?

 

if xp try this reg file on one (copy n paste and save as something.reg)

 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"GpNetworkStartTimeoutPolicyValue"=dword:0000003c

[Andthomson]

Whoops, forgot to mention the OS, they're Windows 7 machines.

[Andthomson]

I know sted's reply above was said it was for XP only but I tried it on a Win7 client and low and behold it worked.

 

Before I deploy this to my network, was there any specific reason this shouldnt be aplied to 7, or just it hadn't been tested?

[sted]

I know sted's reply above was said it was for XP only but I tried it on a Win7 client and low and behold it worked.

 

Before I deploy this to my network, was there any specific reason this shouldnt be aplied to 7, or just it hadn't been tested?

 

Iirc i tried it once and win7 complained like mad but was a while ago