Server Core Installation Option of Windows Server 2008 Step-By-Step Guide What is a Server Core installation? Benefits of a Server Core installation

Transcription

1 Server Core Installation Option of Windows Server 2008 Step-By-Step Guide This step-by-step guide provides instructions for building a server in your test lab that is based on the Server Core installation option of the Windows Server 2008 operating system. It includes information about installation, initial configuration, and managing a server that running a Server Core installation. What is a Server Core installation? The Server Core installation option is a new option that you can use for installing Windows Server A Server Core installation provide a minimal environment for running specific server roles, which reduces the maintenance and management requirements and the attack surface for those server roles. A server running a Server Core installation supports the following server roles: Active Directory Domain Services (AD DS) Active Directory Lightweight Directory Services (AD LDS) DHCP Server DNS Server File Services Print Services Streaming Media Services Web Server (IIS) To accomplish this, the Server Core installation option installs only the subset of the binary files that are required by the supported serve roles. For example, the Explorer shell is not installed as part of a Server Core installation. Instead, the default user interface for a server running a Server Core installation is the command prompt. Benefits of a Server Core installation The Server Core installation option of Windows Server 2008 provides the following benefits: Reduced maintenance. Because the Server Core installation option installs only what is required to have a manageable server for the AD DS, AD LDS, DHCP Server, DNS File Services, Print Services, and Streaming Media Services roles, less maintenance is required than on a full installation of Windows Server Reduced attack surface. Because Server Core installations are minimal, there are fewer applications running on the server, which decreases the attack surface. Reduced management. Because fewer applications and services are installed on a server running the Server Core installation, there is less to manage. Less disk space required. A Server Core installation requires only about 1 gigabyte (GB) of disk space to install and approximately 2 GB for operations after the installation. Known issues for deploying a Server Core installation There is no way to upgrade from a previous version of the Windows Server operating system to a Server Core installation. Only a clean installation is supported. There is no way to upgrade from a full installation of Windows Server 2008 to a Server Core installation. Only a clean installation is supported. There is no way to upgrade from a Server Core installation to a full installation of Windows Server If you need the Windows user interface or a server role that is not supported in a Server Core installation, you will need to install a full installation of Windows Server Steps for manually installing a Server Core installation Follow this procedure to install a Server Core installation of Windows Server To install a Server Core installation 1. Insert the appropriate Windows Server 2008 installation media into your DVD drive. 2. When the auto-run dialog box appears, click Install Now. 3. Follow the instructions on the screen to complete Setup. 4. After Setup completes, press CTRL+ALT+DELETE, click Other User, type Administrator with a blank password, and then press ENTER. You will be prompted to set a password for the Administrator account.

2

3

4 Steps for configuring a Server Core installation The following procedures explain how to configure a computer running a Server Core installation. The steps include: Setting the administrative password Setting a static IP address A DHCP address is provided by default. You should perform this procedure only if you need to set a static IP address. Joining a domain Activating the server Configuring the firewall To set the administrative password 1. When your computer starts for the first time after the installation completes, press CTRL+ALT+DELETE. Type Administrator for the user name and leave the password blank. 2. The system will inform you that the password has expired and will prompt you to enter a new password. 3. Type an appropriate password. To set a static IP address 1. At a command prompt, type the following: netsh interface ipv4 show interfaces 2. Make a note of the number shown in the Idx column of the output for your network adapter. If your computer has more than one network adapter, make a note of the number corresponding to the network adapter for which you wish to set a static IP address. 3. At the command prompt, type: netsh interface ipv4 set address name="<id>" source=static address=<staticip>mask=<subnetmask> gateway=<defaultgateway> ID is the number from step 2 above StaticIP is the static IP address that you are setting SubnetMask is the subnet mask for the IP address DefaultGateway is the default gateway 4. At the command prompt, type: netsh interface ipv4 add dnsserver name="<id>" address=<dnsip>index=1 ID is the number from step 2 above DNSIP is the IP address of your DNS server 5. Repeat step 4 for each DNS server that you want to set, incrementing the index= number each time. s If you set the static IP address on the wrong network adapter, you can change back to using the DHCP address supplied by using the following command: netsh interface ipv4 set address name="<id>" source=dhcp where ID is the number of the network adapter from Step 2. To join a domain 1.

