![]() ![]() Apparently if the server can not communicate with the SQL XenApp datastore at a magical moment during boot up, it looks in the registry and does not apply the policy. No one could log on that morning!! Another reboot fixed it. After one of the 3am reboots we perform each night it reverted back to looking for CITRIX1 as the license server. ![]() Fast forward a few days, now the server is in production. Rebooted again and this time it did not complain and was working fine. I checked my XenApp computer policy and it still said the license server was XENAPP-LS. Date: License type: NFR Grace period: 30. License sharing for the same client device: allowed Serial. Update: Version 1.1 supports XenDesktop Licenses in Addition to XenApp Licenses. It has been upgraded to 11.12.1 and the 6.5 farm can acces. ![]() Just trying out Xenapp/desktop 7.6 but having an issue connecting to my license server in Studio. On the next reboot it popped up a message saying 'Citrix License Error: Citrix XenApp cannot contact the license server CITRIX1'. Problem Well, as I was installing things I needed to do a reboot. I removed the license server off of CITRIX1. Did a reboot and bingo, good to go! It starting use the new licenses. I figured out you have to create a XenApp Computer Policy and add the following setting 'License Server Host Name' with the appropriate name of the new license server (i.e. I wasn't exactly sure how to tell the CITRIX1 XenApp server to point to the new XENAPP-LS license server so did some Google searches. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |