kjrtaqoea
04-05-2011, 08:18 AM
From Techotopia PreviousTable of ContentsNext Configuring BitLocker Drive Encryption on Windows Server 2008Adding New GPT and MBR Disks to Windows Server 2008 Systems
Windows Server 2008 is, because the title suggests, a server running product. Within the real world this means that programs operating Windows Server 2008 will almost certainly be found in substantial rack systems inside a server room. As this kind of, it will be hugely unlikely that strategy administrators are going to wish to must physically have a look at each and every of those servers to perform schedule administrative tasks this kind of as method configuration and monitoring. A far preferable situation consists of these administrators remotely logging to the servers from their own desktop techniques to carry out administrative jobs. Thankfully Windows Server 2008 supplies exactly this performance by way of Remote Desktop plus the remote administration benefits in the Device Management Console (MMC). Within this chapter we are going to examine the steps important to remotely administer Windows Server 2008 techniques making use of Remote Desktop.
one What's Remote Desktop?
2 Enabling Remote Desktop Administration around the Remote Server
3 Managing Remote Desktop Access
4 Remote Desktop Group Policy
5 Commencing the Remote Desktop Client
6 Remote Desktop Consumer Configuration Methods
seven Remote Session Monitoring
eight Logging out from a Remote Desktop Session
nine Running A number of Remote Desktops
[edit] What's Remote Desktop? Remote Desktop makes it possible for the graphical interface of the remote Windows product to get displayed in excess of a network onto a local method. In addition, keyboard and mouse occasions on the local model are transmitted towards the remote product enabling the nearby consumer to execute jobs on the remote procedure as if they were physically sitting at the remote process. Conversely,Purchase Windows 7 (http://www.windows-7-key.us/), assets (such as printers and disk drives) on the nearby method may be created out there on the remote system for your duration for the connection. This remote control is established within a number of options, which include around huge region networks (WAN), nearby area networks (LAN) or around cyberspace.
In the circumstance of Windows Server 2008, this services is provided by Terminal Services operating to the remote techniques along with the Remote Desktop Connection (RDC) consumer on the community model.
Terminal Services run in two completely different modes,Office Pro 2007 Key (http://www.office2007-key.co.uk/), Administration and Virtual Session. Remote Desktop for Administration supplies total administration performance to the remote administrator (like access for the console session and visibility of notification messages). Remote Desktop for Administration will be the equivalent to functioning directly on the remote system's console. In virtual session mode the user is subject to some limitations such as the capability to set up programs and watch console notification messages.
Windows Server 2008 imposes some administrator logon restrictions. Particularly, a optimum of two administrators might be logged on at any an individual time, possibly two logged on remotely, or one particular neighborhood and one remote administrator. This assumes, nevertheless, that a variety of accounts are getting chosen to log on. In other words, the exact same user may perhaps not log on locally and remotely simultaneously.
[edit] Enabling Remote Desktop Administration on the Remote Server As talked about previously, remote desktop features about the server is provided by Terminal Providers. It can be very important to be aware, having said that,Office 2007 Standard (http://www.office2007-key.ca/), that Terminal Companies do not have for being explicitly enabled about the server to assistance Remote Desktop Administration. Actually, all that needs to be accomplished would be to permit Remote Desktop Administration. It is configured by opening the Manage Panel from your Launch menu and picking the Model icon (if the Manage Panel is in Control Panel Dwelling mode this really is situated beneath System and Servicing). With the Project area within the top rated left hand corner from the System page select Remote settings to screen the subsequent properties window:
The Remote properties dialog provides several methods. The default setting may be to disallow remote connections on the laptop computer program. The next option lets remote desktop connections from any version of your Remote Desktop client. The third, and most secure selection, will only permit connections from Remote Desktop purchasers with Network Stage Authentication assistance. This normally will only allow for entry to programs offering secure network authentication such as Windows Vista and Windows Server 2008.
If the Windows Firewall is active, the act of enabling Remote Desktop administration also brings about the development of a firewall exception enabling Remote Desktop Protocol (RDP) customers to pass due to on TCP port 3389. This default port can be transformed by shifting this setting with the Registry crucial HKEY_LOCAL_MACHINESystemCurrentControlSetControlTe rminalServerWinStationsRDP-tcpPortNumber. The easiest tactic to locate this registry vital worth is usually to execute regedit in the Run window or perhaps a command prompt,Office 2007 Key (http://www.office2007-key.in/), select Edit - > Find and enter RDP-tcp.
[edit] Controlling Remote Desktop Access The default configuration for Remote Desktop could be to allow all members of your Administration group to connect remotely. Energetic Directory also contains a Remote Desktop Users group to which users may be added to provide Remote Desktop access privileges. To provide users with remote desktop accessibility, open the Control Panel -> Method and Servicing -> System -> Remote settings and click about the Decide on Users button to invoke the Remote Desktop Users dialog illustrated in the following figure:
Be aware that users with administrative privileges never need to get added to this list; by default they already have Remote Desktop entry. To add additional users click around the Add... button to exhibit the Decide upon Users dialog. Enter the title with the consumer inside text box entitled Enter object names to find and click on Check names to list names that match the name entered. Pick out the appropriate identify through the list. The subsequent example shows user Bill on server winserver-2:
Click on OK to apply the change. The new consumer will now appear from the list of users with Remote Desktop entry to the Remote Users screen. Click OK to close this screen and click on Apply while in the Method Settings screen. The specified person will now have remote desktop entry to your product.
[edit] Remote Desktop Group Policy A vast array of configuration possibilities for Terminal Companies is accessible by using the Group Policy settings. To accessibility these values start out the Group Policy Object Editor (open the Get started menu and enter gpedit.msc in to the Search box). Inside Group Object Policy Editor navigate to Personal computer ConfigurationAdministrative TemplatesWindows ComponentsTerminal Services or Person ConfigurationAdministrative TemplatesWindows ComponentsTerminal Solutions to entry the range of policy settings out there.
Policy opportunities include, amongst other methods, items this sort of as management more than resource redirection (printers, audio etc), setting session time limits and security settings. A complete overview of all the settings is beyond the scope of this book but almost without exception the various settings are largely self-explanatory.
[edit] Commencing the Remote Desktop Customer With the appropriate configuration tasks completed about the remote technique the next step is usually to launch the Remote Desktop Consumer about the local strategy. The client can be run in both administration mode which provides full integration with the console in the remote server, or virtual session mode which gives you some administrative privileges but does not provide console entry or make it easy for programs to be installed.
To invoke the Remote Desktop Customer in virtual session mode either select Commence -> All Programs -> Accessories -> Remote Desktop Connection or enter the subsequent while in the Run dialog or at a command prompt:
mstsc To initiate the Remote Desktop Client in administrator mode run the subsequent command:
mstsc /admin In either case the subsequent initial screen will appear requesting details of desktop computer to which the consumer is usually to connect:
This can either be an IP address or a laptop computer title. If previous connections have been established the Person title field will be populated with the user title used inside the preceding session. If you need to log in as a a variety of consumer this opportunity will be supplied on the next screen which appears after the Connect button is pressed:
With this screen enter the password for that selected user (notice that remote desktop entry is only attainable for person accounts which are password protected). If a user other than the a single shown is required, simply click on the Use another account link and enter the needed details. Click on OK to establish the connection. After a short delay the remote desktop will appear around the neighborhood personal computer screen.
[edit] Remote Desktop Customer Configuration Selections The Options>> button displayed about the initial screen from the Remote Desktop Customer can provide six tabs,Windows 7 Starter (http://www.key-windows-7.co.uk/), every single containing a range of configuration alternatives:
General - Allows for login credentials to become configured and session information for being saved. Screen - Configures the resolution and color settings to be put to use when displaying the remote desktop around the local process. Community Sources - Specifies which nearby resources (sound, disk drives, printers etc) are to be designed accessible on the remote strategy during the Remote Desktop session. This page also supplies alternatives to manage the situations under which special primary combinations these as Ctrl-Alt-Del are interpreted by the local or remote methods. Programs - Makes it possible for specified programs for being automatically invoked each and every time a remote sessions is established. Experience - Controls which desktop elements are enabled or disabled for your Remote Desktop session. For example, over a slow dial-up connection it is unwise to get the desktop background displayed and font smoothing enabled. Either choose the connection type and speed to see recommended settings, or use Custom to configure your personal settings. This particular screen also gives the preference to have the connection automatically re-established within the event that a session is dropped. Advanced - Enables and disables remote server verification. This ensures that the remote server to which you are connected is indeed the server you wanted. Also on the market are TS Gateway settings. By default the Remote Desktop Customer is configured to automatically detect TS Gateway settings. [edit] Remote Session Monitoring With Remote Desktop access implemented it truly is often useful to find out at times who is logged into a program. This is often achieved working with the quser command-line tool. To obtain details of logged in users on a community strategy simply run quser at a command prompt or inside of a Run dialog:
C:UsersAdministrator> quser USERNAME SESSIONNAME ID STATE IDLE TIME LOGON TIME administrator 1 Disc 3:18 7/11/2008 12:36 PM bill rdp-tcp#0 2 Energetic . 7/14/2008 9:11 AM nas console three Lively none 7/11/2008 12:58 PM To obtain information for a remote method simply run quser with the /server:<hostname> command-line choice. For example:
C:UsersAdministrator> quser /server:winserver-2 USERNAME SESSIONNAME ID STATE IDLE TIME LOGON TIME administrator 1 Disc 3:22 7/11/2008 12:36 PM bill rdp-tcp#0 two Lively . 7/14/2008 nine:11 AM nas console 3 Active none 7/11/2008 12:58 PM [edit] Logging out from a Remote Desktop Session When the Remote Desktop Customer is exited by pressing the 'X' around the management panel the remote session continues to run to the server even though no client is connected. Next time the person connects the desktop session will appear exactly as it was left before.
To end the session find Start with the remote desktop session, click on the right arrow button while in the bottom right hand corner for the menu and decide upon Log Off. This will close down the remote desktop session and close the remote desktop consumer.
[edit] Operating Many different Remote Desktops A number of concurrent remote desktops can be run and managed within a single window employing the MMC Remote Desktops snap-in. This may perhaps either be snapped to the MMC or launched in the command-line or even a Run dialog by typing:
tsmmc.msc Once launched, right click about the Remote desktops item during the tree inside left hand panel and pick Add a new connection through the menu. Once selected the Add New Connection dialog will appear as follows:
Within this dialog enter the IP address or computer system name of your remote program together with the Person name and then the title to become assigned to this connection (this is certainly essentially the title by which this connection will be listed and administered inside the Remote Desktops snap-in). For an administrative session (as opposed to a virtual session) set the Connect with /admin box. Click OK to add the session towards the snap-in. Once added, the session will appear inside left hand panel under Remote Desktops. Repeat these measures to add connections to any additional remote techniques required.
To establish a remote desktop connection, right click on the name for the session in the left hand panel and pick out Connect from your menu. The remote session will appear while in the window. To commence another session simply right click on the session name and once again decide upon Connect. To switch between sessions simply click to the identify of the session while in the left hand panel and also the corresponding desktop will be shown. The subsequent figure illustrates two sessions operating in Remote Desktops:
To change configuration solutions for every single session right click about the desired session inside left hand panel and decide on Properties. This panel has various tabs which enable credentials, screen size and program start off properties to become defined.
Windows Server 2008 is, because the title suggests, a server running product. Within the real world this means that programs operating Windows Server 2008 will almost certainly be found in substantial rack systems inside a server room. As this kind of, it will be hugely unlikely that strategy administrators are going to wish to must physically have a look at each and every of those servers to perform schedule administrative tasks this kind of as method configuration and monitoring. A far preferable situation consists of these administrators remotely logging to the servers from their own desktop techniques to carry out administrative jobs. Thankfully Windows Server 2008 supplies exactly this performance by way of Remote Desktop plus the remote administration benefits in the Device Management Console (MMC). Within this chapter we are going to examine the steps important to remotely administer Windows Server 2008 techniques making use of Remote Desktop.
one What's Remote Desktop?
2 Enabling Remote Desktop Administration around the Remote Server
3 Managing Remote Desktop Access
4 Remote Desktop Group Policy
5 Commencing the Remote Desktop Client
6 Remote Desktop Consumer Configuration Methods
seven Remote Session Monitoring
eight Logging out from a Remote Desktop Session
nine Running A number of Remote Desktops
[edit] What's Remote Desktop? Remote Desktop makes it possible for the graphical interface of the remote Windows product to get displayed in excess of a network onto a local method. In addition, keyboard and mouse occasions on the local model are transmitted towards the remote product enabling the nearby consumer to execute jobs on the remote procedure as if they were physically sitting at the remote process. Conversely,Purchase Windows 7 (http://www.windows-7-key.us/), assets (such as printers and disk drives) on the nearby method may be created out there on the remote system for your duration for the connection. This remote control is established within a number of options, which include around huge region networks (WAN), nearby area networks (LAN) or around cyberspace.
In the circumstance of Windows Server 2008, this services is provided by Terminal Services operating to the remote techniques along with the Remote Desktop Connection (RDC) consumer on the community model.
Terminal Services run in two completely different modes,Office Pro 2007 Key (http://www.office2007-key.co.uk/), Administration and Virtual Session. Remote Desktop for Administration supplies total administration performance to the remote administrator (like access for the console session and visibility of notification messages). Remote Desktop for Administration will be the equivalent to functioning directly on the remote system's console. In virtual session mode the user is subject to some limitations such as the capability to set up programs and watch console notification messages.
Windows Server 2008 imposes some administrator logon restrictions. Particularly, a optimum of two administrators might be logged on at any an individual time, possibly two logged on remotely, or one particular neighborhood and one remote administrator. This assumes, nevertheless, that a variety of accounts are getting chosen to log on. In other words, the exact same user may perhaps not log on locally and remotely simultaneously.
[edit] Enabling Remote Desktop Administration on the Remote Server As talked about previously, remote desktop features about the server is provided by Terminal Providers. It can be very important to be aware, having said that,Office 2007 Standard (http://www.office2007-key.ca/), that Terminal Companies do not have for being explicitly enabled about the server to assistance Remote Desktop Administration. Actually, all that needs to be accomplished would be to permit Remote Desktop Administration. It is configured by opening the Manage Panel from your Launch menu and picking the Model icon (if the Manage Panel is in Control Panel Dwelling mode this really is situated beneath System and Servicing). With the Project area within the top rated left hand corner from the System page select Remote settings to screen the subsequent properties window:
The Remote properties dialog provides several methods. The default setting may be to disallow remote connections on the laptop computer program. The next option lets remote desktop connections from any version of your Remote Desktop client. The third, and most secure selection, will only permit connections from Remote Desktop purchasers with Network Stage Authentication assistance. This normally will only allow for entry to programs offering secure network authentication such as Windows Vista and Windows Server 2008.
If the Windows Firewall is active, the act of enabling Remote Desktop administration also brings about the development of a firewall exception enabling Remote Desktop Protocol (RDP) customers to pass due to on TCP port 3389. This default port can be transformed by shifting this setting with the Registry crucial HKEY_LOCAL_MACHINESystemCurrentControlSetControlTe rminalServerWinStationsRDP-tcpPortNumber. The easiest tactic to locate this registry vital worth is usually to execute regedit in the Run window or perhaps a command prompt,Office 2007 Key (http://www.office2007-key.in/), select Edit - > Find and enter RDP-tcp.
[edit] Controlling Remote Desktop Access The default configuration for Remote Desktop could be to allow all members of your Administration group to connect remotely. Energetic Directory also contains a Remote Desktop Users group to which users may be added to provide Remote Desktop access privileges. To provide users with remote desktop accessibility, open the Control Panel -> Method and Servicing -> System -> Remote settings and click about the Decide on Users button to invoke the Remote Desktop Users dialog illustrated in the following figure:
Be aware that users with administrative privileges never need to get added to this list; by default they already have Remote Desktop entry. To add additional users click around the Add... button to exhibit the Decide upon Users dialog. Enter the title with the consumer inside text box entitled Enter object names to find and click on Check names to list names that match the name entered. Pick out the appropriate identify through the list. The subsequent example shows user Bill on server winserver-2:
Click on OK to apply the change. The new consumer will now appear from the list of users with Remote Desktop entry to the Remote Users screen. Click OK to close this screen and click on Apply while in the Method Settings screen. The specified person will now have remote desktop entry to your product.
[edit] Remote Desktop Group Policy A vast array of configuration possibilities for Terminal Companies is accessible by using the Group Policy settings. To accessibility these values start out the Group Policy Object Editor (open the Get started menu and enter gpedit.msc in to the Search box). Inside Group Object Policy Editor navigate to Personal computer ConfigurationAdministrative TemplatesWindows ComponentsTerminal Services or Person ConfigurationAdministrative TemplatesWindows ComponentsTerminal Solutions to entry the range of policy settings out there.
Policy opportunities include, amongst other methods, items this sort of as management more than resource redirection (printers, audio etc), setting session time limits and security settings. A complete overview of all the settings is beyond the scope of this book but almost without exception the various settings are largely self-explanatory.
[edit] Commencing the Remote Desktop Customer With the appropriate configuration tasks completed about the remote technique the next step is usually to launch the Remote Desktop Consumer about the local strategy. The client can be run in both administration mode which provides full integration with the console in the remote server, or virtual session mode which gives you some administrative privileges but does not provide console entry or make it easy for programs to be installed.
To invoke the Remote Desktop Customer in virtual session mode either select Commence -> All Programs -> Accessories -> Remote Desktop Connection or enter the subsequent while in the Run dialog or at a command prompt:
mstsc To initiate the Remote Desktop Client in administrator mode run the subsequent command:
mstsc /admin In either case the subsequent initial screen will appear requesting details of desktop computer to which the consumer is usually to connect:
This can either be an IP address or a laptop computer title. If previous connections have been established the Person title field will be populated with the user title used inside the preceding session. If you need to log in as a a variety of consumer this opportunity will be supplied on the next screen which appears after the Connect button is pressed:
With this screen enter the password for that selected user (notice that remote desktop entry is only attainable for person accounts which are password protected). If a user other than the a single shown is required, simply click on the Use another account link and enter the needed details. Click on OK to establish the connection. After a short delay the remote desktop will appear around the neighborhood personal computer screen.
[edit] Remote Desktop Customer Configuration Selections The Options>> button displayed about the initial screen from the Remote Desktop Customer can provide six tabs,Windows 7 Starter (http://www.key-windows-7.co.uk/), every single containing a range of configuration alternatives:
General - Allows for login credentials to become configured and session information for being saved. Screen - Configures the resolution and color settings to be put to use when displaying the remote desktop around the local process. Community Sources - Specifies which nearby resources (sound, disk drives, printers etc) are to be designed accessible on the remote strategy during the Remote Desktop session. This page also supplies alternatives to manage the situations under which special primary combinations these as Ctrl-Alt-Del are interpreted by the local or remote methods. Programs - Makes it possible for specified programs for being automatically invoked each and every time a remote sessions is established. Experience - Controls which desktop elements are enabled or disabled for your Remote Desktop session. For example, over a slow dial-up connection it is unwise to get the desktop background displayed and font smoothing enabled. Either choose the connection type and speed to see recommended settings, or use Custom to configure your personal settings. This particular screen also gives the preference to have the connection automatically re-established within the event that a session is dropped. Advanced - Enables and disables remote server verification. This ensures that the remote server to which you are connected is indeed the server you wanted. Also on the market are TS Gateway settings. By default the Remote Desktop Customer is configured to automatically detect TS Gateway settings. [edit] Remote Session Monitoring With Remote Desktop access implemented it truly is often useful to find out at times who is logged into a program. This is often achieved working with the quser command-line tool. To obtain details of logged in users on a community strategy simply run quser at a command prompt or inside of a Run dialog:
C:UsersAdministrator> quser USERNAME SESSIONNAME ID STATE IDLE TIME LOGON TIME administrator 1 Disc 3:18 7/11/2008 12:36 PM bill rdp-tcp#0 2 Energetic . 7/14/2008 9:11 AM nas console three Lively none 7/11/2008 12:58 PM To obtain information for a remote method simply run quser with the /server:<hostname> command-line choice. For example:
C:UsersAdministrator> quser /server:winserver-2 USERNAME SESSIONNAME ID STATE IDLE TIME LOGON TIME administrator 1 Disc 3:22 7/11/2008 12:36 PM bill rdp-tcp#0 two Lively . 7/14/2008 nine:11 AM nas console 3 Active none 7/11/2008 12:58 PM [edit] Logging out from a Remote Desktop Session When the Remote Desktop Customer is exited by pressing the 'X' around the management panel the remote session continues to run to the server even though no client is connected. Next time the person connects the desktop session will appear exactly as it was left before.
To end the session find Start with the remote desktop session, click on the right arrow button while in the bottom right hand corner for the menu and decide upon Log Off. This will close down the remote desktop session and close the remote desktop consumer.
[edit] Operating Many different Remote Desktops A number of concurrent remote desktops can be run and managed within a single window employing the MMC Remote Desktops snap-in. This may perhaps either be snapped to the MMC or launched in the command-line or even a Run dialog by typing:
tsmmc.msc Once launched, right click about the Remote desktops item during the tree inside left hand panel and pick Add a new connection through the menu. Once selected the Add New Connection dialog will appear as follows:
Within this dialog enter the IP address or computer system name of your remote program together with the Person name and then the title to become assigned to this connection (this is certainly essentially the title by which this connection will be listed and administered inside the Remote Desktops snap-in). For an administrative session (as opposed to a virtual session) set the Connect with /admin box. Click OK to add the session towards the snap-in. Once added, the session will appear inside left hand panel under Remote Desktops. Repeat these measures to add connections to any additional remote techniques required.
To establish a remote desktop connection, right click on the name for the session in the left hand panel and pick out Connect from your menu. The remote session will appear while in the window. To commence another session simply right click on the session name and once again decide upon Connect. To switch between sessions simply click to the identify of the session while in the left hand panel and also the corresponding desktop will be shown. The subsequent figure illustrates two sessions operating in Remote Desktops:
To change configuration solutions for every single session right click about the desired session inside left hand panel and decide on Properties. This panel has various tabs which enable credentials, screen size and program start off properties to become defined.