spoofffed ✭✭✭✭✭

I do not trust my phone because when I am in meetings it will somehow figure out how to call where ever it is 3am at in the world from my contact list, set volume to max and put in speaker mode after dialing so I am made aware of this fact when a loud voice screams from my pocket "Do you have idea what time it is!?". I do…

Thanks, Kevin! You were 100% right. I took the empty lines out of the text file and it works without errors after changing "False" to $false.

Weirdly enough, even though it spits out an error, it still works as it is intended. The applications become unmanaged for the time (1 day) specified. I'll play with it using your example to see if it works better.

Using $False gave me a different error: Invoke-SwisVerb : no viable alternative at input '' in Where clause At line:13 char:9 + Invoke-SwisVerb -SwisConnection $SwisConnection -EntityName O ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [Invoke-SwisVerb],…

Using $False gave me a different error: Invoke-SwisVerb : no viable alternative at input '<EOF>' in Where clause At line:13 char:9 + Invoke-SwisVerb -SwisConnection $SwisConnection -EntityName O ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [Invoke-SwisVerb],…

* Isn't the 3rd parameter manage until, $laterUTC in my example. 1st - Application ID, 2nd Unmanage from, 3rd unmanage until, and 4th False?

Greg! Did you ever find a solution or work around with this? I tried to write the alert object to not trigger if the component message was ''An error occurred while creating the pipeline.' but still seeing some of these down.

Hi Kevin - Any news on this?

I'm really looking forward to hear how to make this work

Great query, Amit!! Do you have the SWQL code too?