Interview Questions For Citrix

Q1.  What is Delivery Controller?

• Delivery Controller is the Core component of XenDesktop v5 & above, using  FMA.
• It is the server that centrally manages the XenDesktop site.
• At least one delivery controller is installed on a site.
• The delivery controller communicates with the database.
• It runs several services that manages.
• The hypervisor resources.
• The user authentication and authorization/access.
• The broker between the user requests and their virtual desktops and applications.
• Monitoring. 
• The power management (shutting down of virtual desktops when needed), and so on.
• It includes the functionality of Data Collector and Desktop Delivery Controller (DDC) roles that existed in previous XenDesktop versions up-to v4 that uses IMA.

Q2. What is the impact to end users if Delivery Controller (FMA) is unavailable?

Ans: 

• If none of the Delivery Controller Servers are available in a Site, VDA’s fails to registerthemselves with Delivery Controllers and thus will be unavailable for new session launches.  Thus users cannot access their applications or desktops.  However, the sessions that are already connected will continue to work.
• If just one of the Delivery Controller is unavailable, then VDA’s instantly (15-90 seconds) auto load-balances to other available Delivery Controllers in the Site.
• If specific service on Delivery Controller is unavailable then its respective resources will become in accessible for users.  If Delivery Controller is unavailable

Q3. What is Data Collector?

Ans:

• Data Collector is the component of IMA used in XenDesktop up to v4. It is a Zone level role.
• By default, in a XenDesktop farm, the initial Desktop Delivery Controller (DDC) installed is the farm master acts as the Data Collector, performing desktop resolution operations during starting the desktop and managing the hosting infrastructure.
• Data collector exists as an in-memory database that maintains dynamic informationabout the servers in the zone, such as server loads, session status, published applications, users connected, and license usage
• Data collectors receive incremental data updates and queries from servers within their zone. Data collectors relay information to all other data collectors in the farm
• The data collector communicates information to the data store on behalf of the other servers in the farm
• They act as communication gateways between zones in server farms that have more than one zone.

Q4. What is the impact to end users if Data Collector (IMA) is unavailable?

Ans:

• Data Collector is Zone level role. If Data Collector is unavailable, a new data collector is automatically elected for the zone based on a simple ranking of servers (indicated by server’s election preference setting) in the zone.
• The Data Collector election process is almost instant, automatic (without administrative interference) and is not dependent on the data store thus existing as well as incoming user sessions are unaffected by the election process.

Q5. What are differences between StoreFront (SF) and Web Interface (WI)?

Ans: StoreFront validates the user credentials with the help of the Active Directory domaincontroller which wasn’t the case with WI.  StoreFront will check the application subscription data store for the existing user subscriptions and then store those in the memory.

Q6. What are the ICA and Session Reliability ports?

Ans:

• The Independent Computing Architecture (.ICA) uses TCP 1494 port.  ICA was initially defined for Intelligent Console Architecture.
• The Session Reliability/Citrix Gateway Protocol (CGP) uses TCP 2598 port.

Q7. What is Connection Leasing?

Ans: Connection Leasing is a XenDesktop built-in capability, which lets users connect or reconnect to their most recently used applications and desktops, even when the site database is unavailable. However, this doesn’t help new or first time user scenarios.  With Connection Leasing enabled each DDC, or Controller, caches the users connections to his or her recently used applications and or desktops. By default connections are cached for a period of two weeks.

Q8. Does connection leasing allow users without a current session to connect to Citrix apps while the database is down? 

Ans: Yes.  The delivery controller will keep a list of previous connections from the user. Those previously used connection parameters will be used in the future if the database is unavailable. The default timeframe is 2 weeks, but this can be modified with PowerShell.

Q9. Is the local text echo functionality part of XenApp 7.6?

Ans: HDX has been enhanced over many years to improve upon the responsiveness and interactivity of the user session, something Local Text Echo did but in a slightly different manner. So Local Text Echo, as it was in 6.5, is not part of 7.6, but HDX includes interactivity enhancements that make the need for Local Text Echo obsolete.

