| In SMS 1.2 | In SMS 2.0 | Notes |
|---|---|---|
| You create a package to collect an inventory of the software installed on clients — provided that you can supply characteristics such as the file name and file size of the software. | If you enable software inventory, client agents search the headers of .exe and other types of files for information about software. They also gather and inventory software installed on clients. | Software inventory is enabled and configured for all clients in the site and runs as a background process on the client at the interval you specify in the site-wide setting. |
| In software inventory, when the job to collect inventory is run on the client, SMS reports the full inventory, regardless of whether there had been changes since the last inventory. | Report information is limited to summaries and changes, an approach that reduces the impact of software inventory on network bandwidth. | SMS 2.0 inventory components include new and custom applications. Users cannot hide a program by renaming the executable file. |
| A limited form of hardware inventory is collected from clients automatically. | Hardware Inventory, which includes many more object
types than were previously available, can now be enabled or
disabled on a site-wide basis.
Report information is limited to summaries and changes, an approach that reduces the impact of software inventory on network bandwidth. Hardware Inventory runs as a background process on the client on a schedule you specify in the site-wide setting. |
|
| To view inventory data for a client, you double-click the client's computer name in the Sites window for the site. | To view inventory data, you open a collection that contains the client, right-click the client, and click Resource Explorer. | Resource Explorer gives you access to hardware and software inventory and to collected files. |
| To collect files from clients, you create a package. | You specify files to collect from clients by
changing the software inventory settings for the site.
The client sends a copy of a specified file to the CAP only if the file has not been sent before or if it has changed. You view collected files only from the SMS Resource Explorer — they are not directly accessible from the server's hard drive. |
Client agents search clients for the files in a background process that runs on a schedule you specify in the site-wide setting. |
| Some software distribution components refer to a common script directory named Mstest, which is located on the SMS logon server. | The logon server role is divided among logon points, CAPs, and distribution points. SMS then places application scripts and package files on a distribution point. | In SMS 2.0, the Mstest directory no longer exists and is no longer supported. |
Related Topics
