Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11For a reliable export of SCCM (Configuration Manager) global conditions, use the documented Get-CMGlobalCondition PowerShell cmdlet and pipe the results to Export-Csv. The admin console is where you browse and manage the conditions; Microsoft does not document a direct export from that console page. A SQL function-based query is also published by the community, but its availability and support status are not guaranteed across Configuration Manager versions.
What global conditions are and where to find them
Global conditions are reusable business or technical rules used to specify how applications are provided and deployed to client devices. In the Configuration Manager console, open Software Library > Application Management > Global Conditions to view or manage them. Microsoft’s global conditions documentation describes their purpose and console location.
Export global conditions to CSV with PowerShell
Microsoft documents Get-CMGlobalCondition for retrieving global-condition objects. Run Configuration Manager cmdlets from the Configuration Manager site drive, such as PS XYZ:>. The following is an illustrative export pattern; verify that the selected localized property names exist in your installed release before relying on them.
Get-CMGlobalCondition |
Select-Object CI_ID, CI_UniqueID, LocalizedDisplayName, LocalizedDescription |
Export-Csv -Path '.GlobalConditions.csv' -NoTypeInformation -Encoding UTF8- Open the Configuration Manager PowerShell environment and switch to the appropriate site drive.
- Inspect the returned objects with
Get-CMGlobalCondition | Get-Memberif you are unsure which properties your release exposes. - Adjust the selected properties to match those available, then run the export. The file is written to the path supplied to
-Path.
The cmdlet supports retrieval by name or CI_ID and includes security-scope filters. Microsoft documents CI_ID as the identifier used with -Id; see Get-CMGlobalCondition for parameters and release-specific details.
#1 Best Overall
- Book - powershell for sysadmins: workflow automation made easy
- Language: english
- Binding: paperback
SQL query option and its limits
A community example published on April 1, 2022 uses fn_ListGlobalConditions_List(@LocaleID) to list global conditions. This adapted query removes the original visible-and-in-use filters, so it does not intentionally exclude rows based on those two flags:
declare @LocaleID int = (select LocaleID from vSMSData);
select
gc.CI_ID,
gc.DisplayName,
gc.IsHidden,
gc.ConditionInUse
from fn_ListGlobalConditions_List(@LocaleID) as gc
order by gc.DisplayName;The example uses a function in the site database, not an interface established as a supported, stable public contract by Microsoft’s reporting documentation. The function’s availability across versions, complete output schema, and locale behavior should be validated on the target site. Microsoft’s SQL statement reference for reports documents querying Configuration Manager views but does not document this function. Do not modify or remove Configuration Manager-owned SQL objects; Microsoft warns that doing so can cause serious issues and recommends leaving them unchanged. See Microsoft’s Configuration Manager account guidance.
For an established reporting workflow, run the query against the relevant site database using an account with appropriate read access, then save the results from your SQL client as CSV. Confirm the function and its returned columns locally before building a recurring report around them.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What the console query feature can—and cannot—do
The console’s documented query builder is at Monitoring > Queries. It supports creating queries, editing WQL, importing query statements from MOF files, and choosing resource or query attributes. That documentation does not describe a query that exports the Global Conditions node. Use the console for browsing and management, and use PowerShell or a validated SQL workflow for a tabular export. See Create queries in Configuration Manager.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Best Value
Rank #3
Which export route should you use?
| Route | Strength | Limitation | Best fit |
|---|---|---|---|
| PowerShell | Microsoft documents retrieval of global-condition objects; standard PowerShell CSV tooling makes it straightforward to repeat. | Inspect available properties in the installed release before selecting fields. | Repeatable exports and scripts. |
| SQL function | A compact community example returns fields including CI_ID, DisplayName, IsHidden, and ConditionInUse. | Function availability, schema, and support stability are not established by Microsoft’s reporting reference. | Existing reporting workflows where the site implementation has been validated. |
| Admin console | Officially documented place to browse and manage global conditions. | No direct export from the Global Conditions node is documented in the sources cited here. | Manual inspection and management. |
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