Q10.  How much RAM should one give to the “Cache in RAM with overflow to disk” feature for XenApp 7.6?

Ans: Any amount will be a benefit.  I’ve seen 1, 2 and 3GB of RAM allocated per VM show significant value to a XenApp VM resulting in IOPS of less than 1 per user.

Q11.  When migrating (not rebuilding), does the XenApp server have IMA and FMA running at the same time?

Ans: No.  When you are ready to migrate a XenApp 6.5 worker to the XenApp 7.6 site, the upgrade wizard will remove the 6.5 worker from the farm, uninstall the 6.5 software and install the 7.6 VDA while placing the server into the 7.6 site.

Q12. Is there a difference/risk in using the migration tool over doing a rebuild of the farm (assuming that the underlying operating system isn’t changing)?

Ans: Migrating the farm and policy settings via the migration tool is just a time saver, especially for large, complex environment.  As for the XenApp workers, many people prefer to rebuild in that it is an opportunity to refresh the server back to a clean state (assuming you aren’t using something like PVS for image management). The benefit of the upgrade wizard for the workers is that you don’t have to go through the app install/configuration again.

Q13. If my policies are stored in Active Directory instead of XenApp, do I need to run the Policy Export utility?

Ans: No, the export/import is only for Farm stored information. For AD policies, you will continue to use them

Q14. Does the import farm utility also include application icons?

Ans: Yes.  The icons are exported and imported as part of the migration utility

Q15. Does the migration utility work for XenApp 6? 

Ans: Yes, although it is experimental. The commands used to gather the farm, policy and application settings from XenApp 6.5 are the same in XenApp 6.0, but the migration utility has not been tested nearly as in-depth as XenApp 6.5.

Q16. In XenApp 6.5, if we launch two different apps that are both hosted from the same server, it only creates 1 session. Is this still the case in 7.6?

Ans: This is called session sharing and it does work in XenApp 7.6

Q17. Can be VDA installed on Windows 2003 server?

Ans: No, the VDA is only supported on Windows 2008R2 SP1, 2012, 2012R2, 7 SP1, 8 and 8.1

Q18. How do we enable that Provisioning Services RAM Cache feature that conserves IOPS for XenApp 6.5 environments?

Ans: You need to upgrade to the latest Provisioning Services version and your XenApp 6.5 servers must be managed by Provisioning Services.

Q19. Is App-V required for XenApp 7.6 if I would still like to stream my applications like I did in XenApp 6.5?

Ans: Yes. Application Streaming that was part of XenApp 6.5 has been replaced with Microsoft App-V.  XenApp 7.6 includes integration with App-V to simplify publishing and integration.

Q20. Can a XenApp 7.6 site include Windows 2008 and 2012 servers?

Ans: Yes. Based on the new FMA architecture you can have a single site using Windows 2008R2, Windows 2012 and 2012R2.

Q21. What happens if one of the delivery controllers goes offline? Is there a service failure?

Ans: No. In XenApp 7.6, all delivery controllers within a site are Active-Active.  If you recall, in XenApp 6.5 and previous versions, you have a Zone Data Collector, and if that data collector fails, a new one will be elected, which also might be hosting apps.  This has caused performance issues if not configured correctly.  This risk is no longer relevant in XenApp 7.6

Q22. If I upgrade to XenApp 7.6 from 7.5, do I have to upgrade StoreFront?  Do I have to upgrade Web Interface to Storefront?

Ans: No. You can stay on your current version. However, there might be a situation where a new feature in XenApp will not work with an older component or you won’t be able to use a new StoreFront feature.

Q23. What file do you use to configure the StoreFront App Aggregration feature?

Ans: Located here: C:\inetpub\wwwroot\Citrix\storename\web.config, where “storename” is the name of your store. Also, make a backup copy of your web.config file before modifying.