Citrix NetScaler Deployment Guide For Microsoft Exchange

9m ago
3.72 MB
50 Pages
Last View : 21d ago
Last Download : 2m ago
Upload by : Aiyana Dorn

Citrix NetScaler Deployment Guide forMicrosoft Exchange 2010

Table of ContentsCitrix NetScaler Deployment Guide for Microsoft Exchange 2010 . 1Introduction . 3Solution Requirements . 3Prerequisites . 3Deployment Overview . 4Network Diagram . 7NetScaler Deployment . 7Client Access Server . 7Configuring NetScaler for Outlook Web App (OWA) . 9Configuring NetScaler for Microsoft Exchange ActiveSync (AS) . 22Configuring NetScaler for Microsoft Outlook Anywhere (OA). 23Configuring NetScaler for IMAP4 . 24Configuring NetScaler with POP3. 28Configuring NetScaler for RPC Client Access. 32Edge Transport Servers . 34Configuring NetScaler for Edge Transport Servers . 34ConfiConfiguring NetScaler GSLB with Edge Transport Servers in multiple Data Centers . 36NetScaler Management Pack Deployment . 43Introduction . 43Dependencies . 44Prerequisites . 44Installing Citrix NetScaler Management Pack . 44Importing Management Packs . 46Setting Up Security . 46Override MP for Customizations . 47How it Works . 48Page2

IntroductionCitrix NetScaler optimizes the delivery of Web applications—increasingsecurity, improving performance, and expanding Web server capacity. Thisapproach ensures the best total cost of ownership (TCO), security, availability,and performance for Web applications. The Citrix NetScaler solution is acomprehensive network system that combines high-speed load balancing andcontent switching with state-of-the-art application acceleration, layer 4-7 trafficmanagement, data compression, dynamic content caching, SSL acceleration,network optimization, and robust application security to provide a single, tightlyintegrated solution. Deployed in front of application servers, the NetScalersignificantly reduces processing overhead on application and database servers,resulting in reduced hardware and bandwidth costs.The purpose of this guide is to help you deploy NetScaler for load balancingMicrosoft Exchange 2010 Client Access servers. Configuration can beperformed by using the web-based configuration utility or the command-lineinterface (CLI).Within the Exchange 2010 server architecture, a NetScaler is located in front ofthe Client Access servers with one single virtual IP address and balances thetraffic across the Client Access server pool. Exchange client traffic is bound to aClient Access server through NetScaler. Each Client Access server within theClient Access server pool handles the server applications, security, authentication,and connection and protocol processing. The Mailbox server at the back endhandles the mailbox data, such as mail and contacts. Therefore, the same clientcan be processed by any Client Access server in the pool at any given time.For readers less familiar with the architecture of Exchange 2010, Microsoftprovides a useful overview at Files/exchange2010.pptx.Solution Requirements Citrix NetScaler or Citrix NetScaler VPXMicrosoft Exchange 2010 Client Access Server, Server, Edge TransportServer and Hub Transport Server. (Note: One Exchange 2010 system canimplement multiple server roles.)Prerequisites Citrix NetScaler running version 9.0 build 61.9 or later (Quantity x 2 for HA)Microsoft Exchange 2010 Client Access servers and other Exchange 2010components.Client laptop/workstation running various Microsoft Exchange clients.ActiveSync will require Apple iPhone, handheld running Microsoft WindowsMobile or other Exchange-compatible software.Page3

In cases where it is impractical to deploy actual clients, you may be able to useMicrosoft’s online Microsoft Exchange Server Remote Connectivity Analyzer tosimulate the end-user protocols. That service can be found ment OverviewThis deployment guide provides the NetScaler configuration for the front-endMicrosoft Exchange 2010 Client Access servers and Edge Transport servers.This guide does not explain Microsoft Exchange server deployment or thecomponents in the Client Access server or Edge Transport server deployments.Be sure to follow the Microsoft Exchange 2010 Planning guide to deploy theExchange components.In accordance with the Microsoft Exchange Planning Guide, the NetScaler willparse the headers of all the incoming requests and decide which Client Access orEdge Transport servers to send the request. In addition, NetScaler providessecurity and protection for the Client Access or Edge Transport systems andincreases server performance and efficiency.NetScaler can provide the following key benefits: Improved L4 through L7 Performance. Provides 15 gigabits per second(Gbps) throughput.Maximum Feature Concurrency. Supports complex policies by using featuressuch as compression, content switching, and application firewall.Accelerated Application Response. Provides advanced compression, TCPoptimization, and static and dynamic caching to speed applicationperformance.Page4

