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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
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...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER