Thin Client devices that work to enumerate applications on older version Netscalers do not work on newer ones.
A trace shows that after the client sends POST with credentials, the Netscaler responds with a redirect to /cgi/setclient?wica (normal).  Along with this redirect will be the Set-Cookie: NSC_AAAC=xxxxx.  This is the user's login cookie and should be used by the client from here out.  Now, when the client performs the GET request to /cgi/setclient?wica, we would normally expect to see the response including the session profile information on the store location (/citrix/store/xxx).  In this case the response includes a 302 redirect which sends the user back to /vpn/index.html.
 

Upgrade thin client firmware to the latest version.  
Check with the vendor to determine version compatibility with Netscaler Gateway.

---

Problem Cause

The client is not using the NSC_AAAC cookie when performing the GET for /cgi/setclient?wica to Netscaler.  This forces the Netscaler to redirect the user back to login instead of returning the necessary session profile information for enumeration.

Thin Clients version compatibility with Netscaler is managed by the vendor and not Citrix.  The thin client firmware may be intended to only be compatible up to a certain version of Netscaler.  When the Netscaler is upgraded or another one is used that is a higher version, the thin client may no longer be compatible.

These thin clients may be able to enumerate with an older version Netscaler or before an upgrade.