Roaming Profile not found

[PhilEvelyn]

I have just created a new user but AD is refusing to setup the roaming profile.

I have tried to let AD create the directory itself but when I set the H:\ home folder to \\server1\user$ AD tells me that it can't find the network path.

So I deleted the folder and profile settings and created the folder with a new name and then setup the profile. this time it all works fine until the user logs in, then the login is unable to find the roaming profile.

Help!

Phil

 

[danomac]

A couple points to note:

-On the server the user$ share needs Authenticated Users and SYSTEM to have Create and Write access;
-The home folder isn't a roaming profile. In the box Profile path: box enter "\\server1\user$\%username%"

The %username% designation will create a directory under the share with the username of the person.

Hope this helps

Daniel.

 

[PhilEvelyn]

I really wish it had helped Daniel, and sorry about confusing the roaming profile and home folder, I guess I should have explained myself better.

I have created the profile folder manually, when the user logged in it could not find the profile. When I deleted the user and created a new one and asked AD to create the profile folder, it didn't do it.

I gave up mapping the home folder and I thought that not working may be a symptom of the roaming profile not being found.

Any new suggestions greatfully received as I am about to throw the pc and the server out the £$%^&*$£" window!

Phil

 

[PhilEvelyn]

I am confused, I made it work. How? I created the profile folder manually and used a capitaql letter as I had in the profile.

This made it work! I was under the belief that it was not case sensitive.

Phil

 

[Seaspray0]

Are you giving the path \\server1\user$ as the path in the profile? Set the path to \\server1\user$\%username% in active directory instead. Note: %username% will be rewritten by the system to the actual username. The username folder should not exist prior to the user logging on, the system should create it and assign the proper permissions for it inside \\server1\user$. If it doesn't work, then check your share and NTFS permissions on \\server1\user$

 

[danomac]

This sounds like a permission problem to me.

On the server, check the Security settings. AD won't create a new profile without adequate permissions.

Under the Security tab, make sure the following permissions exist:

Group/Permission Set
1. Users/Modify
2. SYSTEM/Full Control
3. Authenticated Users/Special (go to the Advanced Tab, select Authenticated Users, click Properties, and make sure that a. Create Files/Write Data is checked and b. Create Folders/Append Data is checked.)

Without these permissions set on the Profile share, it won't work.

As far as the home folder, again, if the permissions aren't correct the user will not be able to map to it.

Daniel.