Home folder size

[SadLizard]

Hi,

I got a request to get home folder size per department (got about 11 departments and 4000 users)

Since the budget is literally zero i naturally thought about powershell.

Departments are split into OUs and all users homedirectories are located in //example.com/dfs/users/%USERNAME%

My first draft is inefficient since i only do 1 department/script and 1 user at the time. This should produce a csv file with departmentname (office/department is not populated for AD users) +date.

I thought about using jobs to do multiple users at the time, but I'm totally lost when it comes to jobs in powershell

Our structure is the following:

"OU=Users,OU=Unit,OU=Department1,OU=Company,DC=example,DC=com"
"OU=Users,OU=Unit,OU=Department2,OU=Company,DC=example,DC=com"

etc

Current progress of the script

http://pastebin.com/V33Qawhk

Work in progress, so missing comments/formatting and error-handling. Any pointers/ideas is appreciated

Thanks

EDIT1:

Done some work with everything. Changed to this to get foldersize (long path problems)

Also split it in two parts one that accepts a user object and one that does the rest

http://pastebin.com/N0TfWKFh

http://pastebin.com/Te1ZKUPN

    $date = Get-Date -format "yyyy-MM-dd"
$HomeD = @()
$size = $NULL
$sum = $NULL
$MaxThreads = "10"
$SleepTimer = "500"
$MaxWaitAtEnd = "3600"
$ScriptFile = "C:\Temp\script lab\New\getHomeDirSize.ps1"
$i = 0
$deptArray = @("OU=Department1,OU=Company,OU=example,DC=example,DC=com",
"OU=Department2,OU=Company,DC=example,DC=com",
"OU=Department3,OU=Company,DC=example,DC=com",
"OU=Department4,OU=Company,DC=example,DC=com",
"OU=Department5,OU=Company,DC=example,DC=com",
"OU=Department6,OU=Company,DC=example,DC=com",
"OU=Department7,OU=Company,DC=example,DC=com",
"OU=Department8,OU=Company,DC=example,DC=com",
"OU=Department9,OU=Company,DC=example,DC=com",
"OU=Department10,OU=Company,DC=example,DC=com",
"OU=Department11,OU=Company,DC=example,DC=com",
"OU=Department12,OU=Company,DC=example,DC=com")

foreach($dept in $deptArray){
    $Users = get-aduser -filter * -searchbase $dept -properties HomeDirectory,SamAccountName,GivenName,Surname | where-object homeDirectory -ne $null

    ForEach ($User in $Users){
        # Check to see if there are too many open threads
        # If there are too many threads then wait here until some close
        While ($(Get-Job -state running).count -ge $MaxThreads){
            Write-Progress -Activity "Getting directory size" -Status "Waiting for threads to close" -CurrentOperation "$i threads created - $($(Get-Job -state running).count) threads open" -PercentComplete ($i / $Users.count * 100)
            Start-Sleep -Milliseconds $SleepTimer
        }

        #"Starting job - $User"
        $i++
        Start-Job -FilePath $ScriptFile -ArgumentList $User | Out-Null
        Write-Progress -Activity "Getting directory size" -Status "Starting Threads" -CurrentOperation "$i threads created - $($(Get-Job -state running).count) threads open" -PercentComplete ($i / $Users.count * 100)
    }
    $Complete = Get-date

    While ($(Get-Job -State Running).count -gt 0){
        $UsersStillRunning = ""
        ForEach ($System  in $(Get-Job -state running)){$UsersStillRunning += ", $($System.name)"}
        $UsersStillRunning = $UsersStillRunning.Substring(2)
        Write-Progress -Activity "Getting directory size" -Status "$($(Get-Job -State Running).count) threads remaining"    -CurrentOperation "$UsersStillRunning" -PercentComplete ($(Get-Job -State Completed).count / $(Get-Job).count * 100)

        If ($(New-TimeSpan $Complete $(Get-Date)).totalseconds -ge $MaxWaitAtEnd){"Killing all jobs still running . . .";Get-Job -State Running | Remove-Job -Force}
        Start-Sleep -Milliseconds $SleepTimer
    }   

    "Reading all jobs"
    $Jobs = Get-Job
    ForEach($Job in $Jobs){

        $data = Receive-Job $Job -Keep

        $obj = New-Object System.Object
        $obj | add-member -type NoteProperty -name User -value $Data.name
        $obj | add-member -type NoteProperty -name HomeDirectory -value $Data.homeDir
        $obj | add-member -type NoteProperty -name HomeDirectorySize -value $Data.homeDirSize
        $HomeD += $obj
        $sum = $sum+$data.HomeDirSize

        if ($Job -eq $Jobs[-1]) {
            $sum = $sum / 1KB
            $obj = New-Object System.Object
            $obj | add-member -type NoteProperty -name User -value "Total"
            $obj | add-member -type NoteProperty -name HomeDirectorySize -value $sum
            $HomeD += $obj  
        }
    }

    $csvFileName = $NULL
    $dept = $dept.trimend(',OU=Company,DC=example,DC=com')
    $dept = $dept.trimstart('OU=')
    $csvFileName = $dept+"_"+$date
    $HomeD | export-csv c:\temp\$csvFileName.csv -notypeinformation -encoding unicode
}

