Profile Issue

[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!

 

[Jim in Arizona]

I don't have much experience with what you're referring to but I am curious
about it. Is the xyz you're referring to a number like 001 or 002?
The only time I would ever see an appendage like that is when I had deleted
an AD account and recreated it for a user, which when they logged onto a
machine they had previously been on would create a new profile for them with
their username appended by a number, so you would see jsmith and also
jsmith.001.

This sounds like a replication problem, but I'm not sure either.

 

[TheMachineRNC]

Hi Jim,

XYZ would represent our domain name, but I don't want to announce that. ;-)
I point to an AD replication problem also, but I'm not quite sure how to
identify it.

If anybody else has information, I'd love to hear it.

Thanks!

 

[Guest]

Hi,
we have the same problem in our company, we can quickly fix it on user side
but we do not know the cause. As I have information we made two changes
before the problems started. We install SP2 on domain controler (Win2000).
And we upgraded Symantek Antivirus. Did you using Symantek anti virus
solutions or you install SP2???

Jarda

 

[TheMachineRNC]

We have been upgrading servers to Server 2003. Our desktops have also been
upgraded to SAV Corporate Edition 10.1.5.5000, then to SAV 10.1.5.5010 and
then to SAV 10.1.6.6000 and the problem still occurs. Domain controllers
have also been getting SAV upgraded also.

Is the SAV upgrade on your desktops or servers?

Thanks

 

[Guest]

Hi,
we are using SAV Corporate Edition 10.1.5.5000 on our desktops and on
servers.
There is theory that SAV (when PC starting) scanning directory with user
profile and "block" it for Win and Win then automaticly make new profile. But
it is only theory we do not know if it is right.

 

[TheMachineRNC]

Interesting. This issue started to appear after going to SAV 10.1.5.5000.
Same for you? Subsequent issues have not solve the problem.

Also - are your users laptop users who travel or do they stay in the office?
If travel, do you have a VPN client?

 

[Guest]

Hi,
It look like I have some good news - look on this page
http://service1.symantec.com/SUPPOR...5736a007c8a79?OpenDocument&seg=en&lg=en&ct=uk

It is prove that our suspicions about Symantec were right. We download fix
and start testing it. I hope it help.

 

[TheMachineRNC]

We took laptops from 10.1.5.5000 to 10.1.5.5010 with the MRT patch and it
didn't seem to help. We've since gone to 10.1.6.6000 and still have the
problem occurring

Curious to see if it helps in your situation.