SHIFT

--- Sjoerd Hooft's InFormation Technology ---

User Tools

Site Tools


Sidebar

Sponsor:

Would you like to sponsor this site?
Or buy me a beer?:


Recently Changed Pages:

View All Pages
View All Q Pages


View All Tags


Sign up for Q to post comments.





WIKI Disclaimer: As with most other things on the Internet, the content on this wiki is not supported. It was contributed by me and is published “as is”. It has worked for me, and might work for you.
Also note that any view or statement expressed anywhere on this site are strictly mine and not the opinions or views of my employer.


Terms And Conditions for Q users


Pages with comments

PageDateDiscussionTags
2019/05/01 14:08 2 Comments
2019/03/15 16:02 1 Comment
2019/03/15 16:02 1 Comment
2019/03/15 16:02 3 Comments
2017/04/20 15:28 1 Comment
2017/04/20 15:23 1 Comment
2017/04/19 14:44 1 Comment
2017/04/17 20:10 1 Comment
2017/04/17 20:07 1 Comment
2017/04/17 19:58 1 Comment
2017/04/17 19:52 1 Comment

View All Comments

dnseventid4013

Fix: DNS Event ID 4013

When working with isolated environments, for example Test Environment Setup and Site Recovery Manager testing, we ran into problems (sometimes) with DNS. We found that with isolated environments DNS sometimes is waiting for AD sync to complete. According to this MS kb article you can disable that by creating the following registry key on the DC/DNS server:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
 Value name:  Repl Perform Initial Synchronizations
 Value type:  REG_DWORD
 Value data: 0
Note: This configuration change is not recommended for use in production environments or in any environment on an ongoing basis!

After this I restarted the Active Directory Domain Services and everything works.

Note that you might also need to AD DC Role Seizing
You could leave a comment if you were logged in.
dnseventid4013.txt · Last modified: 2014/12/09 12:45 by sjoerd