System -- aka the computer account of the primary site which holds that status rule.
On March 1, 2014 7:37:01 AM CST, Stuart Watret <[email protected]> wrote: >Do we know what user context a script runs under that is triggered by a >status filter rule? > >Sent from a dog and bone. > >On 1 Mar 2014, at 03:43, "Mote, Todd" ><[email protected]<mailto:[email protected]>> wrote: > >I hadn't even gotten to the status filter rule yet, I was just trying >to run the powershell from the site server. It seems to run and return >'0', but the computer in the collection I run it on still has a PXE >advertisement when I look at it in the console... > >From: >[email protected]<mailto:[email protected]> >[mailto:[email protected]] On Behalf Of Johan van Dijk >Sent: Friday, February 28, 2014 5:04 PM >To: [email protected]<mailto:[email protected]> >Subject: RE: [mssms] Clear pxe flags on collection > >If your filter rule for the email has the same criteria it won't be >processed since only 1 rule will be actually doing something. >I have a clear PXE and remove from collection action in 1 script >executing based on TS success criteria. Doing it separate didn't work >for me. > >Details: >http://ccmexec.com/2012/07/remove-from-collection-and-clear-pxe-flag-vbscript-using-status-filter-rule/ > >Adding an entry to the eventlog might help as well to see what is >actually being executed....(if it is executed).. :) > >From: >[email protected]<mailto:[email protected]> >[mailto:[email protected]] On Behalf Of Mote, Todd >Sent: Friday, February 28, 2014 10:14 PM >To: [email protected]<mailto:[email protected]> >Subject: RE: [mssms] Clear pxe flags on collection > >I was needing to do this just last night and started looking into it. >I've set up status filter rules before to send email on specific task >sequence success, so this wasn't a stretch to get to work. However, >the lines below, run (with the correct local info) even return status >code 0, but the objects in the collection still have their PXE >advertisements. This may not do what we think it does, or we aren't >calling it correctly... > > > >From: >[email protected]<mailto:[email protected]> >[mailto:[email protected]] On Behalf Of Stuart Watret >Sent: Friday, February 28, 2014 11:06 AM >To: [email protected]<mailto:[email protected]> >Subject: RE: [mssms] Clear pxe flags on collection > > >Cheers Trevor try that Monday. > > > >Stuart Watret > >Offshore - IT Ltd > >________________________________ >From: >[email protected]<mailto:[email protected]> ><[email protected]<mailto:[email protected]>> >on behalf of Trevor Sullivan ><[email protected]<mailto:[email protected]>> >Sent: 28 February 2014 16:26 >To: [email protected]<mailto:[email protected]> >Subject: RE: [mssms] Clear pxe flags on collection > >Stuart, > >I think you should be able to use the following: > >$Collection = Get-WmiObject -Namespace root\sms\site_lab -Class >SMS_Collection -Filter "CollectionID = 'SMS00001'"; >$Collection.ClearLastNBSAdvForCollection(); > >Make sure to replace the "lab" with your site code, and the "SMS00001" >with your collection ID. Let me know how this works. > >http://msdn.microsoft.com/en-us/library/cc146058.aspx > >Cheers, >Trevor Sullivan > >From: >[email protected]<mailto:[email protected]> >[mailto:[email protected]] On Behalf Of Stuart Watret >Sent: Friday, February 28, 2014 10:14 AM >To: [email protected]<mailto:[email protected]> >Subject: [mssms] Clear pxe flags on collection > > >Been trying to do this for a couple of hours and can't find a working >script. > > > >Tried a VB example and the powershell stuff; having issues with both. > > > >Whatever I use I want to trigger from a status filter rule. > > > >Anyone have a working example? > > > >Stuart Watret > >Offshore - IT Ltd -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
