SBS2003 to Windows 2008R2 migration

I recently added 4 new servers including a new domain controller to our network.  On the new domain controller I did the ntdsutil command to transfer the fsmo roles, but somehow that isn't working right.  The new domain controller is acting up, and when i shut down the previous role holder (the sbs2003 server) ((note:  i did not demote it, in case something went wrong and i needed it back)) things went haywire.  the network only seems to work if it is up and running.  I have created other domain contorollers in the lan and made them GC's.  Could this be caused because i didn't demote the sbs box?  What is the downside to doing that?  As a  side issue which i believe is related my system clocks keep going haywire and areoff by 7 minutes.  All desktops get this but only about half the servers.  The new DC has a bad time setting but the old sbs has the right time.
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.

did you ran first the in your sbs schema master
these commands
adprep /forestprep
adprep /domainprep
oncall4youAuthor Commented:
yes I had to before I could do the dcpromo on the 2008 r2 box

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
oncall4youAuthor Commented:
I just ran the ntdsutil to view the list and all 5 current masters are held by the new domain controller.  
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

try this command in the new dc
c:\net time
and see from where it geting the timeing

and then go to your old dc and time the same command and see from where you get the timing

maybe you have problem with w32time service
based on my experience if you havemore than 5 minutes difference between the dc you will get problem
make manually the time and set the same time on the server and then see

also check from where the both getting the time
oncall4youAuthor Commented:
The time coming from the host server (the dc is virtual) and I reset the time.  Is there any issue with demoting the sbs server?
U should be sure that the 5 rules moved to the 2008 server, and don't demote the sbs2003 now, just turn it off for few days, if everything went smoothly then u can demote it.
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.