Roming Profiles not working in 2003 Domain with Win 7 Pro
Testing out Windows 7 Pro in our 2003 Domain. When an existing domain user with a roaming profile logs on to the Windows 7 box they get a pop up saying the profile couldn't be loaded and a temporary profile will be used. Event log shows error 1521 with access denied. Checked permissions on the profile directory and the users have full control. Created a new user from scratch and logged on to the Windows 7 machine and recieved the same error messages, plus the user profile folder doesn't get created on the server.Any ideas welcome, I'm pulling my hair out.
October 15th, 2009 6:53pm

Hi, This issue can occur if the local user profile is corrupted or the network setting is incorrect. You can refer to the following steps to troubleshoot the issue. Step 1: Delete a user account in Windows 7 ========================= 1. Restart the computer to Safe Mode and logon to the Administrator account. 2. Copy anything you do not want to lose from the C:\Users\(user name) folders for the problematic account and save it to another partition. 3. Open the Control Panel and click "User Accounts" 4. Click "Manage another account" and click the problematic account. 5. Click "Delete the account" and click "Delete Files" button, and then select "Delete Account" button. Then, the problematic account will be removed. Please proceed to step 2. Step 2: Delete the User Account Profile ========================= 1. Click Start Menu and type Regedit in the open box, and then press Enter. If prompted, click on Yes in the UAC prompt. 2. In the Registry Editor, on the left pane, navigate to the following key by expanding the plus sign (+): HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList 3. There will be several long SIDs in the left panel, select one of them and look at the right panel. There will be a ProfileImagePath key. 4. Double click ProfileImagePath key and see if the value data is the same as problematic user account that you deleted in step 1 above. If not, please click another long SIDs until you locate the same one and move on the next steps. 5. Right click on the SID key, and click on Export. 6. Type in a name and save the REG file to a safe location. NOTE: This is a backup. To Restore the Backup, please double click on the REG backup file. 7. Right click on the SID key and then click delete. 8. Restart the computer to Normal Mode. Step 3: Create a new user account and restore the saved user files ========================= 1. Open the Control Panel and click "User Accounts" 2. Click "Manage another account" and create a new account. 3. Type a user name and select "Administrator" option, and then click "Create Account" button. 4. Copy all saved user files to the C:\Users\(user name) folder. For more information to create new account and transfer data, please refer to the link below: How to copy data from a corrupted user profile to a new profile However, if the issue still persists, please perform the suggestions from the link below to re-create a roaming profile. Configuring Roaming User Profiles How to Create and Copy Roaming User Profiles in Windows XP Thanks, Novak
Free Windows Admin Tool Kit Click here and download it now
October 16th, 2009 10:57am

Thanks for the reply Novak. No local user folders are being created. When any user with a roaming profile log on to the Windows 7 system, it forces them to a temporary local profile. The profiles for these accounts all behave as expected on Windows XP computers joined to the domain so I know the profiles aren't corrupted, we only experience the issue on a Windows 7 machine. I've since confirmed that it happens with 100% of users that have roaming profiles.Any other ideas would be appreciated.Thanks,Scott
October 16th, 2009 8:06pm

After doing further research, the issue can also occur by following causes: 1. This problem may occur if you use NetBIOS over TCP/IP (NetBT) to connect to your network, and you have a roaming user profile. 2. This issue may occur if your roaming profile or home folder is located on a computer that has ICF turned on. 3. The user may not have necessary permissions to the user profile/ 4. The workstation may have different time against the DC. You can try the following steps for a test. 1. Make sure you have correct DNS settings and the workstation can access the computer where is roaming profile located. 2. Disable ICF on the computer that stores the user profile. 3. Move the user's roaming profile or home folder to a computer that has ICF disabled. 4. Check the user permissions to the user profile on the DC side. 5. Make sure the workstation has correct time synchronized with the Domain Controller. Thanks, Novak
Free Windows Admin Tool Kit Click here and download it now
October 20th, 2009 11:08am

Thanks again Novak. The profiles are located on a DC, so ICF is not enabled. The users have full control of their profile directory, the time for the workstation is received from the DC and the 2 are in sync, the workstation is properly resolving DNS.Is it possible this will not work without a Server 2008 R2 DC? The domain is currently at a 2003 functional level.Thanks,Scott
October 22nd, 2009 8:30pm

Hi,The roaming profile can work without the Server 2008 R2 DC. At this stage, I suggest you perform the suggestions from the link below:Temporary ProfileIf the issue persists, please upload the following information to Skydrive (www.skydrive.live.com) and share the link to me. 1. Registry key: HKLM\SOFTWARE\MICROSOFT\WINDOWS NT\CURRENTVERSION\PROFILELIST 2. Application and System Logs. Thanks,Novak
Free Windows Admin Tool Kit Click here and download it now
October 23rd, 2009 9:32am

Have you found a resolution to your issue. I am having the exact same issue with Win 7 and a Windows SBS (NOT R2) fully patched server and roaming profiles. Greppling for ideas. Have not managed the domain on a win 7 machine. Maybe it's group policy. Wonder if AdPred from 2k8 r2 would yield dividends.Groping at straws
January 14th, 2010 10:34pm

Hi all, i got the same issue and already found the problem. when we create roaming profile path, for example \\servername\usertest actually in windows 7 professional in windows registry roaming profile path location will create "\\servername\usertest.V2" so in that "servername" you need to create share folder named "usertest.V2" with aproviate access security. after that just try to login again in your Windows 7 Professional PC. hope this solution solved your problem. cheer
Free Windows Admin Tool Kit Click here and download it now
December 8th, 2010 3:02am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics