After some testing of the failed vDesktop, we were unable to find anything wrong with the installation of the agent.
Finally, the primary connection server was bounced and the vDesktop agent was recognized. This is not a good story, saying that when a new vdesktop is provisioned, the only way to add it to a pools is to restart the primary connection server. More testing is needed to validate this.
No comments:
Post a Comment