Skip to main content

Filesystem 0.99 update (DFS-R!)

Filesystem Update 
Another update / bug fix for my module Filesystem. The latest release can be downloaded here. For more info on the module see here.


In update v0.99, DFS-r management has been released...with a couple of other changes :

NOTE: dfsradmin.exe is required to be installed for the DFSR functions to work

Updated


list-DFSRoots has been renamed to get-dfsroots due to list not being on the approved verb list (an alias exists to redirect list-dfsroots to get-dfsroots for now)

list-DFSLinks has been renamed to get-dfslinks due to list not being on the approved verb list (an alias exists to redirect list-dfslinks to get-dfslinks for now)
get-NTFSPermission - fixed issue with inherited only permissions

 
New DFS-r functions


add-dfsrGroupMember
disable-dfsrGroupMember
enable-dfsrGroupMember
get-DFSrGroup
get-dfsrGroupConnection
get-DFSRGroupfolder
get-dfsrGroupMember
new-DFSRgroup
new-dfsrGroupConnection
new-dfsrGroupFolder
new-dfsrPropagationReport
new-dfsrPropagationTest
remove-DFSRgroup
remove-dfsrGroupConnection
remove-DFSRGroupfolder
remove-dfsrGroupMember
remove-dfsrPropagationTest

Other New Function

get-NTFSExplicitPermissions - a great time saver when working out who has been assigned permissions below the root of a folder structure

In a separate post, I'll explain what goes on with new-dfsrgroup



cheers

Adam

Comments

Popular posts from this blog

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

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 - 10.1.1.254,10.1.1.3 - 10.1.4.254 …

compare-object in Powershell - comparing mulitple values

I'm starting to use compare-object more and more, and one thing I noticed, is that you can compare 2 objects based on multiple attributes. here is how it is constructed...
Compare-Object -ReferenceObject $object1 -DifferenceObject $object2 -Property a,b,c,d,eIf a,b,c and d are the same, but e is different, compare object will return a difference. In the following example, I use "-eq $null" as a check because by default compare-object returns $null if the objects are the same.
#create an array of objects to check against

$collection = @()
foreach ($entry in ("aaaaa","bbbbb","ccccc","ddddd")){
   $store = "" | select "a","b","c","d","e"
   $store.a = $entry*1
   $store.b = $entry*2
   $store.c = $entry*3
   $store.d = $entry*4
   $store.e = $entry*5
   $collection += $store
}

#create an object similar to those in the array
$object = "" | select "a","b…