1Y0-201 · Question #140
Scenario: A Citrix Administrator receives instructions to reallocate XenDesktop licenses. After the administrator downloads the license file, users are unable to connect to the desktops. Why are users
The correct answer is A. The administrator specified the wrong Hostname.. When reallocating Citrix licenses, the hostname entered during allocation must exactly match the license server's hostname; a mismatch causes the license server to reject the license file, preventing users from connecting.
Question
Scenario: A Citrix Administrator receives instructions to reallocate XenDesktop licenses. After the administrator downloads the license file, users are unable to connect to the desktops. Why are users unable to connect to the desktops?
Options
- AThe administrator specified the wrong Hostname.
- BThe administrator reallocated the incorrect product key.
- CThe administrator specified the incorrect MAC address.
- DThe administrator changed the .LIC filename prior to saving it in the MyFiles folder.
How the community answered
(44 responses)- A82% (36)
- B5% (2)
- C5% (2)
- D9% (4)
Why each option
When reallocating Citrix licenses, the hostname entered during allocation must exactly match the license server's hostname; a mismatch causes the license server to reject the license file, preventing users from connecting.
Citrix license files are bound to the specific hostname of the license server during the allocation process on citrix.com; if the administrator enters an incorrect or mismatched hostname, the generated .LIC file will not be recognized by the actual license server, making all licenses unavailable and blocking user connections.
Reallocating an incorrect product key would result in the wrong license type or edition being active, but existing valid licenses for the correct product would still allow connections rather than blocking all users.
Citrix license allocation is bound to the server hostname, not a MAC address; MAC address is not a parameter used in the Citrix license generation or binding process.
While the .LIC file must be saved with its original filename in the correct directory, the question states the file was downloaded and then users could not connect, making a filename change less likely than a hostname mismatch during the online reallocation step.
Concept tested: Citrix license reallocation and hostname binding
Source: https://docs.citrix.com/en-us/licensing/current-release/admin-no-console.html
Topics
Community Discussion
8
Bao N.Jun 26, 2026The answer is A, the administrator specified the wrong Hostname. Citrix licensing ties the license file to a specific License Server by hostname, so if that hostname does not match the actual server name exactly, the License Server will reject the file entirely and users get blocked at connection. This is one of those questions where B and C feel tempting because reallocation and MAC addresses sound technical enough to be the culprit, but Citrix XenDesktop licensing does not bind to MAC addresses, and as long as you are reallocating the right product edition, the key itself is not the issue. The filename in D is a distractor too, the .LIC filename does not have to match anything specific as long as it lands in the right directory, so hostname mismatch is the classic gotcha on this topic.
Jovan I.Jun 28, 2026Hostname match is dead-on, but worth adding that the check is case-sensitive on Linux-hosted License Servers, so a capitalization difference alone will cause the same rejection without any obvious mismatch at a glance.
Jovan I.Jun 26, 2026Tripped on this one myself during the actual exam because I second-guessed the hostname angle and almost circled C, but then I remembered that when you reallocate a license file the binding is to the License Server hostname, not a MAC, so a mismatch there kills checkout requests before they ever reach the desktop broker. Glad I caught it before submitting.
Thekla S.Jun 28, 2026The hostname bind is the classic gotcha, though worth noting that if the License Server itself is behind a load balancer or has had a FQDN change without a corresponding re-host, the feature strings inside the license file become invalid too, which is a separate failure path that looks identical from the client side.
Hiroshi T.Jun 26, 2026The correct answer is A. When you download a reallocated license file from MyCitrix, the file is bound to the hostname you specify during the reallocation process. The License Server uses that hostname to validate the license, so if the administrator entered a hostname that does not match the actual License Server hostname, the server will not be able to check out licenses and users will be blocked from connecting to desktops. The official Citrix Licensing documentation is clear that hostname binding is set at reallocation time and cannot be corrected without returning and reallocating the license again with the correct hostname.
Thekla S.Jun 26, 2026The hostname binding is everything here, because the license file is cryptographically tied to the server name you specify at allocation time, so if that value is wrong the license server simply will not recognize the file as valid. Double-check that the hostname in the portal matches the actual FQDN or NetBIOS name of your Citrix License Server before you download.
Hiroshi T.Jun 29, 2026Thekla is right that the hostname must match, but worth adding that on Windows the License Server defaults to the NetBIOS name, so if your environment resolves by FQDN you need to explicitly enter the FQDN during allocation, not just accept the default, or the Citrix Licensing Service will reject the file at startup per CTX114501.
Mateus R.Jun 25, 2026Honestly my first instinct was D, because I figured somebody probably renamed the .LIC file and that broke it. But then I thought about how a Citrix license server actually works, and it clicked. Think of the license server like a house with a specific mailing address, and the license file is a piece of certified mail that can only be delivered to that exact address. When you download a reallocated license from MyCitrix, the file is cryptographically bound to the hostname of the license server you specified during the reallocation process, so if the administrator typed the wrong hostname, that license file is basically addressed to a house that does not exist on your network. The license server receives it, looks at the binding, sees the names do not match, and refuses to serve licenses, which is exactly why users cannot connect, even though the file itself looks perfectly fine sitting in the MyFiles folder.