Roaming Profile Issues after 2003 to 2012 Migration

Recently we migrated a client's Server 2003 domain controller to Server 2012 R2. That migration included roaming user profiles. The profiles were copied from the 2003 machine to the 2012 machine using Microsoft SyncToy. Subsequently, we used AD to map the user accounts to the profiles on the 2012 server.

Here's the roaming profile environment:
User profiles are mapped to \\SERVER\profiles$\%USERNAME%
User Home Folders connect X: to \\SERVER\Userdata$\%USERNAME%
Using Group Policy, the Desktop, Documents, Pictures, Music, and Videos folders are redirected to \\SERVER\Userdata$\%USERNAME%\

I'm only assuming that these issue are related to roaming profiles, but here are the symptoms (Windows 7):
Internet Explorer (11) takes 20-30 seconds to open. Opening new tabs in IE takes as long. Otherwise, IE functions normally.
The Services.msc console (and I assume other MSC consoles) takes 20-30 seconds to open
Searching from the Start menu takes a very long time

We're really pulling our hair out trying to figure out these issues. Any help is greatly appreciated. I can provide any additional info you need.
James ParsonsAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Robin CMSenior Security and Infrastructure EngineerCommented:
Check the path variable (system and per user) to make sure it isn't referencing anything that doesn't exist.

You could also check out my blog post where I had similar issues, and tracked them down via Process Monitor.
Ganesamoorthy STech LeadCommented:
Is user location and the profile server location are different? is any network latency, check below link

James ParsonsAuthor Commented:
Though we haven't discovered the exact reason, the issue was most certainly related to DNS. We created a DNS A record for OLDSERVER pointing to the new server's IP, and all symptoms previously mentioned were instantly resolved.
James ParsonsAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for James Parsons's comment #a40916495

for the following reason:

Robin CMSenior Security and Infrastructure EngineerCommented:
So exactly as I suggested, you have a reference to the old server somewhere (probably registry) on the clients or in the profiles. Your DNS A record just means that when the clients try and connect to the old server, they're being pointed at the new server. That's a workaround not a resolution, but if you're happy with it I suppose that is good. But I can almost guarantee it isn't a DNS issue, you've just used DNS as your workaround to make the old server "look" like it is still available, rather than having to wait for the timeout.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.