VMM SSP 2.0 Components (High Level)

This post will touch a few basic details on the components present in VMM SSP 2.0. If you have further questions, please post a comment and I can go in more deeper.

VMM SSP 2.0 primarily has two components:

· Web Component

· Server Component

Server Component

This really is a windows service. We sometimes also refer to it as an engine or a service or the provisioning service (although it does not really do any fancy provisioning as such!). To identify the VMM SSP 2.0 service in service control manager (Start -> Run -> services.msc), here is what you should look for:

Service Name: DITSCProvisioningService

Service Display Name: Virtual Machine Manager Self Service Portal 2.0

The service like any other windows service should always be running. If for some reason this service is not running, then you will have problems with certain sections of the web site (see below) that attempt communication with the service. You can troubleshoot any service related issues by referring to the log file that the service creates. You can find the log file in the folder: <installation folder>\Service. The log file will have the name: VMMSSPService.log. Additionally the service also logs certain errors to the Event Log under its own log with name: Virtual Machine Manager SSP. The service has its own configuration file with name: Microsoft.DITSC.ProvisioningService.exe.config found in the same folder as above. This file, as the name suggests, contains all configuration related information for the service

I also sometimes refer to the Service component as the service component or just service.

Web Component

This really is a website. The website can be deployed separately on a stand alone machine after you have deployed the Server component. For the most part, the website is self-sufficient. However, there are certain sections of the website (certain pages) where the website attempts communication with the service (deployed on the same server or on a different server). The web site has a log file of its own with the name: VMMSSPWeb.log. You can find this log file in the folder: <installation folder>\Portal. You can always refer to the log file to troubleshoot any web specific issues or any communication related issues between the web site and the service. During installation, the web configuration screen will let you specify the web site name, application pool name, port number and the application pool identity account. Based on the details you specify during installation the Web site is created. You can always refer to the website here: Start -> Run -> inetmgr. The website has its own configuration file with name: Web.config found in the same folder as the website.

I sometimes refer to the Web component as the website.

Thanks,

Sai Kodi