vember 4, 2017 9:15 AM
> To: exchange@lists.myitforum.com
> Subject: Re: [Exchange] RE: Outlook rules errors
>
> But if it's a warning shouldn't I use WarningAction Stop?
>
> > On Nov 3, 2017, at 5:37 PM, Joseph L. Casale <jcas...@activenetwerx.com>
> wrote:
> &g
ilto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith
>> Sent: Friday, November 3, 2017 3:00 PM
>> To: exchange@lists.myitforum.com
>> Subject: [Exchange] RE: Outlook rules errors
>>
>> You have two hyphens in front of WarningAction instead of one.
>>
>&
o:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith
> Sent: Friday, November 3, 2017 3:00 PM
> To: exchange@lists.myitforum.com
> Subject: [Exchange] RE: Outlook rules errors
>
> You have two hyphens in front of WarningAction instead of one.
>
> -Origina
sts.myitforum.com>
Subject: [Exchange] RE: Outlook rules errors
Sorry,
I am 100% confident on this one. The indeterminate behavior results from myriad
of error handling practices possible. The default preference and its implicit
behavior, all pet peeves of mine.
When writing a binary cmdlet,
.myitforum.com] On Behalf Of Michael B. Smith
> Sent: Wednesday, November 1, 2017 1:46 PM
> To: exchange@lists.myitforum.com
> Subject: [Exchange] RE: Outlook rules errors
>
> I gotta jump in here:
>
> >> By invoking Get-Mailbox outside the pipeline the way you are,
th
> Sent: Wednesday, November 1, 2017 1:46 PM
> To: exchange@lists.myitforum.com
> Subject: [Exchange] RE: Outlook rules errors
>
> I gotta jump in here:
>
> >> By invoking Get-Mailbox outside the pipeline the way you are, all the
> objects are
> >> accumulat
rshell/
-Original Message-
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Joseph L. Casale
Sent: Wednesday, November 1, 2017 3:30 PM
To: 'exchange@lists.myitforum.com'
Subject: [Exchange] RE: Outlook rules errors
Sure,
$i references a mailbox. Tha
Sure,
$i references a mailbox. That has the offending owner of the invalid rule.
Here is a rule I require all code I work with to follow, otherwise it gets
filed in G:)
Always use `Set-StrictMode -Version Latest`
For every cmdlet that exposes it, use the -ErrorLevel parameter and either
