Beruflich Dokumente
Kultur Dokumente
5 for
Windows Server 2008 R2
Training Document
Content
Design and Plan... .1
- Virtualization infrastructure..1
Determining the number of XenApp Servers to Deploy.. 4
Installing and Configuring Citrix XenApp 6.5...5
- Part1 Installing Windows Component....5
- Part2 Installing Microsoft .Net Framework 3.5 SP1....18
- Part3 Installing Data Store..21
- Part4 Installing and configuring Citrix XenApp and License Server 38
- Part5 Configuring Web Interface...61
- Part6 Configuring Remote Desktop Service..,,97
- Part7 Configuring Citrix Policy99
A Citrix License Server is required for all XenApp deployments. Install the license
server on either a shared or stand-alone server, depending on your farms size. After
you install the license server, download the appropriate license files and add these to
the license server.
AMR Asia Co., Ltd.
2
Dat a St ore
The data store is the database where servers store farm static information, such
as configuration information about published applications, users, printers, and servers.
Each server farm has a single data store.
Dat a Collect or
You can deliver applications to users by either virtualizing them on the desktop
(streaming) or by virtualizing them on the server (hosting). If you are virtualizing
applications on the desktop, either streaming to the client or server, create a streaming
profile server in your environment. To virtualize applications on the desktop, you create
profiles of the application and then store the profile on a file or Web server. The profile
consists of the manifest file (.profile), which is an XML file that defines the profile, as
well as the target files, a hash key file, the icons repository (Icondata.bin), and a scripts
folder for pre-launch and post-exit scripts.
Web Int erf ace
XenApp Web and XenApp Services sites (formerly known as Access Platform and
Program Neighborhood Agent Services sites, respectively) provide an interface to the
server farm from the client device. When a user authenticates to a XenApp Web or
XenApp Services site, either directly or through Receiver or the Access Gateway, the
site:
Forwards the users credentials to the Citrix XML Service
Receives the set of applications available to that user by means of the XML
Service
Displays the available applications to the user either through a Web page
or by placing shortcuts directly on the users computer
Cit rix XM L Service and t he Cit rix XM L Broker
The Citrix XML Broker functions as an intermediary between the other servers in
the farm and the Web Interface. When a user authenticates to the Web Interface, the
XML Broker:
Receives the users credentials from the Web Interface and queries the
server farm for a list of published applications that the user has
permission to access. The XML Broker retrieves this application set from
the Independent Management Architecture (IMA) system and returns it to
the Web Interface.
Upon receiving the users request to launch an application, the broker
locates the servers in the farm that host this application and identifies
which of these is the optimal server to service this connection based on
several factors. The XML Broker returns the address of this server to the
Web Interface.
The XML Broker is a function of the Citrix XML Service. By default, the XML
Service is installed on every server during XenApp installation. However, only the XML
Service on the server specified in the Web Interface functions as the broker. (The XML
Service on other farm servers is still running but is not used for servicing end-user
connections.) In a small farm, the XML Broker is typically designated on a server
dedicated to several infrastructure functions. In a large farm, the XML Broker might be
configured on one or more dedicated servers.
The XML Broker is sometimes referred to as a Citrix XML Server or the Citrix
XML Service. For clarity, the term XML Broker is used to refer to when the XML Service
functions as the intermediary between the Web Interface and the IMA service,
regardless of whether it is hosted on a dedicated server or collocated with other
functions.
After you identify the applications you are delivering to your users and their
methods of delivery, you can estimate the number of XenApp servers required for your
deployment. For applications virtualized on the server, the number of servers required
depends on the following factors:
The processing requirements of the applications and the processing
capacity and available RAM of your servers. To determine the processing
requirements for an application, see its product documentation.
The native operating system of the applications. Running 32-bit
applications on 64-bit operating systems requires more RAM than
running a 32-bit application on a 32-bit operating system.
Whether you are streaming applications to the server or installing the
applications on the server. Depending on the network topography and the
application being delivered, a deployment where applications are
installed on the servers can service more users than a deployment with an
equal number of servers where the applications are streamed to the
servers.
The size of the files with which your users work and how they use them.
Using this data you can roughly estimate the number of servers to deploy in your test
farm. After setting up your test farm, use Load Testing Services on the XenApp servers
to simulate how your users run applications on your servers. With Load Testing
Services, you can track a variety of Perfmon counters, such as Total Processor Time,
Thread Queue Length, Memory Consumption, and Pages Per Second, to determine the
resource limits of the servers in your environment. This will help you determine the
number of servers to deploy in your production environment.
1.2 Role
Add Roles
1.3 Next
1.4 Component
Application Server
check box
1.5
1.6 1.5
Application
Next
1.7 Next
1.8
Select Role Services check box
)
Next
1.9 Next
1.10
10
1.11
Type Terminal Licensing Per User
Next
1.12 Next
11
1.13 Next
1.14 Next
12
1.15 Next
1.16
Select Role Services
13
1.17
1.18
Web Server(IIS) Support HTTP Activation
Next
14
1.19 Next
1.20
Select Role Services
IIS6 Management
Compatibility
Next
15
16
1.22 Windows
Component
1.23
Windows Component
Windows
Restart Close
17
Restart
18
2.2
Select Features
Fatures
(Installed)
install
check box
Next
19
2.3 Install
20
2.5 Close
21
Data
Store admin
console
manage Farm
manual
Data Store
Farm
SQL Express 2008
Replicate Database
( local Admin Domain
Admin)
3.1
Citrix XenApp 6.5 Server CD
Drive
Open
22
3.2 Support\SqlExpress_2008
setup
23
3.4
Tab
( 1)
Passed
OK
3.5 Next
24
3.7 Install
25
3.8
Tab
( 1)
Passed
Next
3.9
Next
26
3.10
Next
3.11 Next
27
3.12
Account Name SQL Server Database Engine
drop down
<<Brows>>
3.13
(Local)
28
3.14
Enter the object name to
LOCAL SERVICE
select OK
Next
3.12
3.15
29
3.16 Next
3.17
Tab
( 1)
Passed
Next
30
3.18 Install
SQL Express 2008
3.19 Next
31
Your
3.21 configure
Start> All Programs>
Microsoft SQL Server 2008> SQL Server Configuration Manager
32
Manage Database, User account, etc
33
3.24
File SQL Management Studio
34
3.26 Next
3.27 Asdf
35
3.28
Restart Server OK
Restart Server
36
3.30
Authentication:
Password: password
3.15
Connect
3.31 manual
Database Tab
Database
New Database ( XenApp 6.5
SQL
Database
manual
37
3.32
Database
Database name: (
=
XenAppDB) OK
3.33 Database
38
4.2
39
40
4.6
Roles XenApp Server (
XenApp)
Next
41
4.7 Next
4.8 Next
42
4.9 Install
43
4.11
Citrix XenApp Server Role Manager
Reboot
4.12 reboot
Citrix XenApp Server Role Manager
Resume Install
44
4.13 Install
45
4.15
Specify Licensing
configure License
Server
4.16
Password
46
4.18
Administrator
47
Submit
License(2)
48
4.21 Browse
4.22
account
license
49
4.24 Import
OK
50
license
Import
51
4.27
License Server Reread license
52
4.30
License server name:(1) Computer name
License Server Test Connection(2)
Next
53
4.31
Select the
model at a later time(2) Apply(3)
54
Licensing
specified(1) Configure(2)
Create Farm
XenApp
(
XenApp
join Farm
Add this
server to an existing server farm)
55
4.35
New XenApp Server farm name: (1)
Farm
(
XenAppFarm)
) Next (3)
4.36
Database
New
database Next ( database
56
4.37
Database server name: (1) drop down Server
Name\SQLEXPRESS (
Server Name=CTXXA)
Next
3.15
57
4.40
58
4.41 Next
4.42 Next
59
4.43 Apply
4.44 configure
Finish
60
4.46 Reboot
Citrix XenApp Server Role Manager
61
1.
Web Browser
2.
Citrix Online Plug-in Agent Citrix Receiver
2
Web Interface Component
Server
Server (
Design
http://support.citrix.com/proddocs/topic/technologies/wi-library-wrapper-allversions.html)
Web interface
Citrix XenApp
1.
Web Browser user Web browser
URL
ip computer name Web Interface Server
2.
Citrix Receiver set server
ip computer name Web Interface Server
Note: Web Interface
XenApp Server
62
5.2
site user
Web browser
5.3
site
Set as the default page for the IIS site (
63
5.4 Next
5.5 Next
64
5.6 Next
5.7 Add
Add Server Farm XenApp
65
5.8 localhost
Add XenApp Server Web Interface (
FQDN XenApp Server host file Web Interface
Server XenApp Server )
5.9
Server (in failover order): (1) list XenApp Server
66
5.10 Next
5.11 Next
67
5.12 Next
5.13 Next
68
5.14 Finish
site Web browser
5.15
site
site
69
5.17 Properties
70
5.19
Domain list: Pre-populated
71
5.21
Domain list: (1) Net Bios name
OK
72
5.22 OK
5.23 Site
Client Deployment
73
5.24 Properties
5.25
Perform client detection at logon(1)
Never (2) (
Web browser detect Citrix Receiver
logon) OK
74
5.26
site user
Citrix Receiver
5.27 Next
75
5.28 Next
5.29 Next
76
5.30 localhost
Add XenApp Server Web Interface (
FQDN XenApp Server host file Web Interface
Server XenApp Server )
5.31
Server (in failover order): (1) list XenApp Server
80
88 Next(3)
77
5.32 Next
5.33 Finish
78
5.34
site
site
5.35
Citrix XenApp Server Role Manager
79
5.36
configure
Farm XenApp
80
5.38 Next
5.39
XenApp Next
81
5.41 Next
82
list
Tab Administrators
Add administrator (
Add Local Admin User
Farm Admin )
83
Note:
Add user
Add
Add local
administrator
5.45
Full Administration Finish
84
5.47
Publish Application User
Tab Applications
Publish application (
85
5.48 Next
5.49
Application
Display name:
User Next
86
5.50 Next
5.51 Browse
87
C:\Windows\System32\notpad.exe)
5.53
Command line: (1) Working directory: (1)
directory Next(2)
88
5.54 Add
Server
User Application
5.55
Servers
89
5.56
Server
(1) (
CTXXA) server
OK
90
5.58 Add
User Group User
Application
91
5.61 User
(1)
OK(2)
92
Next(2)
5.63 Next
93
5.65 Next
94
5.66 Next
5.67 Next
95
5.69
Minimum color quality: (1) Better Speed (16-bit)
Finish
96
97
98
End a disconnected session 30 (
status user disconnected 30
end session )
When session limit is reached or
connection is broken: (3) Disconnect from session
(
session connection
6.4
Restrict each user to a single session No
user User account
session
Yes
User active
user
account , session active
session
99
7.2
Client Printers
Add Tab Auto-create client
printers
100
XenApp Map
default printer client XenApp Server)
101
7.6 Add
Direct connections to print servers
102
print print
WAN)
103
7.9
Value: Use universal printing only if requested
driver is unavailable OK (Policy
7.10 OK
Policy