<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Get Started - Category - Chai on Tech</title>
        <link>https://posts.chaibuilds.com/categories/get-started/</link>
        <description>Get Started - Category - Chai on Tech</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Fri, 24 Oct 2014 00:00:00 &#43;0000</lastBuildDate><atom:link href="https://posts.chaibuilds.com/categories/get-started/" rel="self" type="application/rss+xml" /><item>
    <title>Citrix Products Evolution</title>
    <link>https://posts.chaibuilds.com/posts/citrix-products-evolution/</link>
    <pubDate>Fri, 24 Oct 2014 00:00:00 &#43;0000</pubDate><guid>https://posts.chaibuilds.com/posts/citrix-products-evolution/</guid>
    <description><![CDATA[From the time citrix started below are the editions and name changes with year numbers. Citrix was founded in Richardson, Texas, in 1989 by former IBM developer Ed Iacobucci .
Citrix Version Name Year MultiUser 1.0 1991 MultiUser 2.0 1992 WinView 1993 WinFrame 1995 MetaFrame 1.8 TSE(Terminal Services Edition) 1998 MetaFrame 1.8 and MetaFrame 1.8 Feature Release 1 and Metaframe sof solaris, IBM AIX, and HP UX 2000 MetaFrame XP TSE and Metaframe XP TSE FR1 2001 MetaFrame XP FR2 2002 MetaFrame XP FR3 2003 MetaFrame Presentation Server 3.]]></description>
</item>
<item>
    <title>Make Secondary DB Server as primary in Citrix</title>
    <link>https://posts.chaibuilds.com/posts/make-secondary-db-server-as-primary-in-citrix/</link>
    <pubDate>Tue, 02 Jul 2013 00:00:00 &#43;0000</pubDate><guid>https://posts.chaibuilds.com/posts/make-secondary-db-server-as-primary-in-citrix/</guid>
    <description><![CDATA[Below mentioned is a real time scenario with Questions and Answers:
We have Presentation Server 4.5 on 2 servers. Everything is on our Server1. Server2 is currently just used as another Citrx server in the same Farm for deploying Citrix applications. We need to take Server1 down for maintnance. I need to move everthing to Server2 including the database. Both servers have Microsoft SQL Server 2005 Express Edition installed. The Citrix database is on Server1 in its Microsoft SQL Server 2005 Express Edition database.]]></description>
</item>
<item>
    <title>Move SQL datastore from one server to another</title>
    <link>https://posts.chaibuilds.com/posts/move-sql-datastore-from-one-server-to-another/</link>
    <pubDate>Tue, 02 Jul 2013 00:00:00 &#43;0000</pubDate><guid>https://posts.chaibuilds.com/posts/move-sql-datastore-from-one-server-to-another/</guid>
    <description><![CDATA[How to Move a Microsoft SQL Server Desktop Engine Data Store From One Server to Another
Summary
This article describes how to move a Microsoft SQL Server Desktop Engine (MSDE) data store from one server to another.
Background
The steps involved in moving an MSDE data store from one server to another is similar to those used for an Access database.
A step-by-step process is detailed below.
Server 1 is the old server]]></description>
</item>
<item>
    <title>IMA and SMA services not starting</title>
    <link>https://posts.chaibuilds.com/posts/ima-and-sma-services-not-starting/</link>
    <pubDate>Wed, 22 May 2013 00:00:00 &#43;0000</pubDate><guid>https://posts.chaibuilds.com/posts/ima-and-sma-services-not-starting/</guid>
    <description><![CDATA[IMA Service and Citrix SMA Service fail to start and MFCOM Service is unresponsive, when the state of the status is Starting.
The reason in the Event viewer mentions that the SMA and IMA Service failed to start because a dependent Service or Service group could not be started.
When you start the MFCOM Service manually, it times out with the following error message:
“1053: The service did not respond to the start or control request in a timely fashion”]]></description>
</item>
<item>
    <title>Session Sharing</title>
    <link>https://posts.chaibuilds.com/posts/session-sharing/</link>
    <pubDate>Tue, 21 May 2013 00:00:00 &#43;0000</pubDate><guid>https://posts.chaibuilds.com/posts/session-sharing/</guid>
    <description><![CDATA[Session sharing is a mode in which more than one published application runs within a single ICA/HDX connection. Session sharing occurs when a user has an open session and launches another application that is published on the same XenApp server; the result is that the two applications run in the same session. Session sharing is configured by default when you specify that applications appear in seamless window mode.
Inconsistent results may occur when applications are configured for different requirements, such as encryption and color depth.]]></description>
</item>
<item>
    <title>SpeedScreen</title>
    <link>https://posts.chaibuilds.com/posts/speedscreen/</link>
    <pubDate>Fri, 17 May 2013 00:00:00 &#43;0000</pubDate><guid>https://posts.chaibuilds.com/posts/speedscreen/</guid>
    <description><![CDATA[SpeedScreen Folder
The SpeedScreen folder contains a rule that enables you to remove or alter compression. When client connections are limited in bandwidth, downloading images without compression can be slow.
Image Acceleration Using Lossy Compression
This rule defines ways in which images can be compressed to improve the responsiveness of graphics-intensive applications:
Normal lossy compression Progressive display compression Heavyweight compression If your server farm includes servers running different releases of XenApp, you may not be able to apply all of these image acceleration techniques to all of the servers in the farm.]]></description>
</item>
<item>
    <title>Function of the Local Host Cache</title>
    <link>https://posts.chaibuilds.com/posts/function-of-the-local-host-cache/</link>
    <pubDate>Sat, 04 May 2013 00:00:00 &#43;0000</pubDate><guid>https://posts.chaibuilds.com/posts/function-of-the-local-host-cache/</guid>
    <description><![CDATA[Each XenApp server stores a subset(a portion or part from the whole part, but not full part) of the data store in the Local Host Cache (LHC). The LHC performs two primary functions:
• Permits a server to function in the absence of a connection to the data store.
• Improves performance by caching information used by ICA Clients for enumeration and application resolution.
The LHC is an Access database, Imalhc.]]></description>
</item>
<item>
    <title>ICA Policy Settings</title>
    <link>https://posts.chaibuilds.com/posts/ica-policy-settings/</link>
    <pubDate>Sat, 04 May 2013 00:00:00 &#43;0000</pubDate><guid>https://posts.chaibuilds.com/posts/ica-policy-settings/</guid>
    <description><![CDATA[The ICA section contains policy settings related to ICA listener connections, mapping to the Clipboard and custom channels, connecting to server desktops, and controlling the launch behavior of non-published programs.
ICA listener connection timeout Applicable products: XenApp; XenDesktop
This setting specifies the maximum wait time for a connection using the ICA protocol to be completed. By default, the maximum wait time is 120000 milliseconds, or two minutes.
ICA listener port number Applicable products: XenApp; XenDesktop]]></description>
</item>
<item>
    <title>ICA Timeout vs Session Reliability</title>
    <link>https://posts.chaibuilds.com/posts/ica-timeout-vs-session-reliability/</link>
    <pubDate>Sat, 04 May 2013 00:00:00 &#43;0000</pubDate><guid>https://posts.chaibuilds.com/posts/ica-timeout-vs-session-reliability/</guid>
    <description><![CDATA[Session reliability works at the client end. It allows a client to reconnect and avoid inconvenience to a user during a short network interruption. Instead of removing all unresponsive apps and desktops from the client workbench, they will be kept open until the ICA client is able to reconnect to the terminal server. It uses port 2598 and is available with Advanced and Enterprise versions.
Whereas ICA Keep-Alive works at the server end allowing a server to detect broken sessions and put them into a &lsquo;disconnected&rsquo; state if it can&rsquo;t ping the client device.]]></description>
</item>
<item>
    <title>IMA Information</title>
    <link>https://posts.chaibuilds.com/posts/ima-information/</link>
    <pubDate>Sat, 04 May 2013 00:00:00 &#43;0000</pubDate><guid>https://posts.chaibuilds.com/posts/ima-information/</guid>
    <description><![CDATA[**How does IMA traffic get sent and processed amongst Citrix servers?
**Citrix has what we call a transport “function” that is responsible for getting packets of information from one host to another. The transport component is relatively small and does not actually care about the data it is transporting. This is a small set of functions for setting up bindings to host and subsequently sending packets to those hosts.
How does IMA know who the hosts in a farm are to ensure communication requests are from approved sources?]]></description>
</item>
</channel>
</rss>
