The ISV proxy and single client scenario both have similar workflows with respect to communication, but they differ for setup in Microsoft System Center Configuration Manager 2007.

ISV Proxy

The workflow for an ISV proxy can be split into two paths. One is for setting up the ISV proxy, the second is for managing communication between the ISV proxy and its clients. Your ISV proxy implementation must account for many of these tasks. Some however, such as providing configuration information, must done by the administrator. Information about these tasks is available in Configuring an ISV Proxy Application in Configuration Manager.

ISV Proxy Setup

  1. The ISV proxy software, which includes the management point interfaces, is installed. Typically, this is in on the same computer as the management point. During installation the administrator must provide the location of the management point, the site mode (native or mixed) and the site code. There is no supported means for the ISV proxy to automatically discover this information.

  2. A certificate is deployed to the ISV proxy computer. If the site is being run in native mode, it will be a certification authority-issued PKI certificate. It is created and installed by the administrator. If the site is being run in mixed mode, it will be a certificate, self-signed, by the ISV proxy. The certificate will be created when the ISV proxy software is first run. For more information, see About Configuring an ISV Proxy Application.

  3. Next, the administrator registers the ISV proxy certificate with the Configuration Manager 2007 database. To do this, the administrator must export the ISV proxy certificate from the ISV proxy computer, and import it into Configuration Manager. For more information, see About Configuring an ISV Proxy Application.

  4. When the certificate is imported, Configuration Manager generates an SMSID to identify the ISV proxy.

ISV Proxy Client Registration and Communication

  1. To establish communication with the management point, the ISV proxy registers with Configuration Manager by using the management point interfaces. In return, the ISV proxy will receive its SMSID identifier. The ISV proxy must obtain it’s SMSID by using a Client Registration Request before it can act on the behalf of ISV proxy clients. For more information, see How to Register a Client with Configuration Manager.

  2. The ISV proxy clients are deployed.

  3. The ISV proxy registers each client with Configuration Manager by using the management point interfaces. The ISV proxy uses its own certificate to sign the registration request on behalf of each client. After a successful registration, a client will have an SMSID identifier assigned to it. For more information, see How to Register a Client with Configuration Manager.

  4. The clients send and receive management data to and from the ISV proxy in their own proprietary format. The ISV proxy uses the management point message XML to convert the client management data into a format that the management point endpoint can understand. Each message is signed by using the ISV proxy certificate. The client itself is identified, in the message, by the SMSID it received during registration.

Single Client

Single Client Setup

  1. The single client installation software is configured with the site code, site mode (mixed or native) and management point location.

  2. The single client software, which includes the management point interfaces, is installed on each client that requires it. Typically this is done using Configuration Manager software distribution.

Single Client Registration and Communication

  1. The client registers itself with the management point, and receives an SMSID in return. For more information, see How to Register a Client with Configuration Manager.

  2. Management data is sent to and from the management point through the management point interfaces. The client has its own certificate that the management point interfaces use to sign messages. Messages from the client are identified by the SMSID that the client received during registration.

See Also

Send comments about this topic to Microsoft.