Performing Common Server Tasks with Server Core When a server is installed, the administrator generally gets a configuration wizard or a familiar Start button or Control Panel where the
Trang 18 On the Where Do You Want to Install Windows page, select the disk where you plan
to install the Windows system files Alternatively, you can click the Drive (Options)
to create, delete, extend, or format partitions In addition, click Load Driver to install
drivers for the Windows 2008 installation that are not available on the media
NOTE
If the only drive available is Unallocated Space, Windows Ser ver 2008 automatically
creates a par tition based on the largest size and formats the par tition with NTFS
The installation process will commence by copying the files, installing the Windows
oper-ating system, and configuring features After this process is complete, the server
automati-cally reboots itself, and the logon page is invoked
Performing Common Server Tasks with Server Core
When a server is installed, the administrator generally gets a configuration wizard or a
familiar Start button or Control Panel where the administrator can change the server
name, IP address, join a domain, or the like Because Server Core doesn’t have the Start
button or GUI interface tools, however, this section covers the common tasks performed
in completing the configuration of the Server Core system
All these tasks are performed at the command prompt of the Server Core system from
command-line tools included with Server Core
FIGURE 4.9 Selecting a custom installation
Trang 2Launching the Command Prompt in a Server Core Installation
Remember, the Start menu does not exist Because of this, one of the most important tasks
an administrator must understand when managing a Server Core installation is how to
launch the command prompt The following steps will assist you:
1 Click Ctrl+Alt+Delete
2 Select Start Task Manager
3 On the Windows Task Manager screen, select File, New Task (Run)
4 In the Create New Task dialog box, type cmd.exe, and then click OK.
Changing the Server Core Administrator’s Password
Similar to deploying a regular Windows 2008 implementation, the administrator password
is no longer assigned during the Server Core installation process Therefore, the syntax to
assign an administrator password is this:
Net user administrator *
After the command has been executed, you are prompted to type a password for the user
Enter the password, and then retype it for the confirmation process It is a best practice to
use a complex password when assigning passwords to the administrator account
Changing the Server Core Machine Name
After the Server Core installation is complete, another common task is to change the
machine name of the server By default, Windows automatically generates and assigns a
server name starting with LH and followed by a string of characters The syntax to change
the Server Core machine name follows:
netdom renamecomputer %computername% /newname:<NewComputerName>
When manipulating this syntax, replace the <NewComputerName> argument with the new
machine name for the Server Core installation Changing the server name to ServerCore is
depicted in the following example:
netdom renamecomputer %computername% /newname:ServerCore
Assigning a Static IPV4 IP Address and DNS Settings
Another common Server Core management task is assigning an IP address, including the
primary and secondary DNS settings Before this task can be executed, you must run the
following script to obtain and identify the names of the network interfaces installed on
the server This includes capturing the unique ID associated with each network interface
To display a list of network interfaces, including their respective unique IDs, run the
following script:
netsh interface ipv4 show interfaces
Trang 3The next step is to make a note of the network interface name and unique ID that you
must change The ID is located in the leftmost column and is referred to as Idx This is
depicted in the output of the netsh interface ipv4 show interfaces command, as
displayed in Figure 4.10
NOTE
If you plan to change the IP address settings on more than one inter face, take note of
all the inter face names and Idx unique IDs
Now that you have captured the names and IDs, use the following syntax to change the IP
address for a desired interface
netsh interface ipv4 set address name=”<ID>” source=static address=<StaticIP>
mask=<SubnetMask> gateway=<DefaultGateway>
Replace the ID argument with the network interface name or ID In addition, enter the
static IP address, subnet mask, and default gateway in subsequent arguments An
example follows:
netsh interface ipv4 set address name=”1” source=static address=192.168.115.10
mask=255.255.255.0 gateway=192.168.115.1
The final step when configuring the network interface is to enter a primary and secondary
DNS entry for the interface Do this by using the following syntax:
netsh interface ipv4 add dnsserver name=”<ID>” address=<DNSIP>index=1
The same command is used and repeated when entering more than one DNS entry
However, increment the index each time When finalized, run IP Config /all to verify
the IP address settings
FIGURE 4.10 Reviewing the Idx ID for a network inter face
Trang 4Adding the Server Core System to a Domain
The following script illustrates the basic syntax of how to add a Server Core system to a
Windows domain:
Netdom join %computername% /domain:<domain> /userd:<domain>\<username> /passwordd:*
Input the domain name and supply the user account and password for an account that
has permissions to add computers to the domain
Enabling Remote Management and Remote Desktop to Server Core
Because the Server Core system can’t have administration tools run directly on the system,
you need to enable remote management so that the server can be remotely administered
and managed To enable remote management, enter the following:
netsh advfirewall firewall set rule group=”Remote Admin” new enable=yes
If you want to enable the Remote Desktop function so that you can take control of the
Hyper-V Administration console remotely, enter the following command:
cscript \windows\system32\scregedit.wsf /ar 0
cscript \windows\system32\scregedit.wsf /cs 0
Rebooting and Shutting Down a Server Core System
Even something as simple as shutting down or rebooting a Server Core system needs to be
done from the command prompt because there is no Start button from which to choose
to shut down or reboot the server The command to reboot a Server Core system is as
follows:
shutdown /r /t 0
The command to shut down a Server Core system is as follows:
shutdown /s /t 0
Installing Hyper-V Server Role on a Server Core System
The typical Windows server roles can be configured on a Server Core installation Because
this book is about the installation of Hyper-V, the command sequence to install the
Hyper-V role on Server Core is as follows:
ocsetup Microsoft-Hyper-V
After you run this command, you are prompted to reboot the server The server will then
come up, and the Hyper-V role will have been installed To add virtual guest sessions or
administer the Hyper-V host system, you must go to another system that has the Hyper-V
Administration tool on it and remotely administer the Hyper-V Server Core system
Trang 5Server Core Roles and Feature Installations
Now that the Hyper-V role installation process has been covered, this section covers the
general server role installation process (for those interested in the process of adding other
server roles to a Server Core system)
The following server roles are currently supported on a Server Core installation:
Active Directory Domain Services
Active Directory Lightweight Directory Services (AD LDS)
Dynamic Host Configuration Protocol (DHCP) Server
DNS Server
File Services
Hyper-V Virtualization
Print Server
Streaming Media Services
Web Server (IIS)
The following are optional features that are also supported on a Server Core installation:
Microsoft Failover Cluster
Network Load Balancing
Subsystem for UNIX-based Applications
Windows Backup
Multipath I/O
Removable Storage Management
Windows Bitlocker Drive Encryption
Simple Network Management Protocol (SNMP)
Windows Internet Naming Service (WINS)
Telnet Client
Quality of Service (QoS)
The OCSetup command-line program is responsible for setting up and configuring the
server roles and features on a Server Core installation You can configure the OCSetup
command-line options using the following syntax:
ocsetup.exe [/?] [/h] [/help] component [/log:file] [/norestart] [/passive]
[/quiet] [/unattendfile:file] [/uninstall] [/x: parameter]
Trang 6TABLE 4.2 Available Command Options for OCSetup
Parameter Description
/?, /h, /help Explains all the options available for OCSetup
component Represents the name of the component you plan on installing,
such as DNS, DHCP, Web Ser ver (IIS), and more /log:file Specifies the log file location if you do not want to take advantage
of the default location /norestart Does not reboot the computer after the installation
/passive Suppresses unnecessar y noise and only includes progress status
/quiet Does not require user interaction
/unattendfile:file Requires additional configurations
/uninstall Removes ser ver components
/x: parameter Supplies additional configuration parameters
TABLE 4.3 Ser ver Role Installation Command Lines with OCSetup
DNS Ser ver role start /w ocsetup DNS-Server-Core-Role
DHCP Ser ver role start /w ocsetup DHCPServerCore
File Ser ver role start /w ocsetup FRS-Infrastructure
Print Ser ver role Start /w ocsetup Printing-ServerCore-Role
Active Director y Lightweight Director y
Ser ver role
start /w ocsetup DirectoryServices-ADAM-ServerCore
Windows Deployment Ser ver
(Windows DS) role
start /w ocsetup Microsoft-Windows-Deployment-Services
Use Table 4.2 to understand each of the options that are available when using the
OCSetup command-line program
Performing a Server Role Installation on a Server Core Installation
Table 4.3 outlines basic server role installation examples based on the use of the OCSetup
command-line tool
The previous sections are a prelude to some of the common Server Core command-line
arguments for installing and configuring elements on a Windows Server 2008 Server Core
installation
Trang 7Summary
The Windows Server 2008 installation process is similar to those found in earlier versions
of Windows The Windows Server 2008 installation process is simpler, however, because
certain things such as the server name, IP address, domain name, time zone, and so on are
no longer prompted for during the installation Instead, they are part of a post-installation
process This simplification enables administrators to start the installation process by just
choosing the version of Windows 2008 they want to install on the server and selecting the
disk subsystem on which to install Windows Administrators can then come back 20
minutes later and the server will have gone through the entire installation process on its
own The administrator walks through the post-installation wizard to enter the server
name, IP address, time zone, and other server specifics, and then the system is fully
configured
The new Windows Server Core installation has been an anticipated feature for the
Windows 2008 family of operating systems and has been popular as the base installation
for Hyper-V host servers One reason for this is that the lack of a GUI on the virtual host
means a significant decrease in the attack surface on the host system Server Core
installa-tions meet today’s administrator and organization needs by providing a way to use the
Windows 2008 operating system with the fewest number of binaries, in the most highly
secured fashion, while also reducing management overhead
Best Practices
The following are best practices from this chapter:
Verify that your hardware, devices, and drivers are supported by Windows Server 2008
As a Hyper-V virtualization host server, you need far more RAM, processor, and disk
space than a normal “minimum requirement” server configuration See Chapter 3 to
properly size the Hyper-V server with the hardware requirements needed
Before beginning the installation of Windows 2008 on the server, make sure the
system supports hardware-assisted virtualization through the use of an Intel EM64T
or AMD64 processor
Only install the x64-bit version of Windows 2008 on the server; the 32-bit (x86)
version of Windows 2008 does not support Hyper-V host virtualization
Considering installing either the Enterprise Edition or the Datacenter Edition of
Windows 2008 (not the Standard Edition) if you plan to have three or more virtual
guest sessions on the system (from the perspective of licensing cost under the
Microsoft virtual server rights licensing policy)
Use the Windows Server 2008 Initial Configuration Tasks Wizard to conduct
post-installation tasks
Use Windows Server Core installations when the highest level of security is warranted
Trang 8Use a consistent naming convention to name the servers and client machines
Use only Internet standard characters in your computer name This includes the
letters A–Z (upper- and lowercase), the numbers 0–9, and the hyphen (-)
As soon as you complete the installation, rename the administrator account and
assign a strong password, for the sake of security
Have the installation media and license keys needed for the installation of the
host operating system handy when you are about to install the operating system
on the server
Join the Hyper-V host to an Active Directory to take advantage of domain
adminis-tration and management capabilities If the Hyper-V host will be in a DMZ or
nonsecure location, however, you may choose to keep the Hyper-V host as a
stand-alone server
Enable Remote Management on a Server Core system so that you can remotely
man-age and administer the server
Trang 9ptg6432687
Trang 10Installing a Guest Session on Hyper-V
Choosing the Guest Session Operating System
Installing a Windows-Based Guest Operating System Session
Installing a Linux-Based Guest Operating System Session
Modifying Guest Session Configuration Settings
Launching a Hyper-V Guest Session
Installing the Windows Guest Session Integration Tools
Using Snapshots of Guest Operating System Sessions
So far in this book, we have gone through the process of
planning the migration of physical servers to Hyper-V virtual
guests (Chapter 2, “Best Practices at Planning, Prototyping,
Migrating, and Deploying Windows 2008 Hyper-V”), sized
and scaled our host server to have enough memory and
processing capability to support our planned virtual guest
sessions (Chapter 3, “Planning, Sizing, and Architecting a
Hyper-V Environment”), and we have installed the core
Windows 2008 operating system and added the Hyper-V role
to the server (Chapter 4, “Installing Windows 2008 Server
and the Hyper-V Role”) The next step is to start building out
guest sessions
This chapter covers the creation of new guest sessions on
Hyper-V Guest sessions on Hyper-V can be both Windows
images and non-Windows (Linux) images For organizations
that are looking to migrate existing physical servers or
convert existing virtual server sessions to Hyper-V virtual
sessions, that is covered in Chapter 10, “Creating Guest
Images from Existing Production and Virtual Systems.” This
chapter just focuses on the creation of net new guest images
from installation media
Choosing the Guest Session
Operating System
Although you can effectively boot and try to install any
operating system on Hyper-V and can frequently get to the
point where the operating system will work under Hyper-V,
Microsoft officially supports only specific versions of
operat-ing systems as guest sessions