Quite confusing and incomplete, I'm afraid.
WIS is a generic service which does the complete processing and installation of a .MSI file. So an application like Office2000, in its setup.exe, contains:
a) A check whether WIS is there. If so, launches WIS. If not, first installs WIS.
b) The link to the MSI file.
The service also supports other specific MSI features, like
* Install on demand: an extra option (e.g. Clipart) of an app is not on C:. First time user clicks on a menulink needing the option, it is installed from the LAN to C:
* Association. E.g. while Acrobat Reader is not installed on C:, the PDF extension is associated with the Acrobat MSI. When doubleclicking a PDF file, the install job is launched (similar to surfing and clicking on your very first Flash site).
Indeed WIS _also_ publishes applications through the Add/Remove option of W2K. It's the preferred supplier to this option, though NT/W98 style registering of apps is also allowed.
Finally two more confusions:
* MSI files can also be _built_, next to the Microsoft WIS toolkit, by products from Installshield and WISE
* Windows 2000 Server contains Application Installation Service which checks in Group Policy for Assigned/Published MSI files, and then for each workstation launches WIS to execute the Group Policy jobs. Sometimes Microsoft confuses AIS with WIS, but they are different layers. AIS solely works for W2K Pro desktops, while WIS runs under W2K, NT, Windows 9x.
At your service, - The Netherlands