You must first enable remote management of this snap-in. The snap-in does not require any further configuration, but when you use it to monitor a Server Core computer, you can only monitor performance data. Reliability data is not available. On another computer, click Start , click Run , type mstsc , and then click OK. In Computer , enter the name of the server that is in Server Core mode, and click Connect.
When the command prompt appears, you can manage the computer using the Windows command-line tools. When you have finished remotely managing the Server Core computer, type logoff in the command prompt to end your Remote Desktop session. If you are running the Remote Desktop Services client on a previous version of Windows, you must turn off the higher security level that is set by default in Windows Server There may be situations in which you need to use the graphical user interfaces available in Server with a GUI mode.
You can switch the system to Server with a GUI mode by following the steps below, although a restart is required. After you have accomplished the management tasks, you can switch the server back to Server Core mode whenever it is convenient a restart is required with the Windows PowerShell cmdlet Uninstall-WindowsFeature Server-Gui-Mgmt-Infra -restart.
If the driver for the hardware is included in Windows Server , Plug and Play will start and install the driver. At a command prompt, open the folder where the driver files are located, and then run the following command:. Service Updates on a Server Core Server. Configure and Manage Server Core Installations. Windows Server Installation Options. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. The administrator can convert the servers to Server Core installations to reduce the image size and increase servicing advantages without having to reprovision all of their servers.
An administrator installs a Server Core installation and now needs to make a change or troubleshoot something that is not possible with the remote GUI. The administrator may not know how to make the change from the command line or cannot find a command-line equivalent. The administrator can convert the server to a full installation, perform the changes, and then convert it back to a Server Core installation to reduce the image size and maintain servicing advantages.
An administrator wants to use the GUI for all of the initial configuration steps to make the initial configuration experience as easy as possible, yet wants to reduce the image size and maintain the servicing advantages that a Server Core installation provides. The administrator can install a full installation, configure the server as needed, and then convert it to a Server Core installation. An enterprise mandates a single server operating system image, so it cannot use a Server Core installation because it requires two images.
Windows Server integrates the Server Core installation and the full server installation options. To understand what an "installation option" is, let's say you've purchased a volume license that lets you install a copy of Windows Server Enterprise Edition. When you insert your volume-licensed media into a system and begin the installation process, one of the screens you'll see, as shown in Figure , presents you with a choice of editions and installation options.
In Figure , your volume license or product key, for retail media gives you two installation options you can choose between: the second option a Full Installation of Windows Server Enterprise and the fifth option a Server Core Installation of Windows Server Enterprise , with the latter selected in this example.
Since the early days of the Microsoft Windows platform, Windows servers were essentially "everything" servers that included all kinds of features, some of which you might never actually use in your networking environment. For instance, when you installed Windows Server on a system, the binaries for Routing and Remote Access Service RRAS were installed on your server even if you had no need for this service although you still had to configure and enable RRAS before it would work.
Windows Server improves earlier versions by installing the binaries needed by a server role only if you choose to install that particular role on your server. However, the Full installation option of Windows Server still installs many services and other components that are often not needed for a particular usage scenario. That's the reason Microsoft created a second installation option—Server Core—for Windows Server to eliminate any services and other features that are not essential for the support of certain commonly used server roles.
The result is the new Server Core installation option, which can be used to create a server that supports only a limited number of roles and features. When you finish installing Server Core on a system and log on for the first time, you're in for a bit of a surprise. Figure shows the Server Core user interface after first logon. There's no desktop! That is, there is no Windows Explorer shell, with its Start menu, Taskbar, and the other features you may be used to seeing.
All you have is a command prompt, which means that you have to do most of the work of configuring a Server Core installation either by typing commands one at a time, which is slow, or by using scripts and batch files, which can help you speed up and simplify your configuration tasks by automating them. You can also perform some initial configuration tasks using answer files when you perform an unattended installation of Server Core.
For administrators who are experts in using command-line tools like Netsh. For those who are not experts, however, all is not lost. You just need to use them on a different system running either a full installation of Windows Server or Windows Vista with Service Pack 1. You'll learn more about configuring and managing a Server Core installation in Chapters 3 to 6 of this book, while later chapters deal with how to manage specific server roles and other components.
To learn more about the various Windows command-line tools and how to use them, there are two good resources to consult:. Table lists the main GUI applications, together with their executables, that are available in a Server Core installation. That's a pretty short list! Now here's a list of user interface elements that are not included in Server Core:. NET Framework is also not present in Server Core, which means there's no support for running managed code on a Server Core installation.
In summary, any GUI applications that depend on either the. NET Framework or on the Explorer. Because Windows PowerShell requires the.
0コメント