journal wrap error in sbs 2008

I have a sbs2008 server that keeps giving event ID 13568 every time I reboot. I tried to push a group policy recently, but was unsuccessful, it was a software installer. I looked up several articles regarding this and I am getting conflicting messages. One is telling me to do this:
Click down the key path:
Double click on the value name
   “Enable Journal Wrap Automatic Restore”
and update the value. - See more at:

But then I read an article where that will cause issues with not being able to login because the sysvol disappears,

then I read an article that suggested I do a non-authoritive restore (D2) which would be the correct method...
But that confuses me as well. How can you do a non authoritative restore with no other DC on the network??
1. Click Start, and then click Run.
2. In the Open box, type cmd and then press ENTER.
3. In the Command box, type net stop ntfrs.

(make a backup copy of the contents of the Pre-existing folder if it exists, then copy those to the parent folder)
4. Click Start, and then click Run.
5. In the Open box, type regedit and then press ENTER.
6. Locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\NtFrs\Parameters\Backup/Restore\Process at Startup
7. In the right pane, double-click BurFlags.
8. In the Edit DWORD Value dialog box, type D2 and then click OK.
9. Quit Registry Editor, and then switch to the Command box.
10. In the Command box, type net start ntfrs.
11. Quit the Command box.

Within a minute or two, you should see event ID 13516 post in the event viewer:
see the link below...
Another post says to do a D4
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.

Neeraj KumarSystem adminCommented:

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
williamstechnologygroupAuthor Commented:
Thank you, I think that did the trick. I have been doing this for a long time, but I always get nervous messing with AD and the Sysvol. I did run the best practice analyzer and it did not show the error. I am assuming it will not show up in the event viewer on the next reboot as well.....
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

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.