Transcript MGMT13

Systems Management
Server 2.0 Architectural
Overview
Martin Dey
Development Manager
Systems Management Server
Microsoft Corporation
Objective




Provide detailed, technical explanation of
Systems Management Server 2.0 architecture
Describe how Systems Management
Server 2.0 implements many Systems
Management features
Describe how Systems Management
Server 2.0 interoperates with WMI and
benefits provided
Explain how third-party management
products can integrate with Systems
Management Server 2.0
Non-Objectives

Does not cover all features




Network Monitor 2.0
Software Metering
Does not drill into Toolkit Schema
Does not cover C++ Toolkit
code development

See session XXXX by Russell Wilson
Our Route Through SMS 2.0
SMS and
NT5
Management
at Microsoft
Architecture
Features
NAL
Client
assignment
and setup
Site
Architecture
Discovery
S/W Distribution
Inventory
Questions
Server
Architecture
Client
Architecture
Status reporting
Health Monitoring
Site SDK
and
Admin UI
®
SMS And Windows NT 5.0
Feature
NT4
NT5
Desktop Locking
Roaming User
Disk Quotas
Client Caching
Remote Boot
Basic S/W distribution
Advanced S/W distribution
16-bit Client Support
HW and SW Inventory
Centralized Diagnostics/Troubleshooting
SMS
Systems Management
Server 2.0 Feature Review

Server setup

Scalability and
performance
Simplified dialog sequence
 Evaluation (“reviewer”) mode
 Multi-threaded despooler
and scheduler
 Integrated SQL setup
 No PDC/BDC requirement
 Database schema redesigned
 Secondary site setup from CD
 SQL Triggers replace
DB polling
 Configurable sec-site upgrade
 SMS 1.2
 Communication
upgrade/interoperability
 Fan-out distribution
 Admin UI
 Courier sender
 Integrated with MMC
 Admin UI exposes Link
 Extensible framework
profiling
 “Active” HTML help
 Improved client slow
link support
 Client UI
 32-bit version simpler, cleaner
 Design based on NT5 ZAW UI

Systems Management
Server 2.0 Feature Review

Software Metering







System Status Reporting
Detects and monitor all
 “Job” status tracking
applications (EXE, COM, etc.)  Background DB maintenance
Supports suite licensing
 SMS Installer
Active control or passive
 Application repackager
monitoring
 Installation roll-back
Restrict usage by license
 Multi-generational patching
quota, user, group, machine,
 SMS status reporting
or time
NDS Support


Support for native
NDS clients
Support for Novell Client32
Discovery or Netware
resources
Systems Management
Server 2.0 Feature Review

Software distribution






16-bit hardware inventory


CIM schema data for accuracy
and consistency
Only delta MIFs transferred by
client to server
Improved accuracy
Software inventory redesign


Based on version resources
Audit rule database obsoleted
Netmon 2.0





Real-time capture
Expert framework
NetDiscovery

32-bit hardware inventory


Rules-based dynamic targeting
Flexible targeting rule set
Unattended installation on client
Drop PGC support

Discover topology
Discover devices
NetTrace for SMS servers


Site network map
Server role polling
Systems Management Server
Top Level Architecture
Site hierarchy
Central site
Primary site
Primary site
Primary site
Secondary site
Secondary
site
SMS Site Architecture
Server dataflow
To parent site
To child sites
Admin
Console
SQL
Server
DB
Senders
Metering
SQL
Server
Site
Server
DB
Metering
Server
Logon
Server
Distributio
n
Point
Client
s
Client
Access
Point
Systems Management
Server Site System “Roles”

System roles in SMS 2.0 include:





Site Server
SQL Server
SMS Logon Server
Client Access Point
A role may exist…







Only on the Site Server
Or on strictly one server within a site
Or on one or more servers within a site
Distribution Point
Component Server
Software Metering Server
Admin UI
Systems Management Server
2.0 Site “Components”

SMS Site Servers







Site Configuration Manager
Hierarchy Manager
Inbox Manager
Collection Evaluator
Status Manager
Status Summarizers





Scheduler
Despooler
Replication Manager
LAN Sender
RAS Senders
Courier Sender Confirmation













Inventory Data Loader
Hardware Inventory Processor
Software Inventory Processor


Discovery Data Manager
Client Confign. Manager
Client Confign. Request Distn.
Client Install Data Manager
Network Discovery
SMS Server Discovery
NT User Group Discovery
NT User Discovery
NT Logon Discovery Manager
NT Logon Installation Manager
NT Logon Manager
License Metering

Inventory Processing

Client/Resource Discovery

Inter-site Replication



SMS License Server Manager
License Metering Service
Software Distribution


