Active Directory

Are those folders empty on all of your domain controllers or only one/some of them?

Since I think you posted on this earlier, regarding the "DR server didn't have sysvol and netlogon" probably the easiest thing to do is force demote and then re-promote.

yes, you are right, thank you very much for the support. Is there any other way to fix the issue.

yes, the issue with only on secondary domain controller which sysvol and netlogon folder not present, any way to reproduce. please help me. Thank You.

probably the easiest thing to do is force demote and then re-promote. is there a reason you don't want to do this? anything else is going to be difficult and will depend on whether you are using FRS or DFS/R.

Sure sir, Thank you very much for the support. I will do the same.

yes, the issue with only on secondary domain controller which sysvol and netlogon folder not present, any way to reproduce. please help me. Thank You.

Then it is not a DC yet. How long have you waited? Are all the required ports open? What DFS errors are you getting?

Already all ports are open and now the issue is that sysvol and netlogon folder not present, any way to reproduce.

What DFS errors are you getting?

Unless the exact same thing happens again

We are getting event id is 2213 sir, thank You

Did you follow the process in?
https://support.microsoft.com/en-us/help/2846759/dfsr-event-id-2213-in-windows-server-2008-r2-or-windows-server-2012

No sir, shall we run this , no impact right?. Please suggest. thank you

No sir, shall we run this , no impact right?. Please suggest. thank you

Always make/have a backup

The description of event 2213 contains a wmic command that's also shown in the article Shaun posted above. You can simply copy the command from the event description or the article into an elevated command prompt and run it. I've had to do this on many occasions for many customers, and it's never caused a problem. I have occasionally had to perform additional steps after running the command - if the database had been sitting in a dirty-shutdown state for a long time, for example - but that command is usually all that's required to resolve the issue. Check the DFSR event log for further events after running the command, and it should be pretty clear whether any additional steps will be required.

Sure, Thank you very much sir and All. I will do the same.

Please apologies me for the delay response. Thank You.