Managing Servers - Adaptive Applications - BlueCat Gateway - 21.1

BlueCat Overlay for Microsoft

Product name
BlueCat Gateway

Before you can begin to import information into Address Manager, you must add the Windows Servers to the BlueCat Overlay for Microsoft.

To add Windows Servers

  1. Log in to BlueCat Gateway.
  2. Under AVAILABLE ACTIONS, click Manage Server.
  3. Under Server Credential, enter the following information:
    • Configuration—select the BlueCat Address Manager Configuration where the Windows Servers will be added.
    • Windows Server—type the name of the server that you are adding. If you are updating an existing Windows server, select the name of the server from the list of servers.
    • IP Address—enter the IPv4 address of the Windows Server.
    • Server Type—select Windows DNS or Windows DNS/DHCP. The servers represent the following:
      • Windows DNS: Add the Windows Server to Address Manager as the "Other DNS Server" profile. Select this option if the server is only used for DNS operations.
      • Windows DNS/DHCP: Add the Windows Server to Address Manager as an unmanaged "BlueCat DNS/DHCP - 100-D" profile. Select this option if the server is used for DNS and DHCP operations.
        Note: You can update the Server Type later if the role of the server changes.
    • Hostname—enter the FQDN of the Windows Server. If the server is a standalone Windows Server and not a member of the Active Directory Domain, enter the hostname with the DNS suffix. For example, <server_name>.<dns_suffix>
    • Username—enter the username of the account that will be used for retrieving and pushing changes to the Windows Servers.
      Note: This account must have the necessary privileges to read DNS and DHCP information from the Windows Servers, and execute commands in PowerShell.
    • Password—enter the password for the associated user account.
    • PowerShell Session Configuration Name (Recommended)—enter the PowerShell Session Configuration name.

      By default, all commands run by the user account are run in default PowerShell Session. Windows Server Administrators can provide specific access and controls to user accounts by creating a new PowerShell Session Configuration on Windows Servers. Additionally, certain actions, such as Windows DHCP Failover, require this configuration to be set to ensure that commands are executed correctly.

      To create a new PowerShell Configuration, execute the following command on the Windows Server:
      Register-PSSessionConfiguration <CONFIG_NAME> -RunAsCredential <USER_NAME> -NoServiceRestart -Force
      • CONFIG_NAME represents the name of the PowerShell Session Configuration.
      • USER_NAME represents the username for commands to be executed in the session.

      For more information on PowerShell Session Configuration, refer to

    • Windows Relay for Remote PowerShell—enter the hostname or IP address of the Windows Server that can be used as a proxy when communicating with this server.
      Note: This can be used in scenarios where the user does not have PowerShell permissions or the server does not have PowerShell enabled.
    • Click the Enable SSL checkbox to enable SSL connections to the Windows Server.
  4. Click Test to verify that the server details are correct. This also retrieves the PowerShell Session Configurations available on the Windows Server that was selected.
  5. Click Add to add the Windows Server to Address Manager.
Once you have added the Windows Server, repeat the steps to add additional Windows Servers to Address Manager.