We have been having an intermittent problem since upgrading from the
Zenworks 4 agent to Zenworks 7 on our XP desktops. Users have been
reporting that their profiles are not loading on login and the error
message appears:

"Windows cannot load the locally stored profile. Possible causes of this
error include insufficient security rights or a corrupt local profile. If
this problem persists, contact your network administrator."

Examination of the event log yields the following errors in this order:

Event ID 1508:
Windows was unable to load the registry. This is often caused by
insufficient memory or insufficient security rights.

Event ID 1502:
Windows cannot load the locally stored profile. Possible causes of this
error include insufficient security rights or a corrupt local profile. If
this problem persists, contact your network administrator.

Event ID 1515:
Windows has backed up this user's profile. Windows will automatically try
to use the backed up profile the next time this user logs on.

Event ID: 1511:
Windows cannot find the local profile and is logging you on with a
temporary profile. Changes you make to this profile will be lost when you
log off.

Event ID 1517:
Windows saved user <user name> registry while an application or service
was still using the registry during log off. The memory used by the
user's registry has not been freed. The registry will be unloaded when it
is no longer in use. This is often caused by services running as a user
account, try configuring the services to run in either the LocalService
or NetworkService account.

Our systems are running Windows XP SP2 with the latest patches and Novell
Client 4.90 SP2. We did not encounter this problem when we were using
the Zenworks 4 agent. The only recent change we have made to the
environment is the upgrade to Zenworks 7. Therefore it appears that in
our case, the Zenworks 7 agent is the cause. The issue has not occurred
on every PC yet, however every day it seems that we get more and more
calls regarding this issue. Some users report that a reboot will fix the
problem while other users have seen a more persistent occurrence. For
the time being, we are installing UPHClean on the affected machines per
http://support.microsoft.com/default...b;en-us;837115 However,
we need more testing to see if this will actually resolve the problem.
Furthermore, our objective is to determine why this issue has presented
itself after the Zenworks upgrade and what we can do from the Novell
perspective to fix it. Is there a possibility that Zenworks 7 agent is
not allowing these profiles to open? Could the upgrade to Zenworks 7
negatively impacted user profiles on these systems?

We performed the upgrade on a number of test systems without issue. We
pushed the Zenworks 7 MSI via a NAL object. The MSI essentially removed
Zenworks 4 and installed version 7.

Any help with this issue is appreciated.

Thanks.