Are there any general best practices for running 2X ApplicationServer on Windows Server 2012? It seems that launching published appilcations takes an unreasonable amount of time. On our Windows Server 2003 terminal server running 2X, things are quite snappy. Are there perhaps some changes I can make to authentication levels that might help, for example? Any suggestions would be greatly appreciated!
Anyone? This is so strange. I have 2X installed on two Windows Server 2012 RDS servers, both pretty much configured identically from a Windows standpoint and from a 2X standpoint. They are running the same build of 2X, the agents and gateways are configured exactly the same, they have the same Windows Updates installed, etc. I am also using the exact same 2X Client Policies on both. I have also tried using client-side configurations rather than Client Policies. One of them takes about eight seconds to launch a published app. The other one takes about 30 seconds. Even just doing a right-click/refresh on the connections from the client yields drastically different results. One is almost instant, and the other one takes about 17 seconds to come back. If I establish a direct RDP session to these same two servers using the same credentials, I connect very quickly to both. Does anyone have any insight into what might be going on here? Any suggestions on what I might check? Thank you!
The issue you are experiencing appears to be an authentication issue. If you have a lot of filtering rules or a complex AD you should try the latest beta and switch the filtering rules to SID format. Are the published applications on the same server you are connecting to via direct RDP? Which connection mode are you using? PS: Replies on the forum are not usually instantaneous. If you want time-critical replies try contacting the actual 2X Support
Thank you. You nailed it. I had an AD security group specified in the filering rules for the application in question. That group is a master group that contains groups from the rest of our AD domains. Do you think performance would be better if I explicitly added every user to the filtering list rather than the group? Or is installing the latest beta that uses the SID format the only way this is going to improve? As this is going into production, I hesitate to use a beta product. Are there any other best practices for filtering an application that will be published to many users in several AD domains? And I realize that forum replies are not instantaneous. That's why I waited a couple of days before posting again. This forum doesn't seem to receive much traffic, and sometimes I never receive a reply. I apologize if I came across as impatient, but this is truly an urgent matter for my company. As such, I had opened a support case yesterday as well (WDZ-445-42885). If you are able to help me further in this thread, I will simply close that case. Thanks!
Apparently, the convert to SID option was introduced in ASXG v10.6 so you could try that. To use the SID format in 10.6, right click on the root publishing tree and click on convert filter to SID.
Hi dsmithpdx, I installed 2XASXG latest build on Windows Server 2012, enable RDS roles, disable firewall and try to launch publish apps . My problem is any published apps cannot be open from client side. I can see each and every apps that I published, that mean the connection to the server is established. I'm not sure whether the problem comes from the RDS or the 2X itself. Would you care to share some tutorial and steps on how to actually configure the RDS on Windows Server 2012 with 2X ASXG. I've done this several times on Windows Server 2008 but I have no problem with that. Thank you in advance.
ASXG v11 on Server 2012 R2 App launch speed results with filtering options. SID filtering to AD Security Group = 12 / 13 seconds. SID filtering to AD user = 4 / 5 seconds.
Was there a resolution to the issue with delay in login when dealing with security Groups Users? This would be good to know, as we deal in Groups vs. Users in our 2x environment.
