This is a step-by-step instructions for setting up a machine on which to install the Linux VDA, and the target to help existing Windows administrators without Linux experience up and running quickly.
If you are reading this, then I suppose you have before you set up a XenApp or XenDesktop environment, you know them in XenCenter and you are familiar with Windows domains and AD, but They have never worked before today with Linux.
This manual describes the setup process for Red Hat Enterprise Linux 6 (RHEL) and CentOS 6, cover from the templates provided in XenServer 6.5 SP1.
Officially we only Linux VDA on Red Hat and SuSE Enterprise Linux, CentOS but is almost identical to RHEL, and support as a free alternative, it is the simplest choice for setting up a test environment.
Getting Started
performed all procedures in this manual are the terminal, either through the virtual machine console in XenCenter or via SSH, if you prefer. Copy and paste the commands from this manual directly in the terminal will help to reduce the likelihood of errors.
It will help to have the following information about your environment at hand before you start. listed some of the instructions in this guide, you must have the appropriate values for your environment to replace:
| | the desired hostname for your machine. |
| | , the user name of your Red Hat subscription account. |
| | , the FQDN of the Windows domain controller. |
| | is the name of a user account on the Windows domain. |
| | is the name of a domain admin account on your Windows domain. |
| | is the NetBIOS name of your Windows domain activated. |
| | Kerberos realm name of your Windows domain activated. |
| | is the hostname of the appliance, activated |
you can by Hat in the Red customer portal Red Hat download 6 installation media, here :. https: //access.redhat.com/downloads
There are three variants of Red Hat. Desktop, server and workstation are only workstations and servers capable of and for the purposes of this guide, I use and recommend Workstation
You can download the CentOS 6 Install media directly, here :. http://wiki.centos.org/Download
As of this writing, the current point release for RHEL and CentOS 6 was 6.6, so that's what I've used for this guide. ( UPDATE: Since then I have also confirmed these steps to version 6.7 to work)
Build your VM in XenCenter with the Red Hat Enterprise Linux 6 (64 - bit) or CentOS 6 (64-bit) templates. Configure your VM optionally for this guide I used default options throughout. If the VM is booting an installation wizard, restart for this guide I will use the default options.
Once the installation is complete, log in as root User:
Intro to Vi
In this manual we will be 1945004 to change the vi [] text editor configuration files. If you have never used vi , it can intuitively behave a little counter first, so for the sake of those brand new to this, we will cover briefly basic functionality, ie open, edit and saving a file. Note that all keystrokes in vi case sensitive
an existing file open for editing, or create a new one, giving .:
vi
Vi has several different modes: one is normal mode in which typed keys interpreted as vi operations; the other is the insert mode, are inserted into the typed keys in the document. When vi first starts, it will run in normal mode, and that is what most new users is on.
Before you start typing in vi, press i button Insert mode display. When done typing, press the Esc button to return to normal mode.
to save the changes while typing in normal mode, a colon to the command mode:
: w
Where
: q
commands can be combined. store For example, in the same period type and end:
: wq
Sometimes vi require [1945011!] as confirmation before performing an action, the data could be discarded. For example, vi to quit without saving the changes type:
: q
All covers you have the tasks remaining to complete the leader , Vi has to offer a whole range of advanced features, and there are many tutorials in depth to guidelines of this text editor.
configuration of the network
Before we can do anything else, we need to set to get networking.
vi / etc / sysconfig / network-scripts / ifcfg-eth0
Change the ONBOOT [1945011:ZunächstwerdenwirdieNetzwerkschnittstellemitdemBefehlkonfigurieren] variable yes , so that the crosslinking is started automatically in the future, and set BOOTPROTO either static or dhcp .
If you are using a statically assigned IP address, then you need the variables [add IPADDR NETMASK GATEWAY DNS1 and DOMAIN and give them to your own environment the corresponding values:
If you just use DHCP configuration is much simpler:
If, as I , you have an environment where you want to obtain an address from DHCP, but must provide your own DNS server, you can add them to PEERDNS variable and reinstall it on No and then give it to the DNS1 [1945004und] DOMAIN variables, as we for static configuration did. Save
and terminate once the changes are complete [1945002[
If you have to manually specify a DNS server, regardless of whether you use DHCP, then you need to edit a second file:
vi /etc/resolv.conf
This file can be completely empty when you first open. Later this file is generated automatically, but right now you have to manually enter your DNS and domain name as follows:
Save and exit once the changes are complete.
Now we need to put our hostname. This includes a few different steps, the first is to change what our hostname will be set to boot:
vi / etc / sysconfig / network
Change HOST field to something more appropriate:
Note: Linux AD integration supports reliable no NetBIOS name more than 15 characters. To ensure that you do not run into problems later on, select a host name with 15 characters or less.
Save and exit.
The second step is to modify the Hosts file so that our hostname and FQDN properly reported for the loopback address:
vi / etc / hosts
they change so they list the rows with loopback addresses the FQDN, host name, and 'localhost', resulting in a file that looks like this:
save and exit
the final steps are to set the current host name and then restart the network service .:
hostname
service network restart
Once the service is restarted, you should have network connectivity.
Check the network configuration
on us for the changes to quickly check by following these instructions Before joining:
hostname
hostname -f
ifconfig
These commands should report the new hostname, FQDN and IP address of the computer, or
of the unit
Use register the following command to the system to Red Hat .:
-username register Subscription Manager =
updating the machine
This step is optional, it is recommended , The following command all available software updates to install:
yum update
Install Packages
the following command the tools are installed, we need, as we go through this guide progress:
yum lokkit ntp CIFS utils samba-winbind krb5-workstation authconfig pam_krb5 oddjob-mkhomedir
install we will install and configure the essential packages for Linux VDA:
yum java-1.7.0-openjdk postgresql postgresql-server postgresql-jdbc
service postgresql initdb
install service postgresql start
chkconfig postgresql on
We can confirm that PostgreSQL successfully initialized by the data dictionary query:
sudo -u postgres psql -c 'show data_directory '[1945002
Finally, we need to install a desktop environment:]
you should see something. The CentOS and RHEL 6.5 developed 6 Assists XenServer as lightweight server and does not come with a default:
yum group "Desktop" "Desktop Platform" "Fonts" "General Purpose Desktop" "X Window System", "Internet browser "
installation XenTools
In XenCenter, click VM -> XenServer Tools install . Once the XenTools ISO was mounted, enter the following commands:
mkdir / mnt / xentools
mount / dev / xvdd / mnt / xentools
/ mnt / xentools / Linux / install.sh
Start the VM
Start the VM with the following command:
reboot
When the machine comes back up, you may be presented with a configuration program:
If so choose exit.
Log on again as root continue users.
starting firewall
This step is optional, but recommended. Start the firewall with the following command:
lokkit -enabled
configuration NTP
Open the NTP configuration file with the following command:
vi /etc/ntp.conf
is NTP be configured refer to the Red Hat pool server default. Pay attention to the lines instead of server , remove the default entries and add your own start (this will usually be your domain controller):
Save and finish
they start the NTP service and make sure that it is set at boot time using the following commands to start .:
service ntpd restart
chkconfig ntpd join the following to
to the domain
is a single command. It takes care of the majority of configuration steps required domain users to authenticate via Winbind:
authconfig -disablecache -enablewinbind -enablewinbindauth -smbsecurity = ads -smbworkgroup =
Winbind default the system will not create keytab that require Kerberos tools to authenticate the computer account. We will fix this in the Samba configuration file:
vi /etc/samba/smb.conf
Add the following two lines in the [global] section of the file to make sure to stay outside of the , which generates authconfig for us:
kerberos method = secrets and keytab
winbind refresh tickets = true
This will force Winbind to create a system kEYTAB file and automatically renew tickets.
save and exit.
We also need to configure PAM to enable Kerberos ticket caching and creation of home directories for Winbind:
vi /etc/security/pam_winbind.conf
add or change to ensure the three lines below to comment on it (remove all leading semicolon) in the process:
krb5_auth = yes
krb5_ccache_type = file
mkhomedir = yes
[1945002speichernundbeenden]
now we are ready to actually join the domain .:
net ads join -w
service winbind start
winbind chkconfig on
verify domain authentication
the following steps are optional, but ESP recommended. The most common problems of this point are encountered further all domain authentication related, so it is helpful to ensure that the previous steps before he was to be successful.
It is worth mentioning that domain authentication for users noting and the machine itself to work through different mechanisms, it is possible that a production well to succeed while the other fails (eg domain user to a can log machine may that even successfully failed the domain join)
places it was sure to join the domain successfully.
net ads TESTJOIN
ensure that the keytab file was created, and contains valid key:
klist - ke
Verify that the machine is cached with the domain controller and a TGT ticket can authenticate:
kinit -k
klist
that domain user Make sure can authenticate to the domain:
wbinfo –krb5auth=
Finally, make sure that PAM is properly configured, and that the domain users can log in via Winbind. The easiest way to do this is to give:
exit
try Then login as a domain user: 
give
Thereafter, They exit sign again and again, like the root users.
Delivery Configuring Controller
Each of your Delivery Controller to change its broker service can be configured before they will be capable of arranging meetings to Linux VDAS ,
in citrix-linuxvda-scripts-1.0.0.zip package you get a PowerShell script find named Update BrokerServiceConfig.ps1 , that must be performed on each and eVERY Delivery controller in the farm:
These changes are the placement of Windows VDAS not prevent configured to use the same delivery controllers. A single controller can manage farm and brokerage sessions both Windows and Linux VDAS seamlessly.
See section Delivery Controller to update to provide additional explanation Linux desktops in Linux Virtual Desktop Installation Guide.
Share of machinery catalogs and delivery groups
Now the machine in the domain, you can create your machine catalogs and delivery groups. The procedure is the same as for Windows VDAS, but with some restrictions
For machines catalogs for Linux VDA machines create .:
- Select 'server OS ' or ' Windows Server OS " for your operating system.
- Put not performed your machine as a power.
- Select Another service or technology " for your deployment method.
- do not mix Windows and Linux machines in the same catalog.
When creating delivery groups for Linux VDA equipment:
- Select 'desktops' for your delivery type [1945056not]. Machinery / catalogs in the same delivery group allow unauthenticated / anonymous login.
- not Windows and Linux mix.
See section about adding Linux machines machines catalogs and delivery groups in the Linux Virtual Desktop Installation Guide for more information.
Installation of Linux VDA
Now all the pieces in place, we are ready to install the Linux VDA. To do that, we need to get the RPM package on the machine. In my case I did this on a Windows share using the following commands: mount
mkdir / mnt / share
-tcifs -ousername =
cp /mnt/share/XenDesktopVDA-1.0.0.161-0.x86_64.rpm ~ /
Once a copy the RPM , install it using the following command:
yum install XenDesktopVDA-1.0.0.161-0.x86_64.rpm
This will draw in the last package dependencies
[the last step is the VDA to configure using the following command:
ctxsetup.sh
, the script will ask a series of questions about your environment. If you have followed these instructions literally then satisfies the standard answers to most questions. The only user information that it is need to provide the FQDN of your DDC:
When the script is complete HDX and VDA were configured and started services. You can confirm the services with the following commands are executed:
Service ctxhdx status
Service ctxvda status
If everything is configured correctly is, registration will occur within 10 to 20 seconds. Updating Citrix Studio and it should confirm that the registration was successful:
All that remains is to sign up to showcase and start your Red Hat 6 (or CentOS 6) Common Hosted desktop
that's it! Thank you for reading; I hope this has helped people start.
0 Komentar