Citrix Xenapp Performance Essentials (Paperback) ; By Luca Dentella ; Indie Bestsellers · Foundation. By Isaac Asimov. Full List ; Indie Next List · One Italian. Getting Started with Citrix Xenapp 6: Design and Implement Citrix Farms Based on Xenapp 6 Rs. · Getting Started with Citrix XenApp 6: Book by Guillermo. If you are a system administrator or consultant who wants to implement and administer Citrix XenApp farms, then this book is for you. This book will help. LAKE THUNDERBIRD REAL ESTATE Вы можете прийти к нам.
Not in stock. Usually arrives in Days This book cannot be returned. Description Install, configure, and support your XenApp systems with the power of Citrix XenApp Key Features Familiarize yourself with Citrix applications and desktop virtualization Maintain and troubleshoot your XenApp environment to minimize system downtime A hands-on, step-by-step guide with a practical approach and real-world examples to get you up and running with XenApp systems Book Description If you want to effectively deploy the various components of Citrix XenApp to create an enterprise environment for application and desktop delivery, this hands-on guide is perfect for you.
What you will learn Make the use case for Citrix XenApp and design your first system Prepare your existing IT infrastructure for XenApp and learn what licenses you need Install and configure the XenApp infrastructure Enable access with StoreFront and NetScaler Gateway Enable load balancing with NetScaler Maintain servers and publish applications and desktops Manage printing in a Citrix environment Troubleshoot your environment using advanced tools and methodologies employed by Citrix Escalation Teams.
Shopping cart There are no products in your shopping cart. An Evening With David Sedaris. New Orleans Indiebound. About Kobo eBooks. Affiliate Program Become an Affiliate. It may increase only if you create several zones in your farm but this is a discouraged practice. Anyhow, I strongly suggest you to dedicate one server to act as the zone data collector; if the data collector is running on a server that also publishes applications, it may experience resource contention and the resolution process may slow down.
Farms choose the data collector for each zone with an election between all the servers in the zone that can run the component session-host only servers are excluded. XenApp administrators may change the election preference for each server to statically choose which server will be the data collector for the zone.
The following screenshot displays the election preference options for the data collector:. Set the election preference to Most Preferred only on the dedicated server to be sure it will be chosen as the data collector during the election process. If the data collector becomes unavailable, a new election is performed. You may also consider to define the backup server a second dedicated server or a server running rarely used applications setting its election preference to Preferred.
The other servers in the farm should keep the default value Default Preference. When a user logs on to the Web Interface, it displays the list of applications retrieved from the XML service to the user. When the user selects an application, the XML Broker responds with the address of a server running that application. As the XML Broker works closely with the data collector, it is recommended that you install the XML Broker on the same server running the data collector component.
If you add more XML Broker servers, you can configure the Web Interface or add an external load balancer for example, a Citrix NetScaler to balance the requests between them. The following screenshot displays the option of selecting an XML Broker server for load balancing:. The license server stores and manages Citrix licenses. The first time a user connects to a XenApp server, the server checks out a license for the user.
Subsequent connections of the same user share the same license. A single license server is enough for farms with thousands of servers and users; you could install a second license server in your farm but the two servers cannot share licenses. Because the license server is contacted when the user connects to a XenApp server, slow responses may increase the login time. You should place the license service on a dedicated server or, in case of small farms, on a server that doesn't publish applications.
The license server process is single-threaded so multiple processors do not increase its performance. If the license server is not available, all the servers in your farm enter a grace period of hours; during this period users are still allowed to connect. This means that you usually don't need a high-availability solution for your license server.
If a server fault occurs, you can install a new license server during the 30 days of the grace period or power on a second license server you prepared and kept turned off cold standby. The Web Interface provides users access to the published application through a web browser. You should expect many connections to the Web Interface when the users arrive at work in the morning or after lunch, so size your Web Interface server based on the number of users you expect will log on at the same time.
A tip to provide high availability and load balancing for this component is to deploy two Web Interface servers and balance the incoming connections using an external HTTP load balancer, as shown in the following diagram:. Session host servers publish and run the applications in your farm.
Correctly sizing these servers is one of the most critical tasks during the design of your infrastructure; if you underestimate the servers, users will eventually complain about application slowness or worse, some users won't be able to run them at all. If you overestimate them, your boss will probably complain about the cost of the project.
The number of servers you need and their hardware configuration depends on the number of users and applications, but even more on the kind of the applications and how you deliver them to the users. My suggestion is to set up a test farm and to use it to verify the load each application produces. Later in this chapter you'll learn how to use Citrix EdgeSight for Load Testing to simulate real users.
Citrix XenApp supports five ways to deliver applications to the users. Each method has pros and cons and the choice of one or another highly changes the resource requirements of the session host servers. The methods are explained in the following sections:. Applications are installed on the server. When a user launches an application, it runs on the server. Session host servers, therefore, require sufficient resources CPU and RAM for the applications, while user devices may be lightweight devices thin clients, tablets, and smartphones.
No offline access is possible. Applications are put in profiles and stored on a file or web server. When a user launches an application, this streams to the server where the execution takes place. When a user launches an application, this streams to the user device. This device must have enough resources to run the application and must run Windows OS. Applications are cached on the user device, so offline access is possible.
When a user launches an application, XenApp tries to stream it to the user device. If this is not possible — the device runs an unsupported OS — the application is streamed to the server. This is a more versatile method, but session host servers still require sufficient resources to run the applications in the backup mode. The traditional and most common method to deliver applications is to install them on the session host servers.
Two strategies available for placing applications on servers are: siloed and nonsiloed. In this approach applications are installed on small groups of servers; you could even have servers running a single application. Applications are usually grouped by their use, for example, all the applications used by the Financial department are installed on the same servers, while the applications used by the HR department are installed on different servers.
This approach is sometimes required if your applications have different hardware requirements or may cause conflicts if installed on the same server. Some application vendors, moreover, don't consider a different licensing if their applications are published through XenApp. So if you pay license fees simply counting the number of installations, you may reduce the cost of installing them on a small number of servers.
In this approach all the applications are installed on all the servers. This approach is more efficient as it reduces the number of required servers and it may also improve the user experience because it allows users to share the same server session with different applications. If you're using Provisioning Services, a nonsiloed approach also helps you to reduce the number of different vDisks you have to create and maintain.
My suggestion is to use the nonsiloed approach when possible. Later in this book you'll learn that, with worker groups, you will still be able to logically group applications on servers even with this approach. The Provisioning Services infrastructure allows computers to be provisioned from a single shared image. This technology is widely used in XenDesktop, the desktop virtualization product by Citrix. System administrators prepare a small pool of images and, using Provisioning Services, deploy them to the users.
Provisioning Services also becomes very helpful in a XenApp infrastructure, when you need to deploy several session host servers. The use of this technology offers many benefits. With Provisioning Services, system administrators create and maintain a small number of images or a single image if all the applications are installed on all the servers for their servers.
If a new application has to be published or an update for an installed application is available, the administrator only has to modify the "master" image and when servers reboot, the change will be deployed on every farm. Server consistency is so assured that there's no risk that some of your servers weren't updated or still run the older version of the application.
You may also perform a test of the new image assigning it to a couple of test servers and, if everything is ok, deploy it to the production servers. If something goes wrong the updated application doesn't work, an installed patch conflicts with some other component, and so on and you kept the previous version of the image, a rollback is very easy. Just assign the old image to your servers and reboot them.
Provisioning Services also help to reduce storage costs. The image is streamed via network from a central repository; a local storage is usually required for runtime data caching, but in some scenarios you can remove it entirely. The use of Provisioning Services certainly requires some more effort during the installation phase, but from my experience I suggest you to consider using this feature if your farm has more than 5 to 10 servers. The time you spend to deploy the Provisioning Services infrastructure is less than the time you would spend for the daily tasks to maintain your farm.
In the following sections, you will learn the key concepts of this technology; for a real implementation, please refer to the Citrix documentation. The Provisioning Services infrastructure is composed by several components. A database; you can place Provisioning Services database on the same database server that hosts your farm's data store.
One or more Provisioning Servers; these run stream services, the software used to stream virtual images to provisioned servers. A store, where the images of your servers are saved. You can place the store on the Provisioning Servers or on an external file server. A Provisioning Services infrastructure is logically divided into a hierarchy of items. Do not confuse this farm with the farm of your XenApp infrastructure; they don't share configurations or items.
Provisioning Services sites allow administrators to logically group items that belong to the same physical site for example, all the resources located in the headquarters or in a branch office. You need at least one site, which is created when you install your first Provisioning Server. Administrators may create different sites to delegate administrative tasks. You can indeed create accounts that can only administer items in a given site.
Servers : The Provisioning Servers in that site. Device collections : Logical groups of target devices. A target device belongs to one device collection. Views provide an alternative method for grouping and managing target devices; a target device may indeed belong to different views. You can create views at farm level or at site level; a view at site level may only contain devices from the same site, while views at farm level may contain all the target devices in that farm.
You can perform some administrative tasks at view level, so views become useful with a large number of target devices. For example, you can reboot all the session host servers that publish an application adding them to a view and issuing the Restart A store is a storage location where you save your vDisks. It may be a local hard disk or a network share. They consist of a. Shared image mode; shared between multiple devices with read-only access.
In shared image mode, target devices can only read the content of the vDisk. Write requests can be cached in four different ways as follows:. In cache on device hard drive option, write requests are cached on a local hard drive of the target. This is the most common setup, as it frees up the Provisioning Server and doesn't require a large amount of RAM memory. Target servers must have a local hard drive. In cache in device RAM option, write requests are cached in the target device's memory.
This is the fastest method for caching but consumes memory of the target device, reducing the total memory available for running applications. In cache on a server option, write requests are handled by the Provisioning Server and cached on a temporary file; in the Store properties you can set the location of these files. This method should be used only if the target device doesn't have a local storage because it increases the network usage and the Provisioning Server load.
All the previous options are volatile; write cache is lost when the target device reboots. With the cache on a server persistent option, you can set the cache file to be persistent: Provisioning Server creates a cache file for each target device and doesn't clean it if the target reboots. A drawback is that any changes to the original vDisk invalidate all the cache files. Invalid cache files are not automatically deleted. Remember to periodically check if any exist and manually delete them to free some space.
When a target device boots, it first needs a bootstrap program, a small software that runs before the operating system. Provisioning Services use a particular bootstrap program to set up the streaming session with a Provisioning Server. Through this session the target device is then able to receive the assigned vDisk and boot the operating system. The most common configuration is the use of a DHCP server. The response includes the scope options 66 and 67 with the name and the location of the bootstrap file.
This downloads it to the target. The target device establishes a stream session with the Provisioning Server and boots the assigned vDisk. Begin by building a XenApp master server. A best practice is to choose the session-host only mode during the XenApp installation.
Join the server to your farm or use the wizard to create a new farm if this is the first server you deploy. Install all the needed applications and publish them to your users. Choose to remove the server from the farm but don't choose to clear the database location unless you plan to create an Active Directory policy to configure it.
Now, install the Provisioning Services Target Device software. At the end of the setup, the Imaging Wizard should start automatically. If not, run it from the Provisioning Services folder in the Start menu. First, you need to connect to your PVS farm; enter the name or the IP address of one of the servers in your farm and the network port.
If you're running the wizard with a user that can administer the farm, choose to use the Windows credentials, otherwise enter the appropriate credentials. PVS can configure and manage Windows licensing. The Imaging Wizard can create a new vDisk for you; as an alternative, if you've previously created an empty vDisk, you can choose it.
The final step is to create a target device in your PVS farm that corresponds to the server you're running the wizard on. Select the name of the device, the MAC address associated with the NIC you chose during the installation of the target device software, and the collection to add the device to.
Review the information, then click on Finish to start the conversion process. After some minutes your vDisk will be ready to use; just remember to change the access mode to Standard image before booting new servers with it. You can manually create new session host servers for example, from the vSphere client if you're on a VMware infrastructure or use the Streamed VM Setup wizard from the PVS console to create your servers at once.
If you need to modify the vDisk, make a copy, change the mode to Private , and assign it to a server. Boot the server, perform the changes, and before shutting it down, remember to launch the Prepare server again for the imaging and provisioning wizard. This product is available on the Citrix website; at the moment I'm writing the latest version, 3. You need a valid XenApp license to download and run the product.
It's included in the Enterprise or Platinum version. Using EdgeSight for Load Testing, you are able to simulate real user sessions to analyze how your farm performs with different loads; it's a very helpful tool to correctly design your infrastructure. The Controller ; used to design and configure test plans and coordinate the launchers during the test execution.
One or more Launchers; that receive commands from the controller, create ICA sessions to the target hosts, and replay the test plan, simulating user actions. You need to change the remote desktop services configuration on the session host servers on which load tests will be applied, using the Remote Desktop Session Host Configuration tool.
No disconnected sessions must remain when virtual users disconnect from servers. If you're going to use multiple copies of the same virtual users to perform your test, you need to remove the limit of one session per user, and change the Restrict each user to a single session setting to No.
It's very common to use the Citrix Web Interface to provide users a portal where they may view and run their applications. If you want to test this component with EdgeSight, you need to install on the server an optional component named Web Interface Support that hosts the Web Interface, included in the EdgeSight for Load Testing setup package.
Using this component, simulated users will be able to log on to the Web Interface, retrieve the published application you want to test, and run it. You may install both Controller and Launcher on the same test machine, or you may install Launcher on dedicated servers.
Следующая статья session executablepath winscp