Not to pullup an old thread, but I thought I would shead some light on this for you...
The problem is multi parted and can come from a number of things. The most common is an admin looking at another users NTuser.dat and in so doing locking the file. And if they don't unload it, it will stay locked. So when the user goes to log on, they can't find their Registry data and so a new(default) profile is created. This is the most common reason that I have found.
Others include Account migrations in AD, (which isn't your problem since your using Novel), account changes/updates (not limited to password), and general computer problems...
The easiest way to fix it is to correct the registry, since that is where the pointers are housed. Look here...
HKLM\software\microsoft\windows NT\CurrentVersion\profilelist
here you will find a list of profiles by guid. Under these you will look for the logon name of the profile in question. Once found, (in your case you will have to look twice) change the ProfileImagePath to the folder you wish to use. This is something you can do even for testing and troublshooting as well. it's very convient when you need to change profiles... and you only have to have them log off and back on to correct the link. no reboot required, and this can also be done totally remote.
Good luck and I hope that helps...