v1.0.0
Released January 2026releasedInitial public release of Add Device To Collection. The product is sold in the Essentials tier of the TontonTools suite. A 14-day free trial is available without a credit card.
Added
- Bulk addition of devices to an SCCM device collection (CollectionType = 2). Symmetric counterpart of Add User To Collection. Supports three rule types: direct member rules (SMS_CollectionRuleDirect), include collection rules (SMS_CollectionRuleIncludeCollection), and exclude collection rules (SMS_CollectionRuleExcludeCollection).
- Two input methods for the device list: file import (CSV/TXT, one device name per line) and paste list (multi-line text area). Both feed the same bulk processing pipeline.
- SCCM device resolution via SMS_R_System on Name. Devices not found in SCCM are reported in the activity log and skipped — no rule is created for unresolved devices.
- Idempotent execution: before adding a device, ADC checks SMS_FullCollectionMembership to verify the device is not already a member of the target collection. Already-member devices are skipped with a clear log entry.
- Circular-reference safety for include / exclude rules: a collection cannot be added to itself, and chained inclusion cycles are detected and refused at rule creation time.
- Filterable collection picker dialog: type a partial collection name to narrow the list of CollectionType = 2 collections. Sorted alphabetically.
- Bulk RequestRefresh on the target collection after all membership rules are added.
- SCCM connection via the standard WMI namespace root\sms\site_<X> with the in-dialog Auto-detect cascade.
- CMTrace-compatible activity log written to C:\TEMP\AddDeviceToCollection.log.
- DPAPI-encrypted credential storage shared across the suite at %AppData%\TontonTools\credentials.dat.
- Read-only fallback mode in license grace period.
Security
- No agent installed on managed endpoints — the product only communicates with the SCCM site server (RPC) and the TontonTools license endpoint.
- No telemetry, no cloud backend, no third-party analytics.
- Kerberos authentication under the signed-in Windows user — no service account required, no Graph permissions required.
- TLS 1.2 enforced on the license validation request.