powershell-3.0

I developed a PowerShell script, and it's working absolutely fine. The only challenge is the files in the subfolders are not getting moved to the destination. get-childitem -Path "\\servername\location" | where-object {$_.LastWriteTime -lt (get-date).AddDays(-31)} | move-item -destination "C:\Dumps" I am unable to customize the script further. Musaab Al-Okaidi Use the -Recurse option on the Get-ChildItem command to get through to the files in the sub folders and then move each individually by piping the collection to Move-Item Get-ChildItem -Path "C:\Test" -Recurse | Where-Object {$_

How can I check in Powershell to see if a file in $fullPath is older than "5 days 10 hours 5 minutes" ? ( by OLD, I mean if it was created or modified NOT later than 5 days 10 hours 5 minutes) Here's quite a succinct yet very readable way to do this: $lastWrite = (get-item $fullPath).LastWriteTime $timespan = new-timespan -days 5 -hours 10 -minutes 5 if (((get-date) - $lastWrite) -gt $timespan) { # older } else { # newer } The reason this works is because subtracting two dates gives you a timespan. Timespans are comparable with standard operators. Hope this helps. Test-Path can do this for you

PowerShell 3.0 CTP1 introduces a new feature [ordered] which is somewhat a shortcut for OrderedDictionary . I cannot imagine practical use cases of it. Why is this feature really useful? Can somebody provide some useful examples? Example: this is, IMHO, rather demo case than practical: $a = [ordered]@{a=1;b=2;d=3;c=4} (I do not mind if it is still useful, then I am just looking for other useful cases). I am not looking for use cases of OrderedDictionary , it is useful, indeed. But we can use it directly in v2.0 (and I do a lot). I am trying to understand why is this new feature [ordered]

I can start 5 new PS sessions on a remote server and see them all by running Get-PSSession PS C:\> New-PSSession -ComputerName MyServerName Id Name ComputerName State ConfigurationName Availability -- ---- ------------ ----- ----------------- ------------ 1 Session1 MyServerName Opened Microsoft.PowerShell Available [repeat 4 more times] As expected, when I try to open a 6th session, I get the error saying that's a no-no (due to PoswerShells default limit of 5 concurrent remote PSSessions). But running Get-Session shows all 5 sessions so all is working as it should be so far: PS C:\> New

I'm a relative newbie on PowerShell, wanted to know a bit more about functions, CmdLet and human readable values. Usually for learning new things, looking at what others do works well. So I went looking and bumped into the source for a Get-DiskUsage CmdLet. I can . source this into PowerShell, then call the function. Somehow, it always uses the current directory for getting the results no matter how I call it. What am I missing that it will not take the given -Path parameter? PS D:\bin> . .\DiskUsage.ps1 PS D:\bin> Get-DiskUsage -Path D:\ -h Size Folder ---- ------ 405M PS D:\bin> Get