I have some laptop and wireless workstations that are not on the network at the time the user logs on, but later once they get a desktop they can create a vpn which will give them full server access.
At the time they boot up, they get a 'guest wireless' connection which does not allow them to our servers and does not provide them with our DNS settings. I can deal with the DNS settings via script to point them to our domain, at that point they could run gpupdate even if it is manual. The problem is that some updates, specifically the Computer Configuration Policies must run at startup, before the user has logged in. (I am not trying to install software, just apply computer policies.) Is there a way to instruct Windows XP to cache the computer policies and startup scripts and process them once the computer has a vpn with the right DNS settings? I've looked at the "Wireless Policy" that came out with Server 2003, but since the DHCP server does not provide our DNS settings, I don't see that ever working, unless I'm missing something. At one point I attempted to use GPO to set the DNS settings, but that threw them into the registry where laptop users who attempted to take the machines home could not change them, I need to leave the DNS settings DHCP by default, or at least leave them visible to the user. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
