Previous Topic: Create an Asset Converter Engine TaskNext Topic: Configure the Collect Options


Configure the SMS Server Option

The SMS Server tab is used to provide information about the SMS Site server that will be the target for the extraction.

Use this procedure to configure the SMS server option.

To configure the SMS Server option

  1. In the Server field, enter the host name or address of the SMS Site server from which to extract information.
  2. In the Site ID field enter the site ID of the SMS installation to contact.

    Each SMS Site installation has a three-letter site ID. It is possible to install several SMS sites on the same server as long as they have different site IDs, and, in such cases, this field must be used to specify which site the Asset Converter task connects to.

    When only one SMS site is present on the server, this field should be left empty, as the Asset Converter automatically chooses the only available site ID.

  3. In the Username field, enter the domainname/username to use when connecting to the SMS Site server. If left empty, the current user context of the engine performing the task is used.
  4. In the Password field, enter the password to use when connecting to the SMS Site server. If left empty, the current user context of the engine performing the task is used.

    The user specified must be able to access (remotely) the SMS WMI classes on the server machine.

  5. Click the Test Connection button to determine if the server details currently specified allow a connection to an SMS site to be established.
  6. Click Next.

A successful result here does not guarantee the same outcome from the task once it is performed by an engine, as it could then be running on a different machine and in a different user context. The test performed when you click on the Test Connection button in the Create New Task dialog is performed on the machine running the GUI and in the context of the user running the GUI. When the actual SMS Converter task is run it is done on the engine machine and in the context of the user account used by the engine (the local system account by default). This means that a successful test does not guarantee a successful connection when the task is actually run. You can eliminate the potential differences by making sure you include the domain name in the Username field of the configuration (in this format: domainname\username). If this is not done it will default to the domain of the current user which for a default engine amounts to the local users of the engine machine. If possible the test should also be performed on a machine which has the exact same access to the SMS installation as the engine machine meant to perform the conversion.