Installing the Second Server in .NET framework

Creation ECC200 in .NET framework Installing the Second Server

2. 3.

Scroll down to near the bottom of the Features list and select Windows PowerShell, as shown. Click Next to open the con rmation page. You ll see a list of features that are going to be installed, and a warning that this might require a reboot. Don t worry, the server will not reboot as long as this is the only feature you re installing. Click Install to begin the actual installation. When the installation completes, you ll see the Installation Results page. Any problems will be highlighted here, or it will simply report that the installation was successful. Click Close to exit the Add Features Wizard.

Now, you re almost done. A couple of little con guration steps will simplify your use of Windows PowerShell, so let s take care of that right now. First, let s pin Windows PowerShell to the Start menu to make it easier to use. After all, Command Prompt is there, so why shouldn t Windows PowerShell be there, too To pin Windows PowerShell to the Start menu, follow these steps:

1. 2.

Click Start, click All Programs, and then click Windows PowerShell 1.0. Right-click Windows PowerShell and select Pin To Start Menu, as shown in Figure 23-24.

While you re there, add Windows PowerShell to your Quick Launch toolbar. Now you have easy access to Windows PowerShell without having to dig into the menus to get to it.

PowerShell and a 32-bit version called Windows PowerShell (x86). For virtually everything, you ll want to use the 64-bit shell.

By default, Windows PowerShell installs in the safest way possible, prohibiting you from running any scripts or con guration les. This lets you use the command line but severely limits your ability to customize or do much of anything with Windows PowerShell beyond simple shell commands. This restriction is called the execution policy of the shell. Four levels of execution policy are available:

on the local network to run without being signed, but any script that was downloaded from the Internet must be signed by a trusted publisher.

where it came from. Scripts or con guration les that originated on the Internet will prompt you before you can run them, however. We think the default value of Restricted is a bit much, and frankly we re just not willing to get a code-signing certi cate just to run our own scripts, so even AllSigned is a bit much. In an environment that fully supports code-signing certi cates, and where you want to restrict the scripts that can be run to only those that are approved and signed, AllSigned makes sense. But for most SBS networks, we think RemoteSigned is a good compromise. To change the execution policy to RemoteSigned, follow these steps:

1. 2. 3.

Click Start, right-click the Windows PowerShell, and then select Run As Administrator. Select Continue at the User Account Control prompt to open Windows PowerShell with administrative privileges. At the Windows PowerShell prompt, run the following command:

To con rm that the change has taken effect, you can use the Get-ExecutionPolicy command, shown in Figure 23-25.

ext on the ICT Wizard list is a link to enable Remote Desktop. Remote Desktop allows administrators to connect directly to the server without having to sit

down at the console in the server room. Windows Server 2008 introduces version 6.1 of the Remote Desktop Protocol (RDP). The Remote Desktop Client version 6.1 is included in Windows Vista Service Pack 1 (SP1) and Windows XP SP3, and version 6 clients are downloadable from Microsoft Knowledge Base Article 925876 at http://support.microsoft.com/kb/925876.

Version 6 and later of RDP includes many improvements over earlier versions, including 32-bit color, server authentication, resource redirection, font smoothing, and Terminal Services Remote Programs. For remote administration of a server, the most important improvement is server authentication, which ensures that you are actually connecting to the computer you think you are. To enable Remote Desktop on the new server, you don t have to do anything at all. When the server is joined to the SBS domain, the SBS con gured Group Policy will automatically enable Remote Desktop on the server. Nice.