SMS 2.0 Software Distribution Details and Advanced Information Wally Mead Program Manager SMS Product Group Microsoft Co - PowerPoint PPT Presentation

oshin
slide1 l.
Skip this Video
Loading SlideShow in 5 Seconds..
SMS 2.0 Software Distribution Details and Advanced Information Wally Mead Program Manager SMS Product Group Microsoft Co PowerPoint Presentation
Download Presentation
SMS 2.0 Software Distribution Details and Advanced Information Wally Mead Program Manager SMS Product Group Microsoft Co

play fullscreen
1 / 29
Download Presentation
SMS 2.0 Software Distribution Details and Advanced Information Wally Mead Program Manager SMS Product Group Microsoft Co
766 Views
Download Presentation

SMS 2.0 Software Distribution Details and Advanced Information Wally Mead Program Manager SMS Product Group Microsoft Co

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. SMS 2.0 Software Distribution Details and Advanced InformationWally MeadProgram ManagerSMS Product GroupMicrosoft Corporation

  2. Session Agenda • An overview of Systems Management Server (SMS) 2.0 software distribution • Package distribution flow • Package location selection • Collection creation and update flow • Advertisement creation flow • Running advertised programs at the client • Detecting advertisements flow • Running an advertised program flow • Tracking package and advertisement status • Troubleshooting software distribution

  3. Software Distribution Misconception • Most problems reported for software distribution are regarding program installation • SMS 2.0 does delivery and status only • Delivers packages to distribution points • Delivers programs to clients • Generates status messages • Windows Installer, SMS Installer, third-party utilities are installation programs • They control how a program is installed on a target computer

  4. Site Server Advertisements Packages CAP Distribution Point Target Clients The Software Distribution Process

  5. Package Tidbits • No source packages useful for utilities already installed on client • Don’t need to resend the advertised program • Create compressed version if source is not permanent • Original source files on CD • SMS automatically creates compressed version for child sites • Share distribution folder uses syntax of Share\Folder • Only one package can use a share otherwise • Priority is only for distribution to child sites

  6. Program Tidbits • If necessary, have SMS restart computer • If program restarts computer, may experience unreliable success status messages • Configuration of user context • Most confusing aspect of software distribution • Advertised programs can be chained • The programs don’t need to be advertised, but must be created in the appropriate package • When program is assigned • For each user, or computer only • Disabling an advertisement quickly • “Disable this program on computers where it is advertised” check box

  7. Program Run User Contexts • Running programs in user versus administrator mode • By default, program runs under logged on user context • If program requires administrative rights • Can use logged on user or SMS account • SMS does not check to see if user is an administrator • Runs with administrative rights uses SMSCliToknAcct& • Use Windows NT® client software installation account uses configured account

  8. SMS Administrator Contexts • SMSCliToknAcct& is not a local administrator • SMSApm adds SMSCliToknAcct& to local Administrators group for program execution • It is removed from the local Administrators group after the program terminates • Windows NT client software installation account • Encrypted in client’s SAM • Added to local Administrators group for program execution • It is removed after program terminates • Only required if program requires access to remote resources (server other than where it is being run from)

  9. SMS SQL Monitor Distribution Point Site Database sender Distribution Manager Replication Manager Scheduler Inbox Manager CAP Package Distribution • If required, compresses package files • Chooses drive on distribution point • Copies package source files • Creates .pkg, .nal files If there are child sites

  10. Location of Distributed Packages • Packages directory: Smspkgx$ • Drive with most available space • SMS may choose a new drive with each new package • Specifying the target directory • For an individual package: • Specify target share during package creation • For all packages: • Create distribution point as a Windows NT share instead of Windows NT Server

  11. Tracing Package Creation • SMS Status System • SMS Distribution Manager • 2300, 2301, and 2311 for package creation or modification • 2343, 2329, and 2330 for distribution to DP • SMS Replication Manager, SMS Scheduler, SMS Lan Sender – sending data to child sites • SMS log files • Smsdbmon.log – creation of .pkn files • Distmgr.log – creation of package, distribution to DP, sends to child sites • Inboxmgr.log – replication of files to CAPs • Replmgr.log, Sched.log, Sender.log – sending files to child sites • Despool.log, Replmgr.log, Distmgr.log – receiving files at child site

  12. Collection Evaluator All Windows® 98 All Windows NT Offer Manager • Windows NT • Service Pack 6a Updating a Collection Computer 6 Computer 12 Computer 22 2 3 Site Server 1 Add 4 Service Pack 6a Windows NT Computer 22

  13. SMS SQL Monitor Collection Evaluator sender Replication Manager Scheduler Site Server How Collections Are Updated • Runs collection queries • Updates collection membership If there are child sites

  14. Collection Tidbits • Collection definitions automatically sent to child sites • As soon as new collection is created • When a new child attaches • On a scheduled basis (weekly by default) • Collections are updated on a schedule, not when a new resource is discovered • Hourly for built-in collections • Administrator scheduled • Administrator forced • Be careful with collections using custom data • May cause Collection Evaluator errors

  15. Tracing Collection Processing • SMS Status System • SMS Collection Evaluator • 2513 and 2516 for collection creation and membership update • SMS Replication Manager, SMS Scheduler, SMS Lan Sender – sending data to child sites • SMS log files • Smsdbmon.log – creation of .adc, .udc, .dc files • Colleval.log – creation of collection, update of collections, replication to child sites • Replmgr.log, Sched.log, Sender.log – sending files to child sites • Despool.log, Replmgr.log, Colleval.log – receiving files at child site

  16. SMS SQL Monitor Offer Manager Inbox Manager sender Replication Manager Scheduler CAP Site Server Implementing Advertisements • Creates lookup files • Creates instruction files • Creates offer file If there are child sites

  17. Advertisement Lookup Files • Advertisements can sent be to computers, users, or user groups • Each target class receives unique lookup file • Computers (systems) - ???Systm.lkp • Users - ???User.lkp • User groups - ???Usrgp.lkp • Offer Manager creates each as necessary • Offer Data Providers (ODPs) on client look for each unique file

  18. Advertisement Tidbits • Advertisements automatically sent to child sites • Regardless of targeted systems • Offer Manager at child site advertises program to local resources if appropriate • Rerunning previously advertised programs • If not assigned, simply use Advertised Programs • If assigned, need a recurring schedule • Can’t be “As soon as possible” • Add a new scheduled time • Create a new program • SMS tracks by program names

  19. Tracing Advertisement Creation • SMS Status System • SMS Offer Manager • 3900 for advertisement creation • SMS Replication Manager, SMS Scheduler, SMS Lan Sender – sending data to child sites • SMS log files • Smsdbmon.log – creation of ofn files • Offermgr.log – verification the package is ready, enumerating members, presenting offers to members, replication to child sites • Inboxmgr.log – replication of files to CAPs • Replmgr.log, Sched.log, Sender.log – sending files to child sites • Despool.log, Replmgr.log, Offermgr.log – receiving files at child site, creating local files

  20. Software Distribution Files • Check for these files if problems occur • Site Server: • Sms\Inboxes\Pkginfo.box - package and NAL files • Sms\Inboxes\Offerinf.box - lookup files, offer files, and instruction files • Smspkgs - compressed package files • CAP: • CAP_site\Pkginfo.box - package and NAL files • CAP_site\Offerinf.box - lookup files, offer files, and instruction files • Distribution Point: • Smspkgx$\PackageID - package source files

  21. The Advertised Programs Monitor • Accessed from Control Panel • Allows user to view programs for status or schedule • User will see: • Scheduled programs • Programs that have already been run • Unscheduled programs that are available to run are displayed in Advertised Programs Wizard

  22. Offer Data Providers Advertised Programs Manager Launch32 Client Status Messages Running Programs at the Client • Check lookup files • Check instruction file • Check offer file CAP

  23. Advertised Programs Tidbits • All clients detect advertised programs at scheduled intervals • No such thing as “right now” deployment • Interval is hourly by default (configurable at the site level or at each client) • Can force offer data providers to search • If multiple advertisements are available for a single program • SMSAPM merges the offers into a single offer • Earliest start time, latest expiration time • Create multiple advertisements of single program to multiple collections • Balances load at one point in time • Controls which group of recipients runs program

  24. Tracking Package Status • Package creation • Program creation • Distribution point assignment • Advertisement creation • Package processing

  25. Tracking Advertisement Status • Advertisement creation • Advertisement processed by Offer Manager • Client receipt of advertisement • Program run by client • Program run successfully • AdvertView tool • Support utility to offer more detailed look at advertisement status

  26. Site Hierarchy Issues • These flow down to children automatically: • Package definitions • Collection definitions • Advertisement data • Package data only goes down to child if requested • Parent targets child distribution point • Child targets own distribution point • Status flows up the hierarchy automatically • Package and advertisement status • All site-to-site communications are compressed and scheduled, and the bandwidth is throttled • Courier Sender helps in slow link environments • Uses tapes, CDs, floppy disks as source media to child • Package routing can help control link usage • Package uses existing path and intermediate site

  27. Additional Resources • SMS 2.0 Administrator’s Guide • Hard copy can be ordered (part no. 271-00617) • SMS 2.0 Resource Guide • Microsoft® BackOffice® Resource Kit 4.5 • SMS Security Essentials white paper • SMS 2.0 SP2 CD and Web site • Microsoft Systems Management Web site • http://www.microsoft.com/smsmgmt/ • Product information, white papers, downloads • Microsoft product newsgroups • msnews.microsoft.com • microsoft.public.sms

  28. Summary • Software distribution is the most used feature of SMS • SMS 2.0 adds new and improved features to software distribution • Has new administrative controls • Is able to target computers, users, and user groups • Can automatically send advertised program to new recipients • Is able to chain programs • Tracing the distribution process can be done through flow charts, log files, status messages, and files