I think the SCCM audit status messages will have the information you need. Try 
creating a package and then take a look at the audit status message that is 
produced. I borrowed this idea from a script that 1e provided to us that 
enables Nomad for any newly created package.

Scott Ewing

From: [email protected] [mailto:[email protected]] On 
Behalf Of [email protected]
Sent: Wednesday, May 15, 2013 4:36 PM
To: [email protected]
Subject: [mssms] RE: SMS File information for CM2007

I like that idea but the intention could be either on / off that's why I was 
hoping I could use the .SMS file method.  Do the status messages enumerate that 
information that I could grab using the Status Filter rule method?
Thanks

Henry E. WILSON

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Ewing, Scott L
Sent: Wednesday, May 15, 2013 3:45 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: SMS File information for CM2007

How about setting up an SCCM status filter rule that runs a script each time a 
package is created based on the Audit status message that is written?

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of 
[email protected]<mailto:[email protected]>
Sent: Wednesday, May 15, 2013 3:31 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] SMS File information for CM2007

Working in CM2007 our packagers are asking if there are commands that can be 
added to the SMS file to enable/toggle the highlighted options?
[cid:[email protected]]
I found a script that will change all packages but that would not be a good 
idea.  Also, the SMS file is created before the package ID is generated (saw 
another script for that too).  This becomes a real PITA when you have to check 
these after the package is created.

Any help would be appreciated.
Thanks






<<inline: image001.jpg>>

Reply via email to