Through trial and error I've come across a working method for installing Intel's Setup and Configuration Service (SCS) on a server that does not have Notification Server, and thus Out of Band Management, installed. When NS is installed, all rights, etc, are already assumed by logging in as the Application Identity. Intel SCS installs fine this way, but when on a separate server certain prerequisites and configurations need to be met before the installed SCS will function properly.

 

 

 

 

Introduction

For the best results, the prerequisites should be met before hand. If SCS has already been installed, the necessary components can be added or configuration changed to support it properly. The first section of this article I'll assume we'll do the install from scratch, while with the second I'll cover how to reconfigure SCS if it has already been installed so it works successfully. This is with version 6.2 of Out of Band Management Solution.

 

 

 

New SCS Installation

NOTE: This is for an Intel SCS installation that is not on an existing Notification Server with Out of Band Management installed.

 

First, we need to prep the system for the actual install of Intel SCS. The following components are required for Intel SCS to function normally:

 

 

  • Windows 2000 Server, Windows 2003 Server

  • Internet Information Services (IIS)

  • Microsoft .NET 2.0

 

 

 

 

Run through the following steps to install Intel SCS. I've assumed the above prerequisites have already been met.

 

 

  1. Log onto the system as the Application Identity user for Notification Server.

  2. Using the ‘Pull' method, install the Altiris Agent from the Server that houses Out of Band Management:

    1. Typically the URL is formatted as: http://%3cnsname%3e/Altiris/NS/Agent/AltirisAgentDownload.aspx.

    2. Use the resulting page to download and install the Altiris Agent. Typically it takes a few minutes to complete the process of installing and registering with the Notification Server.

  3. If needed, provide the App ID account local administrator rights on this Server. In one case this was not the case, and the service was unable to connect to the NS.

  4. Browse to the following path on the NS:
    <NS_Name>\NSCap\Bin\Win32\X86\OOB\IntelSCS\

  5. Launch the EXE AMTConfServer.exe.

  6. Click ‘Next' on the Welcome screen and accept the license agreement and click ‘Next'.

  7. Choose ‘Complete' as the type of setup and click ‘Next'.

  8. In the User name and Password fields put in the Application Identity for the NS.

  9. Check the Web details.

  10. Leave ‘Force Secure Connections (HTTPS)' checked if you will use TLS to encrypt AMT traffic, or uncheck it if you will not be using TLS. Click ‘Next'.

  11. Under ‘Database Server' select the database name and instance to use. This should be the SQL Server used to install the IntelAMT database when OOB was originally installed on the notification Server, or if the database was never created, this should be the same server and SQL Instance where the Altiris database that hosts Out of Band Management is installed.

  12. Check the database details. Click ‘Next'.

  13. Click the ‘Install' button to proceed with the install using the parameters set.

  14. If the IntelAMT database was previously created, you'll receive a notice saying that the database IntelAMT already exists. Make sure to click ‘Yes' so it uses the existing one. This is especially important if you have provisioned systems already in the database. If no database exists by name IntelAMT, a new one will automatically be created and no prompt will appear.

  15. At the Complete screen, leave the ‘Start Intel® AMT Config Service' checked and click ‘Finish'

  16. From the Notification Server, at this location:
    <NS_Name>\c$\Program Files\Altiris\OOBSC\, copy the file oobprov.exe to the same path on the SCS Server (default will be C:\Program Files\Altiris\OOBSC\).

  17. NOTE! You must use the same path that it used on the Notification Server, this is a limitation with our implementation at this time.

  18. Copy to the same folder the attached file Interop.AeXClient.dll.

 

 

  1. Normally the script (oobprov.exe) is properly registered to the correct path, but if it is not, we must manually change it.
         NOTE: Using this option to install SCS on a different server than the NS often leaves the csti_configuration table poorly configured. If this is the case, the following two steps must be done to fix the problem.

  2. Open SQL Query Analyzer or SQL Enterprise Manager. Run the following query:

    1. USE IntelAMT
                SELECT Props_script_path, use_props_script
                FROM csti_Configuration

  3. Check the path and make sure it matches the remote and local Intel SCS install. Also verify that the use_props_script is set to 1, which means ‘True' (0 means ‘False'). Now run the following query if they need to be updated, but take note to change the path to match your environment:

    1. UPDATE csti_configuration
                SET props_script_path = ‘C:\Program Files\Altiris\OOBSC\oobprov.exe'
                SET use_props_script = 1
                WHERE configuration_id = 1

  4. Everything should now be in place for the new Intel SCS install to work with systems being provisioned, including all maintenance and post-provisioning actions.

  5. As one last check, let's ensure the Intel SCS installation registered itself in the IntelAMT database. If this part has failed the service AMTConfig will not be able to start, throwing an exception about database connection in the Application Event Log.

  6. On the Database Server, run the following query:
         USE IntelAMT
         SELECT * FROM csto_servers

  7. You should have one entry for every Intel SCS install you've completed, even the original OOB install if you also installed Intel SCS originally on the NS. Note the server_name column to contain the name of the server you installed Intel SCS onto. If it is not here the problem generally stems from SQL database access rights on the SQL Server. Please ensure the account you are using has rights to create a new database, or update an existing one.

 

