Friday Reminiscing: Terms that originated with, or were strongly specific to, Microsoft Systems Management Server (SMS)
From SMS Nightmares to ConfigMgr Dreams: How Microsoft's Slapdash Server Shaped My IT Soul (And Scarred It a Little)
I started my professional IT journey in the mid-90s, right around when Microsoft released SMS 1.0 in 1994. At the time, managing large networks of computers was a nightmare—think manual inventories, clunky software deployments, and no real centralized control. SMS promised to change all that, and I jumped in headfirst. It was my first real dive into enterprise software, and man, did I cut my teeth on it.
The early days were rough. SMS wasn’t exactly a polished product; it felt like someone at Microsoft slapped it together over a weekend and just shipped it. Installation was a beast—requiring SQL Server, dealing with finicky site hierarchies, and praying your network didn’t choke on the replication. Bugs were everywhere: inventory scans would hang, software distribution jobs would fail mysteriously, and remote control sessions? Forget about it if your client wasn’t perfectly configured. But despite the headaches, there was something revolutionary about it. For the first time, we could automate hardware and software inventories across hundreds or thousands of machines, push out updates without walking to every desk, and even monitor network health in a somewhat unified way.
As SMS evolved—through versions like 1.2 (with better remote tools and SNMP support) and into 2.0 (which helped with Y2K prep)—it got better. By SMS 2003, it was a solid tool with the “Advanced Client” that scaled to handle massive environments. It laid the groundwork for what we’d later know as System Center Configuration Manager (SCCM) in 2007, and eventually Microsoft Endpoint Configuration Manager (MECM) or just ConfigMgr today. That progression turned SMS from a quirky experiment into a cornerstone of modern endpoint management, influencing everything from patch management to OS deployments.
But the real magic for me wasn’t just the tech—it was the people. Through SMS, I connected with folks at Microsoft and built a vibrant community. Conferences like the old Microsoft Management Summit (MMS) were epic; they’d pack halls with IT pros swapping war stories about failed deployments or clever workarounds. I met engineers, MVPs, and product managers there, and many of those relationships are still going strong today. The SMS community was tight-knit, much like today’s Sentinel or Intune crowds—passionate people solving real problems together. It’s what hooked me on IT for life.
Reminiscing on SMS Terminology: Ghosts of IT Past
One of the fun parts of looking back is remembering the lingo. SMS introduced a ton of terms that defined how we talked about systems management, but many have been retired, renamed, or evolved beyond recognition as the product matured into ConfigMgr. Some were clunky, some innovative, but they all remind me of simpler (or more frustrating) times. Here’s a list of some key ones that no longer exist in their original form, along with what they meant and what replaced them (if anything).
Below is a curated list of terminology that originated with, or was strongly specific to, Microsoft Systems Management Server (SMS). These are terms that were either introduced by SMS, or became canonical within the SMS product model and later carried forward (sometimes renamed) into SCCM / ConfigMgr.
I’ve grouped them by concept area, and each group is grounded in historical SMS documentation and overviews rather than modern MECM abstractions.
Core SMS Architecture Terms
SMS Site – The fundamental administrative boundary in SMS, defining the scope of managed resources and services
SMS Site Server – The primary Windows server where SMS is installed and where site management occurs
SMS Site System – Any server that hosts one or more SMS roles for a site (not necessarily the site server itself)
Primary Site – An SMS site with its own database that can have child sites
Secondary Site – A subordinate SMS site without its own database, managed by a parent site
Hierarchy – The parent/child structure that links multiple SMS sites together
Client & Discovery Terminology
SMS Client – The managed endpoint running the SMS client agent
Resource Discovery – The SMS process used to locate computers, users, and network resources
Resource – Any manageable object in SMS (computer, user, group, network component)
Site Roles Unique to SMS
Logon Point – An SMS site system role used as the initial contact point between clients and the SMS site (unique to early SMS versions)
Client Access Point (CAP) – A site system role that provided policy, inventory upload, and client communication services in SMS 2.0/2003
Distribution Point (DP) – A server role that stores and distributes software packages to clients (term introduced in SMS)
Software Deployment Model (Classic SMS Terms)
Package – A collection of source files used for software distribution in SMS
Program – A command line and execution definition associated with a Package
Advertisement – The mechanism used to offer or mandate a Program to a target (later renamed Deployment)
Collection – A dynamic or static grouping of resources used for targeting
Inventory & Management Terms
Hardware Inventory – SMS feature for collecting detailed hardware data from clients
Software Inventory – SMS feature for tracking installed software and file usage
Software Metering – SMS capability for tracking application usage for licensing and reporting
Administrative & Data Access Concepts
SMS Administrator Console – The MMC snap‑in used to administer SMS sites
SMS Provider – The WMI provider that exposes the SMS site database for consoles, automation, and APIs (term persists today)
WBEM (Web‑Based Enterprise Management) – The standards model used by SMS for data collection and presentation
Legacy / Historically SMS‑Specific Language
BackOffice Integration – SMS was positioned as a Microsoft BackOffice component in early releases
Push Installation – SMS‑specific term for remotely installing the client agent from the site server
Why this list matters (contextually)
Many of these terms:
Do not exist at all in modern Intune
Were renamed (Advertisement → Deployment, CAP → Management Point)
Still leak into conversations (“SMS Provider”, “Primary Site”, “DP”) even today
If you’re dealing with legacy docs, migration discussions, or archaeology‑grade Microsoft conversations, this vocabulary is still highly relevant.
Below is a clean, explicit list of SMS terms that are considered retired / no longer used in modern Microsoft Configuration Manager (SCCM / MECM), along with why they are obsolete. I’m intentionally not mixing in renamed-but-still-existing concepts unless the original term itself is dead.
Client Communication & Site Roles (Fully Retired)
Client Access Point (CAP)
Used in SMS 2.0/2003 as the primary client communication endpoint. Completely removed and replaced by the Management Point starting with SCCM 2007.Logon Point
Early SMS role used during user logon to assign sites and distribute client configuration. Eliminated as client installation and assignment models changed.Sender (LAN Sender / Standard Sender)
Used for site-to-site data replication in SMS hierarchies. Replaced by SQL-based replication mechanisms.
Software Deployment Model (Terminology Removed)
Advertisement
SMS term that defined how packages/programs were offered or required on clients. Renamed to Deployment; the term Advertisement no longer exists in product UI or documentation.Package / Program (Classic Model)
While “packages” technically still exist in ConfigMgr for backward compatibility, the SMS package/program deployment model is deprecated in favor of Applications, Deployment Types, and detection logic. The SMS meaning of these terms is obsolete.
Inventory & Metering (Removed or Deprecated)
Software Metering (Classic SMS)
The original SMS metering implementation is deprecated; modern telemetry and reporting supersede it.Discovery Data Record (DDR)
Still exists internally, but the term is no longer surfaced, discussed, or relevant in modern admin workflows.
Administrative & Platform Concepts (Obsolete)
SMS Administrator Console
The MMC-based console was specific to SMS. Fully replaced by the standalone Configuration Manager Console.BackOffice Integration
SMS branding and architecture tightly tied to Microsoft BackOffice is fully obsolete.Push Installation (SMS-era meaning)
Still conceptually exists (“client push”), but the original SMS push model tied to Logon Points and CAPs does not.
Hierarchy & Site Model (Terminology Retired)
Site Boundary Defined by IP Subnet Only (SMS-era)
SMS used rigid subnet-based site assignment. Modern ConfigMgr uses flexible Boundary Groups, rendering this concept obsolete.
🚫 Terms That Look Obsolete—but Aren’t
(Calling these out explicitly because they sound dead but are not.)
SMS Provider – Still actively used (WMI / AdminService layer)
Primary Site / Secondary Site – Still valid constructs
Distribution Point – Still core
Collection – Still core
These terms take me back to late nights troubleshooting why a CAP wasn’t responding or why an advertisement wouldn’t fire. SMS was revolutionary because it forced us to think about scale—managing not just one machine, but entire enterprises. Sure, a lot of this stuff got refined or ditched as tech advanced (hello, cloud and Intune!), but without SMS paving the way, we wouldn’t have the slick tools we do today.
If you’re an old-timer like me, what SMS terms or horror stories do you remember? Drop ‘em in the comments or hit me up on X. And if you’re new to IT, trust me—learning this history will make you appreciate how far we’ve come. Cheers to the pioneers!