1 / 22

Microsoft Systems Management Server Implementation at SLAC

Microsoft Systems Management Server Implementation at SLAC. Freddie Chow fchow@slac.stanford.edu Stanford Linear Accelerator Center. Contents. Overview SLAC NT Environment Current Status Work-In-Progress Some Recommendations

brit
Télécharger la présentation

Microsoft Systems Management Server Implementation at SLAC

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Microsoft Systems Management Server Implementation at SLAC Freddie Chow fchow@slac.stanford.edu Stanford Linear Accelerator Center

  2. Contents • Overview • SLAC NT Environment • Current Status • Work-In-Progress • Some Recommendations • Summary 1

  3. Overview • Systems management tool set by Microsoft • Require MS SQL Server 6.x or 7.0 • Current SMS Version 2.0 with SP1 • SLAC uses v1.2 and working on upgrading to v2.0

  4. Components of SMS • Software/Hardware Inventory • Remote Tools • Software Distribution • SMS Installer • Shared Network Application • Network Monitor 2

  5. SLAC NT Environment • Single master domain model • 13 Windows NT domains • ~1400 NT machines • Windows NT is supported 3

  6. A Bit of History • ~ 2 1/2 years back searched for a central management software • Looked at NICE/NT, SMS, LANDesk Mgmt, etc. • SMS matched SLAC environment • Collaborated with BSD, project started • SLAC Computing Service and other departments wide collaboration project

  7. SMS Architecture at SLAC • 2 SMS primary sites • 9 NT domains managed by SMS • ~1000 Windows NT machines (~71%) • Business Service Division - One site • To support secured network • 8 other domains - One site 4

  8. Architecture - continued • SLAC-wide Site • Primary site server • Dual PP200, 256MB • 3 Distribution servers • 2 Dual PP200, 256MB, RAID 5, 1 PP200, 128MB • BSD Site • Primary site server, also distribution server • PII 400, 256MB

  9. Security Models • Integrated, Standard, Mixed modes • Standard mode at SLAC on v1.2 • Requires MS SQL server login + NT login • More granular security on v2.0

  10. What have been done? • Standardize on hardware and software configuration (on going) • Software distribution • Use of remote tools • Inventory reports • Shared Network Application (tested) 5

  11. Hardware Standardization • Name brand vendor for hardware • Clone not recommended • Workstations, laptops - Dell • Servers - Compaq, Dell

  12. Desktop Standardization • Scripted install of workstations • Maintain known configuration • Format disk and reinstall as time permits

  13. Software Distribution • Use Package Command Manager service • Unattended install • NT 3.51 to 4.0 upgrade, NT4 SP3, SP4, SP5, Post-SP Hotfixes, IE 4.x, Netscape Communicator 4.x, Meeting Maker, Virus Definition Files, SolidEdge CAD Software, InocuLAN, Software Patches, Uninstall VirusScan, TeraTerm, AFS Client 3.5 (beta), etc.

  14. Use of Remote Tools • User support • Remote trouble-shooting, user education • Servers support • Essential tool for work-from-home admins • Network Monitor - restricted usage

  15. Inventory Reports • Some samples: • Check for NT Service Pack in a domain, in all domains • List IP address of machines in a domain (for network change) • List CPU MHz, RAM, user, office number, etc. • Customized reports - use Crystal Reports

  16. Shared Network Application • Tested, but not in production

  17. Miscellaneous Issues • Locked/powered off machines resulted in failed software distribution • Home connections very slow for software distribution support • Domain administrators need to keep accurate machine lists

  18. Benefits • Shorter response time • Shorter downtime, higher productivity • Reduce TCO • No more house calls for software install/upgrade • Quick response to security vulnerability • Apply NT hotfixes to a domain in one night • Eliminate human errors

  19. In Progress • Upgrade to SMS Version 2.0 - testing • Develop internal training material • Evaluate complementary tools • Evaluate Windows2000 deployment 4

  20. Anticipated Usage with SMS 2.0 • All of the above • Enforcing software licensing requires all NTs on SMS • Turn on software metering • Fine-tune security • Security fixes, Service Packs on Windows2000, etc.

  21. Some Recommendations • Architecture is based on environment • SMS 2.0 with SP1, SQL Server 7.0 • Servers requirement sizing • CPU MHz, RAM, disk space, RAID • How many servers ? • Where to put which server ? • Test, test, test before deployment

  22. Summary • Essential tool set for managing Windows environment • Reduce TCO • Complexity - high • SLAC NT administrators like it 6

More Related