Service Group IT
Ulm University James-Franck-Ring D-89069 Ulm
Building O27, Floor 2
The Windows pool is operated with so-called "roaming profiles". These allow individual settings per user, which "roam" from one machine to another.
Technically, this is implemented in such a way that the profile is copied to the local disk with each login and back to the server with each logout. If you log in to the Windows pool several times, you can only hope that this is always followed exactly and that the last logout profile from previous logouts is overwritten. There is no guarantee.
Copying during login and logout of course takes time and roaming profiles are broken from time to time (we see admins often, but it happens much less than once per student and study). Therefore some parts of the roaming profile are redirected to subdirectories of h:\.win7_profile. These parts, such as the desktop, do not "roam" with us, but still move between the machines.
The remaining part of the roaming profile is not located on the H: drive, but in a location that cannot be reached via drive letters, but it also burdens the own disk quota. If a profile becomes large, and thus the quota is heavily loaded and the login and logout times become long, or if Windows behaves strangely, probably because of strange settings, you can try to clean up the profile under c:\users\<accountname>\AppData\Roaming itself carefully. c:\users\<accountname>\AppData\Roaming is the location of the roaming profile while logged in under Windows. Rare is <accountname> supplemented by additional characters. The profile contains essential parts for Windows to work correctly for your account, so be careful when deleting it.
As a last resort, you can also contact the SGI so that we can delete your profile completely. This will only work if you are not logged in at the time. The next time you login, a fresh roaming profile will be created and everything should work again. However, many of your own settings for Windows and some applications will be lost. Typically, the loss is not critical; we have never experienced anyone missing data afterwards.