Offer Manager
Distribution Manager
Network Abstraction
Layer (NAL)

NOS independent file access



COM based architecture



Systems Management Server modules written
independently of NOS
future NOS protocols easily added
Also offers plain ‘C’ and C++ APIs via wrapper
NOS objects defined in abstract pathnames
Utilized by many internal components

Server side, Client side, Site Configuration File,
SDK Provider, User Interface
NAL Path Syntax

Generic syntax is:
<provider>:\\<path>\<component>\<component>
Where:
<provider> - NOS provider ID, e.g. MSWNET, NWBIND NWNDS
<path>
- NOS specific path, e.g. \\products1
<component> - component of pathname, e.g. \relapps

Qualifiers may be inserted as follows:
[“<name>=<value>”]
Resource Discovery
And Assignment
Finding potential targets



Resources - Potential targets for
Systems Management Server operations
Discovery - Any process which identifies
resources within a given site
Assignment - Allocation of selected
resources to a site
Server Roles Demo
Resource Discovery
What is it?



An extensible architecture to discover
potential targets for Systems
Management Server operations
Modular to allow various resource
types to be controlled by Systems
Management Server
Offers sites a complete view
of the systems and devices in
their environment
Discovery And Assignment
START
Any changes
to assignment?
Obtain discovery
data from
device/source
Resource
already known
to SMS?
Check site
assignment rules
N
N
Y
Trigger install
of SMS client
Add new resource
data to SMS DB
Y
Y
Merge new
discovery data
with existing
Any changes to
resource data?
N
EXIT
Discovery Methods

‘System’ Architecture Discovery Methods






Windows Networking Logon
NetWare Bindery Logon
NetWare NDS Logon
Network Discovery
Client Heartbeat Discovery
Other-Architecture Discovery Methods


Windows NT User
Windows NT User Group
Logon Discovery
Server Side Dataflow
Admin
Console
SQL
Server
DB
Senders
Metering
SQL
Server
Site
Server
DB
Metering
Server
Logon
Server
Distributio
n
Point
Client
s
Client
Access
Point
DDM Process Cycle
Save in \bad_ddrs
folder
Disc Data
Data Inbox
Inbox
Disc
DDR File
Parent
Site
N
Valid
DDR?
DDR?
N
SCA File
SCA
File
.SC*?
SCD File
SCD
File
Y
SCA File
SCA
File
• Test against assignment rules
• Update assignment list
• Add resource to database
Y
SMS
DB
• Update assignment rules
• Review and update
assignment of all resources
• Update database entries
•• Copy
new/changed
Copy new/changed
DDRstotoinboxes
inboxes
DDRs
of of
registered
registeredconsumers
consumers
•• Invoke
InvokeReplication
Replication
Manager
Manager
Sites in site
assignment list
DDM processes incoming discovery data files and
assignment rule changes
Discovery Demo
Network Discovery



Aim: To discover the network topology within
a Systems Management Server site and all
systems and devices attached to it
Constraint: Must use passive techniques
as far as possible to minimize impact on
the network
Coverage: IP and NetBIOS in Systems
Management Server 2.0 release


Other protocols may be added in future
Techniques: ARP, DHCP, OSPF, RIP, WINS,
DNS, NetBIOS and SNMP
Network Discovery
Architecture
WMI
Application
bootstrap
SMS
DB
Address
discovery
module
Discovery
controller
SNMP
interrogator
module
Cache
Future
modules
Assigning Resources
To Sites



IP Subnet / IPX network based
Resources check their own site
assignments during discovery
Resources may be assigned to
multiple sites

One “principal” site selected to
resolve any configuration conflicts
Client Components
4
Optional Components
Inventory
HW
SW
Remote
Control
Software
Distribution
Software
Metering
2
3
Client Core Framework
Base Components
WinMgmt
1
Event-Trap
Translator
APM
Client
Service
Launch32
CCIM
Copy Queue
Shared DLLs
NAL
Discovery and Installation Bootstrap
Logon
Bootstrap
Installation
Wizard
Remote
Bootstrap
Inventory

32-bit hardware inventory



16-bit hardware inventory


Uses WMI schema data for accuracy
and consistency
Only inventory deltas transferred
Rewrite to improve accuracy
Software inventory redesign


Remove need for rules-database
Use executable version resource data
®
Win32 Inventory
Client
Access
Point
CopyQ
Hardware
Inventory
Agent
NOID
MIFs
CIM Object
Manager (CIMOM)
Other
Providers
Win32
Provider
CIM
Schema
Asset Inventory Demo
Operational Terms
Grouping and targeting
Package
Collection
Advertisement
Custom setup
Binaries
PC
Advertisement
properties include
schedule, expiry and
dependency details
Min setup
PC
PC
PC
Typical setup
Programs
Package definition
includes properties of
setup image, replication
settings and associated
command lines
Resources
Collections defined by rules:
e.g., “All PCs running NT4
with 3c509 LAN card
installed”
Collections

