Try to change the owner of the homedir in the Terminal with chown to change the owner of the homedirectory.
Funktion: chown (change owner)
chown [-Rcfv] [-recursive] [-changes] [-silent] [-quiet] [-verbose] [owner][:.][group] file ...
The chown utility changes the user ID and/or the group ID of the specified files. Symbolic links named by arguments are silently left unchanged unless -h is used.
The options are as follows:
-H If the -R option is specified, symbolic links on the command line are followed. (Symbolic links encountered in the tree traversal are not followed.)
-L If the -R option is specified, all symbolic links are followed.
-P If the -R option is specified, no symbolic links are followed. This is the default.
-R Change the user ID and/or the group ID for the file hierarchies rooted in the files instead of just the files themselves.
-f Don't report any failure to change file owner or group, nor modify the exit status to reflect such failures.
-h If the file is a symbolic link, change the user ID and/or the group ID of the link itself.
-v Cause chown to be verbose, showing files as the owner is modified.
The -H, -L and -P options are ignored unless the -R option is specified.
In addition, these options override each other and the command's actions are determined by the last one specified.
The owner and group operands are both optional, however, one must be specified. If the group operand is specified, it must be preceded by a colon (``:'') character.
The owner may be either a numeric user ID or a user name. If a user name is also a numeric user ID, the operand is used as a user name. The group may be either a numeric group ID or a group name. If a group name is also a numeric group ID, the operand is used as a group name.
The ownership of a file may only be altered by a super-user for obvious security reasons.
chown -R shortname directoryname
should do it.
What happens if you create other new users with WGM? Is that working fine?
Are you using WGM at the server or from a client?
I've just tried running the command dscacheutil-flushcache
on the server and now when the user logs in his name is not in the permissions at all, and if he logs into Lion it just says "fetching" for the user, so I'm not sure if I've made this better or worse!
When he logs in now he can use most apps but now all the adobe apps refuse to launch, tho they still launch if another user logs in.
unable to restart duing a working day, I have created another user with a completely different name and that worked ok.
I'm using WGM on the server.
I did also find this in the Open Directory Log:
2012-04-19 09:40:06 BST - T[0x0000000103381000] - Misconfiguration detected in hash 'Global SID':
2012-04-19 09:40:06 BST - T[0x0000000103381000] - User 'marekbernat' (/LDAPv3/127.0.0.1) - ID 1029 - UUID 90545D87-26A6-43A6-BF51-92DB782BBC56 - SID
ok does't look like I can just make a new user after all, I just made a user called "Test" created the home folder which was also called "Test" and logged in. As soon as I opened up Adobe Bridge I saw that it created a Home folder on the server called "Marek Bernet" which was the original misspelt user name!!!
How on earth can a completely fresh user do this!!!
I am using WGM to make the home directory, what I'm saying is when I opened up Adobe Bridge from the test account it automatically created a home directory for the old deleted user and created an adobe folder in this new home directory. which should be completely impossible because the fresh test user has no preferences