Is this what you need?

function Remove-Items
{
    $targetFolder = "\\MyUNCpath"

    if (Test-Path -Path $targetFolder)
    {
        $thirtyDaysAgo = (Get-Date).AddDays(-30)       
        Get-ChildItem -Path $targetfolder -Recurse | Where-Object { $_.CreationTime -lt $thirtyDaysAgo } | Remove-Item
    }
    else
    {
        Write-Host "$targetFolder does not exist."
    }
}

Remove-Items

That basically removes any item that is a child of the supplied path that is older that 30 days.

What about this?

function Remove-Items
{
    $targetFolder = "\\MyUNCpath"

    if (Test-Path -Path $targetFolder)
    {
        $thirtyDaysAgo = (Get-Date).AddDays(-30)       
        Get-ChildItem -Path $targetfolder | Where-Object { $_.CreationTime -lt $thirtyDaysAgo } | ForEach-Object {
            if ($_.PSIsContainer)
            {
                if ((Get-ChildItem -Path $_.FullName -Recurse | Where-Object { $_.CreationTime -gt $thirtyDaysAgo }).Count -gt 0)
                {
                    return
                }
                else
                {
                    return $_
                }
            }
            else
            {
                if ($_.CreationTime -lt $thirtyDaysAgo)
                {
                    return $_
                }
                else
                {
                    return
                }
            }
        } | Remove-Item -Recurse
    }
    else
    {
        Write-Host "$targetFolder does not exist."
    }
}

Remove-Items

Try this:

Please do note that it will delete all empty directories!

Use Foreach-Object to perform the desired action and then pass the item on to the next pipeline task.

Be aware that you might need to perform some formatting depending on how you want the items to be logged. Another option might be to do the Remove-Item first and do the logging last.

From Get-Help Remove-Item -Detailed:

    -Force []
        Allows the cmdlet to remove items that cannot otherwise be changed, such as hidden or read-only files or read-o
        nly aliases or variables. The cmdlet cannot remove constant aliases or variables.  Implementation varies from p
        rovider to provider. For more information, see about_Providers. Even using the Force parameter, the cmdlet cann
        ot override security restrictions.

I include it to remove hidden or read-only files. I think you'll still get an error for other scenarios such as access denied.

Here's a very quick reply, I'll try to post a possible solution later tonight (sorry it's been so long since my last post... work's been kicking my rear!)

The -Exclude parameter for Get-ChildItem only matches names (not paths) so any file whose name is not Exception will still match even if it resides inside an Exception folder.

I think what you want to do is filter by FullName. Perhaps something like this:

Oops! Nope, it does not need to be in double-quotes although using double-quotes won't hurt anything in this case. The problem is that the -match operator expects a regular expression and '*\Exception\*' is not a valid regular expression. It is a valid wildcard pattern so we should be able to use the -like operator:

If you still want to use a regular expression then it should look like the following:

if ($_. -ne $null)
{

$_.Refresh();
.... more code
}

Geez! Another uncharacteristic mistake on my part... That's what happens when I don't try out suggestions before making them. -notlike is the correct operator to use as you correctly point out.

If you want to check the object in the pipeline against null then your condition is simply $_ -ne $null. Notice there is no period there after the $_. That's what the error is trying to tell you. Notice that the unexpected token is the period. The <<<< delimiter points to the character it was not expecting, in this case the period after the $_.