Integrated Application Security. Provides an application firewall feature toblock attacks against Web applications. Improved Datacenter Efficiency. Accelerates datacenter performance byoffloading compute-intensive TCP connection set-up and teardownoperations. NetScaler supports Secure Socket Layer (SSL) key generation andbulk encryption to improve server efficiency.Follow the specific instructions in this guide for configuring a load balancingsetup for the Client Access server components. Load balancing improves serverfault tolerance and end-user response time. The load balancing feature distributesclient requests across multiple servers to optimize resource utilization andimprove server performance. NetScaler uses load balancing criteria to acceleratethe application response time by forwarding each client request to the server bestsuited to handle the request when it arrives. The load balancing feature providestraffic management from Layer 4 (TCP and UDP) through Layer 7 (FTP, HTTP,and HTTPS).The basic building blocks of a typical load balancing configuration are servicesand load balancing virtual servers. The services represent the applications on theservers. The virtual servers abstract the servers by providing a single IP addressto which the clients connect. To ensure that client requests are sent to a server,you must create services for every server and bind the services to the virtualserver. To connect to a NetScaler appliance, clients use the IP address of thevirtual server and the virtual IP address (VIP). When the NetScaler appliancereceives client requests on the VIP, it sends the requests to a server determinedby the load balancing algorithm. Load balancing uses a virtual entity called amonitor to track whether a specific service (server plus application) is available toreceive requests. By default, the NetScaler binds a monitor to each service.Alternatively, you can create customized monitors to suit your requirements.To configure load balancing, you typically need to perform the following steps: Create customized monitors to track the health of the back-end servers(optional). Create services that represent applications on the back-end servers. Create a virtual server to abstract the back-end servers.A load balancing setup can be configured by using the following NetScaler userinterfaces: Configuration utility. You connect to the configuration utility using a webbrowser. The Java Runtime Environment (JRE) 1.4 or greater is required onthe client system running the web-based configuration utility. Theconfiguration utility runs as a Java application.Command-line interface (CLI). You connect a workstation or laptopcomputer to the NetScaler by using the supplied serial cable, and thenconnect to the CLI by using terminal emulation software. You can also usePage5

secure shell (SSH) to access the CLI via IP when configuring a physical orvirtual NetScaler.Note: This guide provides configuration instructions by using the configurationutility. Many configuration sections also include a summary of NetScalercommands.To launch the configuration utility Connect the NetScaler to a management workstation or network.Open a browser and type: http:// IP address of the NetScaler Type the appropriate user name and password in User Name and Password,respectively. By default, the user name and password are nsroot.In Start in, select Configuration.Click Login.Page6

Network DiagramA NetScaler appliance resides between the clients and the Client Access andEdge Deployment servers, so that client requests and server responses passthrough it. The NetScaler ensures optimal distribution of client traffic by the wayit directs client requests. You can segment application traffic according toinformation in the body of an HTTP or TCP request, and on the basis of L4-L7header information, such as URL, application data type, or cookie. Numerousload balancing algorithms and extensive server health checks provide greaterapplication availability by ensuring that client requests are directed to theappropriate servers. The following network diagram illustrates the CitrixNetScaler deployment in a typical Exchange 2010 enterprise deployment.Requests originate from the clients and go through the NetScaler to the ClientAccess servers. Client Access servers get all the information from the backendExchange components and respond to the incoming request.NetScaler DeploymentThe following sections provide instructions for configuring the NetScaler forClient Access servers and Edge Transport servers.Client Access ServerThe Client Access server role is one of five distinct server roles for Exchange2010. The Client Access server role accepts connections to your Exchange 2010server from different clients. Software clients such as Microsoft Outlook Expressand Eudora use POP3 or IMAP4 connections to communicate with thePage7