Fixing a Previous SCS Install

If you've already install SCS, and provisioning is not occurring (see the following article group for troubleshooting steps: http://juice.altiris.com/book/3699/troubleshooting-altiris-manageability-toolkit-vpro-technology), we need to go through the steps to provide the remote Intel SCS Install the necessary configuration to properly work with the remote IntelAMT database and Notification Server.

 

 

 

 

 

The following steps provide the right changes to ensure everything is setup correctly:

 

 

  1. Log onto the Server with the NS Application ID.

  2. Uninstall the Altiris Agent from the system. If it is not installed simply continue through the steps.

  3. Check to ensure the account that is running the Intel SCS service, AMTConfig, has admin rights to the NS. If it does not, add the user to the Admin group on the Notification Server.

  4. Check to ensure the Application ID has local administrative rights to the server Intel SCS is installed on.

  5. Install or reinstall the Altiris Agent, ensuring it is pointing to the NS where Out of Band Management is hosted.

  6. Once the five preceding steps are completed successfully, move to Database server and launch SQL Enterprise Manager against the IntelAMT database.

  7. Run the following query:
         USE IntelAMT
         SELECT Props_script_path, use_props_script
         FROM csti_Configuration
    !csti_configuration.jpg!

  8. Please note the following details from the resulting line:

    • use_props_script - This column needs to be set to TRUE (1). If this is set to 0 no provisioning attempts will even be executed. I've seen this set to 0 at times.

    • props_script_path - This value is passed to the Intel SCS service that's available to run oobprov.exe. This must be the same location on both the NS and the remote server.

    • props_script_timeout - This timeout should be set at 180.

  9. If the values are not set right, use the following query to update the table to have the correct values (note that the props_script_path may be different in your environment. If so, change the query to match your installation setup):
         UPDATE csti_configuration
         SET props_script_path = ‘C:\Program Files\Altiris\OOBSC\oobprov.exe'
         SET use_props_script = 1
         SET prop_script_timeout = 180
         WHERE configuration_id = 1

  10. Once the above changes have been made, restart the AMTConfig service on the local Intel SCS Server to have all cached items dropped so the changes are filtered down properly.

 

Functional Intel SCS

The immediate question after installing and/or fixing an existing install of Intel SCS is are things working correctly? Time will definitely tell, but if you want to know immediately you can use the following process to check the workability of the install:

 

  1. On the Intel SCS server, go into the Services Manager within Administrative Tools. Is the AMTConfig service running? If not, try to start it. Also check the Event Log for failures. If it stays running, it can successfully start and then connect to the IntelAMT database. Note that if it starts but then stops a minute or two later, the database is likely unreachable by the service.

  2. On the Notification Server, browse in the Altiris Console from View > Solutions > Out of Band Management > Configuration > Provisioning > Logs > Actions Status. Do you see any successful Provisioning requests since the time you finished configuring the Intel SCS install?

  3. If possible, manually configure a system to provision and see if it goes through. The reason the existing ones trying to provision may not work is due to IP Address changes that make it impossible or SCS to connect back to the system. New Hello Packets will remedy this situation in the long-term.

 

Conclusion

These processes should allow you to properly install and configure Intel SCS on a server that is not where the Notification Server and Out of Band Management are installed and running.