Creating a Software Distribution Console
The initial steps to create a software distribution snap-in are the same as for creating the help desk console described earlier in this chapter; they are repeated in this section. In the Console Tree Items dialog box, however, you will select a different set of console tree items to meet the desired functionality of a software distribution console. To create this snap-in, use the following procedure.
To create a software distribution snap-in
- If the SMS Administrator console is running, exit the program. Then, at the command prompt, type the following:
mmc.exe
MMC will run without installing any snap-ins. The console displays a child window labeled Console Root. Because no snap-ins are installed, the console tree displayed is empty; only a root item (Console Root) visible.
- On the Console menu, click Add/Remove Snap-in.
- In the Add/Remove Snap-in dialog box, click Add.
- In the Add Standalone Snap-in dialog box, select Systems Management Server from the list of available snap-ins and then click Add.
- In the Database Connection Wizard Welcome page, click Next.
- In the Locate Site Database page, specify the SMS site database to which you want to connect. You can connect to the default site database or to another in your site hierarchy.
- If you want to reconnect to the default site database, verify that Reconnect to the site database for this site server is selected.
- If you want to connect to another site database in the site hierarchy, click Connect to the site database for this site server and either type the name of a primary site server or click Browse and select a site server in the Server Selection dialog box. Then, click OK.
- Click Select console tree items to be loaded (custom), and then click Next.
The Console Tree Items dialog box displays the SMS console tree items you can include in the console.
- To clear all the items shown, click Clear All and then select the following items: SMS Advertisements, SMS Collections, and SMS Packages. Then, click Next.
- The Completing the Site Database Connection Wizard page displays a list of the console tree items you chose for this console. Either click Back to make any required changes or click Finish to finish creating the snap-in.
- Close the Add Standalone Snap-in dialog box.
- In the Add/Remove Snap-in dialog box, click OK.
The customized snap-in you created now runs as a snap-in loaded into an MMC console. Note that the Systems Management Server console tree item appears beneath the Console Root item.
- Click Systems Management Server.
- On the Action menu, click New window from here.
A second child window opens within the MMC console. The new window displays Systems Management Server as the root console tree item.
- On the Windows menu, select the original child window and close it.
- With MMC still running and the Systems Management Server window displayed as the only child window, click Save As on the Console menu.
- In the Save As dialog box, type the name of the new custom snap-in and then click Save.
As with any customized snap-in, you can include additional SMS object classes and instances in this console, depending on the functionality desired. For example, you can add SMS System Status to your software distribution snap-in so that an administrator can view the status of software advertisements.
Table 4.2 lists the suggested security permissions for software distribution.
Table 4.2 Suggested Security Permissions for Software Distribution
SMS object | Security permissions |
---|
Advertisements | Read, Create, Modify, Delete (or Administer) |
Collections | Read, Advertise, Read Resource |
Packages | Read, Create, Distribute, Modify, Delete (or Administer) |
Warning Each time you use an SMS Administrator console, the SMS Provider allocates approximately 50 KB of memory for the console session. When you close the console, this memory is made available for other MMC sessions. However, when a console is shut down abruptly, as in the case of a network failure or an unexpected computer restart, the allocated memory is not properly released. This will cause the virtual memory usage of the SMS Provider server to increase. If this occurs when a large number of SMS Administrator console sessions are running, you should restart Windows Management on the site system hosting the SMS Provider or, alternatively, restart the server itself.