Aucune remarque pour cette diapositive
Il apparaitévidentque les décideursinformatiquessontconfrontés à de véritables challenges, posés par leurscollaborateurs.Ilest important d’apporterune solution à cesnouvellesproblématiques, car quand les utilisateursdisposentd’outils qui leurconviennentilssontplus impliqués, plus créatifs, plus productifs.Cettedémarchepermetégalement de garder le contrôle et de sécuriserle poste de travail et les informationsqu’ilcontient.
Connection Broker : équilibre de chargeRD Gateway : passerelle pour l’extérieur de l’enteprisePortail Web : ouque je soisdansl’entrepriseRD Virtualization : rôle à installer sur le srvHyperV[Build 1] – The following slide provides a high level overview of the components in RDS. We will look at the new RDSH and RDVH technologies in depth later on.Remote Desktop Session Host Server provides a similar set of functionality as Terminal Server.RD Virtual Host Server is a hyper-v based server that is used to provide VDI functions.RemoteApp and Desktop Web Access Server provides a web based interface for RemoteApp enabled applications as well as one click access to virtual desktops. Highlight that you need Windows 7 on the client to take full advantage of Desktop Connections.RD Gateway to offer secure remote access to RDS servers and infrastructureAll components require an RDS licensing serverPermissions and policy is stored in Active Directory[Build 2]Remote Desktop Client gets connection information from the RD Web Access Server. If the client is outside the network the client connects through the RD Gateway server, if they are internal then can connect directly to an RDSH or RDVH server. In both cases the server that the client connects to is negotiated by the RD connection Broker. The connection broker plays a central role in RDS to make sure clients get connected to appropriate resources. It also helps clients reconnect to disconnected or interrupted session, and makes sure that clients are connecting to the correct servers for VDI resources. At a high level the remote client uses the RD Gateway to obtain access to the RDSH RD Session Host and RDVH servers.The RD Connection Broker connects clients to sessions and VMs on the RDSH and RDVH servers.All Remote Desktop Servers require validation with an RD Licensing Server.
Eliminates duplicate app dataLess storage spaceLower storage costThe scenario is that the shared cache allows the client machines to have a 1:many relationship with the SAN storage. Many machines can access one location, grab the virtual application and use it within their virtual desktop. They do not need to stream the application at launch as it is already preloaded in the cache. This makes the application launch faster. By using the shared cache IT save tons on SAN Storage as the application no longer needs to be delivered/duplicated/stored at each virtual desktopYou have the following:1. A regular desktop client that is on hardware think today's laptop2. That client has the ability to launch a connection to a server that hosts a virtual desktop.3. The virtual desktop is stored on a SAN and is delivered over the network to the client4. Inside of the virtual desktop are the virtual applications.5. When the virtual desktop is delivered to the client is pulls the application from the single SAN storage area. The application runs from the storage location6. The desktop client received the virtual desktop over the network and the applications are running and ready to go, they do not have to wait for the applications to be delivered separatelyThis scenario applies to multiple desktops/clients so if there are 1000 machines that are running virtual desktops they would get it in this manner.Scenario Deviation: This scenario can be initiated from a thick desktop client or a thin client.