Forum Discussion
New user and roaming profile
Hi
I added a new user to domain controller and I also added a profile path (roaming profile). I went to client computer and tried to login the new user, after logging in it is saysing that the profile was not successful and need to logout amd try again. It is doing this over and over again until I delete the path from the user in domain controller then I can login the user to the machine. After successful login I can put back the profile path in domain controller and when I try to login the user again it is working fine.
How to solve this issue?
2 Replies
Summary of Key Areas to Check:
- Permissions on the profile share and folder.
- Folder Creation: Ensure the profile folder exists and is writable.
- Network Connectivity between the client and the server.
- Group Policy settings to ensure roaming profiles are not restricted.
- Event Viewer Logs for any error or warning messages.
After completing these steps, the issue should be resolved. If not, it may be worth testing this with different user accounts or even reinstalling the RDS or user profile-related components on the client machine.
Verify Profile Path
- Ensure that the profile path in the user’s properties is correct.
- Open Active Directory Users and Computers.
- Right-click the user > Properties > Profile tab.
- Check that the Profile Path is correctly specified (e.g., \\server\profiles\username).
Step 2: Check Folder Permissions
- Permissions on the Roaming Profile Folder:
- Ensure the user has Full Control permissions on the folder where the profile is stored.
- Navigate to the share folder on the server (e.g., \\server\profiles\username).
- Right-click the folder > Properties > Security tab.
- Make sure the user or the Domain Users group has Full Control.
- Check Share Permissions:
- Also, ensure the share permissions are correct.
- Right-click the folder > Properties > Sharing tab > Advanced Sharing > Permissions.
- Make sure the user or group has Read/Write access.
Step 3: Profile Folder Creation
Roaming profile folders should be created automatically the first time the user logs in, but sometimes the folder may fail to be created due to permission issues or a slow network connection.
- Try manually creating the profile folder on the server for the user, ensuring it has the correct permissions.
- Manually create a folder named username under \\server\profiles\.
- Set the same Full Control permissions as in Step 2.
Step 4: Check Network Connectivity
- Ensure there are no network-related issues preventing the client computer from connecting to the server where the profile is stored.
- Test the connection from the client machine to the server via ping or \server\profiles.
Step 5: Check Group Policy Settings
- There might be Group Policy settings preventing the profile from loading correctly. Specifically, check the following Group Policy settings:
- Computer Configuration > Administrative Templates > System > User Profiles.
- Ensure the following are not configured to prevent issues:
- Only allow local user profiles.
- Do not use the specified user profile path.
- Set roaming profile path for all users.
Step 6: Review Event Viewer Logs
- Check the Event Viewer for any relevant error messages related to user profiles.
- On the client machine, open Event Viewer (type eventvwr.msc in the Start menu).
- Navigate to Windows Logs > Application and Windows Logs > System.
- Look for any errors or warnings related to the profile loading process, especially under User Profile Service.
Step 7: Check for Antivirus or Security Software
- Sometimes, antivirus or security software on the client machine may block the creation or download of roaming profiles.
- Try disabling the antivirus temporarily (if safe to do so) and attempt to log in again.
- If successful, check the antivirus software's settings for profile-related restrictions.
Step 8: Test with a New User Profile
- To confirm whether the issue is related to the specific user profile:
- Create a test user in Active Directory with a roaming profile path.
- Log in on the client machine and see if the issue persists for the test user.
Step 9: Delete Profile Cache (if applicable)
- On the client machine, if the roaming profile is cached incorrectly, it could be causing issues.
- Go to System Properties > Advanced > User Profiles > Settings.
- Find the old user profile and delete the cached version, if applicable.
Step 10: Check the Profile Type
- Make sure you're not using a mandatory profile or have accidentally configured it incorrectly for the user.
- Ensure that the user profile is set up as a roaming profile, not a local or mandatory one.
- Ensure that the profile path in the user’s properties is correct.