Skip to main content

new-DFSrGroup

New-DFSRGroup
This function contains pretty much everything about dfs-r groups.  When you create a replication group from the GUI, have you ever noticed the steps that complete on the page after you click create? Ever paid any attention to what they are actually doing? Me neither, until I started looking at this new-dfsrgroup function.  Assuming that there are 2 members to the replication group and all parameters have been entered, my function calls dfsradmin no less that 9 times to complete the task.

So how can we use the function?  here are some examples....

new-dfsrgroup -name "rg2" -description "desc1" -Servers server1,server2 -folderpath e:\data\users -foldername Users

This command will invoke every part of the function and create a fully meshed replication group.  Out of the parameters presented, only name and servers are mandatory.  If you were to omit foldername eg : 

new-dfsrgroup -name "rg2" -description "desc1" -Servers server1,server2 -folderpath e:\data\users

then the group will be created and the server will be added as members and connections will be created, but as there is no replication folder, members cannot be enabled.  Essentially, the folderpath parameter in this example is ignored.  If you were to keep the foldername and omit the folderpath : 

new-dfsrgroup -name "rg2" -description "desc1" -Servers server1,server2 -foldername Users

then in addition to above a replication folder will be created, but still the members will not be enabled as no folderpath was supplied.

I could go on and on as this function has 10 possible parameters.  You can control pretty much anything to do with the replication group creation.  

This is straight out of the help file for the function : 

PARAMETER Name
Mandatory - The name of the Group to create
Postition 0
PARAMETER Description
Optional - A description of the group
Postition 1
PARAMETER Servers
Mandatory - The servers that will be members in the group.  The 
first server in the list will be the primary server
Postition 2
PARAMETER FolderPath
Optional - The path to replicate.  If not included, the group will 
be created but replication not enabled
Postition 3
PARAMETER Foldername
Optional - The name of the folder to appear in the group.  
If not included, the group will be created but replication not enabled
Postition 4
PARAMETER StagingSize
Optional - The size of the staging area - defaults to 4Gb
Postition 5
PARAMETER StagingPath
Optional - The path to the staging area - defaults to within the folder
path.
Postition 6
PARAMETER ConflitDeleteSize
Optional - The size of the Conflict and Deleted folder - default to 350mb
Postition 7
PARAMETER FileFilter
Optional - The file types to exclude from replication eg "*.txt,*.tmp"
Postition 8
PARAMETER FolderFilter
Optional - The subfolders to exclude from replication
Postition 9

You can download the module that contains this function here

I hope it helps dfs-r management, ask any questions in the comments!

cheers

Adam

Labels:

Comments

Post a Comment

Popular posts from this blog

Enable Powershell Remoting (WinRM) via Group Policy

I have been doing some testing on enabling WinRM via group policy, being that WinRM is the service that Powershell v2 sets up it remoting capabilities. Here are the GPO settings that you need to configure WinRM .... set the winrm service to auto start Computer Configuration \ Policies \ Windows Settings \ Security Settings \ System Services Windows Remote Management (WS-Management)  set Startup Mode to Automatic start the service incorporated in to the above - you may need a restart. create a winrm listener Computer Configuration / Policies / Administrative Templates / Windows Components / Windows Remote Management (WinRM) / WinRM Service / Allow automatic configuration of listeners IPv4 filter: * * is listen on all addresses, or if you only want a particular IP address to respond use an iprange eg 10.1.1.1-10.1.1.254 - don't forget that this IP range has to be valid for all hosts that fall in the scope of the GPO you are creating.  You can use 10.1.1.1 -
2 comments
Read more

Assigning Permissions - AGDLP

AGDLP It seems I have been mildly distracted away from the title of this blog site.   It does say AD Admin, but I seem to have been taken away by file system stuff.   I have to say, it has all been worthwhile, but it’s probably time I got back to the real heart of what I do. There are probably a million permission assigning advice pages, but I thought I would put another one out there after referring to AGDLP in my last post. So, what is this all about – AGDLP.   Well, it is something I learned in my MCSE 2003 studies and has become ingrained into my ideals since.   As a contractor, I get to move job often.   This enables me to forge opinions on how to configure things in a domain, and more importantly how NOT to configure things. AGDLP is definitely on the to do list…for anyone in any size domain or forest, as it follows some very basic principals.   I will explain these whilst I go through what AGDPL stands for. A A is for account.   It is the securit
2 comments
Read more

PowerShell 3 behavioural change

It's taken me way too long to get into PowerShell 3, I guess opportunity hasn't shown it's self until now and so, here, my V3 journey begins. I was asked to debug a script that would run fine in PS v2 and not in v3.  The issue was a that a variable length was being checked and was failing in v3.  This is why... In v2 if a variable is undefined , this test returns false PS C:\windows\system32> $var.length -eq 0 False In v3 the same test returns true.... PS C:\windows\system32> $var.length -eq 0 True Not a biggie, but as in this case, a script has broken so something to consider! cheers Adam
Post a Comment
Read more