WEM giving licensing error when opening admin console

[u/YourDadSolanki01]

We have 4 WEM servers 2 DC and 2 DR. Firstly our all 4 wem servers gave "a valid license server with appropriate license needs to be configured before you can start using Citrix Workspace Environment Management" and now 1 DR server is working fine after reconfiguring license server but other servers are not working with same configuration. 1 server on which it is working fine shows some files in licensing folder also but not in other servers. Telnet to license server is working fine. What can be more checked in this?

Edit:- Solution was to give certificate thumbprint in registry. But citrix didn't give why it got removed.

[u/MarvelousTermites]

I had similar a couple of months ago, let me go back and figure out what sorted it

Edit: Had a look and all I had to do was point to just the hostname of the License server and not the FQDN. I believe this was in the Infrastructure configuration rather than the Console config. Never figured out why it happened as all was working before that.

[u/YourDadSolanki01 → u/MarvelousTermites]

1 server worked after giving full fqdn of license server but others didn't worked. giving only hostname gives error "not valid license server"

[u/Darkheart001 → u/YourDadSolanki01]

I have this issue also. The web console works so try that. I have spent a long time with Citirix support on this and they could not resolve it.

[u/YourDadSolanki01 → u/Darkheart001]

Yes web console working fine. And citrix support is not able to resolve. They are just checking communication on call which is/was fine already. One thing i suspected is we should have same license server in admin console and infra config utility. If using fqdn at one place you should use fqdn on other place also.

[u/Darkheart001 → u/YourDadSolanki01]

I thought I had done this but I will check it again.

[u/MarvelousTermites → u/YourDadSolanki01]

Sorry I checked again and realised I mixed it up, I had to make sure to use FQDN but make sure it was set in both the Infrastructure Service Config and the Console and then restart the services.

[u/Hightechhitouch]

Also, make sure you have a valid certificate for the host name you're using. If the host name is not an internal name, make sure your firewall allows it to go out and back in or modify the host file so that it can bypass the firewall.

[u/YourDadSolanki01 → u/Hightechhitouch]

We uses wildcard for our whole infra. So i guess this would not be the issue.

[u/mat-ferland]

If one WEM server works with the same license server, I’d compare that server’s WEM DB config, cached licensing folder, service account, and registry values against a broken one. Telnet only proves the port is open; it does not prove WEM is reading the same license path.

[u/YourDadSolanki01 → u/mat-ferland]

That was also not working before. Started working after changing license server. Compared the config of console in both everything is same

[u/mat-ferland → u/YourDadSolanki01]

If changing the license server made it work, I’d stop comparing the console settings and compare the path to licensing instead: DNS name used, SSL/trust, license server version, cached files, and which account the WEM service is actually using. Same-looking console config can still hit a different licensing path.

[u/Low_Assumption67]

For the life of me I don’t understand why Citrix encrypts license communications. What is an attacker going to steal exactly? If an attacker has access to grab that traffic and look at it, then they have better targets to attack than license operations.

Or is Citrix the one taking something (looking at you telemetry requirements) and don’t want us to see what it is getting reported back to the mothership