Install ControlSuite on multiple nodes

The following section provides the steps needed to install ControlSuite on multiple server nodes. This example describes multinode setup with AutoStore and Output Manager. Prerequisite: an operational server node with AutoStore and Output Manager installed.

To install ControlSuite on multiple nodes, do the following:

  1. Start the ControlSuite Installation Assistant on the server machine that will serve as your first node.
  2. Click Get Started on the Welcome page.
  3. A Questionnaire page opens asking Do you want to check for updated Install Assistant files? Select Yes or No and then click Next to continue.
    If "Yes" is selected, any updated Install Assistant configuration files will be downloaded from the software download server. The files that require updating are not overwritten, and the system creates a backup file with a .bak extension for the older files. Once any updated files are downloaded, click OK on the popup message to continue with the installation.
    Select "No" to continue with the installation without checking for updates.
  4. When asked Do you want to create an offline installer package? select Yes or No and then click Next to continue.
    If "Yes" is selected, a Summary page opens with Offline installer package location field and the package name. Click Next to continue. The Install Assistant will download all ControlSuite component installers and create an offline installer package, but will not install ControlSuite. The Results page opens displaying that the offline installer package was successfully created. Click Finish to continue. See Create an offline installation package for details.
    If "No" is selected, the installation process continues.
  5. Depending on whether ControlSuite is already installed on your system, or if you are performing a fresh installation, one of the following questionnaire screens opens.
    • ControlSuite is already installed on this system. What would you like to do?
    • Do you want to use the Install Assistant Wizard or manually configure the server?
  6. When asked ControlSuite is already installed on this system. What would you like to do? Select one of the following options and then click Next to continue.
    • Upgrade to a newer ControlSuite version or modify current installation. If you select to upgrade to a newer version or to modify a current installation, a Summary page opens listing the currently installed components. Click the Advanced link to modify the components to be installed.
    • Uninstall ControlSuite. All ControlSuite components are uninstalled and removed from the server. Click Yes on the popup message to uninstall ControlSuite and to continue with the installation.
      The Uninstall option only removes the ControlSuite components. Go to Uninstall ControlSuite to uninstall the components and remove configuration data from a previous installation.
  7. When asked Do you want to use the Install Assistant Wizard or manually configure the server? select Manually Configure and click Next.
  8. An Advanced page opens displaying the available installable ControlSuite components. Select Security Framework and click Next to continue.
  9. Click Next in the Summary page.
  10. A Prerequisites page opens displaying the status of the system requirements needed to install and run the selected components.
    It is recommended that requirements relevant for your installation show a green checkmark.
  11. The Results page opens displaying that the installation was successful. Select the Open Configuration Assistant option and click Finish to continue.
  12. Click Next on the Certificate Management page. The Binding Ports window opens updating the IIS certificates. If successful, there should be a green check-mark beside each item. Close the Binding Ports window when done.
  13. A Core Services page opens showing the Distributed Database Service. Click Next.
  14. An Authentication and Security page opens. Create Security Admin User credentials for the security admin to have access to configure ControlSuite security registrations. Enter the Security Admin Credentials Username and Password.
    The Username must be in the form of domain\username. However, the domain is only utilized for ControlSuite, and is not associated with any AD Domain.
  15. Specify a Datacenter name. Click Apply, and then click Next to continue.
  16. The Initializing Security Framework window opens showing progress. Close the window when done.
    You have successfully set up and configured the first node.
  17. Repeat the above steps for the next node until the point when you have the Authentication and Security page open in the Configuration Assistant.
  18. Select the checkbox Connect to an existing server. In the Host Address field type the name of the first node server. Specify a Port.
  19. Type in the Security Admin User credentials you created previously and click Login. A green checkmark is shown next to the Login button on successful login.
  20. Specify a Datacenter name. Click Apply, and then click Next to continue.
  21. The Initializing Security Framework window opens showing progress. Close the window when done.
    You have successfully set up and configured the second node.
  22. Start the Configuration Assistant On the machine where you previously installed AutoStore and Output Manager. Navigate to the Authorization and Security page to connect to the first node.
  23. In the Host Address field type the name of the first node server. Specify a Port.
  24. Type in the Security Admin User credentials you created previously and click Login. A green checkmark is shown next to the Login button on successful login.
  25. From the Datacenter list choose the datacenter name corresponding to the first node. Click Apply, and then click Next to continue.
  26. The Initializing Security Framework window opens showing progress. Close the window when done. Click Next.
  27. A ControlSuite Enrollment page is shown. Select all components and choose Enroll.
  28. The Enrolling Progress window opens showing progress. Close the window when done. Click Next.
  29. A Universal Print Integration page opens.
    1. Select one of the two registration options:
      • Register Azure Universal Print application at a later time. The Universal Print option will not be available until the Universal Print application is registered. Click Next to continue configuring ControlSuite without Universal Print. See Register the Universal Print application manually in Azure AD.
      • Register Azure Universal Print application now. You need a valid Azure subscription to register this option.
    2. If you select to register Azure Universal Print now, choose one of the following options and enter the required information:
      • I have already registered the Universal Print application on Azure portal and will be retrieving required information from the Azure portal.
        • Tenant Id - This is the GUID that refers to a single instance of Azure AD.
        • Client Secret - This is the string that the application uses to prove its identity when requesting a token.
        • Application Id - This is the GUID that uniquely identifies the application in the Microsoft identity platform. Click the Test button to ensure the ID is valid.
      • I will be registering the Universal Print application here using tenant and subscription IDs.
    3. If you select to register the Universal Print application here, click Open Azure portal to continue, sign in with your Azure AD credentials, and do the following:
      • Select Azure Active Directory and copy the Tenant ID.
      • Select Home > Subscriptions, and then select the active subscription for Universal Print to copy the Subscription Id.
    4. Return to Configuration Assistant. The Tenant Id and Subscription Id fields should be pre-populated. Enter the Client Secret and click the Register button to register this in Azure AD.
      • Tenant Id - This is the GUID that refers to a single instance of Azure AD.
      • Subscription Id - This is the GUID that links to your Azure account.
      • Client Secret - This is the string that the application uses to prove its identity when requesting a token.
      • Application Name - This is the user-facing display name of the application. For example, ControlSuite.
      • Application Id - This is the GUID that uniquely identifies the application in the Microsoft identity platform. Click the Test button to ensure the ID is valid.
    An Azure Universal Print Application Registration window shows the configuration status. Close the window when done, and click Next.
  30. A Services page is shown. Select the Service Name checkbox above the list and choose the Start option next to For selected service(s):. Click Next.
  31. A Licensing page opens. Ensure that License server location points to the server that manages your licenses. Click Next.
  32. An AutoStore Licensing page opens. Verify your licensing preferences. Click Next.
  33. An Identity Provider page opens to set the Azure Active Directory (AD) connection parameters.
    A Load Identity Provider Configuration window opens to load and display the current identity provider configuration. When successful, there is a green check-mark beside each item. Close the window when done.
    1. Select the Configure Azure AD for ControlSuite checkbox and enter the required information.
      • Discovery endpoint URL: The discovery endpoint can be used to retrieve metadata about your Identity Server. For example, "https://login.microsoftonline.com/(tenant)/v2.0".
      • Application ID: The application ID is created when ControlSuite is registered in Azure AD. This GUID uniquely identifies the application in the Microsoft identity platform.
      • Client secret: This is the string that the application uses to prove its identity when requesting a token.
      • Domain name: The domain name is populated after validating the registration.
      • Administrative role: This is the name of the Azure AD application role needed for administrative permissions in ControlSuite. The acquired Azure AD token can contain this value. It is set to 'ControlSuite.Admin', and it cannot be updated.
    2. Click the Validate registration button to try to connect to the configured Azure AD tenant and check the required permissions. A Validate Azure AD Configuration window shows the progress. Close the window when done.
    3. Click the Update registration button to re-validate the connection parameters.
    4. Click Apply.

    If the connection parameters are validated, press the Apply/Next button to save the parameters. A Save Identity Provider Configuration window shows the progress. Close the window when done.

  34. Ensure that the System Administrators page shows the current user inserted under the Output Manager database. Click Next.
  35. A Launch Applications page is shown. Select what to start.
    AutoStore:
    • Process Designer
    Output Manager:
    • Console
    • Server Manager