Exchange server. Hardware clients, such as mobile phones, use ActiveSync,POP3, or IMAP4 to communicate with the Exchange server. You must installthe Client Access server role in every Exchange organization and every ActiveDirectory site that has the Mailbox server role installed.This deployment guide provides instructions on how to configure NetScaler tohandle connections from the following clients to the Client Access servers: Outlook Web App in Exchange 2010. Provides access to e-mail from anyWeb browser. Outlook Web App has been redesigned in Exchange 2010.Features such as chat, text messaging, mobile phone integration, andenhanced conversation view, provide an enhanced user experience from anycomputer that has a web browser. Microsoft Exchange ActiveSync client applications. Synchronizes databetween your mobile phone and Exchange 2010. You can synchronize email, contacts, calendar information, and tasks. Microsoft Outlook Anywhere. Allows Exchange access through theMicrosoft Outlook 2010 client by tunneling Outlook’s MAPI protocol overan HTTP connection. (This was formerly known as RPC over HTTP. Theprotocol still functions by wrapping remote procedure calls inside the HTTPlayer, only the name has changed.) Post Office Protocol (POP3) and Internet Message Access Protocol(IMAP4). Allows online and offline access to mail by non-Outlook mailclients. RPC Client Access. Provides access to Exchange mailboxes through MAPI(Messaging API), but in Exchange 2010, moves the connectivity point fromthe Mailbox server role to the Client Access server. Note: The Mailbox andClient Access server roles may be implemented in the same Exchangemachine.The following table from the Microsoft planning guide provides information onthe ports that are utilized for Client Access servers. The VIP Port is the virtual IPaddress that you choose to assign to your NetScaler. This is the address thatclient systems will communicate with. It is NOT the physical IP address of theExchange system.Page8

Ports and Protocols Used by Exchange 2010 ClientsVIP PortClient Access server roleServer PortProtocolOutlook Web App44380HTTPSActive Sync44380HTTPSPOP3995110TCPIMAP4993143TCPRPC Client AccessAnyAnyTCPOutlook Anywhere44380HTTPSNotesConfiguring NetScaler for Outlook Web App (OWA)This section covers the configuration steps for load balancing Client Accessservers for OWA clients. As illustrated in the earlier ―Network Diagram‖ section,a typical OWA request comes in from the Internet through the DMZ and getsterminated at the NetScaler.NetScaler performs the following functions on the request: Terminates SSL connection and performs SSL decryption. This reduces CPUload on the Access Client servers enabling them to handle more clientrequests. (Exchange will need to be reconfigured so as NOT to require SSLwhen processing traffic via NetScaler.)Check health of the Access Client servers. This increases availability of theservers.Load balances multiple Access Client servers to handle OWA requestsefficiently to ensure high availability of the Access Client servers.Compresses traffic to decrease response times.Creating Services for OWAIf any of the menu items are unavailable, be sure the appropriate features areselected by navigating to System Settings and click Change basic features. TheNetScaler should have at least the roles indicated in the following screen shot.Page9

The first step in the configuration process is to identify Client Access servers thatare ready to handle OWA connections and add them as services as shown below.Navigate to Load Balancing Services, click Add, and enter the values as shownin the screen shot. Please note that the IP address that you enter for ―Server‖ willbe the IP address of your Exchange Server. Select the monitor and click Add tobind the http monitor to the service.Enable compression on each service by clicking advanced tab and selecting theCompression check box.You will need to repeat the steps above for each Exchange Client Access serverthat you want to load balance.Page 10

Import SSL certificateBecause the NetScaler will be terminating the SSL connections on behalf of theExchange system (offloading that burden), the NetScaler will need an SSLcertificate imported into its system for use in this role. We assume that thecertificate is available to the user.If you are planning to utilize a certificate from the Exchange system, follow theseinstructions to export the certificate file.On your Exchange System, open the Exchange Management Shell and input thecommand ―Get-ExchangeCertificate.‖ This will output a description of all SSLcertificates for the specified Exchange services.Use these three commands to generate a file ―htcert.pfx‖ from the certificatewith the thumbprint specified by the hex string. When prompted, enter a username and password, which will be used for importing into the NetScaler. Then,transfer the file to the system being used to access the NetScaler.On the NetScaler, navigate to SSL, and click Import PKCS#12 in the detailspane. Provide the required information. The output file name being itsrepresentation on the NetScaler.Page 11