Membership reevaluated periodically



Local sites rebuild collection lists
Queries rerun at regular intervals
 Interval passed as a collection “property”
The advertisement lists are updated as
the member list changes


The lists are updated using
change notification
Clients check advertisement list for
offered programs
Software Distribution
Rules-based software distribution

Based on “Collections” object



Admin defines rules which define a
“collection”of target devices
Collection rule-set includes fixed lists,
user groups and inventory queries
The rule-set is distributed to all sites



No list built at top level
Small rule definition file transmitted with
every package
Each site now aware of “collection” rules
Software Management
Server Dataflow




Software binary files replicated to Distribution Point
(DP) based on Package definition
Advertisement data placed on Client Access Points
(CAP) by site Offer Manager
Client polls CAP for new or changed
advertisements
Site
New advertisements executed
Server
by client on schedule, at
assignment, or by
user request
Logon
Servers
Distributio
n
Points
Clients
Client
Access
Points
Admin
UI
SQL Server
DB
Metering
Servers
What We Can Deliver…

Simple command lines


Installation commands




Regedit, Xcopy, URL
Command line and optional binaries
MSI Packages
Systems Management Server
Installer packages
Third-party packages
Software Distribution Demo
SDK And Admin UI

Builds UI on Systems Management
Server Provider




Provider uses WMI to provide a schema
driven interface
MMC UI objects sit tightly over WMI
All access to Systems Management Server
site via WMI API set
Benefits:



Extensible
Scriptable
Remotable
SMS 2.0 Provider And UI
Architecture
MMC
Remotable
WMI
connection
WMI CIMOM
SMS WMI Provider
Base classes (SMS)
Remotable
SQL
connection
SMS
Database
CIM
Schema
Systems Management
Server Provider

Exposes all Systems Management Server
operations via WMI


Systems Management Server operations
 Packages, collections, queries, status,
inventory, etc.
Systems Management Server configuration
 Client agents, security, roles,
schedules, etc.
Systems Management
Server Provider Demo
SMS Operational Status
Architecture




Requires consistent instrumentation of
all server and client components
Status message stream rolled up and
persisted at Site Servers
Summarizer components analyze stream
and provide (persisted) status overview
Message viewer allows drill down to raw
or filtered status message stream
Status System Architecture
1
Client Access
Points
Status Messages
propagated to
Site Server
Status
Message
Viewer
SMS
DB
2
Admin UI
Summarizer
Snap-ins
Messages
stored in SQL
Client
Components
Status
Manager
Status
Summarizers
UI displays
summaries or raw
status messages
4
4 Summarizers store
rolled-up status in SQL
Server
Components
Windows
NT Event
Log
Replication
Manager
3
Filters control
propagation to Event
log/parent
To Parent
Site
Distributed Service Diagnosis
Problem Scenario



Network outages often
impact distributed
service operations
Operator needs
visibility of network
dependencies
Require tool to test
connectivity between
distributed services
SQL Server
DB
Site
Server
Client
Access
Points
Distributio
n
Points
Clients
Distributed Service Diagnosis
Architecture



Uses network topology data to build filtered
views of network paths in use
Simple connectivity test (ping) gives check of
current status
Current implementation focused on Systems
Management Server services only

Easily extended to other distributed services such
as Exchange, DFS, DS, SQL, etc.
Distributed Service Diagnosis
Architecture
NetDisc
Consumer/
Provider
1
Store Network
Topology in
DB
SMS
DB
Management
Server
Console
Machine
Read topology
data from WMI
2
CIMOM
NetTrace
Viewer
3
Check
network
and display
connectivity Build
network path 4
Ping
Poll
Provider
Network Trace Demo
Basic Health Monitoring
Problem scenario



Operator requires realtime status of distributed
servers and services
Overview of
Server/Service “health”;
a primary requirement
Must allow customization
of “health”
Console
SQL
IIS
SQL
IIS
SQL
IIS
SQL
SNA
Basic Health Monitoring
Architecture
Windows
NT Event
Log
Send NT event
to Event Log
3
HealthMon
Consumer/
Provider
Monitored
Server
Set thresholds
on properties
1
CIM
Schema
Pass Health
Event to
Viewer(s)
4
CIMOM
Threshold event
detected by WMI
and sent to agent
2
WMI
Providers
Console
Machine
HealthMon
MMC
Snap-ins
HealthMon Demo