Implementing Red Hat Enterprise Linux 7 and Cent. OS7 Linux with Citrix Xen. Desktop 7. 1. 1As many of you know, I have a few documentation scripts freely available on my site. One of the scripts is for Citrix Xen. App/Xen. Desktop 7. Citrix introduced so many changes in version 7. I had to fork (to use a Git. Unified Gateway So up until now I’ve been talking about using the NetScaler Gateway option to deliver remote access to Citrix users. All the options above (except. How to build a WebRTC Gateway and integrate IBM Watson Speech-to-Text services 371 Views. Modern chemistry laboratories operate with a wide range of software applications under different operating systems, such as Windows, LINUX or Mac OS X. Instead of. Hub term) the script. Now there is a separate script for Xen. App/Xen. Desktop versions 7. I am working very hard to make sure I document all the details available for all the possible Machine Catalogs and Delivery Groups. Recently Citrix released Linux Virtual Delivery Agent (VDA) 1. I was curious what the differences were when a Linux Machine Catalog and Delivery Group are added to Citrix Studio. Would my script handle the Linux information or would I be in for some work to make my script handle Linux. Time to find out. I know how to spell Linux and that is as far as my Linux knowledge went. First, I had to see what versions of Linux the VDA supported. Off to see what the Citrix documentation stated. The following Linux distributions are supported by the Linux Virtual Desktop product: SUSE Linux Enterprise. Desktop 1. 2 Service Pack 1. Server 1. 1 Service Pack 4.
Server 1. 2 Service Pack 1. Red Hat Enterprise Linux. Workstation 6. 8. Workstation 7. 2. Server 6. 8. Server 7. Cent. OS Linux. A fellow CTP works for Red Hat so I figured I would start with Red Hat Workstation 7. From beginning to end, it took me six hours to get a Linux desktop published and accessed via Store. Front 3. 7. So now that I have a little bit of experience and know what is missing or doesn’t work in the Citrix documentation, I thought I would run through the entire process again using Cent. OS7 (since it is free and a kissing cousin to Red Hat Enterprise Linux) and, this time, document the process. I know there are others out there like me (scary thought) who would like to dip their toes into the Linux water and see what all the fuss is about this Linux VDA. I am using VMware v. Sphere/v. Center 6. U2 as my hypervisor and a Synology 1. TB of SSD storage for my datastore. I want to thank three of my fellow CTPs who know a lot about Linux for answering my hundreds of questions and reviewing this content: The World’s Oldest CTP Tobias Kreidl, Mr. Linux Tom Gamull and pseudo Klingon Chris Rogers. Note: I know some of you Linux people are going to complain and say; I should be doing all this work from the CLI in Terminal. Well, you are what is wrong with the world and why we cannot have beautiful GUIs. Sorry Word. Press does not offer a sarcasm font)Installing and doing the basic configuration of either version is very easy and all done during the installation process. I created a user and set that user as administrator. The first thing I did after logging in was on Red Hat Linux was to register. Then on both systems, I went to Application - > System Tools - > Software Update to make sure my system was up- to- date. Figure 1. Figure 2. Next step was to follow the horribly laid out Citrix instructions for Preparing the Linux machine for Virtual Desktop installation. I will be following the instructions for RHEL7/Cent. OS7. I am sure it is bad practice but I am logged in as root so I don’t get a bunch of “you ain’t the owner of this here file” errors when I attempt to edit a file. To log in as root, logoff as the current user, select Not listed and enter root when prompted for a username.[Tobias: Alternately, if you have the privileges, you could just su to root. Webster: Whatever that means)]Note 1: Enter all commands given in the following steps in Terminal while logged in as root. Note 2: Whenever a file is modified with gedit, Save the file and then exit gedit. Following these two Notes will save me a lot of repeated typing and then I will not have to be redundant and superfluous. Step 1 Verify the network configuration. Make sure your network interface is setup and has an IP address. Applications - > System Tools - > Settings - > Network. Figure 3. Figure 4. Figure 5. Step 2 Set the hostname. To ensure that the hostname of the machine is reported correctly, change the /etc/hostname file to contain only the hostname of the machine. Places - > Computer. Figure 6. Double- click the /etc folder, scroll down to the hostname file, right- click and select Open With gedit. Figure 7. Verify the computer name is correct and exit the editor. What you should see is what we Windows people call the Net. BIOS name. It should not show the FQDN of the host. Stay in the etc folder. Step 3 Assign a loopback address to the hostname. To ensure that the DNS domain name and FQDN of the machine are reported back correctly, change the following line of the /etc/hosts file to include the FQDN and hostname as the first two entries: 1. For example: 1. 27. This one I don’t fully understand. The machine is not a member of a domain yet but the FQDN of the machine is needed here. There are two closely named files: host. It is the hosts file that needs to be changed. Right- click the hosts file and select Open With gedit. Note: If you see Read- only next to the filename, you are not logged in as root and you cannot edit the file. Bad person. You didn’t follow my instructions before Step 1. Tsk, tsk. Note: We are ignoring IPv. Here is my hosts file before and after my change. Figure 8. Figure 9. Step 4 Check the hostname. Verify that the hostname is set correctly. A command prompt is needed. That means Terminal is needed. Applications - > Favorites - > Terminal. Figure 1. 0Type in hostname and press enter. This should return what we Windows people like to call the Net. BIOS name. It should not return the FQDN. That is next. Figure 1. Type in hostname - f and press enter. This should return the FQDN. Figure 1. 2Leave Terminal running. Step 5 Check name resolution and service reachability. Verify that you can resolve the FQDN and ping the domain controller and Xen. Desktop Delivery Controller. Enter the following commands: nslookup domain- controller- fqdnping domain- controller- fqdn - c 4nslookup delivery- controller- fqdnping delivery- controller- fqdn - c 4. Note: Those Linux people sometimes prefer to use dig instead of nslookup. Figure 1. 3Figure 1. Step 6 Configure clock synchronization (NTP)Citrix wants us to edit the /etc/chrony. You should be logged in as root still. Go back to what we Windows people call File Explorer. You should still be in the /etc folder. Right- click the chrony. Open With gedit. Here is my before and after. Figure 1. 5Figure 1. After you save your changes and exit the editor the chrony daemon must be restarted./sbin/service chronyd restart. Note: As you can see in Figure 1. RHEL7/Cent. OS7 preferred command is systemctl restart chronyd. Note: If you are also looking at the Citrix documentation, you will notice many of the commands to follow are preceded by “sudo“. What is this sudo thing? There are two ways to run administrative applications in Linux. You can either switch to the super user (root) with the su command. How you do this will depend upon which distribution you use. Some distributions enable the root. Fedora, Red Hat, open. Su. SE), while some do not (such as Ubuntu and Debian). There are pros and cons for each. Sudo stands for either "substitute user do" or "super user do" (depending upon how you want to look at it). What sudo does is. Linux distributions. Effectively, sudo allows a user to run a program as another. Since we are logged in as root, there is no need to use sudo in front of all the commands. However, I will continue to use sudo because from what I was told, sudo logs all activity so it is good practice. Figure 1. 7Step 7 Install Open. JDKThe Linux VDA is dependent on Open. JDK. The runtime environment should have been installed as part of the operating system installation. Confirm the correct version: sudo yum info java- 1. Figure 1. 8The pre- packaged Open. JDK may be an earlier version. Update to the latest version: sudo yum - y update java- 1. Figure 1. 9Set the JAVA_HOME environment variable by adding the following line to ~/. JAVA_HOME=/usr/lib/jvm/java. What the heck is “~/”? In Linux that is the user’s home folder. Every user has one including the root account we are logged in as. Tobias Kreidl provided me with a very quick way of adding that line to the user’s bashrc file: echo “export JAVA_HOME=/usr/lib/jvm/java” > > ~/. Tobias: The other cool feature of this is that even if JAVA_HOME is defined earlier in the script, in Linux, whatever comes last will override anything defined earlier. Remote Desktop Protocol - Wikipedia. Remote Desktop Protocol (RDP) is a proprietary protocol developed by Microsoft, which provides a user with a graphical interface to connect to another computer over a network connection. The user employs RDP client software for this purpose, while the other computer must run RDP server software. Clients exist for most versions of Microsoft Windows (including Windows Mobile), Linux, Unix, OS X, i. OS, Android, and other operating systems. RDP servers are built into Windows operating systems; an RDP server for Unix and OS X also exists. By default, the server listens on TCPport 3. UDP port 3. 38. 9.[2]Microsoft currently refers to their official RDP client software as Remote Desktop Connection, formerly "Terminal Services Client". The protocol is an extension of the ITU- TT. History[edit]Every version of Microsoft Windows from Windows XP onwards[4] includes an installed Remote Desktop Connection (RDC) ("Terminal Services") client (mstsc. Windows Service Pack. The Terminal Services server is supported as an official feature on Windows NT 4. Terminal Server Edition, Windows 2. Server, all editions of Windows XP except Windows XP Home Edition, Windows Server 2. Windows Home Server, on Windows Fundamentals for Legacy PCs, in Windows Vista Ultimate, Enterprise and Business editions, Windows Server 2. Windows Server 2. R2 and on Windows 7 Professional and above.[citation needed]Microsoft provides the client required for connecting to newer RDP versions for downlevel operating systems. Since the server improvements are not available downlevel, the features introduced with each newer RDP version only work on downlevel operating systems when connecting to a higher version RDP server from these older operating systems, and not when using the RDP server in the older operating system.[clarification needed]Version 4. Based on the ITU- T T. T. share") from the T. RDP (named version 4. Microsoft with "Terminal Services", as a part of their product Windows NT 4. Server, Terminal Server Edition. The Terminal Services Edition of NT 4. Citrix's Multi. Win technology, previously provided as a part of Citrix Win. Frame atop Windows NT 3. Microsoft required Citrix to license their Multi. Win technology to Microsoft in order to be allowed to continue offering their own terminal- services product, then named Citrix Meta. Frame, atop Windows NT 4. The Citrix- provided DLLs included in Windows NT 4. Terminal Services Edition still carry a Citrix copyright rather than a Microsoft copyright. Later versions of Windows integrated the necessary support directly. The T. 1. 28 application sharing technology was acquired by Microsoft from UK software developer Data Connection Limited.[5][6]Version 5. This version was introduced with Windows 2. Server, added support for a number of features, including printing to local printers, and aimed to improve network bandwidth usage. Version 5. 1[edit]This version was introduced with Windows XP Professional, included support for 2. The client is available for Windows 2. Windows 9x, Windows NT 4. With this version, the name of the client was changed from Terminal Services Client to Remote Desktop Connection; the heritage remains to this day, however, as the underlying executable is still named mstsc. Version 5. 2[edit]This version was introduced with Windows Server 2. It also introduces Transport Layer Security (TLS) 1. This version is built into Windows XP Professional x. Edition and Windows Server 2. Editions. Version 6. This version was introduced with Windows Vista and incorporated support for Windows Presentation Foundation applications, Network Level Authentication, multi- monitor spanning and large desktop support, and TLS 1. Version 6. 0 client is available for Windows XP SP2, Windows Server 2. SP1/SP2 (x. 86 and x. Windows XP Professional x. Edition. Microsoft Remote Desktop Connection Client for Macintosh OS X is also available with support for Intel and Power. PC Mac OS versions 1.Server 2. 01. 2 can support RDC 6. Version 6. 1[edit]This version was released in February 2. Windows Server 2. Windows Vista Service Pack 1. The client is included with Windows XP SP3.[1. In addition to changes related to how a remote administrator connects to the "console",[1. Windows Server 2. Version 7. 0[edit]This version was released to manufacturing in July 2. Windows Server 2. R2, as well as with Windows 7.[1. With this release, also changed from Terminal Services to Remote Desktop Services. This version has new functions such as Windows Media Player redirection, bidirectional audio, multi- monitor support, Aero glass support, enhanced bitmap acceleration, Easy Print redirection,[1. Language Bar docking. The RDP 7. 0 client is available on Windows XP SP3 and Windows Vista SP1/SP2 through KB9. RDP 6. 1 client and RDP 7. Windows Server 2. Windows Server 2. Windows XP Professional x. RDP 7. 0 is also not supported on Windows Server 2. RDP 7. 0 clients also do not support connecting to terminal servers running Windows 2. Server.[1. 7]Most RDP 7. Aero glass remote use, bidirectional audio, Windows Media Player redirection, multiple monitor support and Remote Desktop Easy Print are only available in Windows 7 Enterprise or Ultimate editions.[1. SP1 and Server 2. R2 SP1. It adds Remote. FX functionality. Version 8. 0[edit]This version was released in Windows 8 and Windows Server 2. This version has new functions such as Adaptive Graphics (progressive rendering and related techniques), automatic selection of TCP or UDP as transport protocol, multi touch support, Direct. X 1. 1 support for v. GPU, USB redirection supported independently of v. GPU support, etc.[2. A "connection quality" button is displayed in the RDP client connection bar for RDP 8. UDP is in use or not.[2. The RDP 8. 0 client and server components are also available as an add- on for Windows 7 SP1. The RDP 8. 0 client is also available for Windows Server 2. R2 SP1, but the server components are not. The add- on requires the DTLS protocol to be installed as prerequisite.[2. After installing the updates, for the RDP 8. Windows 7 machines, an extra configuration step is needed using the Group Policy editor.[2. A new feature in RDP 8. RDP session nesting; it only works for Windows 8 and Server 2. Windows 7 and Server 2. R2 (even with the RDP 8. The "shadow" feature from RDP 7, which allowed an administrator to monitor (snoop) on a RDP connection has been removed in RDP 8. The Aero Glass remoting feature (applicable to Windows 7 machines connecting to each other) has also been removed in RDP 8.[2. Version 8. 1[edit]This version was released with Windows 8. Windows Server 2. R2. A RDP 8. 1 client update exists for Windows 7 SP1 as well, but unlike the RDP 8. Windows 7, it does not add a RDP 8. Windows 7. Furthermore, if RDP 8. Windows 7, the KB 2. RDP 8. 0 client and server components) update must be installed before installing the RDP 8. Support for session shadowing was added back in RDP version 8. This version also fixes some visual glitches with Microsoft Office 2. Remote. App.[2. 5]Version 8. RDP protocol also enables a "restricted admin" mode. Logging into this mode only requires knowledge of the hashed password, rather than of its plaintext, therefore making a pass the hash attack possible.[2. Microsoft has released an 8. Version 1. 0. 0[edit]Version 1. RDP protocol includes the following new features: Auto. Size zoom (useful for Hi. DPI clients).[2. 9] In addition graphics compression improvements were included utilizing H. AVC.[3. 0]Features[edit]3. RC4 encryption algorithm, as of Version 6.[3. Audio Redirection allows users to process audio on a remote desktop and have the sound redirected to their local computer. File System Redirection allows users to use their local files on a remote desktop within the terminal session. Printer Redirection allows users to use their local printer within the terminal session as they would with a locally- or network- shared printer. Port Redirection allows applications running within the terminal session to access local serial and parallel ports directly. The remote computer and the local computer can share the clipboard. Microsoft introduced the following features with the release of RDP 6. Seamless Windows: remote applications can run on a client machine that is served by a Remote Desktop connection. It is available since RDP 6.[3. Remote Programs: application publishing with client- side file- type associations. Terminal Services Gateway: enables the ability to use a front- end IIS server to accept connections (over port 4.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
October 2017
Categories |