Skip to main content

Filesystem Module update 1

Filesystem - Update 1
This is my first update / bug fix for my module Filesystem. The latest release can be downloaded here. For more info on the module see here.


In version 0.91, the following has been changed :


Fixed


In new-fileshare, the path parameter now points to the share path rather than the parent path
Various help file updates


Added


New function : Get-diskspace
New function : Remove-fileshare


Updated


Add-NTFSpermission and remove-NTFSpermission now have a custom option. Any granular permission can be assigned to the file system this way. e.g. The read permission is actually made up of 3 granular permissions, read, listDirectory and ExecuteFile. These can now be assigned individually with Add-NTFSPermission -path d:\data -object adams -Permission custom -custom ListDirectory. The full list of permissions (from .net class [System.Security.AccessControl.FileSystemRights] ) are :


AppendData
ChangePermissions
CreateDirectories
CreateFiles
Delete
DeleteSubdirectoriesAndFiles
ExecuteFile
FullControl
ListDirectory
Modify
Read
ReadAndExecute
ReadAttributes
ReadData
ReadExtendedAttributes
Synchronize
TakeOwnership
Traverse
Write
WriteAttributes
WriteData
WriteExtendedAttributes

cheers

Adam

Comments

  1. Enable-DFSLinkTarget is not enabling the target. Still disabled. If I run this specifying an enabled target it gets disabled. Disable-EFSLinkTarget works as it should. The enable is the only issue I have run into.

    ReplyDelete
  2. Thanks Mike, just updated to 0.93 to fix this and a couple of other bugs

    cheers

    ReplyDelete
  3. Hi Adam,

    Great Module. I got a small issue with the new-dfsroot function.
    I'm running the script from a Windows 2008 R2 servers, but our Domain Controllers are still Windows 2003.

    So when you create a new DFS root, the syntax for DFSutil is :
    dfsutil root addDom \\SRV3\DomainNameSpace3 V1 "This is V1 Root"

    I will do the adaptation for myself, but it would be nice if you could add the version of the root as additional parameter for new-DFSroot.

    Thanks,
    David

    ReplyDelete
  4. Another comment:
    in the function Add-DFSRoottarget, the share creation line should be:
    $sharecreated = new-FileShare -name $name -server $server -path "$parentpath\$name"

    instead of
    $sharecreated = new-FileShare -name $name -server $server -path $parentpath

    Regards

    ReplyDelete
  5. Thanks David, great feedback! I'll look at adding these to the next release (which hopefully will be in the next couple of weeks)

    cheers

    Adam

    ReplyDelete

Post a Comment

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…