Remote Desktop

ever wished you could access your PC from the road? With Remote backcloth inWindows 7, you jakes. Remote Desktop connects two entropy treat remainss over a net or the Internet. Once connected, youll leave the remote computers desktop as if you were sitting right in sc ber of it, and sacrifice access to every its programs and files. This feature is included with exclusively editions of Windows 7, notwithstanding you croup save connect to computers legislatening the Professional, Ultimate, or Enterprise editions. use up Remote Desktop to access unmatched computer from another remotely.For example, you bear use Remote Desktop to connect to your work computer from home. You exit have access to all of your programs, files, and internet resources, as if you were sitting in front of your computer at work. While you be connected, the remote computer screen entrust appear blank to anyone at the remote perspective who sees it. Server and Client Requirements The computi ng model for thin- leaf node networking means that the horse forcefulness is operose on the emcee end, not the client end. Because the horde will be condescending dozens of people maybe hundreds this is not the time to work on power.Server Hardw ar The notion of victimization a bigger server so that you can skimp on client-side hardw atomic number 18 isnt new. Thats all a file server is a computer performning a big, quick hard saucer so that you dont have to buy big, fast hard disks for everyone in the office. RDS servers are designed on a akin principle if nigh of the processing takes place in a virtuoso location, you can concentrate the hardware resources needed to support that processing in a single location and worry less about power on the client end.Use a Powerful RD academic session army Server Since an RD Session Host server will be luck applications or full desktops to clients, youll need to purchase or build a powerful server. Processing power and RAM are the to the highest degree definitive resources. Depending on the types and repress sittings youre supporting, you may also want to consider boosting disk access and network bandwidth. On the surface, calculating the needs seems straightforward. Just repre move these steps 1. 2. Calculate the resources needed for the in operation(p)(a) dodge. 3. . Calculate the resources needed for a dwarfish soma of sessions ( such(prenominal) as five). 5. 6. Multiply the resources needed for your sessions based on the total deed of sessions you plan to support. If you planned to support one C sessions and you calculated five sessions, youd multiply by 20 (20 * 5 = 100 sessions). 7. 8. hang on the total session resources needed for sessions to the resources needed for the operating system. Although this seems a deal simple math, it never seems to work out that way. synergy is often hard to predict.Synergy (where the whole is greater than the sum of its parts) often results in or soth ing unexpected. Additionally, if the deployment is successful and drug substance abusers are happy with what they can do, they may end up using it very much much than you carryd. You dont need to tell this to the bud pay off people, but its best to rack up a buffer for the unknowns and to plan for expansion. Additionally, you should do more or less in cipherent look starting with Microsofts Remote Desktop Services home www. microsoft. com/windowsserver2008/en/us/rds-product home. aspx. Core Hardware ResourcesFor the purposes of running an efficient RD Session Host server, the stark(a) minimum required to run Server 2008 R2 wont cut it. Although there are no hard-and-fast specifications for an RDS server, some general guidelines for server sizing go along Processor Faster is better to a point. More important than a fast processor is one with enough cache so that it doesnt have to reach out to the (slower) system retrospection for code and data. Faced with a choice between much cache and more speed, go with more cache. close RDS servers these days have multiple processors, and these processors have multiple cores.Although precisely multithreaded applications will actually use more than one processor at a time, if there are multiple processors, therefore(prenominal) threads needing functioning can line up at both. Memory RDS servers tend to be memory bound, not processor bound. Get high-speed, error-correcting memory ready softwood of it and be prepared to add more as you add more users or applications to the RDS server. The amount of memory youll need depends on the applications that people use, the number of concurrent sessions, and the memory demands of the files opened in those sessions computer-aided design (CAD) programs will striving the system more than, say, Notepad.Thankfully, the 64- function operating system goes well beyond the 4GB limit. get moving your calculations with at least 8GB of RAM for the server, and start adding based on the of number of users and memory required by the applications theyll run on the server. Windows Server 2008 R2 will support up to 2TB of RAM. Disk Consider back-to-back Computer carcass Interface ( microscopical computer system interface) disks on an RDS server if at all possible. A small computer system interface disk controller can multitask among all the devices in the SCSI chain.Most people believe that SCSI performs much better both Serial Advanced Technology Attachment(SATA) and Enhanced Integrated Drive Electronics (EIDE) disks, though some people are starting to hap that high-end SATA solutions perform better than low-end SCSI solutions. Disk deed is an important capability in any server, oddly so in an RDS server. Additionally, consider a Redundant Array of bargain-priced Disks (RAID) solution to increase the achievement and/or fault tolerance of the drives.For a high-end RDS server, a RAID 1+0 solution provides both performance gains and redundancy. Network On a busy RDS server, consider commove-balancing high-speed network cards, which can assign multiple NICs to the same IP address and therefore split the load of network traffic. Another alternative is a multihomed server with one NIC dedicated to RDS session traffic. As far as network speed goes, sending application output and client-side input back and frontward requires little bandwidth, but client-print jobs sent to mapped printers can take quite a bit of bandwidth.Mapped drives may also increase the load by qualification it possible to copy files back and forth across the RDP connection. Using the mathematical operation Monitor The exercise Monitor (discussed in Chapter 17) can help you get an idea of how RDS sessions are try oning the server. Server load should scale closely with the number of people using the server therefore, as long as you fragment a representative group of about five people, you should be equal to extrapolate your needs for larger groups. The key obje cts and counters for measuring eneral server stress introduced in that chapter will help you size your RDS servers. But a duad of work Monitor objects are worth examining to give you detailed information for your RDS server. proceeding Monitor Objects Still Called utmost Services Although the name of final stage Services has changed to Remote Desktop Services in Windows Server 2008 R2, its so far called Terminal Services in Performance Monitor. It might look like a typo, but the two objects are called Terminal Services and Terminal Services Session.First, the Terminal Services object has counters representing the number of active sessions (sessions where the user has connected to the RD Session Host server and successfully logged on), inactive sessions (where the user is still logged onto the RDS server but has stopped using the session), and the total combined. anyway simply monitoring activity, you could use this to alert you when the number of active session reaches a cert ain threshold. Say you wanted to know when a server hosts more than 100 sessions. You could do this with a data collector stripe.Chapter 17 discussed data collector comes in more depth, but its possible to set up a simple user-defined data collector set with an alert. This is through with(p) by creating the user-defined data collector set manually (not with a template), selecting Performance Counter Alert, and then setting the threshold for the active sessions. You can then set a task for the alert to notify you with a base script or log the event to a file. Although you can get some session-level information from the Remote Desktop Services Manager, a performance object called Terminal Services Session provides quite a bit more data.Use the Remote Desktop Services Manager to allow out the session you want to monitor sessions are identified in Performance Monitor by their session numbers, not user login name and then add counters to monitor that session. Each session object has processor and memory counters that should look familiar to anyone whos use Performance Monitor, but it also has session-specific counters such as the ones in Table 25. 1. We havent included all the counters here, just the ones to translate you the kind of information that will be useful when youre calculating the load on the server and looking at the kind of performance the sessions are getting.Table 25. 1 Key Terminal Services Session Performance Monitor Counters Counter Description See Also % Processor sentence Percentage of time that all of the threads in the session used the processor to execute instructions. On multiprocessor machines the maximum value of the counter is 100 percent times the number of processors. summarize Bytes aggregate number of bytes sent to and from this session, including all communications protocol overhead. Input Bytes, Output Bytes. Total Compressed Bytes Total number of bytes after compression.Total Compressed Bytes compared with Total By tes is the compression ratio. Total Compression ratio Total communications protocol Cache Hit Ratio Total hits in all protocol caches holding Windows objects likely to be utilized. Hits in the cache represent objects that did not need to be re-sent, so a higher hit ratio implies more cache reuse and possibly a more responsive session. Protocol Save quiz Bitmap Cache Hit Ratio, Protocol Glyph Cache Hit Ratio, Protocol Brush Cache Hit Ratio Working Set afoot(predicate) number of bytes in the Working Set of this session. Virtual Bytes, Page Faults/ irregular Wait on the License Server When experimenting with Remote Desktop sessions to find out how many users youll be able to support for each session, do not set up a license server let the RDS server issue its temporary 120-day licenses for this purpose. Although this sounds counterintuitive, using the temporary licenses prevents you from unwittingly delegate per-device licenses to test equipment. See the Licensing Mode section f or an explanation of how licensing and license tryst works.Client Hardware. When connecting to an RD Session Host server via a native RDP client, youll most often use a PC with a Windows operating system loaded, a Windows destination, or a handheld PC using Windows CE. autochthonic RDP Client In this context, a native RDP client means one available from Microsoft and thus implies Windows. Although Microsoft does not support other platforms (except for its OS X Macintosh client, available for download at www. microsoft. com/mac/products/remote-desktop/default. mspx), Hobsoft link sells a cross-platform (Windows, Mac, Linux, DOS) Java client at www. hobsoft. com/products/connect/jwt. sp, and there is a foreswear Linux RDP client available at www. rdesktop. org. Windows Terminals In its narrowest definition, a Windows lowest is a network-dependent device runningWindows CE that supports one or more display protocols such as RDP or Independent Computing Architecture (ICA), the displ ay protocol used to connect to Presentation Server servers. Many Windows terminals also support some form of terminal emulation. For this section, think of a Windows terminal as any terminal device designed to connect to a Windows RD Session Host server it can run any operating system that has an RDP client.A Windows-based terminal (WBT) is such a device thats running a Windows operating system locally CE or (more rarely) Windows XP/Vista for embed Systems and follows the Microsoft system design requirements for WBTs. The main thing defining a Windows terminal is its thin hardware profile because the main job of most Windows terminals is to run a display protocol, they dont need much memory or processing power, and they dont use any storage. A Windows terminal includes a processor some amount of memory, network, and video support and input devices such as a keyboard (or equivalent) and mouse (or equivalent).The terminals dont generally have hard disks, CD-ROMs, or DVD players. Th e operating system is stored in local memory. Beyond those similarities, Windows terminals range physically from a toaster form factor to a pad to a small box that can attach to the back of a monitor or even be part of the monitor itself. Some models of Windows terminals are receiving set tablets, intended for people (such as doctors and nurses) who would ordinarily use clipboards and be quieters to store information. Although most Windows terminals are constitutionally dependent on their RDS server, a small set of them can run applications locally.The devices still dont have hard disks the applications are stored in ROM like the operating system. The types of applications available depend on the terminals operating system, since locally stored applications mustiness run locally instead of just macrocosm displayed. Generally speaking, however, its more common for Windows terminals to depend on an RDS server for applications. Windows terminals are most pop in environments wher e people are using a single application, where supporting PCs would be logistically difficult, or anywhere else that PCs arent a near(a) fit.However, PCs still outnumber Windows terminals as thin clients. Part of this is because many environments cant depend totally on server-based computing. Companies already have PCs, and unless theyre refreshing the desktop entirely, pickings away a powerful PC to replace it with a less-powerful terminal doesnt really make sense. PC Clients At this point, people are using more than twice as many PCs as Windows terminals for RDS server client machines. This isnt surprising. First, unless theyre starting fresh, people already have the PCs.Even though WBTs are a little less expensive than low-end PCs (not much, though), theyre still an added cost. Second, not all applications work well in an RDS server environment. Its often best to run some applications from the RDS server and some locally. Unless youre buying new hardware and dont anticipate any need to run applications locally, youre likely to have to work with PCs for at least some of your terminal clients. To work with Remote Desktop Services, the PCs must be running a Windows operating system, have the RDP display protocol installed, and have a live network connection usingTCP/IP and a valid IP address.Handheld PCs Were surprised that handheld PCs (H/PCs) arent more popular than they are, given how handy they are. Theyre a terrific substitute for a laptop inexpensive, lightweight, and thrifty with their power so that you can actually use them during the entire flight instead of having to give up two hours after takeoff. (You can also use one on a plane without bedevilment that the person in front of you will suddenly recline their potty and crack your laptops display. ) Usually, they run Windows Mobile (previously known as Pocket PC).You can use wired, wireless LAN, or dial-up connections to connect to an RDS server. What an H/PC looks like depends on who makes it. S ome (mine among them) look like a laptops baby brother. Others fold into a little portfolio shape or are a matt tablet. Some are small pocket-sized deals that are too small to really work on. Some the ones we prefer have keyboards others have only pointers. What all this comes down to is that an H/PC isnt really in a position to replace a desktop PC. Instead, its usually used in cooperation with a desktop machine with which its partnered