T
TheMachineRNC
Hi,
My company has 50 plus global sites. Each with a domain controller and all
replicating on a regular basis, has been experiencing a very odd problem
with end user laptops.
Some of the users when they login they are logging in and receiving a fresh
cached domain profile on their laptop. For example, I login to my laptop
and my cached profile is located at D:\Documents and Settings\Jim.Smith.
Let's say the domain I login to is XYZ and it's the only domain in the
company. Well the problem comes that one day I login and all of a sudden
my profile that I'm attached to on my laptop is now D:\Documents and
Settings\Jim.Smith.XYZ. All of my data and settings reside in the old
profile of D:\Documents and Settings\Jim.Smith.
Any idea why this occurs? I'm betting we have an ailing Domain Controller
out there somewhere that is replicating or not synchronizing correctly. So
when that user goes to login the next day the cached profile appears invalid
and voila - new profile created on the laptop.
Any experience with this? We have a mix of Windows 2000 users and Windows
XP users. The most of the time this happens on 2000, but some occurrences
on XP as well. We have a standard global build on both platforms. We
also have Windows 2000 and Windows 2003 domain controllers. We do not use
roaming profiles.
Thanks!
My company has 50 plus global sites. Each with a domain controller and all
replicating on a regular basis, has been experiencing a very odd problem
with end user laptops.
Some of the users when they login they are logging in and receiving a fresh
cached domain profile on their laptop. For example, I login to my laptop
and my cached profile is located at D:\Documents and Settings\Jim.Smith.
Let's say the domain I login to is XYZ and it's the only domain in the
company. Well the problem comes that one day I login and all of a sudden
my profile that I'm attached to on my laptop is now D:\Documents and
Settings\Jim.Smith.XYZ. All of my data and settings reside in the old
profile of D:\Documents and Settings\Jim.Smith.
Any idea why this occurs? I'm betting we have an ailing Domain Controller
out there somewhere that is replicating or not synchronizing correctly. So
when that user goes to login the next day the cached profile appears invalid
and voila - new profile created on the laptop.
Any experience with this? We have a mix of Windows 2000 users and Windows
XP users. The most of the time this happens on 2000, but some occurrences
on XP as well. We have a standard global build on both platforms. We
also have Windows 2000 and Windows 2003 domain controllers. We do not use
roaming profiles.
Thanks!