• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 97
  • Last Modified:

DFS Replication After a Crytowall

A remove branch user was infected by CryptoWall.   It encrypted the remote DFS server.  The server only synced a few directories to the main DFS server.   We disabled the replication between the servers (via DFS Management) and rebooted the servers to stop replication.   We also restored from backup the encrypted files to the main DFS Server.

How do I go about restarting the DFS Replication with the main server as the correct server for files?
0
edwardq
Asked:
edwardq
  • 3
  • 2
3 Solutions
 
kevinhsiehCommented:
Remove the branch server from the DFS replication group, and then add it back it. The other server(s) will be considered authoritative.
0
 
SteveCommented:
safest way is to stop the DFS service on the remote server and make changes to the main server (and allow AD replication to occur between sites) before re-enabling the serviced on the remote server.
best to remove the replication group and create it again from scratch (delete or move the files from the remote server)
0
 
edwardqAuthor Commented:
Ok.. I did that. And it took the other server as authoritative and started PreExisting backup of folders on the main server.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
SteveCommented:
nice one. did that solve the issue?
0
 
edwardqAuthor Commented:
No it did not solved the issue.     I was hoping for it to start duplication with main server as authoritative.   I did both what Kevinhsieh and totallytoto suggested.  It would still take the bad server as authoritative.

Since it was a Virtual server, How I solved it was to build a new VM server locally, set it up in the DFS replication group. When it finished replicated.  I copyed the VM Server to a removable disk drive and drove it down to the branch and copied it/replaced the bad one.  It took a few days since it took about 4 hours to copy it the disk drive and 4 hours to copy it to the remote server.
0
 
edwardqAuthor Commented:
I selected my solution because it was the only one that worked.
0
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.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now