Looking for interesting Citrix Problems
I am working on some blog entries and content for Citrix CDN and was curious what you guys thought.
If you have time, please leave some comments on problems or suggestions of things you would like to see. Specifically I am looking for some “real” world scenarios that I can present and provide solutions for.
- Customizing WI to support multiple secure gateways. This is a very real world scenario that is simply not supported by standard web interface.
- Creating custom xml broker requests for getting ps address by user + app, and requests to STA to retrieve ticket ids and sta id. Web Interface libraries are simply way too convoluted and do not support more advanced scenarios.
- How to best collect Citrix session data via MPSSDK . Session enumeration can be slow when trying to retrieve applications in session and there are numerous work arounds to getting these scenarios to scale with number of servers, sessions per server. Would be interesting to know the merits of pulling out session data per server vs session per server per farm vs session information via the xml services. The fastest solution for me has been to use the data collectors and merging of session data between zones.
- One that I haven’t been able to figure out is how to test if a session’s connection to a client has been severed when session reliability is being used.
- Generating a Citrix reconnection session id via MPSSDK from the session id structure. Xml services give the correct session “name” to specify when reconnecting but with MPSSDK you have to do some bit magic to get the same thing.
All of these are possible but were definitely challenging and would be awesome if Citrix gave some guidance because reverse engineering things can definitely backfire sometimes.
When and why do you late bind MFCOM objects? In your scripts I saw both early and late binding.
Frank, can you provide some context for the readers? Examples?