I'll try to explain this the best I can, because I'm sure there will be some need information I'm leaving out.
In Active Directory I added another Global Security Group about a week ago, because I created a new file server that I want a group of user to map. I added an ifmemeber command to our logon.bat file so users in this group would automatically have the file servers share mapped. This has worked exactly as planned on all of my hardwired desktop and as soon as they logged off and back on everything worked great.
Then we ran into a snag when these same users logged onto their Laptop (They have both) and the drive wouldn't map. The laptops are on our WLAN and call the same logon.bat file using Intel PROSETS "Start Application" function. I know this works because I added a pause into the script so I could see it run. Then I notice the ifmember command was returning a value like we weren't part of the group.
I ran a gpresult on the laptop and notice it doesn't show me as part of the security group that I added. I then ran gpupdate /force and afterwards the results were the same. I then hardwired the Laptop and rebooted and it worked successfully and pulled down the new Security Group. I then grabbed another Laptop and repeated the wireless steps and I couldn't get the Security Group Policy pulled down. Any thoughts why I can't get the new Security Group pulled down on the WLAN, but on the LAN it works?