SBS 2003 to Server 2008 Migration

We have a company who hired an IT guy for a corporate environment to replace their aging SBS 2003 server.  He migrated the server over to Server 2008.  The company states it took him over 30 hours to do this.  Looks like he migrated over AD, files ok as the new computers can now log into that server.
But they are now experiencing even worse issues then with the old server.  Before they would have to constantly have to reboot the old server because computers would lose their connections, lose drive mappings, lose connection to line of business application, etc.
It seems the only quick fix would be a reboot.

Now the new server is having random issues.  They are having to reboot randomly like every other day, twice a week.  Sometimes computers will log off randomly on their own.  I looked in event viewer and it there are alot of group policy errors.

Could the migration have been done wrong or something?

Would like to get some feedback on what to start on or where to begin.

Thanks in advance.
Who is Participating?
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.

SandeshdubeySenior Server EngineerCommented:
To start with you need first verify the health of exiting DCs run dcdiag /q and repadmin replsum and post the log if error is reported.

Ensure correct dns setting on DCs and client as below.

Best practices for DNS client settings on DC and domain members.

How many days have passed for this migration?

Is the SBS server in domain and still holding the FSMO role?
Lee W, MVPTechnology and Business Process AdvisorCommented:
It sounds like you think 30 hours is a long time.  Might be.  For two users.  For 20, it's not bad.  Most migrations by when you factor in everything that needs to be done will take 20-40 hours to do them properly.  And of course it depends on the company, how they were setup before and the applications they use.

As for what's happening now, could be server issues, could be network switch issues, could ID10T errors.  Tough to say.  You would need examine the log files and try to determine why these things are happening.  Could even be the antivirus software causing issues.  Have to ask, what was done to both systems to cause them to be unstable?  (Yes, you're asking that, but you are in front of them - think about what's in common - are they on the same hardware?)

I think you might have wanted someone to just know what was wrong based on a few symptoms, but your symptoms are very generic and without seeing the network, DNS setup, network switches, event logs, user behavior, giving something specific like that would be a guess.  People can get lucky with guesses, but that doesn't happen often.

Start by examining the event logs of server and a workstation or few.

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
Windows Server 2008

From novice to tech pro — start learning today.