DFS Replication issue Server 2012 R2

We run a single DC domain, but for the last few weeks we have been getting this error:

Log Name:      DFS Replication
Source:        DFSR
Date:          2015-10-20 09:03:20 AM
Event ID:      4012
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      dc01.domain.za
The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 111 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected.
To resume replication of this folder, use the DFS Management snap-in to remove this server from the replication group, and then add it back to the group. This causes the server to perform an initial synchronization task, which replaces the stale data with fresh data from other members of the replication group.
Additional Information:
Error: 9061 (The replicated folder has been offline for too long.)
Replicated Folder Name: SYSVOL Share
Replicated Folder ID: D63839C2-FA50-43C2-93E3-23AC87296296
Replication Group Name: Domain System Volume
Replication Group ID: 47FB958A-E93C-4740-9CA7-E63E0E86AC9B
Member ID: 081FF782-1C9C-4DCE-AC36-243FE36CBB09
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <Provider Name="DFSR" />
    <EventID Qualifiers="49152">4012</EventID>
    <TimeCreated SystemTime="2015-10-20T07:03:20.000000000Z" />
    <Channel>DFS Replication</Channel>
    <Security />
    <Data>The replicated folder has been offline for too long.</Data>
    <Data>SYSVOL Share</Data>
    <Data>Domain System Volume</Data>

I checked in the DFS Management snap-in and found that there is a replication group for the Domain System Volume for contains our DC and server that has NEVER been on our network.
Not sure how this can happen but never in the history of the company has there been a second DC.

How can I go about removing this replication, if serves no purpose and shouldn't be there int he first place.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

DJMohrAuthor Commented:
I managed to find this server under AD Users and Computers/System/DSFR-GlobalSettings/Domain System Volume/Topology

Is it safe to delete from here and will it resolve the problem?
Kamal KhaleefaInformation Security SpecialistCommented:
Check location of fsmo first
Then its fine to remove this server if its give no value to ur environment but first shut it down for a day
As error this server in ad topology
Maybe it was dc and depromoted
DJMohrAuthor Commented:
The thing is that this server is not on the local LAN
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

Kamal KhaleefaInformation Security SpecialistCommented:
Was it before ?
Kamal KhaleefaInformation Security SpecialistCommented:
If you do full backup of your ad
Just delete this server and add it again maybe trust certificate is missing
The only purpose of this to v copy of ur sysvol db

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
DJMohrAuthor Commented:
No, the server was never part of the local LAN. The server it is referring to is situated in a different geographical location and there is no link of any kind between the servers, in fact the server in question is a DC on an entirely different domain.

So there's no reason nor no way there servers could ever have replicated at any point in time.
Interesting.. if you go under ADSS do you see any new sites or replication partners?
DJMohrAuthor Commented:
Nope, no new sites or replication partners.
Did a full backup of the server and deleted the server it was trying to replicate with, all seems fine today, no errors in the event log.
DJMohrAuthor Commented:
Thanks, just wanted to be 100% before deleting.
Would be interesting to find out how it got there.
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
Active Directory

From novice to tech pro — start learning today.