Click OK, and then navigate to SSL Certificates and click Add. Provide theinformation, using the above screen shot as a guide, and click Install. TheCertificate should appear on the NetScaler.Create a Content Rewrite PolicyTo point the NetScaler virtual servers to the correct URL for Outlook Web Appaccess, create a content rewrite policy for the request from the NetScaler to theExchange 2010 Client Access server.On the NetScaler, navigate to Rewrite Actions and click Add. Copy theinformation from the following screen shot, and click Create.Page 12

Then, navigate to Rewrite Policies and click Add. Copy the content from thefollowing screen shot, and click OK.These steps allow the virtual server to add ―/owa‖ to the clients request.Create an SSL virtual serverCreate a virtual server and bind the services that we created previously and enablea persistence scheme and a load balancing algorithm.Page 13

Navigate to Load Balancing Virtual Servers and click Add. Enter the valuesas shown in the following screen shots. Note that each service that you created inthe first step of the OWA configuration will appear as an available service namein the Services screen. The IP address that you enter in the upper-right corner ofthe dialog box is the virtual IP (VIP) address that OWA clients will use to accessOWA.This virtual server will handle all https requests, that is, requests that arrive overSSL sessions.Click Method and Persistence and choose the load balancing algorithm andpersistence scheme as shown in the screen shot. Choose Round Robin(recommended by Microsoft) or least connection for load balancing and choosecookie insert for persistence.Page 14

Click SSL Settings and add the imported certificate to this virtual server byhighlighting on e2010-cert (or whatever the name was of the certificate that youimported earlier) and clicking Add.Click Policies Content Rewrite, and apply the policy created earlier to thevirtual server.Page 15

Click OK and it will create a virtual server that is ready to accept incoming OWArequests encrypted via https. NetScaler will then send these requests to the backend server in clear text using http.This could cause a problem for OWA deployments as the server is not aware ofSSL offload and responds to the queries with redirects that are in http mode.Therefore subsequent requests from the clients show up in the clear on port 80on NetScaler. There are two ways to mitigate this problem. First method requiresthe user to re-configure Exchange servers indicating to them that SSL has beenoffloaded. Following 0(EXCHG.80).aspx) are the steps to do that –1. Start Registry Editor.2. Locate the following registrykey: HKEY LOCAL ge OWA.3. On the Edit menu, click New, and then click DWORD Value.4. In the details pane, name the DWORD value SSLOffloaded.5. In the details pane, right-click SSLOffloaded, and then click Modify.6. In the Edit DWORD Value dialog box, in Value data, type 1.7. Restart the IIS Admin Service (IISAdmin). To do this, open a CommandPrompt window, and then type iisreset /noforce.Page 16

Second way is to configure NetScaler to redirect any traffic that comes to OWAserver on port 80 to port 443. For this, we need to create another virtual serverthat will respond to requests that might arrive, unencrypted, via http on port 80.In Load Balancing Virtual Servers, click Add. This time, select HTTP asthe protocol. You will note that the SSL Settings tab is disabled as HTTP doesnot use SSL. As before, the IP address in the upper-right corner should be theVIP that you have allocated as the external address for OWA users. Be sure notto bind any services to the server.Page 17

On the Method and Persistence tab, use Least Connection LB method andNone for persistence. On the Advanced tab, in Redirect URL, enter the VIPof the https virtual server.Finally, you will need to log on to your Exchange Client Access servers withadministrative privileges to modify the SSL settings of several components toallow Exchange and NetScaler to communicate properly.You can access the Exchange Server system either through a physical console orMicrosoft Remote Desktop. The Exchange OWA service makes use of InternetInformation Services (IIS) co-resident with Exchange. It is within the IISconfiguration where we need to reconfigure the system so that SSL connectionsare not mandatory between the Exchange Client Access server system and theNetScaler.Page 18

