0

Hello all,

I have a continuing problem here that I can not find any articles directly related to.

After recieving Windows Update's on our XPsp2 clients here on our network from our Windows Update Server, many time's the profiles become corrupt (I assume) and then the next successful logon with that user will create the username.000 account's in documents and settings.

None of these mahchines have been through an upgrade process from NT or 2000 (which is the only article's I find in refrence to this problem). All the windows XP OS's come from a ghost image which is regurlary updated or created for new models in our footprint.

Any help is greatly appreciated.

-BenRedSox

4
Contributors
10
Replies
11
Views
9 Years
Discussion Span
Last Post by Tezdoll
0

The reason for could be because there is already configuration on that computer for the same username either on the same domain or a different domain.

0

user will create the username.000 account's in documents and settings.

None of these mahchines have been through an upgrade process from NT or 2000 (which is the only article's I find in refrence to this problem).

I got this issue when upgrading XP home to vista. Using the files and transfer wizard also seems to cause issues

0

"The reason for could be because there is already configuration on that computer for the same username either on the same domain or a different domain. "

This sounds the most logical, but, we are not changing domain's or AD or anything, just windows updates applying. Seems to me that something in that process could be simulating a domain change, or perhaps SSID?

0

yes we do have a local admin account we can log into. This is on about 30% of the machine's here. The older their image is (oldest around2.5 years) the more incrimentle accounts there are i.e .000, .001, .002 etc. Any time we see this there is also a history of events referring to "Unable to load profile - will load temporary profile".

0

You are using roaming/mandatory profiles. The reason you are getting that message is because you don't have access to that location of the profiles usually (\\fileserver\profiles\username or group).

Well that being said, thats when i get that error.

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.