• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 272
  • Last Modified:

Local/Doamin Profile on Windows XP with Windows 2k3 Server

OK. . .windows 2k3 domain with all XP Laptops connected. To date we have set up a domain profile and a local profile - for use when on/off the domain. This is becoming combersome to configure.
We are thinking of just setting up the domain profile and just using the cached copy when off the network.

Any know of any known issues I may run into? Anyone have any negative experience with this?
3 Solutions
Control Panel -> Administrative Tools -> Local Security Policy -> Local Policy -> Interactive logon = 10 is the default and
you may want to change this setting to 50 (Maximum) to let it cache for the longest time. depends on how long they will be without domain access at a time..
But we have used cached logons for years, its the way to go, but I still have dual profiles for just-in-case scenarios, and they do happen...
I believe, for the most part, it should work fine.  I get chewed on occasionally by people who think it just takes too long to log in when disconnected from the domain, but that's life.

If you use a proxy server you may need to show or script a method to change between the two settings for the internet to work from home.

The only problem I really have run into on this is user training.  Yes, you have to log into the domain FIRST to get a profile, THEN you can take it home and log into that profile...

gpradminAuthor Commented:
how long should it take to log in when not connected to the domain?
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

as long as they aren't logging onto more than one machine at a time it will work.

yes, you will have some issues from time to time. It will seem more often to you than to your users. Periodically, it will get corrupted, and they will have to download the entire thing, not just the updates.

I have used it as a test for me personally, and as a tech, it is ok. I feel you might regret it in the long run.

Is it backing up their data that concerns you? Why not simply map a drive through a GPO, tell everyone, if it is company data, copy it up to your "X" drive (x being the letter you assign to it. ) Then you dont have to worry about everyones 20G iTunes folder, pictures of their 3rd cousins wedding, and all the internet files and junk taking up space on your servers. Just a thought. Don't konw your infrastructure or requirements.
Not much longer than when connected to the domain, add a few seconds for the system to determine that it can't connect to the domain, so it in turn uses the cached account.  My users are especially, shall we say, high maintenance?  A few seconds is life or death...
My experience with cached logins are great. Only options I have run into is with Offline Files and connectivity to network resources (due to people cancelling thier synchs....). That, and the time to login is almost instantaneous as on the domain, unless they are plugged into a home network physically. Then it usually takes a few extra moments for the system to realize it cannot find the DC, and then login to the CP.

Other than that, might see some slownesses here and there with network resources being polled, when they arent present, like mapped drives, My network places shortcuts, etc....

For the most part though, the pros outweigh the cons IMHO....

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now