Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 304
  • Last Modified:

Profiles from new server attempting to load from old server

I recently installed a 2008 server, in which I set up a new forest/domain and copied the profiles over to the new server.  After setting up all the permissions and re-directs (even through GP), when logging on to the workstation, the profile tries to load from the old server.  If I go into regedit, I can do a search for the oldserver\oldprofile folder and manually change the entries to the new server, log off and log back on just fine.  I tried re-installing the operating system on the workstation to clear the registry of knowing the old server, but it did not help.  Is there another way around then having to go through each user and change the registry entries?  

I should add that this did not happen on all computers.  Also, all users are in the same OU, and running gpresult on the computers where this is happening, shows the new server providing the GP's.  
0
Technical_Specialist
Asked:
Technical_Specialist
  • 5
  • 5
1 Solution
 
arnoldCommented:
Double check that the user account in the AD is referencing the new location for the profile share. Folder redirection is controlled through GPO, user profiles are configured in AD.

You can select and change multiple users at the same time, but make sure to use %username% variable
\\someserver\profile\%username%

Alternatively, setting this as a DFS share (domain based share) will save you time should you need to once again add/shift where the profiles are stored.
0
 
Technical_SpecialistAuthor Commented:
It is referencing the new location of the profile share.  The correct location is referenced in both AD and through GPO.    Also, II am not using DFS.  
0
 
arnoldCommented:
Does your GPO require that the roaming profiles be deleted?
If the roaming profiles remain on the system, they refer to their original location.
Isn't the registry entry in the HKCU?
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Technical_SpecialistAuthor Commented:
No it does not require they be deleted.  The GPO's ,I left pretty widely open at this point because of the troubles of cleaning up the last IT's dirty work.    I had deleted the users/profiles off the local workstation.  If the users are added to the Power Users group, they can log in and get their profile, but cannot set a default printer, open adobe documents, and many other things.  When I go into the registry, the user is not listed under the HKCU, let alone having full control over it.  When I went through and deleted the user off the workstation once again, and added them to the administrator group, at that point they get the error message that it cannot load their profile from \\oldserver\oldprofile\ect...  At this point, under the login, I can go into the registry and so a search for 'oldserver' or '\\oldserver\oldprofile' and change the needed values to the newserver\newprofile, log the user out and log back in and everything 'seems' to work just fine.  But the next user I log on to the computer (there are about 10 users that go between 3 computers in one office), I have to do the exact same thing.
0
 
arnoldCommented:
If you leave roaming profiles on the systems this might explain why they keep referring to old ones.  
The whole idea behind roaming profiles is that there is no space wasted on the workstations when the user logs out.

The other possibility is that the profile does not cleanly unload on logoff.
http://www.microsoft.com/downloadS/details.aspx?familyid=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en
The above is a tool for OS's up to but not including vista/win2k8 that runs as a service helping the logoff process to release stuck processes/registry locks.

Could you try creating a new GPO that will direct that roaming profile caches be deleted?  Apply this GPO to one workstation and see whether after the GPO is applied and all domain users are removed, the issue remains.

Another thought, how many DC's do you have. they might be out of sync. i.e. one has the old server referenced.

run gpresult /v | more for the user

0
 
Technical_SpecialistAuthor Commented:
The server is running win2k8, so not sure that tool will help.  There is only one DC.  After I go through the registry and make the changes for one user on one computer, I don't have to re-do it again.  Wouldn't clearing the caches take this away?
I haven't tried the /v |more for gpresult, but just the command itself shows all the correct settings.  It's like it is something within the profile itself that was holding onto the old server.  When I had logged in as Administrator after clearing the profiles, I went through the registry and noted/changed any values that referenced the oldserver, but then when the profile logged on, it updated the registry to include it.
0
 
arnoldCommented:
Try the GP option on one work station.
I believe that once you change the registry entry for a user and they successfully logout, their profile ntuser.dat is what contains this information.

Where is the prior DC?
Did you go through the steps of adding the new server as another DC in a domain?  Did you transfer all the roles from the old system to the new system?
It seems that you may not have completed the process.
0
 
Technical_SpecialistAuthor Commented:
After the first time of transfering all the roles and trying to have the two DC's in the domain; I had a problem with the GP's not coming from the new server at all.  They would only see the old one and even when going into the sysvol to check the policies, they're were not in sync with AD.  It was a huge mess.  There was so many problems with AD and the server as a whole when I took over, that when installing a new server came into play, I felt it was just going to be easier to start anew, yet took the advice of a colleague that was the IT previously (a couple people in between us) and merely tried to do the apparently easy way.  After a couple weeks of continued issues, I actually ended up setting up a whole new forest, and created active directory from scratch.  I had copied the profiles over to a newly named directory and stopped all AD, DNS, DHCP, ect. services on the oldserver.  I haven't demoted it yet though and taken it completely offline as I've been trying to figure this profile issue out and it still supplies the email for the clients.  
I will try the GP option when I go in this evening.  With it, no part of the profile will be cached on the workstation?   Although I would like the issue at hand resolved, I feel it is good to have the user's profile also on the workstation as a backup option in case of server down/offilne, that the clients would still be able to access their files in a way.  I have it set up as roaming because of the fact the users sometimes work on computer in the morning, then another in the afternoon and wanted them to be able to keep their settings following them.  
Thanks for all your help so far in trying to figure this out.
0
 
arnoldCommented:
When you setup the new forset, did you use ADMT to transfer the users/computers from the old system?
Are you using the same AD domain name as the old one did?
As long as the OLD server is running, it may assert itself.
Run "systeminfo" on one of the workstations and look at the information dealing with logon server.  Does it reflect the new or the old server?
Double check which DNS servers are reflected for the workstations, new or old server IP.
ipconfig /all | more

If old server is down and the workstation is trying to connect to it, it will use cached credentials to login if the server is unavailable.
0
 
Technical_SpecialistAuthor Commented:
I think I messed up not using ADMT!   Not sure if it will bite me more in the a$$ in the future, but I ended up just going through the registry for the users having this problem and manually switching over to the right paths.  
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now