Launch IIS Manager on the Exchange Client Access server system. (It is found inthe sub-folder of Applications called Administrative Tools.) Expand the menus,as shown below, until the nodes below Default Web Site are visible.There are several web site elements that you will need to modify: EWS,Exchange, Exchweb and OWA. The configuration change is the same for all ofthese. You can apply these changes in any order.Highlight one of the folders, EWS is highlighted in our example, and scroll downon the middle scroll bar until you see IIS Settings (near the bottom).Page 19

Double-click the SSL Settings icon to bring up the detailed settings. As adefault, you will see Require SSL is selected. Clear that check box (as show inour example), and click the radio button for Accept client certificates. Once youhave done this, be sure to click the Apply action in the upper-right corner of thescreen.You will need to repeat the change to the SSL configuration in each of the otherthree folders referenced above.Page 20

Summary of NetScaler Commands for OWAenable ns feature WL LB CMP SSL REWRITEadd server server service Exchange 2010 owa HTTP 80 -gslb NONE -maxClient 0 -maxReq 0 -cip DISABLED -usip NO -useproxyport YES -sp OFF-cltTimeout 180 -svrTimeout 360 -CKA NO -TCPB NO -CMP YESadd service Exchange 2010 owa 2 HTTP 80 -gslb NONE -maxClient 0 -maxReq 0 -cip DISABLED -usip NO -useproxyport YES -spOFF -cltTimeout 180 -svrTimeout 360 -CKA NO -TCPB NO -CMP YESadd rewrite action owa rewrite replace http.REQ.URL "\"/owa\""add rewrite policy owa rewrite policy "http.req.url.eq(\"/\")" owa rewriteadd lb vserver Exchange 2010 owa vserver SSL 443 -persistenceType COOKIEINSERT -cltTimeout 180add lb vserver Exchange 2010 owa http responder HTTP 80 -persistenceType NONE -redirectURL "" -cltTimeout180bind lb vserver Exchange 2010 owa vserver Exchange 2010 owabind lb vserver Exchange 2010 owa vserver Exchange 2010 owa 2bind lb vserver Exchange 2010 owa vserver -policyName owa rewrite policy -priority 100 -gotoPriorityExpression END -type REQUESTbind lb monitor http Exchange 2010 owa 2bind lb monitor ping Exchange 2010 owaadd ssl certKey Exchange 2010 -cert "/nsconfig/ssl/exchange 2010 cert" -key "/nsconfig/ssl/exchange 2010 cert"bind ssl vserver Exchange 2010 owa vserver -certkeyName Exchange 2010Page 21

Configuring NetScaler for Microsoft Exchange ActiveSync (AS)Exchange ActiveSync lets devices such as a cellular telephone or a MicrosoftWindows Mobile powered device access corporate information on a server thatis running Exchange. Exchange ActiveSync is a data synchronization service thatenables mobile users to access their e-mail, calendar, and contacts and retainaccess to this information while they are offline.This section covers the configuration steps for load balancing Client Accessservers that are enabled in ActiveSync mode. As illustrated in the earlier―Network Diagram‖ section, a typical ActiveSync request comes in from theInternet through the DMZ and gets terminated at the NetScaler. NetScalerperforms the following functions on the request: SSL termination to decryptionHealth monitoring of the Client Access serversSource-IP persistence or Rule based persistenceCompressionLoad balancing based on the Round Robin algorithmImport SSL certificateFollow the same instructions that were used to import SSL certificate for OWA.Creating Services for ASFollow the same instructions that were used for creating services for OWA clientand use the appropriate IP addresses for the Client Access servers.Create an SSL virtual serverFollow the same instructions that were used for creating OWA virtual server.Select HTTP health monitor and use the Round Robin load balancing algorithm.Source IP address can be used for persistence, but this could pose a problemwith clients coming from behind a NAT service. Alternatively, if basicauthentication is being used by ActiveSync, NetScaler rule based persistence canbe used using the Authorization header as shown in the following screenshotPage 22

