Problem #1 XenApp 6
We were having an issue with the ability to stream apps to servers or clients. The error message was non specific. One of my coworkers found an obscure article talking about a response from the server of 20000 when running qfarm /load. Turns out, if the server displayed this particular load response, it meant that the licensing was incorrect and apps would not stream.
They will continue to work properly from a standard installed and remotely run model, but will error out when streamed. In our case, the newly created XenApp 6 licensing server policy had the “default” checkbox checked. Which means that it was using the license server that we had typed in during installation. The licensing server we had typed in was for our XenApp 5 farm and was the wrong version for XenApp 6.
It had given us a error message, but we had modified the policy to use the new license server. So, we figured all was well, nope….. Because the default check box was still selected, it was ignoring our new entry. Once we unchecked that box and rebooted the server things worked and the server no longer displayed the 20000 in the command line.
Two of the servers still wouldn’t change their licensing status. For one, the solution was we had to remove it from the farm and then rejoin. Once that was done it worked as it should. The other server was fixed when we went into the policies area and specified the version we were running.
Problem #2 Xen App 5
We were also unable to stream apps on our XenApp 5 farm. All licensing was correct, streaming app profiles done correctly, etc. However, when the app was published, the drop down box was left alone because it appeared you only changed that box when the option directly next to it was selected.