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

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

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

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

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

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

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

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

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

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

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

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

13. Software Distribution b Use Package Command Manager service b 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.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 b User support Remote trouble-shooting, user educationRemote trouble-shooting, user education b Servers support b Essential tool for work-from-home admins b Network Monitor - restricted usage

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

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

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

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

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

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

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

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