Problems adding new server. FRS getting errors

So we are in the process of replacing a SBS 2008 with a new server 2012 Standard R2. I added the new server and promoted it to domain controller but say that SYSVOL and NETLOGON shares were not being created. Started troubleshooting and found this error on the source server:

The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Aside from the new server that I am adding the current server is the only server in this domain. Any articles I found to fix this error seem to indicate that there should be other domain controllers on the network for it to replicate from.

Any help on getting this resolved would be greatly appreciated.
WiddleAviAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Radhakrishnan RSenior Technical LeadCommented:
Hi,

Is FRS and DFS both enabled on both servers? try to disable either one (FRS) and see it makes any difference.

Is the JounalWrap errors appeared  prior to adding the new DC? if so, the best solution would be finding out best copy of SYSVOL from previous backup and restore (alternate location) and replace.

Cheers
RK
0
NinjaStyle82Systems AdministratorCommented:
FRS is deprecated in Server 2012 so if FRS is what your original DC is using you will want to migrate to DFSR. See: https://technet.microsoft.com/en-us/library/dd639809(v=ws.10).aspx
0
WiddleAviAuthor Commented:
RK -  don't know if there were errors previously. This is a new customer and the event log does not go back that far. How can I know if the SYSVOL folder in a backup is healthy ?


Frank - I started going through that. It seems to be getting stuck with the new server changing to migration state prepared. It is stuck in the Start state. Not sure how long it is supposed to take to change to prepared but it's been a while.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

WiddleAviAuthor Commented:
RK - One more thing. FRS is disabled on the new Server 2012.
0
NinjaStyle82Systems AdministratorCommented:
It usually goes really quick. Are you running it on the 2008 server? Maybe that'll help. I think once you get it migrated you'll be all set.
0
piyushranusriSystem Cloud SpecialistCommented:
Requirement for FRS from Root Domain To Site Domain.

1.  Replication should work proper.
          a) replication port
          b) sysvol and netlogon folder shared( if not then manually do it)
2. Restart DFS service on Site Domain Controller
3. You will get some event ID on site domain controller, with passed and failed event id.
4. wait for some time to see the replication passed event id.


please share your finding and event ID..so troubleshoot and suggest the next steps.
0
ZenVenkyArchitectCommented:
If you are not formatted SBS 2008 server then, take SYSVOL data from it and copy it on 2012. Once it is done perform Authoritative restore (D4) using this article.

 https://support.microsoft.com/en-us/kb/2218556
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
piyushranusriSystem Cloud SpecialistCommented:
@WiddleAvi
this issue is solved or still you are looking ...
0
WiddleAviAuthor Commented:
zenvensky - got me going in the right direction. I ended up setting the old server as D4 restore and new server as D2 and that worked great.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.