Re: XP Client Profile Corruption & Recovery
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 13 Nov 2007 12:44:43 -0500
Well LAN, I wouldn't mind using roamers but these just don't work well
unless all the clients are practically clones of each other.
Well - software & OS, yes. Hardware, don't matter.
But if your clients aren't actually logging into multiple desktops, there's
still no harm in setting up roaming profiles just so you have an automatic
copy of the profile up on the server!
I don't
have any clients with these characteristics so roaming profiles just
aren't a practical option for me.
LAN, you're right. I could have skipped the disjoining and rejoining,
could have merely deleted the corrupt profile and logged in, then
copied the XXX profile to the domain local stored profile. That would
have accomplished what I needed to do and saved me some work.
I guess I'm a bit gun-shy. I can't tell you how many times I've
wanted to copy a profile only to find the copy function greyed-out.
Yep.
That's why I made manual copies of child folders
<whispers>
folderredirectionisyourfriend.....folderredirectionisyourfriend.....folderredirectionisyourfriend.....do
not store anything you care about in the profile (wish you could also
redirect IE favorites, but never mind; those are easy to copy).
-- I just don't trust
the copy function to be available to me. I've never figured out what
it is that "poisons" a profile against being copied.
Profile corruption can happen pretty easily. Esp if the profile is large, I
think. User Profile Hive Cleanup seems to help.
The local admin
account trying to do the copy is never a source or target -- daggone
copy function just doesn't always work. (mumble, mumble)
You're right: profiles suck. Tis a black art I'm thinking. You're
about as adept a practitioner as I've ever encountered.
<curtseys>
Thanks for the ideas.
Bilbo
On Mon, 12 Nov 2007 23:48:56 -0500, "Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
An XP SP2 client of SBS2K3 SP1 w/W2K3 SP2 & ExchSrv SP2 experienced
a profile corruption when some kind of script (activex?) ran amok
under FireFox.
(I've seen this a few times before and it's always labor intensive
for me to fix. The causative problem has yet to be identified and
I don't know the nature of the corruption. But I'd have more time
for that if I could recover the profile properly.)
Rebooted client and got a message saying Windows could not load the
domain user profile so it was building a new one -- named TEMP.
(This is a profile that disappears on next re-boot and a new one
gets built.)
Here's what I did to try to recover:
a) PC booted domain user AAA under TEMP profile;
b) AAA profile present but "unusable"; (status="Backup")
Event logs?
c) made manual copy of AAA profile child folders;
There really shouldn't be anything important *in* the profile folders
outside of Outlook's nickname cache & the user's Favorites. You
should use folder redirection for My Documents, Desktop, and
Application Data.
d) created local admin account XXX and logged in as XXX;
e) logged in as administrator and copied AAA profile to XXX;
gave domain user AAA rights to profile XXX;
f) disjoined client from SBS domain; deleted client from SBS;
Oops. Why step F? That isn't necessary or relevant to the user's
profile.....
g) re-booted client PC as administrator;
g) deleted old corrupt AAA profile on client;
h) ran connectcomputer wizard and specified AAA account was to use
profile XXX hoping to use it as a template for a new AAA profile;
Again, this isn't necessary.
SBS re-joined client, assigned user AAA to profile XXX. This caused
lots of shortcut paths, etc, to be broken temporarily until I could
fix 'em manually.
Yep.
What I'd hoped to have happen was for SBS to copy the XXX profile
to a new AAA profile. Didn't happen. SBS simply appropriated XXX
profile for use by AAA.
What do you mean? Don't you have c:\documents and settings\AAA now
as well as \XXX ?
I'm really confused by the way SBS applies profiles to accounts.
The connectcomputer wizard is a godsend when it comes to migrating a
local profile to a domain profile, but doesn't always name the path
as you'd wish.
Note that you can copy a Windows profile to another *domain* account
- no need to create a local one.
If I
understood the logic, perhaps I could do this rather more cleanly
but the daggone thing never works the way I expect and I'm always
in ad hoc clean-up mode. This is a real time-waster.
Where can I go to find out how to do this "properly"? It feels
like a real "crap-shoot" each time I have to salvage an account
this way.
Thanks in advance for advice...
Bilbo
Profiles suck, to be blunt.
What I do -
Use roaming profiles
Use folder redirection so very little is important in the profile
(and the profile is tiny)
Use the User Hive Cleanup Utility on all PCs
If a user's profile has a problem, I can't easily fix, I can just
delete the cached copy from the client using delprof and then log in
as the user again to reload the server copy
If even that fails, I can revert to an earlier copy of the roaming
profile on the server via VSS.
I hate mucking around with desktops crap like this - as you said,
it's a huge waste of time. Keep things simple and clean and ideally
you won't have to do this much!
.
- References:
- XP Client Profile Corruption & Recovery
- From: Bilbo
- Re: XP Client Profile Corruption & Recovery
- From: Lanwench [MVP - Exchange]
- Re: XP Client Profile Corruption & Recovery
- From: Bilbo
- XP Client Profile Corruption & Recovery
- Prev by Date: Re: How secure is our server?
- Next by Date: Re: licenses and antivirus
- Previous by thread: Re: XP Client Profile Corruption & Recovery
- Next by thread: Re: Users dropping from network: SBS 2003 and winxp
- Index(es):
Relevant Pages
|
