I assigned the stack I built on the 2.6 template in the 2.6 manager with the 2.6 agent to my user logged into a 2.6 agent workstation. Could it be that best setup is View 6.1 with VSphere 6.0? Do you know what the new version is tested with? And yes i know thet VSphere 6.0 isn't even officially supported. As Seattle said, i love the technology and are a very happy user but it seems this version has been pushed out to fast due to 6.1 view being released and Appvolumes needed to be ready for that. I'm not quite sure but it seems there are a few loose ends on the 2.6.0 version. The only issue we are having is when logging into a 2.6.0 agent/manager desktop with a 2.5.0 or 2.5.1 Writable volume template the wtritable volume doesn't get attached and login takes more than 3 minute s(in logging we see a timeout on the assignment of exactly this 3 minutes and login without a profile takes over 1 minute which is normal behaviour). We are using VSphere 5.1 though, might this be the issue? We are able to assign appstacks to AD groups. We are also using 2.6.0 manager with a 2.6.0 agent the appstacks being made with 2.5.0 (not even the 2.5.1 template) and we are not seeing this issue./ I LOVE the technology, but can't afford to break everything by updating or be stuck on an older version just because I happened to build my stacks at a given point in time.
#HTTP ERROR 500 VMWARE HORIZON CLIENT UPGRADE#
It feels like more than any other feature that could be added, the upgrade mechanisms and procedures need to be addressed first. Now I have no idea what options I have, but this is very scary, as it's only the 2nd real release. So even with a 2.6.0 Manager and Agent, and an app stack built on the 2.6.0 template with a 2.6.0 Agent, I'm getting Error 500. I uninstalled the 2.5.2 Agent, rebooted, installed the 2.6.0 Agent, rebooted.
Put a VM with the 2.5.2 Agent into maintenance mode, logged in via vCenter console as the user that was assigned the app.
Installed the app, everything good so far. I created a new stack with the updated template. I updated my provisioning machine with the 2.6.0 Agent and updated the templates. I left the Agent in my linked clones at 2.5.2.