Has anyone ever managed to upgrade SME to 7.x with an existing roaming profile setup? The upgrade went smoothly enough - though I restored config and user data onto a clean install of SME 7.2 more or less manually using rsync.
The symptoms are that old accounts and machines work more or less as expected, but that new machines and new users get messages at login saying that the profile can't be located or that it can't be loaded, or even that the domain controller can't be contacted. Different users get different responses on the same desktop.
The environment is 95% WinXP, with 1 remaining Win2k box which is mostly off. I have applied the gpedit hack to stop XP checking for profile ownership (helped some people but not everyone), and tried various settings for the domain master/client session encryption/signing etc. It's easy to make the problem worse and I ended up completely re-installing one machine when it wouldn't talk to the server for login at all - every domain user was rejected. Leaving and joining the domain sometimes makes things better and sometimes worse.
Today I disabled roaming profiles but this doesn't stop desktops complaining that the profiles can't be found nor some systems refusing to log in some users.
I am just about ready to toss Windows out of the place and go with something it's possible to debug... has anyone lived through this before? Are there docs which explain exactly what gpedit settings are needed to work with Samba (or if samba.conf needs tweaking too)?
The most annoying feature of the profile being missing or whatever is that acrobat reader won't start because it wants to write to the user registry which is read-only. Explaining to the poor users that the problem isn't acrobat always generates a blank stare...
3 Replies
1188 Views