ajmcqueen
asked on
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
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
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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
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
FYI, this is also a good series of articles that may help you do the move:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part1.html
http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part1.html
ASKER
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Actually, I have to migrate Exchange over to the 2012 Server - to Exchange 2013.