AP 11.8 Configuration Manager "A referral was returned from the server"

Products

• Automation Point

Issue/Introduction

New Automation Point (AP)11.8 install on new Windows Server 2022.
After successful install unable to launch the Configuration Manager as a user who has administrator privileges.

C:\Program Files (x86)\CA\CA Automation Point\Bin\cfgMgr.exe
A referral was returned from the server.

Environment

Automation Point Release 11.8

Cause

Support could not recreate the problem in house.
They installed AP 11.8 on a clean Windows Server 2022 VM and the Configuration Manager started successfully. Also the same result after they installed the first patch 11.8.0.1 (LU19686).

From searching the error with Google it seems the root cause could be security related. They provided these suggestions:

1. Modify User Account Control (UAC) Settings 
Temporarily lowering UAC settings can resolve the issue, but remember to restore them afterward. 
Open the Control Panel and go to User Accounts > Change User Account Control settings.
Move the slider to Never notify (the lowest security level).
Click OK and restart your server.
After running the program successfully, restore the UAC slider to its default level. 

2. Disable PKI Signature Checks via Group Policy 
You can disable the requirement for applications requesting admin privileges to have a valid PKI signature. 
Run gpedit.msc and navigate to: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.
Set User Account Control: Only elevate executables that are signed and validated to Disabled.
Restart the server. 

NOTE: The properties of file C:\Program Files (x86)\CA\CA Automation Point\Bin\cfgMgr.exe shows no Digital Signatures tab so it is unsigned. Therefore #2 might possibly be relevant.

Resolution

The user made both suggested changes and the problem was resolved. They are unsure which change resolved the problem or if both were required.

Additional Information

AP Engineering subsequently advised the AP 11.8 binaries should have been digitally signed as part of the release process.
So that is the likely root cause and was circumvented with #2 above.
AP Engineering will provide new binaries which are digitally signed at the next AP 11.8 service pack release.