W2008 AD Upgrade Problem

I am looking to upgrade AD from W2008 SBS to W2012.
There are are 2 AD controllers - SBS2008 plus W2008 R2 at another site, permanently connected by a VPN.
I have run the command Dcdiag /v /c /d /e /s:DCName.
Part of the output says (note I have removed direct server and domain name references):

"      Starting test: VerifyEnterpriseReferences
       The following problems were found while verifying various important DN
       references.  Note, that  these problems can be reported because of
       latency in replication.  So follow up to resolve the following
       problems, only if the same problem is reported on all DCs for a given
       domain or if  the problem persists after replication has had
       reasonable time to replicate changes.
       [1] Problem: Missing Expected Value
            Base Object:
            CN="servername",OU=Domain Controllers,DC="domain name",DC=local
            Base Object Description: "DC Account Object"
            Value Object Attribute Name: msDFSR-ComputerReferenceBL
            Value Object Description: "SYSVOL FRS Member Object"
            Recommended Action: See Knowledge Base Article: Q312862
"
Now I believe this refers to missing FRS Objects and FRS attributes and I need the file "Topchk.cmd" to parse the output of "NtrfsUtl ds" command. It just isn't clear to me where I get "Topchk.cmd" from and why its access appears to be restricted?

Thanks for any help
ajmcqueenAsked:
Who is Participating?

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

x
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.

MaheshArchitectCommented:
You don't need to find "Topchk.cmd" mentioned in KB article in question

Just go to adsiedit and go to domain.com\system\File replication services\domain System volume and check server properties and all related attributes are correct
For Ex:ServerReference
You need to find out missing \ invalid attributes mentioned in KB article and need to correct them according to steps provided in KB article

Mahesh
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
While I think its a good idea to run the DCDIAG and diagnose whatever problems it comes up with, I've found that adding a Server 2012 DC to an existing domain is sometimes easier to do from the Server 2012 itself as the checks it does on the network provide fairly good feedback.

http://blogs.technet.com/b/askpfeplat/archive/2012/09/03/introducing-the-first-windows-server-2012-domain-controller.aspx

Once it gets added you can move the FSMO roles over to it and then be sure to fully uninstall Exchange from your SBS before demoting it so you don't leave any remnant Exchange objects in AD.

Jeff
0
ajmcqueenAuthor Commented:
Jeff

Actually, I have to migrate Exchange over to the 2012 Server - to Exchange 2013.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I don't suggest that you run Exchange 2013 on a DC.  While this is not "unsupported" it's definitely not recommended.  Exchange on an SBS was a different story because of the way the wizards configured multiple services at the same time in order to ensure things would run well and be secure.

Since you will have virtualization rights with the Server 2012, you can install a Hyper-V host and then two separate Server 2012's -- one being the DC and the other for Exchange.  Of course, be sure you have a server with enough resources to do this.

Follow this checklist to do the Exchange Migration:
http://technet.microsoft.com/en-us/library/ff805032(v=exchg.150).aspx

And still -- be sure to fully uninstall Exchange 2010 from your SBS before demoting it.  Otherwise you'll leave some nasty legacy stuff in your AD.

Jeff
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
0
ajmcqueenAuthor Commented:
OK. I was aware of the issue of not running Exchange on a DC. The plan is to put a copy of W2012 on the SBS server hardware to run as a DC. Obviously I will need a 3rd server as a temporary stand-in to run as a DC until the SBS has been wiped.
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
That is just another reason that doing it virtually is the way to go.
0

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.