5 1. netdom join <ComputerName> /domain:<domainname> /userd:<username> /password:* ComputerName is the name of the server that is running the Server Core installation. DomainName is the name of the domain to join. UserName is a domain user account with permission to join the domain. 2. When prompted to enter the password, type the password for the domain user account specified by UserName. 3. If you need to add a domain user account to the local Administrators group, type the following command: net localgroup administrators /add <DomainName>\<UserName> 4. Restart the computer. You can do this by typing the following at a command prompt: shutdown /r /t 0 To rename the server 1. Determine the current name of the server with the hostname or ipconfig command. 2. netdom renamecomputer <ComputerName> /NewName:<NewComputerName> 3. Restart the computer. To activate the server slmgr.vbs -ato If activation is successful, no message will return in the command prompt. s You can also activate by phone, using a Key Management Service (KMS) server, or remotely by typing the following command at a command prompt of a computer that is running Windows Vista or Windows Server 2008: cscript windows\system32\slmgr.vbs <ServerName> <UserName> <password>:-ato To configure the firewall Use the netsh advfirewall command. For example, to enable remote management from any MMC snap-in, type the following: netsh advfirewall firewall set rule group="remote Administration" new enable=yes s You can also use the Windows Firewall snap-in from a computer running Windows Vista or Windows Server 2008 to remotely manage the firewall on a server running a Server Core installation. To do this, you must first enable remote management of the firewall by running the following command on the computer running a Server Core installation: netsh advfirewall set currentprofile settings remotemanagement enable Installing a server role on a server running Server Core installation: Overview After the Server Core installation is complete and the server is configured, you can install one or more server roles. The Server Core installation of Windows Server 2008 supports the following server roles: Active Directory Domain Services (AD DS) Active Directory Lightweight Directory Services (AD LDS) DHCP Server DNS Server File Services Print Services Streaming Media Services Web Server (IIS) This section includes a procedure for each server role in the previous list. You need to complete the procedure(s) for only the server roles that you want to install. Prerequisites for installing a server role on a server running Server Core installation To complete this task, you need the following: A computer on which you have installed and configured a Server Core installation of Windows Server An administrator user account and password for the server running the Server Core installation. If installing and configuring a print server, another computer running Windows Vista or Windows Server 2008 on which you can run the Print Management Console to remotely configure the print server. If installing and configuring a DHCP server, the information required to configure a DHCP scope. If installing and configuring a DHCP server, you must configure the server running the Server Core installation to use a static IP address. If installing and configuring a DNS server, the information required to configure a DNS zone. If installing and configuring an Active Directory environment, the information required to either join an existing domain or to create a new domain. If you are going to promote the server running the Server Core installation to be a domain controller in an Active Directory domain, a domain administrator user name and password. Known issues for installing a server role on a Server Core installation You cannot use the Active Directory Domain Controller Installation Wizard (Dcpromo.exe) on a server running Server Core installation. You must use an unattend file with Dcpromo.exe to install or remove the domain controller role. Alternately, you can run Dcpromo.exe on another computer running Windows Server 2008 and use the wizard to save an unattend file that you can then use on the server running