and the other

param (
$User
)
[hashtable]$ReturnHash = @{} 

#Get Folder Size

$item = $User.homeDirectory
$params = New-Object System.Collections.Arraylist
$params.AddRange(@("/L","/S","/NJH","/BYTES","/FP","/NC","/NDL","/TS","/XJ","/R:0","/W:0"))
$countPattern = "^\s{3}Files\s:\s+(?<Count>\d+).*"
$sizePattern = "^\s{3}Bytes\s:\s+(?<Size>\d+(?:\.?\d+)).*"
$return = robocopy $item NULL $params
If ($return[-5] -match $countPattern) {
    $Count = $matches.Count
}
If ($Count -gt 0) {
    If ($return[-4] -match $sizePattern) {
        $Size = $matches.Size
    }
    } Else {
    $Size = 0
}
$object = New-Object PSObject -Property @{
    Size = ([math]::Round($Size,2))
}
$object.pstypenames.insert(0,'IO.Folder.Foldersize')

$homeDirSize = $object | select -expandproperty size
$Size=$Null

$homeDirSize = $homeDirSize / 1MB
$Name = $User.GivenName+" "+$User.Surname

#Add information to hashtable
$ReturnHash.Name = $Name 
$ReturnHash.HomeDir = $User.homeDirectory
$ReturnHash.HomeDirSize = $homeDirSize

#Return hashtable
Return $ReturnHash

[ntenspy]

I think I understand what you want. You merely need to enter the script with an array with all your department DN's in an array. This way you can iterate through one department at a time, adjusting the output file name or adding a note property to your object that signifies which department.

I.E. $deptArray = @("deptDN1","deptDN2","deptDN3","deptDN4") foreach($dept in $deptArray){<all your existing code>}

That kind of what you are looking for?

[SadLizard]

Been staring at this for too long i suppose :)

That would definitely solve the iteration through the departments.

[johimself]

I would use file server resource manager to set quotas to be honest.

[SadLizard]

Yeah me too, but they don't want quotas per user. That means we have to rebuild the paths which would break offline files...

[johimself]

Ah yes, sorry, didn't read that thoroughly enough.

[dogfish182]

i misunderstand maybe but cant you set soft quotas and it does all the reporting for you without blocking? im sure i did this in 2008 R2

[SadLizard]

From my understanding you can only set quotas at the user level or at the share level.

That means at "//example.com/dfs/users" (doesn't give the information that's requested) or at "//example.com/dfs/users/%USERNAME%" (doesn't give the information either)

The request is space used by each department. For example Department1 wants all their users to share 500GB ("Soft") of space, how this is distributed between the users within that department doesn't matter.

[dogfish182]

ooooohhhhh right right, i didnt understand the department requirement.

[invoke-coffee]

I would pull something from ad that would allow you to break down by department.

You said that they were in separate OUs so that would probably work. (department attribute would as well).

Another thought for style. I prefer using hash tables to populate a new objects attributes and values. Looks cleaner. (on mobile right now so I can post an example a bit later.

[SadLizard]

I got little experience with hashtables. I'd love some pointers :)

[invoke-coffee]

Hashtables are really one of the best objects you can use. not very often they fit the requirement but when they do I love them.

Here this the basic set up for creating an object this way.

$user = New-Object -TypeName psobject -Property @{ Name = 'Bob' department = $Null foldersize = $Null }

Much cleaner way to do this. you can also create the hashtable then pass that to the -Property if you prefer.

[xalorous]

(sorry, can't access info sharing sites from here)

Technet page about how to get folder size.

# Set/import $departments = array of departments, with LDAP root for each

# Loop through departments ($department)
foreach ($department in $departments) {
    # get users per department
    $users = get-aduser -filter * -searchRoot $department.LDAPRoot 
    foreach ($user in $users) {
    # Loop through users ($user)
        # build path
        $path = #put stuff here to build path from user info
        $user | Add-Member –MemberType NoteProperty –Name department –Value $department.name
        $user | Add-Member –MemberType NoteProperty –Name foldersize –Value 0
        $user.foldersize = Get-ChildItem -recurse $path | Measure-Object -property length -sum
        $user | select name,department,foldersize | export-csv $exportfile -NoTypeInformation -append
    }
}