Errors when loading roaming profile at remote site
I have been trying to implement roaming profiles but have not been 100% successful. This is my following setup: I have two sites, SiteA and SiteB using DFS to replicate the roaming profile share. The profile share is created in a namespace path \\domain\profiles\%usernam
When I create the initial profile, everything writes to the share fine. I can continue to log in and out throughout SiteA with no issues. Then at night, the share replicates to SiteB. The next day when I login to a machine at SiteB, I get some errors.
The first error I get is "Windows cannot copy file \\domain\profiles\%usernam
Detail - The specified network name is no longer available.
The second error says Windows cannot find the local profile and is loggin you on with a temporary profile...
The second error is expected so thats not a big deal. The main issue is with the first error. When I try to locate the specfic cookie it is trying to copy from the namespace share at both sites, it does not exist which is why I got the Detailed error of "The specified network name is no longer available." My question is, what is instructing the profile to copy that cookie when it doesn't even exist. As I continue to log on and off, I get the same error but for different cookies. I also got cannot copy NTuser.dat file a few times.
In theory, if DFS is replicating the share, why is it not loading at a different site. I will try to exclude cookies in the roaming profile to see if that will make a difference. Please HELP!!!!!!!!!!
When I create the initial profile, everything writes to the share fine. I can continue to log in and out throughout SiteA with no issues. Then at night, the share replicates to SiteB. The next day when I login to a machine at SiteB, I get some errors.
The first error I get is "Windows cannot copy file \\domain\profiles\%usernam
Detail - The specified network name is no longer available.
The second error says Windows cannot find the local profile and is loggin you on with a temporary profile...
The second error is expected so thats not a big deal. The main issue is with the first error. When I try to locate the specfic cookie it is trying to copy from the namespace share at both sites, it does not exist which is why I got the Detailed error of "The specified network name is no longer available." My question is, what is instructing the profile to copy that cookie when it doesn't even exist. As I continue to log on and off, I get the same error but for different cookies. I also got cannot copy NTuser.dat file a few times.
In theory, if DFS is replicating the share, why is it not loading at a different site. I will try to exclude cookies in the roaming profile to see if that will make a difference. Please HELP!!!!!!!!!!
Don S.
Make sure administrator and system have full permissions to every folder and file in all the profiles otherwise replication won't get everything.
When you look at the size of the profiles location is it the same at site a and b? Are permission set correctly on both shares? Also have you turned off off line file caching on the share?
ASKER
Dons6718: I have Domain Admins, Group Roaming (my roaming users are in this group) with full control. I will add System with full control to see how that goes.
bhnmi: The size of the profiles are the exact same at both sites. Permissions were ok but I did not include SYSTEM. Offline caching is off on the share.
bhnmi: The size of the profiles are the exact same at both sites. Permissions were ok but I did not include SYSTEM. Offline caching is off on the share.
You can also run a report with the GPO management tools and see what errors come up when processing the users profile on that machine.
ASKER
bhnmi, when I run the reports, everything appears to be applied correctly. The only place I see errors are in Policy Events for userenv errors which I stated above.
Domain Admins may not be what you really want. It probably should be Administrators. It's generally not the best idea to have domain admins own anything or have explicit permissions. Generally you should use the fact that Domain Admins includes Administrators and have administrators be the owner or the one to have explicit permissions.
At the remote location check the effective permissions of the user, make sure they have full control of all folders within the profile structure.
ASKER
bhnmi, the user has full control of the profile structure. The user is part of Group_Roaming and I assigned Group_Roaming full control to those folders.
I have added "administrator" instead of Domain_Admins to see if that makes a difference.
I have added "administrator" instead of Domain_Admins to see if that makes a difference.
I wouldn't really suggest having temp internet files being replicated from one server to the next anyway, to be honest. If you are using IE, then just set up a GPO for the roaming users to delete temp internet files when closing IE.
ASKER
I don't think it is a permissions issue with the user. If the user can read and write from the share in SiteA, it would make sense it work work at SiteB
ASKER
t taylor, the Temp internet files are not being replicated. By deafult roaming profiles do not include Local Settings which has temp internet files in that directory. Please correct me if I'm wrong.
Or if not using IE, I suppose you could just create a bat script to run on logout to delete the files in temp.
It really depends on if any config has been done to change temp location. What directory is the cookie in that it is failing to find?
ASKER
the Cookies are under \\domain\profiles\%usernam
I would test with a bat to delete files in that directory then. Just create a logout script.
usually coockies ARE a part of your roaming profile along with desktop, apps and favorites.
ASKER
Ok, I have diabled cookies from roaming and I am not getting an error for an .exe file I have on the Desktop. The error I'm getting now is
Windows cannot copy file \\tci.corp\profiles\roamin
DETAIL - The specified network name is no longer available.
I'm thinking there is a problem with keeping the connection up from the server. Are there any tests I could perform?
Windows cannot copy file \\tci.corp\profiles\roamin
DETAIL - The specified network name is no longer available.
I'm thinking there is a problem with keeping the connection up from the server. Are there any tests I could perform?
Well, if it is the exact same file each time, I wouldn't think that it would be a connection issue. If you want, create a test user and set up a profile for him on site b. When you roam to site a, see if you have issues or not.
Have you set a GPO to delete local cached profiles on logout? If it is a connection issue, it may serve you to be moving as few files as possible when you roam.
Have you set a GPO to delete local cached profiles on logout? If it is a connection issue, it may serve you to be moving as few files as possible when you roam.
ASKER
t taylor, it isn't the exact file each time. In fact, its a different file each time. I also have disabled cookies from roaming. I followed your suggestion by creating a user profile in siteB and logging in to siteA and it works fine.
I do not have a GPO to delete local cached profiles on logout.
With the first test profile I was using, it seems as if connection goes down and causes a file to not copy completely which then causes the profile not to load. Any suggestions?
I do not have a GPO to delete local cached profiles on logout.
With the first test profile I was using, it seems as if connection goes down and causes a file to not copy completely which then causes the profile not to load. Any suggestions?
That is actually pretty strange that it works one way and doesn't work the other... Are you having any other connectivity issues to the server on site A or other general weirdness with it? What roles does it have installed?
ASKER
No, the server on siteA is a file and print server. I other issues with server on siteA. I have noticed issues with server on siteB (just a file server). I have an applicance which replicates patches and managed installations to the server on siteB just fine. When users from siteB connect to the server on siteB to download patches and managed installs, it sometime errors out and redirects back to the source (siteA) over the WAN.
When I RDP into a workstation in siteB and copy a 60Mb file from the server (siteB), it takes longer than a usual 60Mb transfer. I think somethings up with the server.
When I RDP into a workstation in siteB and copy a 60Mb file from the server (siteB), it takes longer than a usual 60Mb transfer. I think somethings up with the server.
ASKER
Ok, I think I'm on to something. I think the profile errors out becuase I am not allowing the files to fully replicate. I noticed that the files take some time to stage and they actually replicate. Larger files would take longer than smaller ones. So when the registry looks for a file that has not been fully replicated, it errors out. Is this a possibility?
How long are you giving it to replicate?
ASKER
We'll during the testing, not too long, but I had let it replicate last night so I will see if I can login successfully this afternoon.
ASKER
Ok, it looks like everything works ok now. I logged into the switch a noticed lots of collisions where all the other ports had none so I moved the port and its ok now.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.