Alternatively, to get your users onto the network when they are at a remote location is to setup a Terminal Server. In AD setup Terminal Server Profiles.
Main Topics
Browse All TopicsWe run a number of XP and Vista Business Laptops and desktops on our SBS 2003 network.
Desktop users log into their domain profile all of the time. However although Laptop users can log onto the domain profile whilst off the network the log on takes a long time. (3-5 mins) These are all new top spec lap tops. To that end all of the remote users use their local machine profile as standard. This means that they can't access mapped drives, and printers etc when logged in in the office.
What is the reccomended solution for remote worker profiles.
Can a local machine and domain profile be the same i.e point to the same location.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
If your worried about getting mapped drives to remote users, you can always add a login script that will attach these mapped drives during the login process via Active Directory. That would be the option i would go. Roaming profiles always get bogged down and takes too much time to deal with and local profiles are too limited.
Not sure what the issue is, particularly. However, I would still have them use their domain profiles w/ the cached credentials created upon a successful login on domain, which I'm assuming they must do at some point or another, as their default profile.
With that said, in your login script, you can establish drive mappings and printer mappings that are persistent. If users for some reason lose the drive mappings by manually disconnecting them, creating a simple batch file for them to run (while authenticated on the VPN if remote):
net use x: /delete
net use x: \\server\share /persistent:yes
The length of time of 3-5 minutes, is because your PC is polling around to DHCP to get an IP address, and to find a domain server authorized to validate their login credentials, both of which will timeout after determined not available. A truly local profile is quicker, but adds numerous complexities to managing the user, their PC, and their needs.
Windows doesn't have a perfect solution, but what I've found that helps that process is to shut off the wireless radios with the switch on the side, login with the domain profile, and it will quickly default to cached credentials. After the desktop settles, which it's pretty quick to with the wireless radio shut off, then turn it back on and it'll get the wireless running again.
If one can master the effective timing of that procedure, remote login with a domain profile can actually be quite quick. I do it all the time, personally.
Business Accounts
Answer for Membership
by: pzozulkaPosted on 2009-02-25 at 15:39:07ID: 23739921
You can still have domain profiles for remote users. Setup a VPN connection to your network, so that when they are away from the office, they can login using their domain profiles via VPN.