Our website use cookies to improve and personalise your experience and to display advertisements (if any). Our website may also include cookies from third parties like Google Adsense, Google Analytics, Youtube. By using the website, you consent to the use of cookies.

xenapp

App Volumes works well with both Citrix XenDesktop and Citrix XenApp, either individually or in a combined XenDesktop and XenApp implementation. The same AppStacks that attach to XenDesktop virtual desktops to deliver applications to users can also attach to XenApp servers to deliver applications. To learn more about using App Volumes in a XenApp environment, read Implementation Considerations for VMware App Volumes in a Citrix XenApp Environment. This paper focuses only on App Volumes in a XenDesktop environment

If you're a sysadmin who manages multiple Citrix XenApp Farms then this utility is for you. Introducing the NEW CtxAnalyzer which is a great utility for displaying all the information you need about your Citrix XenApp servers in one screen. Now with multiple Citrix XenApp farms view - export information of multiple farms in multiple domains to Excel or HTML files. So you may be asking yourself what information does this tool display:- Server Status: Online or Offline. Network Configuration: IP Address, Subnet, Gateway, DNS. Windows Information:: Windows Version and Platform (x86/x64), Windows Install Date, Windows Last Boot Date and Machine…

One of the frequently asked questions for Receiver for Web is multiple launch prevention. This is supported in Receiver for Web. When you click on an application or desktop icon to launch it, a spinner is displayed and any clicks on the same icon are ignored while the spinner is spinning. Hence user cannot unintentionally launch multiple instances of the same application/desktop. Out of the box, the time period for the spinner is fixed for three seconds. In StoreFront 2.5, this can be modified by a simple customization. Just insert the following code snippet into custom.script.js in the contrib folder under…

You can see this recommendation in few of our recent best practices – most recently in the excellent “XenDesktop and XenApp Best Practices document”: “The XenDesktop and XenApp servers should be configured to use DNS Aliases when accessinginfrastructure components such as the Citrix License Server and Database Server(s) rather than hostname or IP address. This helps to simplify management during certain maintenance and disaster recovery scenarios.” But what does it exactly mean and how should it be configured? I’m following this best practice for many years and I would like to share few information about how to use it and what are the…