4.1 Considerations for Installing Core Services

Before installing Core Services, review the following considerations:

  • The installation process for Core Services includes the infrastructure for the Web console.

  • The installation program automatically installs and registers a Windows agent on the Core Services computer. You must specify a run-as account for the Windows agent service. The account requires specific permissions, such as the ability to deploy agents to remote computers. For more information about the Windows agent service and permissions, see the NetIQ Secure Configuration Manager Windows Agent Installation and Configuration Guide.

  • Secure Configuration Manager supports IPv4 and IPv6 addresses, but uses IPv4 addresses for communication among the console, Core Services, and the Secure Configuration Manager database. The Core Services computer must be configured for IPv4 addresses at a minimum. Alternatively, you can set up the Core Services computer as a dual-stack host to support both IPv4 and IPv6 addresses.

  • In addition to the files installed in the Program Files folder, the installation program installs a scmnss folder in the root directory on the Core Services computer. Do not remove the scmnss folder or the files within the folder. Secure Configuration Manager requires these files for FIPS communication.

  • If you do not enter a valid license key, the installation program automatically applies a 30-day trial license. You can change the license key any time after installing Secure Configuration Manager. For more information about license keys, see the Help for the Core Services Configuration Utility.

For more information about your server setup, see Deployment Considerations.