Correct Identification and Connection
In a multi-server implementation, where the web application server is a distinct
        machine from the batch server, the fully qualified domain name of the batch server must be available so that both servers can access the Microsoft Message
        Queuing (MSMQ). The name is saved in the ComplianceSetting table of the
          compliance database, as BatchSchedulerHostName. 
If this record is incorrect, it is best practice to re-run the PowerShell installation
        scripts with the correct data. However, you can also update the
          ComplianceSetting table directly. 
In a multi-server implementation, on each server in turn, use the following command to determine the host name and default DNS suffix of the current machine:
ipconfig /allipconfig command). Ping tests reachability as
        well as DNS resolution. If the ping is not successful, remedy any DNS issues or barriers to
        connectivity (assuming that ping itself is not blocked).- Wait ten minutes for the ancillary IIS services to restart (this is the least disruptive in a production environment)
- Restart IIS manually (this restarting approach may be faster in a test environment).
localhost as the batch server name
          when configuring other server functionality.FlexNet Manager Suite (On-Premises)
2021 R1