After you install Active Directory on Windows Server 2008 R2, you may start seeing the following error message after the server boots :
The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically retry the operation. The return code is in the record data.
This occurs because the DFS Namespace service attempts to access Active Directory before it has completely initialized.
To resolve this issue, we simply have to force the DFS Namespace service to start after the Active Directory service has initialized. We can do this by setting the DFS Namespace service to depend on the Active Directory service as well as setting it to a Delayed Startup mode.
To make those changes, start regedit and make the following changes :
- Navigate to the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Dfs
- Modify the DependOnService value and add NTDS to the list.
- Create a new DWORD value named DelayedAutostart and set its value to 1.
Problem Solved. Cheers mate.
Thanks! Not too many resources out on R2 yet.
Great simple fix! Just installed this R2 datacenter server 2 days ago and started receiving the error, you were the first link I clicked about it. Performed the OP, rebooted, no error!
Keep up the great work.
Big Thx!
Just playing with my first server.
If there would be more simple ways like this out there it could be much easier!
Go on!
Thanks !!! Solved.
Great work
Thnaks.İt is workin perfectly.
Fixed my problem. Great post! Thank a lot!!
Excellent! it fixed the error seconds after the reboot and also fixed another problem related to DNS server. Incredible! congratulations and thanks a lot!!!
Fixed my DFS problem with Server 2008 R2
Thanks for the help!! fixed it in one reboot — awesome!
You have now fixed TWO of my problems with my Windows 2008 server. Thank you very much, jcarle!!
Thnak, in my case fix the message in Event Viewer 100Pts
I’m glad that this simple registry setting fixed the problem. Thanks for sharing this valuable info with us.
Fixed my system as well. If a user develops this type registry fix would Microsoft normally incorporate these registry changes in an update or SP? I hope they would. They must be seeing the same errors.
The problem solved. You are so kind. Thank you…
Fantastic!
Thanks for the help!
Yeah, it worked, no error anymore! Thanks a lot.
worked fine. . .
Thanks a lot, for this easy solution . . .!
Brillant, cheers.
Thank! Worked!
Thanks. Pity Microsoft don’t fix these annoyances themselves!
Thanks for the HELP…
Regards from Portugal
You’re awesome and still MS has no official update for this. can I send you a hooker.
you rock !!!!
Thanks
Great post.
It worked.