Remote users and their associated troubles
So we have a few remote users - only ever connect via VPN. This is usually fine, unless - group policy updates need to be done!! Dun dun dunnnn.
Then it stinks.
Here's how we get around it for now: (I've been told that RPC over HTTPS is the cat's meow, but we'll have to wait for 2008 R2 first.)
1. Connect to VPN.
2. Run gpupdate /force.
3. Reboot.
4. Log on using dial up connection, use VPN connection.
5. It works!
Sounds easy, but took forever to figure out that's how it's supposed to be done. There is no real way to auto-run the VPN prior to logging on. You can set up a service to run, but there's no guarantees there.
Another catch is to ensure that the VPN you're using is set up so that anyone on the computer can use it - if you choose 'only for me' when installing your VPN, it won't work, as anyone can use the Windows logon screen!
Then it stinks.
Here's how we get around it for now: (I've been told that RPC over HTTPS is the cat's meow, but we'll have to wait for 2008 R2 first.)
1. Connect to VPN.
2. Run gpupdate /force.
3. Reboot.
4. Log on using dial up connection, use VPN connection.
5. It works!
Sounds easy, but took forever to figure out that's how it's supposed to be done. There is no real way to auto-run the VPN prior to logging on. You can set up a service to run, but there's no guarantees there.
Another catch is to ensure that the VPN you're using is set up so that anyone on the computer can use it - if you choose 'only for me' when installing your VPN, it won't work, as anyone can use the Windows logon screen!
Comments
Post a Comment