It looks like you can edit some, but not others while they are in use. I created an expression Global Condition and was able to edit it after it was in use. I just can't edit that script Global Condition.
It's one of those things that could be intentional on Microsoft's part, or I could just be doing something wrong. The really annoying thing is with revision history, I can't do anything to the script unless I delete the revisions that are attached to it also. On Tue, Jun 11, 2013 at 8:59 AM, Sherry Kissinger <[email protected] > wrote: > Is that global condition currently used in any application (deployed or > not?) I believe that once it's in use--you can't edit it. Because that > could be scary / dangerous if some malicious person decided that format c: > | y was a cool idea to try.... Ok, maybe not maliciously done, but > accidents happen; typos happen, so you aren't allowed to edit a condition > that's being used. > > Sherry Kissinger > Microsoft MVP - ConfigMgr > [email protected] > > > ------------------------------ > *From:* Ryan <[email protected]> > *To:* [email protected] > *Sent:* Tue, June 11, 2013 8:52:20 AM > *Subject:* [mssms] Script Global Conditions in ConfigMgr 2012 > > I created a script global condition to check if any users are currently > logged on. I then attached it to a few Deployment Types for testing, and > noticed I had an error in it. I went to the Global Condition and tried to > edit it, but the script is grayed out. > > [image: Inline image 1] > > How do I edit it? > > If the Global Condition type is an "Expression" I can edit it without a > problem, but when I do a custom script, I can't seem to edit that script. > > >
<<image.png>>
