W2008 R2 DC not create Sysvol shares after dcpromo

[guest]

We are replacing W2003 DC's (two DC's) in an AD. One W2008 R2 DC running in Hyper-V cluster has previously been installed OK, also Exchange 2010 with its schema changes are in place. One W2003 DC has already been depromoted.

When installing the second DC, no Sysvol shares appear. Here are the foundations this far:

- Single-label AD domain
- In Site1, one W2003 DC, DC01
- In Site2, the first W2008 R2 DC03
- Newly installed server HW (DC04) in Site1, W2008 R2 Std, it will replace the old W2003 DC
- During Dcpromo, the "Examining DNS Configuration..." prompt takes about 5 minutes
to pass, and then the following warning text appeared:
"DNS server role is already installed on this server. However, the DNS server
will not be configured because no existing domain controllers in this domain
are authoritative DNS servers for the domain. Domain name resolution for this
domain is provided by DNS servers outside the domain."
Because no server reboots did not help, we completed the Dcpromo despite of the warning
- After dcpromo reboot, all DNS entries, including those under _msdcs folder appear OK in DC04

However, no sysvol nor netlogon share appear.

In Eventlog: the following warnings appear under NTFRS:
- File Replication Service is initializing the system volume with data from another domain controller.
Computer AUTODC04 cannot become a domain controller until this process is complete.
The system volume will then be shared as SYSVOL.
- The File Replication Service has detected an enabled disk write cache on the drive
containing the directory c:\windows\ntfrs\jet on the computer AUTODC04.
The File Replication Service might not recover when power to the drive
is interrupted and critical updates are lost.

No other meaningful warnings or errors seemed to me, at least when fixing the accdenied registry error
as in article http://www.jcarle.com/2009/09/06/fixing ... y-service/
There is DHCP server in DC04.

The "repadmin.exe /showrepl dc01 (or dc03) /verbose /all /intersite" command seems clean,

The "ntfrsutl ds dc04" command run from dc04 results in
ERROR - Cannot RPC to computer, dc04; 00001f47 (8007)

The "ntfrsutl ds dc01" command run from dc04 results in
DC01 IS NOT A MEMBER OF ANY SET!

The "ntfrsutl ds dc03" command run from dc04 seems clean to me.

What should be done to get the new DC04 with sysvol shares?

[guest]

Personally, I would look to migrate this forest to a non-single labeled domain. These things are nothing but a pain. Link below should be checked over to verify your environement.

http://support.microsoft.com/kb/300684

Next I would run diagnostics to see what else might be wrong:

http://blogs.dirteam.com/blogs/paulberg ... ssues.aspx

Can't find a valid rep partner (DNS issues do to single label?)

http://support.microsoft.com/kb/316790

Consider disabling write cache

http://support.microsoft.com/kb/316504

13553 - Just informational

My guess is you have dns issues related to your single label domain and a rep partner can't be found do the this issue.



--
Paul Bergson
MVP - Directory Services
MCITP: Enterprise Administrator
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, Vista, 2003, 2000 (Early Achiever), NT4
http://www.pbbergs.com Twitter @pbbergs

[guest]

As summary, the resolution was as follows:

On the new W2008R2 server, we ran the dcpromo with Advanced checkbox enabled and forced the new (W2008 R2 in another AD site) DC as initial replication partner. Also, during dcpromo, ignored the warning
"DNS server ... will not be configured because no existing domain controllers in this domain
are authoritative DNS servers for the domain. Domain name resolution for this
domain is provided by DNS servers outside the domain."

After the above, the shares created OK. So the DC01 (only W2003 DC) did not work as initial replication partner, but the new W2008R2 DC in another site did.

Remaining problem: the old DC01 was the only DC that held the correct sysvol policy subfolders. As result, GPMC in new DC's result in error messages when viewing some GPO's.
Workaround: after unpromoting the old DC01 we restored the failing GPO's to new DC with GPMC console. (first of course we had taken backup of every GPO with GPMC in DC01, before unpromo).