1 / 36

System Center Configuration Manager Push Software

System Center Configuration Manager Push Software. By, Teresa Behm. Steps involved . Create a Collection List of Computers to receive the software. Create a Package The software link. Create an Advertisement The Schedule to run. Check the Status View report to verify results.

ramya
Download Presentation

System Center Configuration Manager Push Software

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. System Center Configuration Manager Push Software By, Teresa Behm

  2. Steps involved • Create a Collection • List of Computers to receive the software. • Create a Package • The software link. • Create an Advertisement • The Schedule to run. • Check the Status • View report to verify results.

  3. Create a Collection • Right click on the Collections item. • Select New Collection. • Give it a name. There are 2 ways to populate the Collections. Direct Membership or by Query.

  4. Create Direct Membership Rule Click the monitor Select the Resource class System Resource IP Network Attribute Netbios Name, Computer Name, IP Address… Add the value for the attribute.

  5. Create a Query Rule Click the cylinder Give it a name Select Import Query Statement Select software off a list Run it on a schedule to keep your collection current automatically.

  6. Query language based on wizard

  7. Create a Package

  8. Data Source

  9. Data Access

  10. Distribution Settings

  11. *MIF Matching

  12. Security

  13. Program Access

  14. Distribution Point

  15. Program Settings

  16. Requirements

  17. Environment

  18. Advanced Settings

  19. **Windows Installer

  20. ***MOM Maintenance

  21. Create an Advertisement

  22. Schedule

  23. Click the Sun Icon

  24. Distribution Points

  25. Interaction

  26. Security

  27. Check the Status • Status of the push scheduled run can be checked two ways. • Via Browser • Configuration Manager

  28. Report via browser Check the Status xxx = Server Name test = Computer Name • Run a report to check the status. • By Browser • In Configuration Manager

  29. Report on Configuration Manager • Click Reporting • Reports • All advertisements Right click and select Run. Select your advertisement.

  30. Report Example

  31. Status Report

  32. *MIF Reporting SCCM Administration and Automation A knowledge sharing initiative January 18, 2010 What is MIF: Management Information Format? Why SCCM use it? Management Information Format (MIF file) is a format used to describe a hardware or software component. MIF files are used by Desktop Management Interface (DMI) to report system configuration information. Although MIF is a system-independent format, it is used primarily by Windows systems. To install a new device in a Windows 95 system, the corresponding MIF file is needed.SCCM can use MIF files to determine the success or failure of an installation. After a program has finished executing, SCCM will look in the %windir% and %temp% directories for new MIF files (created after the time of the program execution start) and then match them on any or all of the following criteria:•Name of the MIF file (only need to specify the name portion, leaving off the “.MIF”, in package properties)•Publisher•Name•Version Posted by Atul Mishra at 6:41 PM • http://systemcentersupport.blogspot.com/2010/01/what-is-mif-management-information.html

  33. **Windows Installer Purpose Microsoft Windows Installer is an installation and configuration service provided with Windows. The installer service enables customers to provide better corporate deployment and provides a standard format for component management. The installer also enables the advertisement of applications and features according to the operating system. For more information, see Platform Support of Advertisement. This documentation describes Windows Installer 5.0 and earlier versions. Not all the capabilities available in later Windows Installer versions are available in earlier versions. This documentation does not describe versions earlier than Windows Installer 2.0. Installation packages and patches that are created for Windows Installer 2.0 can still be installed by using Windows Installer 3.0 and later. Windows Installer 3.0 and later, can install multiple patches with a single transaction that integrates installation progress, rollback, and reboots. The installer can apply patches in a specified order regardless of the order that the patches are provided to the system. Patching using Windows Installer 3.0 only updates files affected by the patch and can be significantly faster than earlier installer versions. Patches installed with Windows Installer 3.0 or later can be uninstalled in any order to leave the state of the product the same as if the patch was never installed. Accounts with administrator privileges can use the API of Windows Installer 3.0 and later to query and inventory product, feature, component, and patch information. The installer can be used to read, edit, and replace source lists for network, URL, and media sources. Administrators can enumerate across user and install contexts, and manage source lists from an external process. Windows Installer 4.5 and later can install multiple installation packages using transaction processing. If all the packages in the transaction cannot be installed successfully, or if the user cancels the installation, the Windows Installer can roll back changes and restore the computer to its original state. The installer ensures that all the packages belonging to a multiple-package transaction are installed or none of the packages are installed. Beginning with Windows Installer 5.0, a package can be authored to secure new accounts, Windows Services, files, folders, and registry keys. The package can specify a security descriptor that denies permissions, specifies inheritance of permissions from a parent resource, or specifies the permissions of a new account. For information, see Securing Resources. The Windows Installer 5.0 service can enumerate all components installed on the computer and obtain the key path for the component. For more information, see Enumerating Components. By Using Services Configuration, Windows Installer 5.0 packages can customize the services on a computer. Setup developers can use Windows Installer 5.0 and Single Package Authoring to develop single installation packages capable of installing an application in either the per-machine or per-user installation context. • http://msdn.microsoft.com/en-us/library/cc185688(v=vs.85).aspx

  34. ***Microsoft Operations Manager • Purpose • Microsoft Operations Manager (MOM) 2005 provides event-driven operations monitoring, performance tracking, security policy enforcement, and auditing capability. • The MOM software development kit (SDK) provides developers and administrators with information about extending and customizing MOM. The documentation includes information about creating MOM applications with the .NET Framework, creating custom reports, and connecting MOM to other management or help desk products. • http://msdn.microsoft.com/en-us/library/aa505337.aspx

  35. Software Distribution Guide • http://www.microsoft.com/en-us/download/details.aspx?id=18573

  36. Configuration Manager provides: • remote control • patch management • software distribution • operating system deployment • network access protection • hardware and software inventory • http://en.wikipedia.org/wiki/System_Center_Configuration_Manager

More Related