Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

Allow Changing In-use Global Conditions

Currently, a Global Condition cannot be changed or deleted if it is in use in any existing revision of an application. This makes testing a new global condition or fixing an existing global condition extremely cumbersome, either resulting in many duplicates being created or many revisions of the application being deleted every time the global condition must be changed.

While it is beneficial to make it difficult to break an existing application by preventing the global condition from changing, ultimately, SCCM users need the freedom to determine when it is appropriate to change an existing Global Condition on their own.

101 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Patrick Tilsen shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

4 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Andy Cippico commented  ·   ·  Flag as inappropriate

    You can use SCCM Powershell to modify the existing script, even if it has references. I don't know what the implications are for that particular deployment though.
    e.g.:
    Set-CMGlobalConditionScript -FilePath "GetChassisType.vbs" -ScriptLanguage VBScript -Name "Get Chassis Type"

  • James Sweeney commented  ·   ·  Flag as inappropriate

    This is a big bug bear for our organization. Every time we have to make changes to an existing global condition within SCCM, AppV connection groups containing any AppV applications referenced by this condition get removed after the next Application Deployment Evaluation Cycle. We then have to rebuild the affected AppV connection group and run an Application Deployment Evaluation Cycle to get the AppV connection group to reinstall.

Feedback and Knowledge Base