Issue after SBS 2000 to SBS 2003 Migration

[sandingdude]

We recently did a SBS 2000 to SBS 2003 Migration and we ran into some minor problems that need to be fixed but really don't know the next step in fixing them. Our office had 6 users on the SBS 2000 Server and they were all on roaming profiles. When we migrated to SBS 2003 (and we used all the documentation) we kept the roaming profiles and when turned on the new server and shut off the old server all the client machines where looking for the old server on certain directories related to the SBS 2000 server. Example when we log in a user which in on the SBS 2003 and romain profiles it will say "cannot locate \\oldserver\john\desktop" and the network runs a little slow. So we hooked up the old server on the netwokr again and we don't get the error and the network runs fast. When we searched the registries on all these systems we noticed there were still instances of the old server. Is there any way to fix this problem? Will going to each registry and changing the path work? Thank you for your help in advance.

 

[markdmac]

Lots of variable here. Did you use the web page to connect the computers

http://server/connectcomputer?

Did you use ADMT to migrate your users? Why did you change the server name?

The short answer to you would be "probably." All will probably be OK if you search the registry and replace the server names, but htat is dependent on all resources being in the same location.

When I do migrations like this, I cpy the user profile to a local user and use the connectcomputer wizard to have it migrate the profile for me. We also use the same server name to avoid any confusion.

I hope you find this post helpful.

Regards,

Mark