6 Alternately, you can run Dcpromo.exe on another computer running Windows Server 2008 and use the wizard to save an unattend file that you can then use on the server running Server Core installation. Dcpromo.exe will restart the computer immediately when the installation is complete or when Active Directory is removed unless RebootOnCompletion=No is included in answer file. The Web Server (IIS) role does not support ASP.NET in Server Core installations. Because there is no support for managed code, the following IIS features are not available in Serve Core installations: IIS-ASPNET IIS-NetFxExtensibility IIS-ManagementConsole IIS-ManagementService IIS-LegacySnapIn IIS-FTPManagement WAS-NetFxEnvironment WAS-ConfigurationAPI Steps for installing a server role on a Server Core installation To install a server role on a Server Core installation of Windows Server 2008, perform the procedure for the desired role as follows. Ocsetup.exe syntax is case sensitive so be sure to follow the examples explicitly. Available server roles To discover the available server roles, open a command prompt and type the following: oclist This command lists the server roles and optional features that are available for use with Ocsetup.exe. It also lists the server roles and optional features that are currently installed. DNS Server role To install the DNS Server role 1. start /w ocsetup DNS-Server-Core-Role Using /w prevents the command prompt from returning until the installation completes. Without /w, there is no indication that the installation completed. 2. Configure a DNS zone at the command prompt by typing dnscmd or by remotely using the DNS MMC snap-in. Typing start /w ocsetup DNS-Server-Core-Role /uninstall at the command prompt will uninstall the DNS Server role. DHCP Server role To install the DHCP Server role 1. start /w ocsetup DHCPServerCore 2. Configure a DHCP scope at the command prompt by using netsh, or by remotely using the DHCP snap-in from Windows Server If the DHCP server is installed in an Active Directory domain, you must authorize it in Active Directory. The DHCP Server service does not start automatically by default. Use the following procedure to configure it to start automatically and to start the service for the first time. To configure and start the DHCP Server service 1. sc config dhcpserver start= auto 2. Start the service by typing: net start dhcpserver Typing start /w ocsetup DHCPServerCore /uninstall at the command prompt will uninstall the DHCP Server role. File Services role The Server service is installed by default to provide administrative share support for management tools. To install additional file server features use the following commands: To install File Services role features For File Replication Service, type the following at a command prompt: start /w ocsetup FRS-Infrastructure For Distributed File System service, type: start /w ocsetup DFSN-Server For Distributed File System Replication, type: start /w ocsetup DFSR-Infrastructure-ServerEdition For Services for Network File System (NFS), type: start /w ocsetup ServerForNFS-Base start /w ocsetup ClientForNFS-Base

7 Uninstall any file server role options by using these commands with the /uninstall option. Print Services role To install Print Services role features For the Print Server feature, type the following at a command prompt: start /w ocsetup Printing-ServerCore-Role For the Line Printer Daemon (LPD) service, type: start /w ocsetup Printing-LPDPrintService To add a printer to the print server 1. Determine the IP address or host name of the printer. This may be on the printer's test or printer configuration page or you might need to refer to the manufacturer's documentation for instructions. 2. Verify that the print server can communicate with the printer through the network by pinging the printer from the print server. 3. On another computer running Windows Vista or Windows Server 2008, open the Print Management console and add the server running the Server Core installation. 4. Expand the entry for the print server running a Server Core installation, rightclick Drivers, and then click Add Driver. The Add Printer Driver Wizard starts. 5. Complete the wizard to install the printer driver for your printer. 6. In the Print Management console, right-click Printers and then click Add Printer. The Network Printer Installation Wizard starts. 7. Click Add a TCP/IP or Web Services printer by IP address or hostname and then click Next. 8. Enter the printer's host name or IP address (the port name will be the same by default), and then click Next. 9. Make any necessary changes to the printer name, contact information, or sharing status, and then click Next. Active Directory Lightweight Directory Services role To install the AD LDS role s start /w ocsetup DirectoryServices-ADAM-ServerCore Uninstall the AD LDS role by typing the following at a command prompt: start /w ocsetup DirectoryServices-ADAM-ServerCore /uninstall Active Directory Domain Services role This command installs the Active Directory Domain Services role and promotes the server to a domain controller by using the settings in the unattend file. To install the Active Directory Domain Services role dcpromo /unattend:<unattendfile> Where unattendfile is the name of a Dcpromo.exe unattend file. Dcpromo.exe can also be used to demote a domain controller to a server. Streaming Media Services role To install the Streaming Media Services role 1. On another computer, download the Streaming Media Services role installer file from article in the Microsoft Knowledge Base ( LinkId=88046). 2. Copy the appropriate Microsoft Update Standalone package (.msu file) to your Server Core installation. 3. Run the.msu file. 4. start /w ocsetup MediaServer 5. On a different computer, use the Streaming Media Services MMC snap-in to remotely configure Streaming Media Services. Web Server (IIS) role To install the Web Server role 1. For the default installation, type the following at a command prompt and press ENTER: start /w pkgmgr /iu:iis-webserverrole;was-windowsactivationservice;was- ProcessModel 2. For an installation that includes all of the options, type the following at a command prompt and press ENTER: start /w pkgmgr /iu:iis-webserverrole;iis-webserver;iis- CommonHttpFeatures;IIS-StaticContent;IIS-DefaultDocument;IIS- DirectoryBrowsing;IIS-HttpErrors;IIS-HttpRedirect;IIS- ApplicationDevelopment;IIS-ASP;IIS-CGI;IIS-ISAPIExtensions;IIS-ISAPIFilter;IIS-

