Simple powershell script using Get-ChildItem fails

Question

So I have a process that looks for specific files like below:

@(Get-ChildItem -Path \\$Server\c$\temp\* where-object { $_.CreationTime.Date -match "2016" })

This worked just fine until I wanted to try and split my output up. I learned about "$OFS=" "" and wanted to use that (global powershell variable?) and changed it to $OFS="`r`n"..

Now when I run the command above, I receive an error:

Get-ChildItem : A positional parameter cannot be found that accepts argument ' $_.CreationTime.Date -match "2016" '.

I tried resetting it with $OFS=" " and that doesn't seem to help. I can't figure out what I've done to ruin my simple script. Sorry for the very noob question but I've been searching this for ages and cannot come up with an answer. Everything I find online seems to state that my powershell command should work

Olaf Reitz · Accepted Answer · 2017-08-12 00:12:58Z

4

Your powershell command can't work. Get-ChildItem and Where-Object are different Cmdlets, try to pipe (|) the output from Get-ChildItem to Where-Object

@(Get-ChildItem -Path \\$Server\c$\temp\* | where-object { $_.CreationTime.Date -match "2016" })

answered Aug 12, 2017 at 0:12

Olaf Reitz

7143 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

TessellatingHeckler Over a year ago

$_.CreationTime.Year -eq 2016 avoids the conversion to string and the use of regex, and uhh .. the possibility for false positive matches should the script still be running after the year 20160 ;)

user6811411 Over a year ago

@TessellatingHeckler You beat me for the very same comment. (except the year 20160 :-)

Collectives™ on Stack Overflow

Simple powershell script using Get-ChildItem fails

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related