You can use Remote Desktop (also known as Terminal Services for Administration) to administer a Server Core installation remotely in exactly the same way you would administer it from the local console of the server. By default, Remote Desktop is disabled on Server Core, so before you can use Remote Desktop to manage a Server Core installation remotely, you must first enable Remote Desktop on the server.

This can be done in several ways, as the next sections illustrate. Enabling Remote Desktop Using Scregedit.wsf You can use the Scregedit.wsf script to enable Remote Desktop on your Server Core installation by logging on locally to your server and doing the following.

Apr 25, 2016 - Built in commands like mstsc, ping etc. Do not require a separate installation. On the computers where the device action shall be executed popups must be allowed for the. Galactic civilizations patch notes. /d%WINDIR% System32 mstsc.exe /t REG_SZ /f.

C: Users Administrator>cscript%windir% system32 scregedit.wsf /ar /v Microsoft (R) Windows Script Host Version 5.7 Copyright (C) Microsoft Corporation. All rights reserved. System CurrentControlSet Control Terminal Server fDenyTSConnections View registry setting. 0 A value of 0 for the fDenyTSConnections registry value means that Remote Desktop is enabled on the system, while a value of 1 means that Remote Desktop is disabled. If you later decide you want to disable Remote Desktop on your Server Core installation, type cscript%windir% system32 scregedit.wsf /ar 1 at a command prompt. Tip If your current directory is C: Windows System32, you can shorten these commands by omitting the%Windir% System32 portion of them.

Enabling Remote Desktop using Scregedit.wsf also automatically enables the Remote Desktop rule group in Windows Firewall. Enabling Remote Desktop Using an Answer File You can use an answer file to enable Remote Desktop during an unattended install of Server Core. You do this as follows: • Add the following component to the specialize configuration pass of your answer file: Microsoft-Windows-TerminalServices-LocalSessionManager • In the Properties pane, click the box to the right of the fDenyTSConnections setting; a drop-down arrow appears. Click the drop-down arrow and select False, as shown here. • Add the following component to the oobeSystem configuration pass of your answer file: Microsoft-Windows-Shell-Setup FirstLogonCommands SynchronousCommand • In the Properties pane, type C: Windows system32 netsh advfirewall -firewall set rule group='Remote Desktop' new enable=yes in the box beside CommandLine and type 1 (or another number if you are running multiple FirstLogonCommands) in the box beside Order. Tip You can also use WinRS to enable Remote Desktop remotely on a Server Core installation.

See the section 'Using WinRS to Administer Server Core in a Domain,' later in this chapter, for more information. Using Scregedit.wsf to Require Network Level Authentication for Remote Desktop By default, when Remote Desktop is enabled on Server Core, computers running versions of Microsoft Windows earlier than Windows Vista are allowed to connect. You can use the Scregedit.wsf script to prevent computers running versions earlier than Windows Vista from connecting to Server Core using Remote Desktop by logging on locally to your server and doing the following.

C: Users Administrator>cscript%windir% system32 scregedit.wsf /cs 1 Microsoft (R) Windows Script Host Version 5.7 Copyright (C) Microsoft Corporation. All rights reserved. Doing this increases the security of your Server Core installation by requiring that the client you are using to administer Server Core uses Network Level Authentication. For more information, see the section 'Configuring Remote Desktop to Require Network Level Authentication,' in Chapter 3, 'Initial Configuration.'

Using an Answer File to Require Network Level Authentication for Remote Desktop You can use an answer file to require that Network Level Authentication be used for Remote Desktop connections. You do this as follows: • Add the following component to the specialize configuration pass of your answer file: Microsoft-Windows-TerminalServices-RDP-WinStationExtensions • In the Properties pane, click the box to the right of the UserAuthentication setting and type 1 to require Network Level Authentication, as shown here.

You can also configure the SecurityLayer setting to specify how your server and Remote Desktop clients authenticate each other prior to a Remote Desktop connection being established. The possible values for this setting are shown in Table 6-1.

Table 6-1 The SecurityLayer Setting Values Using Remote Desktop to Administer Server Core To use Remote Desktop to administer a Server Core installation, log on to a computer running Windows Vista or Windows Server 2008 and do the following: • Press the Windows key+R to open the Run text box. • Type mstsc and press Enter to open Remote Desktop Connection. • Type the name, either NetBIOS or Fully Qualified Domain Name (FQDN), or the Internet Protocol (IP) address of your Server Core installation in the Computer text box. • Click Options and type the name of a user account that has administrative privileges on the Server Core installation. Be sure to type this user name in the form servername username (if the server belongs to a workgroup) or domainname username (if the server belongs to a domain), as shown here. • Click Connect. When the Windows Security dialog box appears, type the password for the user account you are using to administer Server Core, as shown here.