8 ServerSideIncludes;IIS-HealthAndDiagnostics;IIS-HttpLogging;IIS- LoggingLibraries;IIS-RequestMonitor;IIS-HttpTracing;IIS-CustomLogging;IIS- ODBCLogging;IIS-Security;IIS-BasicAuthentication;IIS- WindowsAuthentication;IIS-DigestAuthentication;IIS- ClientCertificateMappingAuthentication;IIS- IISCertificateMappingAuthentication;IIS-URLAuthorization;IIS- RequestFiltering;IIS-IPSecurity;IIS-Performance;IIS- HttpCompressionStatic;IIS-HttpCompressionDynamic;IIS- WebServerManagementTools;IIS-ManagementScriptingTools;IIS- IIS6ManagementCompatibility;IIS-Metabase;IIS-WMICompatibility;IIS- LegacyScripts;IIS-FTPPublishingService;IIS-FTPServer;WAS- WindowsActivationService;WAS-ProcessModel s To uninstall the Web Server (IIS) role, use the following command: start /w pkgmgr /uu:iis-webserverrole;was-windowsactivationservice;was-processmodel Installing Windows Features: Overview After the Server Core installation is complete and the server is configured, you can install one or more optional features. The Server Core installation of Windows Server 2008 supports the following optional features: Failover Clustering Network Load Balancing Subsystem for UNIX-based applications Backup Multipath IO Removable Storage Bitlocker Drive Encryption Simple Network Management Protocol (SNMP) Windows Internet Name Service (WINS) Telnet client The following procedure describes how to install these features on a server running a Server Core installation. Failover Clustering is not available in Windows Server 2008 Standard Edition. Prerequisites for installing an optional feature on a server running a Server Core installation The following optional features require appropriate hardware: Failover Clustering Network Load Balancing Multipath IO Removable Storage Bitlocker Drive Encryption For more information about the hardware that is required for optional features, see the Additional Referencessection at the end of this document. There are no prerequisites for the following optional features: Subsystem for UNIX-based applications Backup Simple Network Management Protocol (SNMP) Windows Internet Name Service (WINS) Telnet client Known issues for installing an optional feature on a server running a Server Core installation There are no known issues for installing an optional feature on a Server Core installation of Windows Server Steps for installing an optional feature on a server running a Server Core installation To install an optional feature on a Server Core installation of Windows Server 2008, perform the following procedure. The Ocsetup.exe syntax is case sensitive so be sure to follow the examples explicitly. Available optional features To discover the available optional features, open a command prompt and type the following: Oclist This command lists the server roles and optional features that are available for use with Ocsetup.exe. It also lists the server roles and optional features that are currently installed. To install an optional feature start /w ocsetup <featurename> Where featurename is the name of a feature from the following list: Failover Clustering: FailoverCluster-Core Network Load Balancing: NetworkLoadBalancingHeadlessServer Subsystem for UNIX-based applications: SUACore Multipath IO: MultipathIo Removable Storage: Microsoft-Windows- RemovableStorageManagementCore