Configuring NetScaler for Microsoft Outlook Anywhere (OA)In Microsoft Exchange Server 2010, the Outlook Anywhere feature, formerlyknown as RPC over HTTP, allows clients that useMicrosoft Office Outlook 2010, Outlook 2007, or Outlook 2003 connect to theirExchange servers over the Internet using the RPC over HTTP Windowsnetworking component.This section covers the configuration instructions for load balancing ClientAccess servers that are enabled in Outlook Anywhere mode. As illustrated in theearlier ―Network Diagram‖ section, a typical OA request comes in from theInternet through the DMZ and gets terminated at the NetScaler. NetScalerperforms the following functions on the request: SSL termination to decryptionHealth monitoring of the Client Access serversSource-IP or Rule based persistenceCompressionPage 23

Load balancing based on Round Robin algorithmImport SSL certificateFollow the same instructions that were used to import SSL certificate for OWA.If you plan to use the same certificate as used for OWA, you may skip this step.Creating Services for OAFollow the same instructions that were used for creating services for the OWAclient and use the appropriate IP addresses for the Client Access servers.Create an SSL virtual serverFollow the same instructions that were used for creating the OWA virtual server.Select HTTP health monitor and use the Round Robin load balancing algorithm.Source IP address can be used for persistence, but this could pose a problemwith clients coming from behind a NAT service. Alternatively, if basicauthentication is being used, NetScaler rule based persistence can be used usingthe Authorization header as shown in the ActiveSync section.Configuring NetScaler for IMAP4Internet Message Access Protocol (IMAP4) is an Application Layer Internetprotocol operating on port 143 that allows an e-mail client to access e-mail on aremote mail server. Within Microsoft Exchange, IMAP4 clients are serviced bythe Client Access server component.IMAP4 does not offer advanced collaboration features, such as calendaring,contacts, and tasks. IMAP4 is commonly used in e-mail clients, such as WindowsMail, Windows Live Mail, and Mozilla Thunderbird.IMAP4 cannot be used to send messages from a client application to the e-mailserver. E-mail applications that use IMAP4 to send messages rely on the SMTPprotocol to send messages. The connector for receiving e-mail submissions fromclient applications that use IMAP4 is created automatically on every HubTransport server.This section covers the instructions for load balancing Client Access servers thatare enabled for IMAP4 protocol. As illustrated in the earlier ―Network Diagram‖section, a typical IMAP4 request comes in from the Internet through the DMZand gets terminated at the NetScaler. NetScaler performs the following functionson the request: SSL termination for decryptionPage 24

Health monitoring of the target servers using TCP-based health monitorLoad balancing based on Least Connection algorithmImport SSL certificateFollow the same instructions that were used to import SSL certificate for OWA.If you plan to use the same certificate as used for OWA, you may skip this step.Create a TCP level monitor for IMA

Microsoft Exchange 2010 Client Access servers and Edge Transport servers. This guide does not explain Microsoft Exchange server deployment or the components in the Client Access server or Edge Transport server deployments. Be sure to follow the Microsoft Exchange 2010 Planning guide to deploy the Exchange components.

Related Documents:

Citrix NetScaler 1000V Product Overview Citrix NetScaler is the industry's leading web application delivery solution. It increases the performance and availability of all applications and data. Citrix NetScaler 1000V brings together Citrix NetScaler with Cisco Nexus 1000V Switch vPath te

Citrix NetScaler 1000V Product Overview Citrix NetScaler is the industry's leading web application delivery solution. It increases the performance and availability of all applications and data. Citrix NetScaler 1000V brings together Citrix NetScaler with Cisco Nexus 1000V Switch vPath technology for policy-based service insertion and chaining.

Citrix NetScaler Datasheet Citrix NetScaler Make web applications run five times better. Citrix NetScaler is a web application delivery solution that makes applications five times better by accelerating performance, ensuring th

NOTE: NetScaler Gateway is one of the more common used features within Citrix NetScaler. Either it can be used as a feature on the NetScaler VPX/MPX or we can buy the NetScaler Gateway VPX/MPX, which only licensed to do NetScaler Gateway. So for instance if we are using Citrix Receiver for remote access, it will connect directly to

Automation mit NetScaler - AutoScale Cloud Orchestration Internet 1. NetScaler is auto-provisioned M M M 56783. NetScaler monitoring engine auto4. NetScaler triggers 2. NetScaler monitors servers for CPU, Memory, Latency, Throughput . On successful AutoScale, . NetScaler automatic

