T
Tom Penharston
I started a thread almost one year ago:
http://groups.google.com/group/micr...locally+stored"&rnum=1&hl=en#593aa4b85a102cf1
Someone asked me for a response. Looking back, here's my response:
There were two possible problems, maybe more. First, I probably had an
inconsistancy between my local group policy and my registry.
Inconsistancies are simply bad administration. Second, I found that
machines need to be logged-in immediately after a Ghost restoration; if
they sit for over 10-18 minutes the eventual login will be full of
problems. (I wonder if there is some security setting that goes into
effect in XP during an idle login prompt.) Ghost may not be a factor,
it may simply be a login issue, I don't know.
I researched verbose logs for several weeks and learned very little.
The verbose logs provided me with some interesting, detailed analytical
work but it was not really helpful. I was looking for a reason why a
10-18 delay meant a corrupted login. I didn't find a reason.
I learned to never edit the registry; I limit access through Group
Policy only. If a policy does not exist for what I wish to do, then
there's probably a reason for that. Going beyond the GP to "registry
hacks" can cause inconsistancies in the profile that can eventually
come light as a corrupted login.
I also learned that there are many, many reasons for "locally stored
profile errors". It's one error message for a wide range of troubles.
Be careful to compare your situation with others.
http://groups.google.com/group/micr...locally+stored"&rnum=1&hl=en#593aa4b85a102cf1
Someone asked me for a response. Looking back, here's my response:
There were two possible problems, maybe more. First, I probably had an
inconsistancy between my local group policy and my registry.
Inconsistancies are simply bad administration. Second, I found that
machines need to be logged-in immediately after a Ghost restoration; if
they sit for over 10-18 minutes the eventual login will be full of
problems. (I wonder if there is some security setting that goes into
effect in XP during an idle login prompt.) Ghost may not be a factor,
it may simply be a login issue, I don't know.
I researched verbose logs for several weeks and learned very little.
The verbose logs provided me with some interesting, detailed analytical
work but it was not really helpful. I was looking for a reason why a
10-18 delay meant a corrupted login. I didn't find a reason.
I learned to never edit the registry; I limit access through Group
Policy only. If a policy does not exist for what I wish to do, then
there's probably a reason for that. Going beyond the GP to "registry
hacks" can cause inconsistancies in the profile that can eventually
come light as a corrupted login.
I also learned that there are many, many reasons for "locally stored
profile errors". It's one error message for a wide range of troubles.
Be careful to compare your situation with others.