9 Bitlocker Drive Encryption: BitLocker s To install the remote administration tool for BitLocker, type the following at a command prompt: start /w ocsetup BitLocker-RemoteAdminTool Backup: WindowsServerBackup Simple Network Management Protocol (SNMP): SNMP-SC Windows Internet Name Service (WINS): WINS-SC Telnet client: TelnetClient To remove an optional feature, use start /w ocsetup with the appropriate role name and the /uninstall switch. Managing a Server Core installation: Overview You can manage a server running Server Core installation in the following ways: Locally and remotely using a command prompt. By using the Windows command-line tools at a command prompt, you can manage servers running a Server Core installation. Remotely using Terminal Server. By using another computer running Windows, you can use the Terminal Server client to connect to a server running a Server Core installation and manage it remotely. The shell in the Terminal Server session will be the command prompt. Remotely using Windows Remote Shell. By using another computer running Windows Vista or Windows Server 2008, you can use Windows Remote Shell to run command-line tools and scripts on a server running a Server Core installation. Remotely using an MMC snap-in. By using an MMC snap-in from a computer running Windows Vista or Windows Server 2008, you can connect to a server running Server Core installation in the same way that you would connect to any computer running Windows. Prerequisites for managing a server running Server Core installation To manage a server running Server Core installation, you need: A computer that has a Server Core installation of Windows Server 2008 installed and configured. An administrator user account and password for a server running a Server Core installation. Known issues for managing a server running a Server Core installation Not all tasks can be performed at a command prompt or remotely through an MMC snap-in. There is a script included with the Server Core installation of Windows Server 2008 tha you can use to configure the following settings: Enable automatic updates Enable Remote Desktop for Administration Enable Terminal Server clients on previous versions of Windows to connect to a server running a Server Core installation Configure DNS SRV record weight and priority Manage IPsec Monitor remotely The script is located in the \Windows\System32 folder of a server running a Server Core installation. At a command prompt, open the folder, and then use the following command display the usage instructions for the previous options: cscript scregedit.wsf /? You can use this command with the /cli option to display a list of common command-line tools and their usage. If you close all Command Prompt windows and want to open a new Command Prompt window, pressctrl+alt+delete, click Start Task Manager, click File, click Run, and then type cmd.exe. Alternatively, you can log off and log back on. Any command or tool that attempts to launch Windows Explorer will not work. For example, start. used from a command prompt will not work. TheRunonce feature is not supported in Server Core installations. There is no support for HTML rendering or HTML help in Server Core installations. Server Core installations do not support running managed code. Any management tools and utilities that run locally on a server running a Server Core installation must be written native Win32 code. Server Core installations do not generate any notifications for activation, new updates, or password expiration because these notifications require the Windows Explorer shell, which is not part of the Server Core installation. If you need to write a script for managing a server running a Server Core installation, which requires the secure inclusion of an administrative password, see the scripting column o Microsoft TechNet ( Server Core installations support Windows Installer in quiet mode so that you can install tools and utilities from Windows Installer files. Windows Firewall can be configured at a command prompt by using netsh advfirewall. When installing Windows Installer packages on a server running a Server Core installation, use the /qb option to display the basic user interface. To change the time zone on a computer running a Server Core installation of Windows Server 2008, run control timedate.cpl. To change international settings on a computer running a Server Core installation of Windows Server 2008, runcontrol intl.cpl. To use the Disk Management MMC snap-in remotely, start the Virtual Disk Service on a server running a Server Core installation. To do this, type the following at a command prompt: net start VDS Control.exe will not run on its own. You must run it with either Timedate.cpl or Intl.cpl. Winver.exe is not available in Server Core installations. To obtain version information use Systeminfo.exe. Steps for managing a Server Core installation The following procedures explain methods for managing a server running a Server Core installation, including: Managing a server running a Server Core installation locally at a command prompt Managing a server running a Server Core installation remotely at a command prompt Managing a server running a Server Core installation by using Windows Remote Shell Managing a server running a Server Core installation by using Microsoft Management Console (MMC) Adding hardware to a server running a Server Core installation Obtaining a list of drivers installed on a server running a Server Core installation Installing the DNS server role

10 To manage a server running a Server Core installation locally at a command prompt 1. Start a server running a Server Core installation. 2. Log on using an administrator account. 3. At the command prompt, use the appropriate command-line tool for the task you want to complete. s For more information about command-line tools, see "Steps for administering a Server Core installation" later in this document. You can find further information at the Command-Line Reference A-Z (). To manage a server running a Server Core installation by using a terminal server 1. On the server running a Server Core installation, type the following command at a command prompt: cscript C:\Windows\System32\ Scregedit.wsf /ar 0 This enables the Remote Desktop for Administration mode to accept connections. 2. On another computer, click Start, click Run, type mstsc, and then click OK. 3. In Computer, enter the name of the server running a Server Core installation, and click Connect. 4. Log on using an administrator account. 5. When the command prompt appears, you can manage the computer using the Windows command-line tools. 6. When you have finished remotely managing the computer, type logoff in the command prompt to end your Terminal Server session. s If you are running the Terminal Services client on a previous version of Windows, you must turn off the higher security level that is set by default in Windows Server To do this, after step 1, type the following command at the command prompt: cscript C:\Windows\System32\Scregedit.wsf /cs 0 s For more information about command-line tools, see "Steps for administering a Server Core installation" later in this document. You can find further information at the Command-Line Reference A-Z (). Often it is useful to run Cmd.exe in a Command Prompt window on your local computer, rather than in the Terminal Services client. To do this, you need a standard Windows Server 2008 installation and the latest Terminal Services client. To use TS RemoteApp to publish Cmd.exe to your local computer 1. Add the Terminal Services role to the computer running Windows Server 2008 using Server Manager. 2. Start MMC on the computer running Windows Server 2008, add the TS RemoteApp Manager snap-in, and then connect the snap-in to a server running a Server Core installation. 3. In the Results pane of the snap-in, click RemoteApp Programs, and then navigate to \\<ServerName>\c$\windows\system32\cmd.exe (where ServerName is the name of the server running a Server Core installation). 4. In the Allow list, click Remote cmd.exe, and then click Create RDP package. 5. Connect to the server running a Server Core installation by using the Remote Desktop Protocol package. To manage a server running a Server Core installation by using the Windows Remote Shell 1. To enable Windows Remote Shell on a server running a Server Core installation, type the following command at a command prompt: WinRM quickconfig 2. On another computer, at a command prompt, use WinRS.exe to run commands on a server running a Server Core installation. For example, to perform a directory listing of the Windows folder, type: winrs -r:<servername> dir c:\windows ServerName is the name of the server running a Server Core installation. The WinRM quickconfig setting enables a server running a Server Core installation to accept Windows Remote Shell connections. This setting can also be set in an unattend file. See the example in Appendix A at the end of this document. Important For more information about using different security credentials to run commands, see the command-line help for WinRS.exe by typing winrs -? at a command prompt. To manage a server that is running a Server Core installation and is a domain member using an MMC snap-in 1. Start an MMC snap-in, such as Computer Management. 2. In the left pane, right-click the top of the tree and click Connect to another computer. (In thecomputer Management example, you would rightclick Computer Management (Local).) 3. In Another computer, type the computer name of the server running a Server Core installation and click OK

11 installation and click OK. 4. You can now use the MMC snap-in to manage the server running a Server Core installation as you would any other computer running a Windows Server operating system. To manage a server that is running a Server Core installation and is not a domain member using an MMC snap-in 1. If the server running a Server Core installation is not a member of a domain, establish alternate credentials to use to connect to the Server Core installation by typing the following command at a command prompt on your client computer: cmdkey /add:<servername> /user:<username> /pass:<password> ServerName is the name of the server running a Server Core installation. UserName is the name of an administrator account. To be prompted for a password, omit the /pass option. 2. When prompted, type the password for the user name that is specified in the previous step. 3. If the firewall on the computer running a Server Core installation is not already configured to allow MMC snap-ins to connect, follow the steps in "To configure Windows Firewall to allow MMC snap-in(s) to connect." Then return to this procedure. 4. On a different computer, start an MMC snap-in, such as Computer Management. 5. In the left pane, right-click the top of the tree and click Connect to another computer. (In thecomputer Management example, you would rightclick Computer Management (Local).) 6. In Another computer, type the computer name of the server running a Server Core installation and click OK. 7. You can now use the MMC snap-in to manage the server running a Server Core installation as you would any other computer running a Windows Server operating system. To configure Windows Firewall to allow MMC snap-in(s) to connect To allow all MMC snap-ins to connect, Netsh advfirewall firewall set rule group= remote administration new enable=yes To allow only specific MMC snap-ins to connect, Netsh advfirewall firewall set rule group= <rulegroup> new enable=yes Rulegroup is one of the values from the table below, depending on which snap-in you want to connect. MMC snap-in Rule group Event Viewer Remote Event Log Management Services Remote Services Management Shared Folders File and Printer Sharing Task Scheduler Remote Scheduled Tasks Management Reliability and Performance Performance Logs and Alerts Disk Management Windows Firewall with Advanced Security File and Printer Sharing Remote Volume Management Windows Firewall Remote Management s Some MMC snap-ins do not have a corresponding rule group that allows them to connect through the firewall. However, enabling the rule groups for Event Viewer, Services, or Shared Folders will allow most other snap-ins to connect. Additionally, certain snap-ins require further configuration before they can connect through the firewall: Device Manager. You must first enable the Allow remote access to the PnP interface policy setting. To do this, on a computer running Windows Vista or a full installation o Windows Server 2008, open the Local Group Policy Editor MMC snap-in, connect to the computer running a Server Core installation, navigate to Computer Configuration\Administrative Templates\Device Installation, and then enable Allow remote access to the PnP interface. Restart the computer running a Server Core installation. that when Device Manager is used remotely, it is read-only. Disk Management. You must first start the Virtual Disk Service (VDS) on the computer running a Server Core installation. IP Security Monitor. You must first enable remote management of this snap-in. To do this, Cscript \windows\system32\scregedit.wsf /im 1 Reliability and Performance. The snap-in does not require any further configuration, but when you use it to monitor a computer running a Server Core installation, you can onl monitor performance data. Reliability data is not available. To add hardware to a server running a Server Core installation 1. Follow the instructions provided by the hardware vendor for installing new hardware: If the driver for the hardware is included in Windows Server 2008, Plug and Play will start and install the driver. If the driver for the hardware is not included, proceed with the steps 2 and Copy the driver files to a temporary folder on the server running a Server Core

12 2. Copy the driver files to a temporary folder on the server running a Server Core installation. 3. At a command prompt, open the folder where the driver files are located, and then run the following command: pnputil -i -a <driverinf> driverinf is the file name of the.inf file for the driver. 4. If prompted, restart the computer. To obtain a list of drivers that are installed on the server running a Server Core installation sc query type= driver You must include the space after the equal sign for the command to complete successfully. To disable a device driver on a server running a Server Core installation sc delete <service_name> service_name is the name of the service that you obtain by running sc query type= driver. Administering a Server Core installation This section focuses on common administrative tasks that are performed locally or remotely from a command prompt. The commands are grouped into the following sections: Configuration and installation Networking and firewall Updates and error reporting Services, processes and performance Event logs Disk and file system Hardware Remote administration Prerequisites for administering a Server Core installation To complete this task, you need: A computer on which you have installed and configured a Server Core installation of Windows Server 2008 An administrator user account and password for the server running a Server Core installation Known issues for administering a Server Core installation Server Core installation supports Windows Installer in quiet mode so that you can install tools and utilities from Windows Installer files. To use the Disk Management MMC snap-in remotely, start the Virtual Disk Service on a server running a Server Core installation. To do this, type the following at a command prompt: net start VDS If you need to write a script for managing a server running a Server Core installation, which requires the secure inclusion of an administrative password, see the scripting column o Microsoft TechNet ( Steps for administering a Server Core installation The following procedures summarize common administrator tasks for a server running a Server Core installation. Configuration and installation Task Set the local administrative password Join a computer to a domain Confirm that the domain has changed Remove a computer from a domain Add a user to the local Administrators group. Remove a user from the local Administrators group Add a user to the local computer Add a group to the local computer Change the name of a domain- Steps net user administrator * 1. At a command prompt, type on one line: netdom join %computername% /domain:<domain> /userd: <domain>\username> /password:* 2. Restart the computer. set netdom remove net localgroup Administrators /add <domain>\<username> net localgroup Administrators /delete <domain\username> net user <domain\user name> /add * net localgroup <group name> /add

13 Change the name of a domainjoined computer Confirm the new computer name Change the name of a computer in a work group Disable paging file management Configure the paging file Change to a static IP address. Set a static DNS address. Change to a DHCP-provided IP address from a static IP address. Activate the server locally. Activate the server remotely. netdom renamecomputer %computername% /NewName: <new computer name> /userd: <domain\username> /password:* set 1. netdom renamecomputer <currentcomputername> /NewName: <newcomputername> 2. Restart the computer. wmic computersystem where name="<computername>" set AutomaticManagedPagefile=False wmic pagefileset where name= <path/filename> set InitialSize= <initialsize>,maximumsize= <maxsize> path/filename is the path to and name of the paging file initialsize is the starting size of the paging file in bytes. maxsize is the maximum size of the page file in bytes. 1. ipconfig /all 2. Record the relevant information or redirect it to a text file (ipconfig /all >ipconfig.txt). 3. netsh interface ipv4 show interfaces 4. Verify that there is an interface list. 5. netsh interface ipv4 set address name <ID from interface list> source=static address=<preferred IP address> gateway=<gateway address> 6. Verify by typing ipconfig /all at a command prompt and checking that DHCP enabled is set to No. 1. netsh interface ipv4 add dnsserver name=<name of primary DNS server> address=<ip address of the primary DNS server> index=1 2. netsh interface ipv4 add dnsserver name=<name of secondary DNS server> address=<ip address of the secondary DNS server> index=2 3. Repeat as appropriate to add additional servers. 4. Verify by typing ipconfig /all and checking that all the addresses are correct. 1. netsh interface ipv4 set address name=<ip address of local system> source=dhcp 2. Verify by typing Ipconfig /all and checking that DCHP enabled is set to Yes. slmgr.vbs -ato 1. cscript slmgr.vbs -ato <servername> <username> <password> 2. Retrieve the GUID of the computer by typingcscript slmgr.vbs -did 3. Type cscript slmgr.vbs -dli <GUID> 4. Verify that License status is set to Licensed (activated).

14 If Slmgr.vbs fails to activate the computer, the resulting error message advises you to run Slui.exe, along with the error code for more information. Slui.exe is not included in Server Core installations it is available in Windows Vista and full installations of Windows Server Networking and firewall Task Configure your server to use a proxy server. Steps netsh Winhttp set proxy <servername>:<port number> Server Core installations cannot access the Internet through a proxy that requires a password to allow connections. Configure your server to bypass the proxy for internet addresses. Display or modify IPSEC configuration. Display or modify NAP configuration. Display or modify IP to physical address translation. Display or configure the local routing table. View or configure DNS server settings. Display protocol statistics and current TCP/IP network connections. Display protocol statistics and current TCP/IP connections using NetBIOS over TCP/IP (NBT). Display hops for network connections. Trace hops for network connections. Display the configuration of the multicast router. Enable remote administration of the firewall. netsh winttp set proxy <servername>:<port number>bypass-list="<local>" netsh ipsec netsh nap arp route nslookup netstat nbtstat pathping tracert mrinfo netsh advfirewall firewall set rule group= Windows Firewall Remote Management new enable=yes Updates, error reporting, and feedback Task Install an update. List installed updates Remove an update. Configure automatic updates. Enable error reporting. Steps wusa <update>.msu /quiet systeminfo 1. Type at a command prompt: expand /f:* <update>.msu c:\test 2. Navigate to c:\test\ and open <update>.xml in a text editor. 3. In <update>.xml, replace Install with Removeand save the file. 4. pkgmgr /n:<update>.xml At a command prompt: To verify the current setting, type: cscript scregedit.wsf /AU /v To enable automatic updates, type: cscript scregedit.wsf /AU /4 To disable automatic updates, type: cscript scregedit.wsf /AU /1 At a command prompt: To verify the current setting, type:serverweroptin /query To automatically send detailed reports,

15 Participate in the Customer Experience Improvement Program (CEIP). To automatically send detailed reports, type: serverweroptin /detailed To automatically send summary reports, type: serverweroptin /summary To disable error reporting, type:serverweroptin /disable At a command prompt: To verify the current setting, type: serverceipoptin /query To enable CEIP, type: serverceipoptin /enable To disable CEIP, type: serverceipoptin /disable Services, processes, and performance Task List the running services. Start a service. Stop a service. Retrieve a list of running applications and associated processes. Stop a process forcibly. Start Task Manager. Manage the performance counters and logging with commands such as typeperf, logman,relog, tracerprt. Event logs Steps At a command prompt, type either of the following: sc query net start At a command prompt, type either of the following: sc start <service name> net start <service name> At a command prompt, type either of the following: sc stop <service name> net stop <service name> tasklist 1. Use the tasklist command to retrieve the process ID (PID). 2. taskkill /PID <process ID> taskmgr See LinkId=84872 Task List event logs. Query events in a specified log. Export an event log. Clear an event log. Steps wevtutil el wevtutil qe /f:text <log name> wevtutil epl <log name> wevtutil cl <log name> Disk and file system Task Manage disk partitions. Manage software RAID. Manage volume mount points. Defragment a volume. Convert a volume to the NTFS file system. Compact a file. Steps diskpart /? diskraid /? mountvol /? defrag /? convert <volume letter> /FS:NTFS

16 Administer open files. Administer VSS folders. Administer the file system. Verify a file signature. Take ownership of a file or folder. compact /? openfiles /? vssadmin /? fsutil /? sigverif /? icacls /? Hardware Task Add a driver for a new hardware device. Remove a driver for a hardware device. Steps 1. Copy the driver to a folder at %homedrive%\<driver folder>. 2. pnputil -i -a %homedrive%\<driver folder>\<driver>.inf 1. For a list of loaded drivers, at a command prompt, type: sc query type= driver 2. At the command prompt, type: sc delete <service_name>

17