Figure 1. Device choices - dedicated NetScaler MPX HA pair for Tenant 1, NetScaler MPX cluster for Tenant 2 and NetScaler SDX serving Tenants 3-N Instances The second NetScaler multi-tenancy building block is the instance. With instances, administrators can con (gure a single physical appliance to operate as multiple independent NetScaler ADCs.

software is available via download now for NetScaler MPX and VPX platforms running NetScaler 10 (any edition). Each node within the cluster must have a cluster upgrade license. Region Availability All Languages English Product Name Citrix NetScaler 10 Public Announcement Date April 17, 20

NetScaler VPX In this exercise, you will access the NetScaler MAS management console and integrate the NetScaler NS_VPX_01 for management and reporting with NetScaler MAS. The initial NetScaler MAS configuration settings will be reviewed and additional post-setup configuration changes will be applied.

3. CloudStack management infrastructure setup 6 3.1 Install Citrix XenDesktop 7 and supporting components 6 3.2 Add DDCs to XenDesktop 10 3.3 Install the Virtual Desktop Agent 12 3.4 Create machine catalogs 14 3.5 Create XenDesktop delivery groups 18 3.6 Configure StoreFront 22 3.7 Add StoreFront servers to deployment 26 Citrix NetScaler 28 4.

Introduction NetScaler AppFirewall technology is included in and integrated with Citrix NetScaler MPX and VPX, Platinum Edition, and is available as an optional module that can be added to NetScaler MPX . Securing Outlook Web Access (OWA) 2013 with NetScaler AppFirewall 7 Configu

citrix netscaler 1000v appexpert guide citrix netscaler 10.5 december 11, 2014. the specifications and information regarding the products in this manual are subject to change without notice. all statements, information, and recommendations in this manual are believed to be accurate but are presented without

2 As the first part of the two-factor authentication process, the Citrix NetScaler device sends the user name and password to the User Store. For example, the User Store can be AD/LDAP. If the User Store authenticates the user name and password, it returns the group permission details to the Citrix NetScaler device with the authentication response.

Citrix NetScaler 1000V EOL10817 Cisco announces the end-of-sale and end-of life dates for the Citrix NetScaler 1000V. The last day to order the affected product(s) is May 20, 2016. Customers with active service contracts will continue to receive support from the Cisco Technical Assistance Center (TAC) as shown in Table 1 of the EoL bulletin.

Overview NetScaler in Microsoft Azure The NetScaler VPX virtual appliance is available as an image in the Microsoft Azure Marketplace. NetScaler VPX on Microsoft Azure Resource Manager (ARM) enables customers to leverage Azure cloud computing capabilities and use NetScaler load balancing

There is no Citrix Client after update push for upgrade from Citrix Plug-in 11.2 to Citrix Receiver 3.3. Issue. SCCM successfully uninstalled Citrix Plug-in 11.2, but the install of Citrix Receiver 3.3 did not process. Resolution. Run the "Citrix Receiver 3.3 Up

Introduction to Best Practices for NetScaler MPX, VPX, and SDX Security A Citrix NetScaler MPX appliance is an application delivery cont

Citrix Receiver 3.3 correctly, all older version of the Citrix Client must be uninstalled. The following steps should be taken to make sure The all old Citrix Clients are uninstalled, and then install the new Citrix Receiver 3.3. . Once you uninstall a Deployment Guide Deploying Microsoft SharePoint 2016 with NetScaler 8 Deploying Microsoft SharePoint 2016 with NetScaler Deployment Guide After clicking OK, you will see the Basic Settings screen for the LB vserver. Here, you may change settings such as the session persi

Bruksanvisning för bilstereo . Bruksanvisning for bilstereo . Instrukcja obsługi samochodowego odtwarzacza stereo . Operating Instructions for Car Stereo . 610-104 . SV . Bruksanvisning i original

NetScaler VPX has the same features as the NetScale r MPX physical appliance, but is a virtual form of the NetScaler product. VPX is installed as a virtua l machine (VM) on a hypervisor. Currently, VPX can be installed on XenServer, VMware, and Hyper-V. Th e NetScaler VPX can handle up to 3 Gbps of HTTP