Terminal Administrations in Windows Server ® 2008.

Uploaded on:
Category: Sales / Marketing
Terminal Administrations in Windows Server ® 2008 Prologue to Terminal Administrations Arranging and Outline What Is IPD?
Slide 1

Terminal Services in Windows Server ® 2008 Introduction to Terminal Services Planning and Design

Slide 2

What Is IPD? Framework Planning and Design (IPD) gives arranging and configuration direction that means to clear up and streamline the arranging and outline process for Microsoft base advancements. IPD: Defines choice stream Describes choices to be settled on Relates choices and choices for the business Frames extra inquiries for business understanding IPD Guides are accessible at www.microsoft.com/ipd

Slide 3

Getting Started Terminal Services in Windows Server ® 2008

Slide 4

Terminal Services in Windows Server 2008 and the Core Infrastructure Optimization Model Basic Rationalized Dynamic Standardized Identity and access administration Desktop, gadget, and server administration Security and systems administration Terminal Services in Windows Server 2008 Data assurance and recuperation

Slide 5

Purpose and Overview Purpose To give direction to outlining a Terminal Services foundation Agenda Terminal Services in Windows Server 2008 components Terminal Services base configuration process

Slide 6

Terminal Services in Windows Server 2008 Overview Presentation virtualization section of Microsoft’s virtualization innovations Enables brought together application administration

Slide 7

New Features in Windows Server 2008 TS RemoteApp Shortcuts on the Start menu TS Web Access Launch Terminal Services applications through a Web page TS Gateway Remote access without virtual private systems (VPNs) TS Session Broker Load adjusting TS Easy Print No more printer driver disarray

Slide 8

Terminal Services in Windows Server 2008 Architecture

Slide 9

Terminal Services Decision Flow

Slide 10

Determine the Presentation\'s Scope Virtualization Project Determine the area scope Which areas will be served by this execution? Focus the application degree Define which applications Terminal Services will have What advantages are wanted from presentation virtualization? Expense Service levels Remote access Centralized administration Application similarity fix Platform freedom

Slide 11

Determine Which Applications to Deliver and How They Will Be Used Gather data about clients and applications Numbers of clients Applications they run Customizations and prerequisites

Slide 12

Determine Whether Terminal Services Can Deliver Each Application Examine each application’s ability to be served Possible business issues Licensing cost and issues Legal Potential specialized issues Operating framework similarity Multi-client environment similarity Server asset use Bandwidth utilization Rank applications by suitability Good competitor Some issues Not suitable for Terminal Services

Slide 13

Appendix B Job Aid

Slide 14

Categorize Users Categorize how clients utilize their PCs Helps with calculating the number and size of the terminal servers Heavy client Has specific applications, uses propelled application highlights, and spends a large portion of the day at the PC Graphic craftsman, engineer, designer Normal client Frequent PC utilize however runs generally spreadsheets, email customer, and word-preparing applications Administrative colleague, businessperson, maker Light client Uses the PC occasionally to check email or take an interest in a work process Hospital volunteer, cook, mechanical production system laborer

Slide 15

Determine the Number of Terminal Server Farms Each server in a ranch Same applications introduced Configured indistinguishably Start with one homestead and add more ranches just as essential Conditions that may require the execution of extra homesteads:

Slide 16

Map Applications and Users to Farms

Slide 17

Design the Farm Select a structure component for the server CPU, memory, circles, circle limit Determine the quantity of terminal servers needed in the ranch Number of clients/greatest number of clients per server = number of servers expected to handle a most extreme burden Determine the quantity of extra servers needed for adaptation to internal failure Extra servers for expanded client limit in the event that a server goes disconnected from the net Determine the quantity of servers needed for TS Web Access Cannot be shared among homesteads Cannot be facilitated on a terminal server

Slide 18

Step 7 Job Aid

Slide 19

Determine Where to Store User Data Decide client profile approach/stockpiling area Mandatory versus Roaming Storage size and area Different profiles for diverse homesteads fundamental? \\fileserver\share\%FarmName%\%username% Decide client information strategy/stockpiling areas Space obliged Storage area Design stockpiling for client profiles and information Capacity needed for all clients Performance Fault resilience

Slide 20

Size and Place the Terminal Services Role Services for the Farm Design and spot the Terminal Servicesâ  Session Brokers Place no less than one TS Session Broker anyplace there is a topographically isolated ranch, then add more to give adaptation to non-critical failure and handle burden Design and spot the Terminal Services Licensing Servers Start with one TS Licensing server, include another for adaptation to internal failure, then add more as important to handle the heap

Slide 21

Size and Place the Terminal Services Role Services for the Farms Design and spot the Terminal Services Gateway servers Only required if clients without VPN access oblige access through a firewall At slightest one shortcoming tolerant TS Gateway at every purpose of access through a firewall Requires an authentication that is either self-marked or trusted accreditation power (CA) Can be consolidated with Microsoft ® Internet Security and Acceleration (ISA) Server or Microsoft Forefront™ Internet Application Gateway for expanded security If indeterminate what number of part servers are obliged, a heap test can be performed to gauge limit

Slide 22

Job Aid with Role Server Information Added

Slide 23

Secure the Communications Determine the encryption level between customer PCs and the terminal server 56 bit, 128 bit, Federal Information Processing (FIPS) 140 Determine whether to seal the correspondences Use Transport Layer Security (TLS)/Secure Sockets Layer (SSL) to keep a man-in-the-center assault Determine the CA Determine whether to embody with Hypertext Transfer Protocol over SSL (HTTPS) Require HTTPS Web get to so port 3389 can be shut on the firewall.

Slide 24

Conclusion If outlined appropriately, Terminal Services in Windows Server 2008 can spare the association cash while expanding security and application accessibility Planning is key This aide offers major building direction. Allude to item documentation for extra points of interest. All the IPD Guides are accessible at www.microsoft.com/ipd

Slide 25

Questions? .:tslide

View more...