Tecnología Thin Client Sistemas Informáticos

Total Page:16

File Type:pdf, Size:1020Kb

Tecnología Thin Client Sistemas Informáticos 2010 Tecnología Thin Client Sistemas Informáticos Luis Miguel Moya Moirón G990192 25/01/2010 SSII – Tecnología Thin Clients Página 1 Indice Sistema Informático desarrollado……………………………………………………………….......3 Objetivo…………………………………………………………………………………………………………….7 Introducción: ¿Qué es un Thin Client?...................................................................7 Visión general de la tecnología Thin Client………………………………………………………..8 Arquitectura en Red………………………………………………………………………………………….9 Hardware de un Thin Client……………………………………………………………………………..15 Software Thin Client………………………………………………………………………………………..22 Fundamentos Thin Client………………………………………………………………………………...25 Arranque por red…………………………………………………………………………………….…25 Sesión Remota…………………………………………………………………………………………..29 Ventajas de los Thin Client………………………………………………………………………………35 Desventajas de los Thin Client…………………………………………………………………………39 Escenarios Thin Client……………………………………………………………………………………..41 Protocolos Thin Client……………………………………………………………………………………..44 Protocolos para el arranque por red…………………………………………………………..44 Protocolo PXE……………………………………………………………………………………….44 Protocolo DHCP…………………………………………………………………………………….45 Protocolo TFTP……………………………………………………………………………………..47 Funcionamiento del protocolo PXE……………………………………………………….49 NBP………………………………………………………………………………………………………51 Protocolos para sesiones de escritorio remoto…………………………………………..51 X-Window System / XDMCP………………………………………………………………….52 VNC………………………………………………………………………………………………………59 Terminal Services / RDP………………………………………………………………………..60 Tecnología NX……………………………………………………………………………………….63 Comparativa Software Escritorio Remoto…………………………………………………..65 Software Libre en la Tecnología Thin Client……………………………………………………..72 Conclusiones……………………………………………………………………………………………………76 Bibliografía………………………………………………………………………………………………………76 SSII – Tecnología Thin Clients Página 2 Sistema Informático desarrollado El sistema desarrollado consiste en la Adaptación del Sistema Lan Core para el Sistema Operativo Linux, desarrollado inicialmente para el sistema operativo Windows. Lan Core es proyecto software libre con licencia GPL, que implementa en un sistema completo la Tecnología Thin Client que se detallará más adelante en este documento. En este documento nos vamos a centrar en resumir brevemente la adaptación realizada del sistema Lan Core a Linux y en presentar la Tecnología Thin Client. Para más información de Lan Core se puede consultar las siguientes direcciones Web: - Web oficial de Lan Core: http://lancore.sourceforge.net/ - Wiki de Lan Core: http://tedeco.fi.upm.es/wiki/Lan_Core - Source Forge de Lan Core: http://sourceforge.net/projects/lancore El desarrollo se ha realizado sobre un entorno Virtual VMWARE, en donde tenemos una máquina Linux con distribución Ubuntu 9.1 que actúa como servidor y una máquina que simula el Thin Client, se trata de una máquina de 128 Mb de RAM que no tiene disco duro. El desarrollo se ha llevado a cabo en varios pasos: 1. Configuración de los servicios en el servidor Linux para permitir al cliente el arranque por red. Esta tarea se ha realizado mediante la instalación y configuración los siguientes servicios: - Directorio boot de Lancore original. Este directorio mantiene todos los elementos que permiten arrancar al Thin Client: el cargador de arranque del sistema operativo PXELinux, una imagen de un sistema operativo empotrado basado en el kernel de Linux, un sistema de ficheros empotrado, drivers para los dispositivos gráficos y ficheros de configuración para el Thin Client. SSII – Tecnología Thin Clients Página 3 - Instalación y configuración de un servidor dhcp para permitir la asignación de una dirección IP al Thin Client. Esta tarea se ha llevado mediante la instalación del paquete dhcp3-server y la configuración del fichero de configuración dhcpd.conf. - Instalación y configuración de un servidor TFTP con soporte para el protocolo PXE para permitir la descarga del cargador de arranque y del sistema operativo en el arranque del Thin Client. Esta tarea se ha llevado a cabo mediante la instalación del paquete atftpd y su fichero de configuración. 2. Arranque por red del Thin Client y conexión a escritorio remoto de Windows. De esta manera se prueba que el arranque por red sobre Linux funciona correctamente, para posteriormente continuar con el flujo de ejecución que tenía en la versión para Windows y conectarse remotamente al escritorio Windows por RDP. 3. Configuración de un cliente Linux acceda remotamente a un escritorio Linux. Para realizar esta tarea se han realizado los siguientes pasos: - Instalación de una nueva máquina virtual que arranca una imagen Ubuntu 9.1 para simular un cliente Linux. - Instalación del paquete Xnest. - Configuración y habilitación en la máquina servidora de los servicios necesarios para permitir la conexión al escritorio remoto por XDMCP. - Prueba de conexión en local desde la máquina servidora a sí misma. - Comprobación del acceso en red desde la máquina cliente al servidor. SSII – Tecnología Thin Clients Página 4 - Prueba de conexión a escritorio remoto desde el cliente Linux al servidor por Xnest y login en la máquina servidora. 4. Generación del sistema operativo empotrado. En este paso lo que se ha realizado es la generación del sistema empotrado para el Thin Client, actualizando la versión del kernel a una actual. - Descarga de una versión del kernel Linux 2.4.6. - Configuración de los parámetros del kernel para generar una imagen genérica para i386 sobre vmware eliminando las funcionalidades innecesarias. - Compilación de una nueva imagen del kernel Generic- i386VMWare e instalación sobre nuestro directorio boot en el servidor, cambiando los parámetros de configuración para que el Thin Client arranque con la nueva imagen. - Prueba de arranque del Thin Client con la nueva versión del Kernel. 5. Generación del sistema de ficheros empotrado con soporte XDMCP. En este paso se ha generado un sistema de ficheros empotrado para el Thin Client con soporte para XDMCP, incluyendo Xnest como cliente para conexión a escritorio remoto, además se ha actualizado el sistema a las librerías y herramientas actuales. - Actualización de la versión busybox en el sistema de ficheros. - Actualización de las librerías utilizadas en nuestro sistema de ficheros empotrado. - Actualización de drivers, binarios y ficheros de configuración relacionados con el sistema X-Window. - Inclusión de versión actual, acorde a las librerías actualizadas, del binario Xnest. SSII – Tecnología Thin Clients Página 5 - Generación del fichero configuración del sistema X-Window para soporte genérico de dispositivos de E/S y optimizado para fbdev. - Generación del fichero de arranque de X para que llame al nuevo cliente Xnest. - Construcción de los nuevos módulos y drivers X-Window correspondientes a nuestro nuevo sistema actualizado en un fichero Generic-i386VMWare.sys de dispositivos. - Construcción del nuevo protocolo XDMCP.bin - Actualización del directorio boot con el nuevo protocolo, fichero de dispositivos e imagen del kernel. - Configuración de los parámetros para que nuestro Thin Client arranque con el nuevo kernel y sistema de ficheros empotrado. 6. Arranque Thin Client por red sobre Linux y conexión remota a Linux mediante el protocolo XDMCP. En este punto final se han probado los dos pasos anteriores y se ha comprobado el correcto funcionamiento del sistema. El Thin Client arranca por red gracias a nuestro servidor Linux, descarga el sistema actualizado y se conecta remotamente al propio servidor Linux mediante el nuevo protocolo XDMCP. Todos estos pasos se detallarán y explicarán en un Trabajo de Fin de Carrera en el cuál se entrará en profundidad en cada uno de los detalles del ThinOS de Lan Core y en cómo se realiza la actualización y generación de un nuevo sistema operativo empotrado, sistema de ficheros empotrado y protocolo de comunicaciones para conexión a escritorio remoto. A continuación continuamos con un trabajo de documentación en el que se presenta la tecnología Thin Client. SSII – Tecnología Thin Clients Página 6 Objetivo En este documento vamos a presentar y dar a conocer la tecnología Thin Client (Clientes Ligeros) dando una visión global. Los aspectos que se pretenden mostrar son los siguientes: • Visión general de la tecnología. • Como se organiza su arquitectura. • Hardware que entra en juego en la tecnología. • Software que soporta esta tecnología. • Ventajas y beneficios que aporta e inconvenientes. • Escenarios de ejemplo donde se pueden implantar. • Funcionamiento y bases de los sistemas Thin Client. • Protocolos involucrados. • Proyectos software libre actuales relacionados con esta tecnología. Introducción: ¿Qué es un Thin Client? Thin Client (Cliente ligero) es una computadora cliente en una arquitectura de red cliente-servidor que depende primariamente del servidor central para las tareas de procesamiento, y principalmente se enfoca en transportar la entrada y la salida entre el usuario y el servidor remoto, aunque normalmente el término Thin Client no se usa únicamente para denominar al cliente ligero, sino que se usa para nombrar a toda la red cliente-servidor como un sistema informático. A lo largo del presente documento usaremos el término sistema Thin Client para denominar a toda la red como un sistema informático o como una tecnología y cliente ligero para referirnos a una computadora cliente específica del sistema Thin Client. SSII – Tecnología Thin Clients Página 7 Visión general de la tecnología Thin Client Al diseñar un sistema informático o una red informática, hay decisiones que
Recommended publications
  • Lesslinux Handbook
    lesslinux.com Documentation Handbook Mattias Schlenker INUX August-Bebel-Str. 74 L 04275 Leipzig GERMANY ê [email protected] ESS L Contents 1 About LessLinux and this handbook2 2 LessLinux for users3 3 LessLinux for admins4 3.1 Remote access.......................................4 3.1.1 SSH.........................................4 3.1.2 VNC........................................5 3.1.3 RDP........................................6 3.1.4 Xpra........................................7 3.2 Netbooting LessLinux..................................7 3.2.1 CIFS or NFS boot.................................8 3.2.2 HTTP, FTP or TFTP boot.............................8 3.3 LessLinux as thinclient..................................9 3.3.1 Booting to Remmina...............................9 3.3.2 Booting to an RDP login mask.........................9 3.3.3 Booting to a chooser............................... 10 3.3.4 Using XDMCP.................................. 12 3.3.5 Local printers................................... 12 4 LessLinux for builders and contributors 13 4.1 Preparation........................................ 13 4.1.1 Prepare a drive.................................. 13 4.1.2 Create some directories............................. 14 4.1.3 Download the „sources”............................. 14 4.2 Build the first stage.................................... 14 2 Abstract LessLinux is a free Linux system designed to be light and easily modifiable. It is based on Linux from Scratch and was started by Mattias Schlenker in 2009. Since then it has been used as a base for dozens of security and rescue systems published by computer magazines all over the world. It’s simple architecture makes it easy to build LessLinux based systems for use as thinclient, software deployment or the demonstration of software. This book covers the possibilities of LessLinux and tells you how small changes can make LessLinux the lever you need to move your world.
    [Show full text]
  • THINC: a Virtual and Remote Display Architecture for Desktop Computing and Mobile Devices
    THINC: A Virtual and Remote Display Architecture for Desktop Computing and Mobile Devices Ricardo A. Baratto Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in the Graduate School of Arts and Sciences COLUMBIA UNIVERSITY 2011 c 2011 Ricardo A. Baratto This work may be used in accordance with Creative Commons, Attribution-NonCommercial-NoDerivs License. For more information about that license, see http://creativecommons.org/licenses/by-nc-nd/3.0/. For other uses, please contact the author. ABSTRACT THINC: A Virtual and Remote Display Architecture for Desktop Computing and Mobile Devices Ricardo A. Baratto THINC is a new virtual and remote display architecture for desktop computing. It has been designed to address the limitations and performance shortcomings of existing remote display technology, and to provide a building block around which novel desktop architectures can be built. THINC is architected around the notion of a virtual display device driver, a software-only component that behaves like a traditional device driver, but instead of managing specific hardware, enables desktop input and output to be intercepted, manipulated, and redirected at will. On top of this architecture, THINC introduces a simple, low-level, device-independent representation of display changes, and a number of novel optimizations and techniques to perform efficient interception and redirection of display output. This dissertation presents the design and implementation of THINC. It also intro- duces a number of novel systems which build upon THINC's architecture to provide new and improved desktop computing services. The contributions of this dissertation are as follows: • A high performance remote display system for LAN and WAN environments.
    [Show full text]
  • NCD Thin Client Xware User's Guide
    NCD NCD Thin Client Xware User’s Guide Part Number 5401612 June 1998 Network Computing Devices, Inc. 350 North Bernardo Avenue Mountain View, CA 94043-5207 Technical support: 503/641-2200 Technical support FAX: 503/641-2959 Email: [email protected] World Wide Web: http://www.ncd.com Copyright Copyright © 1998 by Network Computing Devices, Inc. The information contained in this document is subject to change without notice. NCD SHALL NOT BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR ANY DAMAGES WHATSOEVER, INCLUDING, WITHOUT LIMITATION, ANY INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL. This document contains information which is protected by copyright. All rights are reserved. Made in the U.S.A. No part of this document may be photocopied, reproduced, or translated to another language without the prior written consent of NCD. Title to and ownership of the Software, and all copies thereof, shall at all times reside with NCD and its licensors, and is protected by United States copyright laws and international treaty provisions. Trademarks Network Computing Devices is a registered trademark of Network Computing Devices, Inc. NCDnet, NCDware, and Thin Client Xware FTP are trademarks of Network Computing Devices, Inc. Apple and LaserWriter are registered trademarks of Apple Computer, Inc. Citrix, WinFrame, and ICA are registered trademarks of Citrix Systems, Inc. DECnet, DECwindows, VMS, VT, and ULTRIX are trademarks of Digital Equipment Corporation. Ethernet is a trademark of Xerox Corporation. Hewlett-Packard and LaserJet are registered trademarks of Hewlett-Packard Corporation. HP-UX is a trademark of Hewlett-Packard Corporation.
    [Show full text]
  • Cheat Sheet – Common Ports (PDF)
    COMMON PORTS packetlife.net TCP/UDP Port Numbers 7 Echo 554 RTSP 2745 Bagle.H 6891-6901 Windows Live 19 Chargen 546-547 DHCPv6 2967 Symantec AV 6970 Quicktime 20-21 FTP 560 rmonitor 3050 Interbase DB 7212 GhostSurf 22 SSH/SCP 563 NNTP over SSL 3074 XBOX Live 7648-7649 CU-SeeMe 23 Telnet 587 SMTP 3124 HTTP Proxy 8000 Internet Radio 25 SMTP 591 FileMaker 3127 MyDoom 8080 HTTP Proxy 42 WINS Replication 593 Microsoft DCOM 3128 HTTP Proxy 8086-8087 Kaspersky AV 43 WHOIS 631 Internet Printing 3222 GLBP 8118 Privoxy 49 TACACS 636 LDAP over SSL 3260 iSCSI Target 8200 VMware Server 53 DNS 639 MSDP (PIM) 3306 MySQL 8500 Adobe ColdFusion 67-68 DHCP/BOOTP 646 LDP (MPLS) 3389 Terminal Server 8767 TeamSpeak 69 TFTP 691 MS Exchange 3689 iTunes 8866 Bagle.B 70 Gopher 860 iSCSI 3690 Subversion 9100 HP JetDirect 79 Finger 873 rsync 3724 World of Warcraft 9101-9103 Bacula 80 HTTP 902 VMware Server 3784-3785 Ventrilo 9119 MXit 88 Kerberos 989-990 FTP over SSL 4333 mSQL 9800 WebDAV 102 MS Exchange 993 IMAP4 over SSL 4444 Blaster 9898 Dabber 110 POP3 995 POP3 over SSL 4664 Google Desktop 9988 Rbot/Spybot 113 Ident 1025 Microsoft RPC 4672 eMule 9999 Urchin 119 NNTP (Usenet) 1026-1029 Windows Messenger 4899 Radmin 10000 Webmin 123 NTP 1080 SOCKS Proxy 5000 UPnP 10000 BackupExec 135 Microsoft RPC 1080 MyDoom 5001 Slingbox 10113-10116 NetIQ 137-139 NetBIOS 1194 OpenVPN 5001 iperf 11371 OpenPGP 143 IMAP4 1214 Kazaa 5004-5005 RTP 12035-12036 Second Life 161-162 SNMP 1241 Nessus 5050 Yahoo! Messenger 12345 NetBus 177 XDMCP 1311 Dell OpenManage 5060 SIP 13720-13721
    [Show full text]
  • Netcat and Trojans/Backdoors
    Netcat and Trojans/Backdoors ECE4883 – Internetwork Security 1 Agenda Overview • Netcat • Trojans/Backdoors ECE 4883 - Internetwork Security 2 Agenda Netcat • Netcat ! Overview ! Major Features ! Installation and Configuration ! Possible Uses • Netcat Defenses • Summary ECE 4883 - Internetwork Security 3 Netcat – TCP/IP Swiss Army Knife • Reads and Writes data across the network using TCP/UDP connections • Feature-rich network debugging and exploration tool • Part of the Red Hat Power Tools collection and comes standard on SuSE Linux, Debian Linux, NetBSD and OpenBSD distributions. • UNIX and Windows versions available at: http://www.atstake.com/research/tools/network_utilities/ ECE 4883 - Internetwork Security 4 Netcat • Designed to be a reliable “back-end” tool – to be used directly or easily driven by other programs/scripts • Very powerful in combination with scripting languages (eg. Perl) “If you were on a desert island, Netcat would be your tool of choice!” - Ed Skoudis ECE 4883 - Internetwork Security 5 Netcat – Major Features • Outbound or inbound connections • TCP or UDP, to or from any ports • Full DNS forward/reverse checking, with appropriate warnings • Ability to use any local source port • Ability to use any locally-configured network source address • Built-in port-scanning capabilities, with randomizer ECE 4883 - Internetwork Security 6 Netcat – Major Features (contd) • Built-in loose source-routing capability • Can read command line arguments from standard input • Slow-send mode, one line every N seconds • Hex dump of transmitted and received data • Optional ability to let another program service established connections • Optional telnet-options responder ECE 4883 - Internetwork Security 7 Netcat (called ‘nc’) • Can run in client/server mode • Default mode – client • Same executable for both modes • client mode nc [dest] [port_no_to_connect_to] • listen mode (-l option) nc –l –p [port_no_to_connect_to] ECE 4883 - Internetwork Security 8 Netcat – Client mode Computer with netcat in Client mode 1.
    [Show full text]
  • The Application Usage and Risk Report an Analysis of End User Application Trends in the Enterprise
    The Application Usage and Risk Report An Analysis of End User Application Trends in the Enterprise 8th Edition, December 2011 Palo Alto Networks 3300 Olcott Street Santa Clara, CA 94089 www.paloaltonetworks.com Table of Contents Executive Summary ........................................................................................................ 3 Demographics ............................................................................................................................................. 4 Social Networking Use Becomes More Active ................................................................ 5 Facebook Applications Bandwidth Consumption Triples .......................................................................... 5 Twitter Bandwidth Consumption Increases 7-Fold ................................................................................... 6 Some Perspective On Bandwidth Consumption .................................................................................... 7 Managing the Risks .................................................................................................................................... 7 Browser-based Filesharing: Work vs. Entertainment .................................................... 8 Infrastructure- or Productivity-Oriented Browser-based Filesharing ..................................................... 9 Entertainment Oriented Browser-based Filesharing .............................................................................. 10 Comparing Frequency and Volume of Use
    [Show full text]
  • WIMP Interfaces for Emerging Display Environments
    Graz University of Technology Institute for Computer Graphics and Vision Dissertation WIMP Interfaces for Emerging Display Environments Manuela Waldner Graz, Austria, June 2011 Thesis supervisor Prof. Dr. Dieter Schmalstieg Referee Prof. Dr. Andreas Butz To Martin Abstract With the availability of affordable large-scale monitors and powerful projector hardware, an increasing variety of display configurations can be found in our everyday environments, such as office spaces and meeting rooms. These emerging display environments combine conventional monitors and projected displays of different size, resolution, and orientation into a common interaction space. However, the commonly used WIMP (windows, icons, menus, and pointers) user interface metaphor is still based on a single pointer operating multiple overlapping windows on a single, rectangular screen. This simple concept cannot easily capture the complexity of heterogeneous display settings. As a result, the user cannot facilitate the full potential of emerging display environments using these interfaces. The focus of this thesis is to push the boundaries of conventional WIMP interfaces to enhance information management in emerging display environments. Existing and functional interfaces are extended to incorporate knowledge from two layers: the physical environment and the content of the individual windows. The thesis first addresses the tech- nical infrastructure to construct spatially aware multi-display environments and irregular displays. Based on this infrastructure, novel WIMP interaction and information presenta- tion techniques are demonstrated, exploiting the system's knowledge of the environment and the window content. These techniques cover two areas: spatially-aware cross-display navigation techniques for efficient information access on remote displays and window man- agement techniques incorporating knowledge of display form factors and window content to support information discovery, manipulation, and sharing.
    [Show full text]
  • Development Version from Github
    Qtile Documentation Release 0.13.0 Aldo Cortesi Dec 24, 2018 Contents 1 Getting started 1 1.1 Installing Qtile..............................................1 1.2 Configuration...............................................4 2 Commands and scripting 21 2.1 Commands API............................................. 21 2.2 Scripting................................................. 24 2.3 qshell................................................... 24 2.4 iqshell.................................................. 26 2.5 qtile-top.................................................. 27 2.6 qtile-run................................................. 27 2.7 qtile-cmd................................................. 27 2.8 dqtile-cmd................................................ 30 3 Getting involved 33 3.1 Contributing............................................... 33 3.2 Hacking on Qtile............................................. 35 4 Miscellaneous 39 4.1 Reference................................................. 39 4.2 Frequently Asked Questions....................................... 98 4.3 License.................................................. 99 i ii CHAPTER 1 Getting started 1.1 Installing Qtile 1.1.1 Distro Guides Below are the preferred installation methods for specific distros. If you are running something else, please see In- stalling From Source. Installing on Arch Linux Stable versions of Qtile are currently packaged for Arch Linux. To install this package, run: pacman -S qtile Please see the ArchWiki for more information on Qtile. Installing
    [Show full text]
  • Gnome Display Manager Reference Manual Martin K
    Gnome Display Manager Reference Manual Martin K. Petersen [email protected] George Lebl [email protected] Brian Cameron [email protected] Bill Haneman [email protected] Table of Contents Terms and Conventions Used in This Manual ...............................................................3 Overview ................................................................................................................................3 Configuration.........................................................................................................................8 Controlling GDM ...............................................................................................................32 GDM Commands................................................................................................................38 Graphical Greeter Themes................................................................................................42 Accessibility.........................................................................................................................49 Example Configurations ....................................................................................................50 License...................................................................................................................................52 Terms and Conventions Used in This Manual This manual describes version 2.6.0.4 of the GNOME Display Manager. It was last updated on 7/14/2004. GDM - Gnome Display Manager. Used to describe the software package as
    [Show full text]
  • Protocol Filter Planning Worksheet, V7.X
    Protocol Filter Planning Worksheet Websense Web Security Solutions (v7.x) Protocol filter (name): Applies to (clients): In policy (name): At (time and days): Legend Action Bandwidth Permit Block Network Protocol (percentage) Protocol Name Action Log Bandwidth Database SQL Net P B N P % File Transfer FTP P B N P % Gopher P B N P % WAIS P B N P % YouSendIt P B N P % Instant Messaging / Chat AOL Instant Messenger or ICQ P B N P % Baidu Hi P B N P % Brosix P B N P % Camfrog P B N P % Chikka Messenger P B N P % Eyeball Chat P B N P % 1 © 2013 Websense, Inc. Protocol filter name: Protocol Name Action Log Bandwidth Gadu-Gadu P B N P % Gizmo Project P B N P % Globe 7 P B N P % Gmail Chat (WSG Only) P B N P % Goober Messenger P B N P % Gooble Talk P B N P % IMVU P B N P % IRC P B N P % iSpQ P B N P % Mail.Ru P B N P % Meetro P B N P % MSC Messenger P B N P % MSN Messenger P B N P % MySpaceIM P B N P % NateOn P B N P % Neos P B N P % Netease Popo P B N P % netFM Messenger P B N P % Nimbuzz P B N P % Palringo P B N P % Paltalk P B N P % SIMP (Jabber) P B N P % Tencent QQ P B N P % TryFast Messenger P B N P % VZOchat P B N P % Wavago P B N P % Protocol Filter Planning Worksheet 2 of 8 Protocol filter name: Protocol Name Action Log Bandwidth Wengo P B N P % Woize P B N P % X-IM P B N P % Xfire P B N P % Yahoo! Mail Chat P B N P % Yahoo! Messenger P B N P % Instant Messaging File Attachments P B N P % AOL Instant Messenger or ICQ P B N P % attachments MSN Messenger attachments P B N P % NateOn Messenger
    [Show full text]
  • "IT Tools in the Virtualization of the Software Implementation And
    INFORMATYKA EKONOMICZNA BUSINESS INFORMATICS 1(23) · 2012 ISSN 1507-3858 Iwona Chomiak-Orsa, Wiesława Gryncewicz, Maja Leszczyńska Wrocław University of Economics e-mail: [email protected] IT TOOLS IN THE VIRTUALIZATION OF THE SOFTWARE IMPLEMENTATION AND MAINTENANCE PROCESS Abstract: By implementing modern technological solutions, companies re-organize their activities. The remote software implementation process and then the remote maintenance mean for companies a new approach to gaining competitive advantage. In practice, it gives the opportunity to reduce costs and hence the prices of services. These two processes beco- me also independent of the geographical location of the client and the contractor, which can significantly reduce response time to reported problems and help ensure the higher quality of service. The IT support is needed to efficiently and quickly virtualize software imple- mentation and maintenance process, so the aim of this paper is to present and characterize such IT tools. Key words: virtualization, implementation, maintenance process. 1. Introduction Nowadays we are witnessing that the world has entered the information society era. The basic resources have become information and knowledge obtained from their processing. Digital products and services dominate the market. The availability of the transmission networks and sources of information has become more common and easier, while significantly reducing the costs of this access. Extensive use of IT tools in the economy, government, education and culture as well as in organization and management, has created new opportunities for all market participants and their environment [Steinmueller 2005, pp. 133–152]. By implementing modern technological solutions, companies re-organize their activities not only in the B&C context, but also in relation to other companies through the value-creation chain [Szpringer 2008, pp.
    [Show full text]
  • Apple Remote Desktop Protocol Specification
    Apple Remote Desktop Protocol Specification Demonology and foreknowable Bobby powwows almost dishonorably, though Rolland intoning his repassages aspiring. Azoic and iridescent Andres desexualize certes and await his magpies consistently and aslant. Ungrudged Virgil reacquires ornately. Free Rdp Demo Animals Way SA. Deciphering the Messages of Apple's T2 Coprocessor Duo. Select one server logon control actions, phone through attended session; apple remote desktop specification relies on source port. Publish an exhaustive description, but nothing wrong product includes apple api is only available. Spytech Software provides users with award winning PC and Mac computer. Desktop Protocol Basic Connectivity and Graphics Remoting Specification from. Remote fork and a Desktop ready for your PC Mac and Linux devices. Rdesktop A long Desktop Protocol Client. Nx client linux skarban. Realvnc multiple monitors mac Arte in zucca. For RDP exist for Microsoft Windows Mic04d and Mac OS X Mic04c. The remote desktop feature a compatible with direct mode run the Apple. VMWare Apple Remote Desktop Microsoft Remote Desktop Connection. Enter your machines. CudaLaunch Barracuda Networks. No longer need this is included in using notepad on? Recipe how the Apple Wireless Direct Link Ad hoc Protocol arXiv. Apple remote and free download mac. Ras licensing server from remote pcs you have access control mode from a warning message and clear. Open source vnc Symmetry Scribes. Live video streaming production software Tech Specs. Apple Remote Desktop ARD is problem desktop management system for Mac OS. Record level accessibility api decides what you can! Remote not Software BeyondTrust aka Bomgar Jump. Remote desktop retina display. Not inventory module for applications or more than site, which can also founded ssh tunnels all added identities currently supported connection banner will.
    [Show full text]