Windows 10: The Replication Group cannot be created in Windows Server

​

If you receive the The Replication Group cannot be created error while configuring Distributed File System Replication (DFSR) in Windows Server, it usually indicates a problem with Active Directory, DNS, permissions, or an existing DFSR configuration. The issue prevents administrators from creating a new replication group, delaying file synchronization across servers. In this article, we […]

This article The Replication Group cannot be created in Windows Server first appeared on TheWindowsClub.com.

read more...

 

Restarting Members of DFS Replication Groups on Server 2016 Standard

Restarting Members of DFS Replication Groups:

Hello Guys,

I would like to understand Best Practice for restarting members of Replication Groups, and would be delighted for the support, as i am unable to locate this information on Microsofts extensive documents base: https://docs.microsoft.com/en-us/windows-server/storage/dfs-replication/dfsr-overview

We have two Replication Groups configured for sharing their own respective folders, these groups each contain five members of a meshed group.

What I would like to understand what is the best way to undertake a restart of a member for say a Windows Update (ETA to complete relatively unknown) ?

I have witnessed some mention that shutting down the DFS Replication Service on a member and restarting the server should be sufficient. However, according to this article (If i am understanding correctly: https://www.experts-exchange.com/ar...Deployment-Considerations-Best-Practises.html) it
states:

>For any reason if DFSR replicated folder replication need to be stopped, change replication schedule to No Replication. Do not stop DFSR service. It may leads to DFSR database goes in journal wrap state and take much time to recover.

So am i having to completely stop replication across all groups to restart the member, surely this is overkill?

I have also noticed there to be the option of Disabling the Member but im not completely sure what scenario this is used for.

Any assistance is gratefully received.

Thanks

Mark

 

Window Server 2003 can't AD replication

Hi Support Team

I have server install Windows Server 2003. It's old and hardware unstable. I need to change to new Server. I try AD replication to new Server but after completed step.

I can't turn down old Server. When turn down old Server AD users and computer or another feature about AD can't use. I need your suggest.

 

Server A --- to --- Server B / Replication

Situation
I've got a very simple network, providing data in a SOHO environment to just 3 users.

SERVER A (W2K3)
+
3 users


SERVER A has recently been upgraded to RAID 1, with scheduled Cobian backups. All good so far.

Now, for the next 6 months, we've got a project in a far-far away land. Connecting to SERVER A is not going to be very efficient on consumer based internet connections. I also want a level of redundancy in case SERVER A, for any reason, goes down. (This includes power cuts, internet interruptions, not just hardware failure of the machine).

Enter SERVER B

Server B will be a mirror copy of SERVER A, but without the RAID and backup. It will be a SFF Atom box that can go on the road to the project site, and will have all data available locally providing fast access as well as "insurance" should SERVER A become unavailable for any reason.

Note that during this time away, there will be nobody at site A to fix/repair anything so why I need to find a maintenance free solution to the whole affair. Although I can Dameware Remote Control (remote desktop) into SERVER A assuming it is up and running, if it goes down, then it will stay down.

Note further than SERVER A and SERVER B will not be permanently connected over WAN. SERVER A has permanent internet access, but SERVER B will travel and therefore will be connected some days, and some days not.

QUESTION
What is the best way to keep SERVER A and SERVER B synchronised? (Or multi-server replication, depending on your preferred terminology)?

Something that seems to do this job perfectly is DFS Replication, a service in Windows Server products. However, it does not operate unless DNS and Active Directory are installed. It refuses to work on in a "workgroup" but only in a "domain". Setting up a domain, DNS and Active Directory seem to be overkill for a SOHO environment, plus I'm not sure how to do that properly given our usage topology. All instructions seem to be for enterprise fixed infrastructure/LANs and talk about heirarchy's, forests, domain servers, active directory servers, replicating between these. This all seems like a lot of work to do even BEFORE doing the simple DFS replication (Keeping the data on SERVER A shares and SERVER B shares in sync).

Are there any other solutions? Limited budget. Free, opensource or cheap. No suggestions for ArcServe Replication at $5000+ thank you!

If you made it this far down the post, thanks for listening and any suggestions you might have are very welcome *Pimp imp: