Microsoft Systems Management Server 2'0: Common Site Design Issues Wally Mead Support Engineer Produ

1
Microsoft Systems Management Server 2.0 Common
Site Design IssuesWally Mead Support
EngineerProduct Support Services - SMSMicrosoft
Corporation
2
Why the Need for This Session?

• Not all Systems Management Server (SMS) 2.0
  deployments are as successful as they could be
• Reasons for unsuccessful deployments
• Misconceptions about product functionality
• Improper site designs
• Product issues
• Deployments with good training, product
  knowledge, and designs were successful
• This session covers site design issues
• Common product misconceptions were covered in the
  March session

3
Session Agenda

• Performing a phased roll-out
• Many SMS sites sharing a single domain
• Sites spanning WAN links
• Account lockouts and orphaned clients
• Custom MIFs and site hierarchies
• Client assignment and installation
• Performing health checks in a site
• Additional resources

4
Performing a Phased Roll-Out

• Non-phased roll-outs
• Problems not uncovered during lab and pilot
  affect all systems
• Network traffic is not controlled
• Enable few subnets simultaneously
• Smsman and Reskit
• Verify results are correct
• When verified enable more subnets
• Create queries and collections to check success
  of roll-out
• Also use built-in status message queries

5
SMS Sites Sharing a Single Domain

• Many companies have BDCs at each remote location
• Customers often properly install SMS sites on
  each BDC
• Should not enable Windows Networking Logon
  Discovery
• Causes DDRs to be replicated throughout WAN
• Only enable Windows Networking Logon Client
  Installation
• Shares domain controllers, need Heartbeat
  Discovery

6
SMS Sites Spanning WAN Links

• SMS assumes high speed connectivity
• Between site server and other site systems
• Between SMS client and CAP (except dial-in)
• SMS does little intrasite network throttling
• Very few polling intervals customizable
• Cannot specify package deployment to distribution
  points
• SMS clients randomly select CAP and distribution
  point
• Not good utilization of a WAN link
• Microsoft BackOffice Resource Kit utilities to
  specify preferred server

7
Account Lockouts and Orphaned Clients

• SMSCliToknAcct used for many client processes
• SMSCliToknAcct is local to Windows NT client
• SMSCliToknAcct is in domain for domain
  controllers
• Lockout occurs because of
• Unique password for SMSCliToknAcct on clients
  and domain controllers
• SMSCliToknAcct should not access the network
• Q244410 for fix
• Avoiding orphaned clients
• Service Pack 1 release notes on creating
  additional SMS client network connection accounts

8
Custom MIFs in Site Hierarchies

• Child site has a custom MIF
• Data sent to parent site, so it is fine
• Parent site creates a collection based on the
  custom architecture
• Collections automatically replicated down to
  child sites
• Any child site without custom architecture fails
• Collection evaluator continually reports error
• Workaround is to ensure all child sites use same
  custom MIFs
• Or no collections using custom architecture

9
Client Assignment and Installation

• SMS 2.0 bases assignment on physical networks
• Either IP Subnets or IPX Networks
• The clients subnet mask is used for assignment
• Listed in Wn_logon.log and in discovery data
• No wildcards, supernets, individual IP addresses
  allowed
• Installation requires assignment and access to
  CAP
• If CAP in resource domain, must add permissions
  for user accounts

10
Performing Health Checks on Your Site

• Monitor any SMS Inbox with Moving Data
• Site Server (24 Inboxes)
• Logon Points (1 Inbox)
• Client Access Points (5 Inboxes)
• Monitoring SMS Status
• Component Status
• Site System Status

11
Additional Resources

• SMS 2.0 Admin Guides (and Release Notes)
• Hardcopy can be ordered (part no. 271-00617)
• SMS 2.0 Resource Guide
• BackOffice Resource Kit 4.5
• www.microsoft.com/smsmgmt/
• Microsoft Systems Management Web site
• Product information, white papers, downloads
• Office Microsoft Curriculum Training
• Microsoft Product Newsgroups
• msnews.microsoft.com
• microsoft.public.sms

12
(No Transcript)