|
Session Preparation |
Session prepare request from Broker service to VDA failed (typically comms error). |
|
Registration Timeout |
VDA did not register in time after being powered on for session launch. |
|
Connection Timeout |
Client did not connect to VDA after VDA was prepared for session launch. |
|
Licensing |
License request failed (typically no license available). |
|
Ticketing |
General licensing-related failure. |
|
Other |
General catch-all for problems between client and VDA that can’t otherwise be identified. |
|
General Fail |
General catch-all for problems during the initial brokering operation that can’t otherwise be identified. |
|
Maintenance Mode |
Machine or delivery group in maintenance mode. |
|
Application Disabled |
Application disabled |
|
License Feature Refused |
Feature being used is not licensed (e.g. license doesn’t allow use of multi-session VDAs). |
|
Session Limit Reached |
No more sessions allowed (e.g. launching second session on VDI VDA). |
|
Disallowed Protocol |
Resource doesn’t allow protocol requested by session launch. |
|
resource Unavailable |
Resource has been removed/disabled since enumeration. |
|
Active Session Reconnect Disabled |
Session is already connected to a different endpoint but session stealing is disabled. |
|
No Session to Reconnect |
Specified session could not be found during reconnect. |
|
Spin up Failed |
VDA could not be powered-on for session launch. |
|
Refused |
VDA actively refused session prepare request. |
|
Configuration Set Failure |
Failed to send required configuration data to VDA prior to session launch. |
|
No Machine Available |
No machine available for launch (e.g. all shared VDI machines in group are in use). |
|
Machine Not functional |
Non-power-managed assigned machine not registered. |