Server 20008 - Module_9_Server_Core
76 Pages

Server 20008 - Module_9_Server_Core

Subject/Unit Code: MCP MCSE MMCP MCSE M, Semester Three 2010

University or Institution: University of Sydney

Word Count: 14276

Rating:

Document Preview

D R A F T - P rSupporting e RTM Published: November 12, 2007 Microsoft Confidential - For Internal and OEM Partner Use Only Windows Server 2008 for Networking Module 9: Server Core Note: Documentation based on Pre-RTM code. Final product may be different from what is shown or described in this workbook. Note: No Lab manual is available for this workbook. DISCLAIMER 2007 Microsoft Corporation. All rights...

Unformatted Document Excerpt
Coursehero >> Australia >> University of Sydney >> MCP MCSE M MCP MCSE M

Course Hero has millions of student submitted documents similar to the one
below including study guides, practice problems, reference materials, practice exams, textbook help and tutor support.

Course Hero has millions of student submitted documents similar to the one below including study guides, practice problems, reference materials, practice exams, textbook help and tutor support.

R D A F T - P rSupporting e RTM Published: November 12, 2007 Microsoft Confidential - For Internal and OEM Partner Use Only Windows Server 2008 for Networking Module 9: Server Core Note: Documentation based on Pre-RTM code. Final product may be different from what is shown or described in this workbook. Note: No Lab manual is available for this workbook. DISCLAIMER 2007 Microsoft Corporation. All rights reserved. M icrosoft, and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. THE CONTENTS OF THIS PACKAGE ARE FOR INFORMATIONAL AND TRAINING PURPOSES ONLY AND ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY K IND, WHETHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE I MPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. No part of the text or software included in this training package may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or any information storage and retrieval system, without permission from M icrosoft. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. To obtain authorization for uses other than those specified above, please visit the Microsoft Copyright Permissions Web page at http://www.microsoft.com/about/legal/permissions This content is proprietary and confidential, and is intended only for users described in the content provided in this document. This content and information is provided to you under a Non-Disclosure Agreement and cannot be distributed. Copying, disclosing all or any portion of the content and/or information included in this document is strictly prohibited. Supporting Windows Server 2008 for Networking Module 9: Server Core Table of Contents Tables Figures Module 9: Server Core Part 3: Support and Troubleshooting Overview The Windows Server Core installation is a new minimal server installation option for W indows Server 2008. It has the same default configuration as the full installation, but with some benefits associated with manageability, security and stability. This lesson will outline the specific Networking roles available and discuss troubleshooting techniques for Server Core. What You Will Learn After completing this module, you will be able to: 1. Explain what Windows Server 2008 Core installation is. 2. Understand the specific Networking roles available in a server core installation, including configuration. 3. Perform troubleshooting tasks within a windows server core installation. DRAFT - Pre RTM 7 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting Topics in this Module In this section, you will learn more about the topics covered in this module. 1. Part 1 Server Core Functional Overview 2. Part 2 Server Core Networking Roles and Features 3. Part 3 Support and Troubleshooting 8 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Part 1: Functional Description This lesson will cover What is a Windows Server 2008 Core Installation? What You Will Learn After completing this Part of the course, you will be able to: 4. Explain what is a Windows Server 2008 Core installation. 5. Install Windows Server 2008 Core. 6. Perform initial configuration of a Windows Server 2008 Core Installation. 7. How to install server Roles. 8. How to install Features 9. Managing a Server Core Installation DRAFT - Pre RTM 9 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting Lesson 1:What is Server Core? Server core is a new minimal server installation option for Windows Server "Longhorn". A server core installation provides a minimal environment for running specific server roles, reducing the servicing and management requirements and the attack surface for those server roles. A server core installation supports the following server roles: 1. Active Directory Domain Services (AD DS) 2. Active Directory Lightweight Directory Services (AD LDS) 3. DHCP Server 4. DNS Server 5. File Services 6. Print Services 7. Streaming Media Services To accomplish this, the server core installation option installs only the subset of the Server binaries that are required by the above four server 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 as shown in the following screen shot: <NEED SCREEN SHOT OF SERVER CORE UI> Benefits of Server Core 1. Increased server stability - Server Core installs only the features required for a select number of server roles and optional components. This results in fewer running services and processes, increasing overall server stability and performance. 2. Reduced software maintenance - Server Core installs only essential functionality for a server to host and manage the available server roles so less maintenance, such as updates or service packs, is required for the server. If a security flaw is discovered in a binary that is not installed, a patch is not required. Server Core would only require approximately 40% of the updates that were required for Windows 2000. 10 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting 3. Reduced attack surface The reduced number of features on Server Core results in fewer services and applications installed and running on the server. There are fewer attack vectors exposed to the network and therefore less of an attack surface. 4. Reduced management With fewer installed features on a Server Core installation, there is less to configure and manage. 5. Less disk space required - Server Core uses approximately 1.5GB of disk space for installation and approximately 2GB for operations. Note that these are new installation minimums and more disk space should be allocated for a production environment. Whats new in the server core installation?... A server core installation of Windows Server "Longhorn" requires initial configuration from the command line. A server core installation does not include the traditional full graphical user interface. Once configured, the server can be managed locally from the command line or remotely using a Terminal Server connection. The server may also be managed remotely using the Microsoft Management Console (MMC) or command line tools that support remote use. Graphical User Interface Applications Graphical User Interface (GUI) application functionality has not been completely removed from Server Core. The following GUI applications, with some limitations, are available in a Server Core installation: 1. Command Prompt (CMD.exe) 2. Notepad (Notepad.exe) 3. Registry Editor (Regedit.exe) 4. System Information (MSInfo32.exe) 5. Task Manager (Taskmgr.exe) 6. Windows Installer (MSIExec.exe) 7. Microsoft Support Diagnostic Tool (Msdt.exe) Note The limitations to the applications above are primarily related to viewing Help and using any Browse features. This is deemed to be an acceptable tradeoff considering the alternative of not including the applications in Server Core. In addition, for Task Manager, the Resource Monitor and Services button DRAFT - Pre RTM 11 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting do not work to launch the relevant MMC consoles since these consoles are not included in Server Core. 12 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Lesson 2:Server Core Architecture As discussed previously, Server Core is not a version of Windows Server 2008 but rather an installation option. Therefore, the Windows Kernel on Server Core is the same as the Kernel on a full installation of Windows Server 2008. If a binary exists on both Server Core and a full installation of WS08, they are the same version. If a configuration option, such as system service startup type or firewall exception, applies to both Server Core and a full installation of WS08, the default configuration is the same. The following diagram shows the basic Server Core architecture as compared to a full installation of Windows Server 2008. Figure : Basic Server Core Architecture In Windows Server 2008, the core operating system elements have been modularized to facilitate the Server Core installation where a subset of the core operating system elements, and the server roles that depend upon those elements, can be excluded from installation. The diagram illustrates that, initially, there is a single Windows Server 2008 installation process. It also shows that both installation types are built on top of a common set of core operating system elements. The bold outline denotes the items that are installed for Server Core. For a full installation of Windows Server 2008, the items within the bold outline and the DRAFT - Pre RTM 13 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting items within the dashed outline are installed. The full installation option includes the core operating system elements block (.Net Framework, Explorer.exe, etc.) that are excluded from Server Core to attain the minimal footprint goal. The main purpose of the diagram above is to illustrate the modular design of Windows Server 2008 and to show how Server Core is built upon a smaller core of operating system elements. The overall architecture, for the common elements, is the same for Server Core and a full installation of Windows Server 2008. FYI A full installation of Windows Server 2008 contains all of the files that are included on Server Core with the exception of scregedit.wsf and oclist.exe, which are discussed later in this module. 14 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Lesson 3: Installing Server Core Installation Scenarios With the server core installation being a minimal installation, one of its benefits is that the security exposure is reduced because there are fewer open ports and running services. This makes it ideal for use in an environment where the server might be exposed such as on the Internet as a web server or DNS server. Also, since the core is a slimmer version, then management and maintenance overhead is reduced. This makes it appropriate for deployment in a branch office where technical resources may be limited. In this instance, one may implement a RODC (Read-only Domain Controller) In this section, you will learn more about installing Windows Server 2008 as a Server Core install. Manual Install To install a server core installation 1. Insert the appropriate Windows Server 2008 media into your drive. 2. Start your computer, and when the auto-run dialog box appears, click Setup. 3. Follow the instructions on the screen to complete Setup, making sure to select either W indows 2008 SERVERSTANDARDCORE, SERVERENTERPRISECORE, OR SERVERDATACENTERCORE, when selecting the Windows Version to install. Note There is no upgrade to Windows Server Core, only clean installations are supported Note This is no upgrade from Windows Server Core, only clean installation for full Windows Server installation. Automated Install Using an unattend.xml file to install server core allows you to perform most of the initial configuration tasks during setup. In addition to benefits typical of using an unattend file, performing an unattended install of server core also provides:the following benefits: DRAFT - Pre RTM 15 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting 1. There is no need to perform the initial configuration using command-line tools. 2. You can include the settings in the unattend file to enable remote administration as soon as setup is complete. 3. You can configure settings that cannot be easily modified from the command line, such as display resolution. To install a server core installation using an unattend file 1. Create an Unattend.xml file using a text editor or Windows System Image Manager. 2. Copy the Unattend.xml file to a local disk or network share. 3. Boot your computer to Windows PE, Windows Server 2003, or Windows XP. 4. Insert the media with the server core installation of Windows Server 2008 into your drive. I f the auto-run setup window appears, click Cancel. 5. From a command prompt, change to the drive that contains the installation media. 6. Type setup /unattend:Path\unattend.xml where Path is the path to your unattend.xml file. 7. Allow Setup to complete. Note Appendix ? of this course contains a sample Unattend.xml with comments explaining the settings in the sample configuration. 16 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Lesson 4: Initial Configuration In this section you will learn about initial configurations of a Windows Server 2008 installation. Overview After installing Windows Server 2008 Core installation, many of the normal settings that administrators are used to doing post install using the UI are not available as there is no GUI. These tasks are similar to what is seen in a normal installation of Windows Server 2008 in the Initial Configurations Task screen on first boot and successful logon. Keep in mind that many of the tasks listed below are required for installing Roles and Features to make the installation functional. Steps for configuring a server core installation The following procedures explain each step necessary to configure a computer running a server core installation. These steps include: 1. Setting the administrative password 2. Renaming the computer 3. Setting a static IP address Note A DHCP address is provided by default, only perform this procedure if you need to set a static IP address. 4. Joining a domain 5. Activating the server 6. Configuring the Firewall Setting the administrator Password On the initial log on of the server the administrator account will have no password. When the administrator attempts to log on they will be prompted for a new password before the desktop is built and a successful log on will proceed. Use the following steps to change the administrator password after the initial logon or use Ctrl + Atl +Delete to get to the security screen. DRAFT - Pre RTM 17 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting To set the administrator password 1. At the command prompt, enter: net user administrator * 2. When prompted to enter the password, enter the new password for the administrator user account and press Enter. 3. When prompted, reenter the password and press Enter. Note In the first step of the previous procedure, remember to include the asterisk (*) and press Enter before typing the administrator password. This prevents the administrator password from being displayed on the screen. Renaming the computer A common administrative task that is much different in Windows Server 2008 Core installations is renaming the computer. Because there is no explorer interfaces, renaming requires the use of the netdom command. To rename the computer. 1. Determine the current name of the server with the hostname or ipconfig command. 2. At a command prompt, type: Netdom renamecomputer <ComputerName> /NewName:<NewComputerName> 3. Restart the computer. Setting a static IP address In most server configurations the IP address is set statically for the installation. Since this task cannot be done during the install, without using an Unattend.xml file and since there is no GUI interface for setting the IP address(es) for the Server, Netsh will have to be used to configure the IP addressing. Tip Any role that requires a static IP address to be configured, like DHCP, will fail to install if a static IP address has not been configured prior to the installation attempt. 18 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting To set a static IP address 1. At the command prompt, type: 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 Where: ID is the number from step 2 above StaticIP is the static IP address 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 Where: 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 you want to set, incrementing the index= number each time. Note If you set the static IP address on the wrong network adapter, you can change back to using a DHCP supplied address 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 above. DRAFT - Pre RTM 19 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting Joining a Domain Even though the Server Core installation is a very scaled down Windows installation it will still need to be joined to a domain in most cases. Because there is no GUI interface for doing this, an administrator will have to use Netdom in order to join a domain. To join a domain 1. At the command prompt, type: netdom join ComputerName /domain:DomainName /userd:UserName /passwordd:* Where: ComputerName is the name of the server 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, enter 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, run the following command: Net localgroup administrators /add DomainName\UserName Note Netdom rename can be used to rename the server running the server core installation after joining the domain. Activating the Server Core installations will have to be activated in order for successful long term operation just like a regular install. In order to complete this task the slmgr.vbs script will need to be used to accomplish this task. To activate the server 1. At the command prompt, type: Slmgr.vbs -ato 20 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Note You can remotely activate a server core-based computer by running the following command at the command prompt of a computer running or Windows Server "Longhorn": Cscript windows\system32\slmgr.vbsServerName UserName password:-ato Firewall Configurations Configuring the firewall will be a common task for administrators in a Windows Server 2008 Core installation. During the installation of a Role or feature in a normal installation, the appropriate firewall exceptions will be added. However, in a Windows Server 2008 core installation, an administrator will have to manually add the exceptions using Netsh. To configure the firewall 1. On another computer running Windows Vista or Windows Server "Longhorn", at the command prompt, type: Netsh 2. In the netsh prompt, type: advfirewall Set machine servername Where servername is the name of the server core based server. 3. Configure the firewall normally from the netsh prompt. Note The firewall must be configured on a server core based computer to allow for remote administration. Note You can also use the Windows Firewall MMC snap-in to remotely manage the firewall on a server core based server. DRAFT - Pre RTM 21 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting Lesson 5: Server Roles on Server Core In this section you will learn about Server Roles available on a Windows Server 2008 Core installation and how to install them. Installing a Server Role on Server Core Overview Once the server core installation is complete and the server is configured for use, you can then install a server role. The server core installation of Windows Server "Longhorn" supports the following server roles: 1. Active Directory Domain Services (AD DS) 2. Active Directory Lightweight Directory Services (AD LDS) 3. DHCP Server 4. DNS Server 5. File Services 6. Print Services 7. Streaming Media Services Prerequisites for installing a server role on a server running Server Core installation To complete this task, you need the following: 1. A computer on which you have installed and configured a Server Core installation of W indows Server "Longhorn". 2. An administrator user account and password for the server running the Server Core installation. 3. If installing and configuring a print server, another computer running Windows Vista or Windows Server "Longhorn" on which you can run the Print Management Console to remotely configure the print server. 4. If installing and configuring a DHCP server, the information required to configure a DHCP scope. 5. If installing and configuring a DHCP server, you must configure the server running the Server Core installation to use a static IP Address. 6. If installing and configuring a DNS server, the information required to configure a DNS zone. 22 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting 7. If installing and configuring an Active Directory environment, the information required to either join an existing domain or to create a new domain. 8. 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 1. You cannot use the Active Directory Domain Controller Installation Wizard (Dcpromo.exe) on a server running Server Core installation. You must use an unattend f ile with Dcpromo.exe to install or remove the domain controller role. Alternately, you can run Dcpromo.exe on another Windows Server "Longhorn" computer and use the wizard to save an unattend file that you can then use on the server running Server Core installation. 2. Dcpromo.exe will restart the computer immediately when the installation is complete or when Active Directory is removed unless RebootOnCompletion=No is included in the answer file. Available server roles Oclist.exe lists the Roles and Features and their state (installed/not installed) on a Windows Server Core installation. When examining this output note the names of the Roles and Features, including case as the ocsetup.exe command to install the roles and features is case sensitive. Figure :Oclist.exe output on a Server Core Install with no Roles or Features installed. Use the listed update names with Ocsetup.exe to install/uninstall a server role or optional feature. Adding or removing the Active Directory role with OCSetup.exe is not supported. It can leave your server in an unstable state. Always use DCPromo to install or uninstall Active Directory. =========================================================================== Microsoft-Windows-ServerCore-Package Not Installed:BitLocker Not Installed:BitLocker-RemoteAdminTool Not Installed:ClientForNFS-Base Not Installed:DFSN-Server Not Installed:DFSR-Infrastructure-ServerEdition Not Installed:DHCPServerCore DRAFT - Pre RTM 23 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting Not Installed:DirectoryServices-ADAM-ServerCore Not Installed:DirectoryServices-DomainController-ServerFoundation Not Installed:DNS-Server-Core-Role Not Installed:FailoverCluster-Core Not Installed:FRS-Infrastructure Not Installed:IIS-WebServerRole | |--- Not Installed:IIS-FTPPublishingService | | | | | |--- Not Installed:IIS-WebServer | | | | | | | | | | | | | | | | | | | | | | |--- Not Installed:IIS-ApplicationDevelopment | | | | | | | | | | | | | | | | | | | | |--- Not Installed:IIS-ASP | | |--- Not Installed:IIS-CGI | | |--- Not Installed:IIS-ISAPIExtensions | | | | | |--- Not Installed:IIS-ISAPIFilter | | |--- Not Installed:IIS-ServerSideIncludes | | |--- Not Installed:IIS-ASP | | |--- Not Installed:IIS-FTPServer | 24 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |--- Not Installed:IIS-CommonHttpFeatures | | | | | | | | | | | | | | | | | |--- Not Installed:IIS-HealthAndDiagnostics | | | | | | | | | | | | | | | | |--- Not Installed:IIS-CustomLogging | | |--- Not Installed:IIS-HttpLogging | | |--- Not Installed:IIS-HttpTracing | | |--- Not Installed:IIS-LoggingLibraries | | |--- Not Installed:IIS-ODBCLogging | | |--- Not Installed:IIS-DefaultDocument | | |--- Not Installed:IIS-DirectoryBrowsing | | |--- Not Installed:IIS-HttpErrors | | |--- Not Installed:IIS-HttpRedirect | | |--- Not Installed:IIS-StaticContent | DRAFT - Pre RTM 25 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |--- Not Installed:IIS-RequestMonitor | |--- Not Installed:IIS-Performance | | | | | | | | |--- Not Installed:IIS-Security | | | | | | | | | | | | | | | | | | | | | |--- Not Installed:IIS-BasicAuthentication | | |--- Not Installed:IIS-ClientCertificateMappingAuthentication | | |--- Not Installed:IIS-DigestAuthentication | | |--- Not Installed:IIS-IISCertificateMappingAuthentication | | |--- Not Installed:IIS-IPSecurity | | |--- Not Installed:IIS-RequestFiltering | | | | |--- Not Installed:IIS-ASP | | |--- Not Installed:IIS-HttpCompressionDynamic | | |--- Not Installed:IIS-HttpCompressionStatic | 26 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting | | | | | | | | | | | | | | | | | | | | |--- Not Installed:IIS-URLAuthorization | | |--- Not Installed:IIS-WindowsAuthentication | |--- Not Installed:IIS-WebServerManagementTools | | | | | | | | | | | | | | | | | | | | | | | | | |--- Not Installed:IIS-IIS6ManagementCompatibility | | | | | | | | | | | | | | | | | | | | |--- Not Installed:IIS-ManagementScriptingTools | | |--- Not Installed:IIS-LegacyScripts | | |--- Not Installed:IIS-Metabase | | | | | | | | |--- Not Installed:IIS-WMICompatibility | | | | | |--- Not Installed:IIS-LegacyScripts | | |--- Not Installed:IIS-FTPServer | | |--- Not Installed:IIS-LegacyScripts | DRAFT - Pre RTM 27 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting | Not Installed:Microsoft-Windows-RemovableStorageManagementCore Not Installed:MultipathIo Not Installed:NetworkLoadBalancingHeadlessServer Not Installed:Printing-ServerCore-Role | |--- Not Installed:Printing-LPDPrintService | Not Installed:QWAVE Not Installed:ServerForNFS-Base Not Installed:SNMP-SC Not Installed:SUACore Not Installed:TelnetClient Not Installed:WAS-WindowsActivationService | |--- Not Installed:WAS-ProcessModel | | | | | | | | | | | | | | | | | | | | |--- Not Installed:IIS-ASP | | |--- Not Installed:IIS-BasicAuthentication | | |--- Not Installed:IIS-CGI | | |--- Not Installed:IIS-ClientCertificateMappingAuthentication | | |--- Not Installed:IIS-CustomLogging | | |--- Not Installed:IIS-DefaultDocument | | 28 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |--- Not Installed:IIS-DigestAuthentication | | |--- Not Installed:IIS-DirectoryBrowsing | | |--- Not Installed:IIS-HttpCompressionDynamic | | |--- Not Installed:IIS-HttpCompressionStatic | | |--- Not Installed:IIS-HttpErrors | | |--- Not Installed:IIS-HttpLogging | | |--- Not Installed:IIS-HttpRedirect | | |--- Not Installed:IIS-HttpTracing | | |--- Not Installed:IIS-IISCertificateMappingAuthentication | | |--- Not Installed:IIS-IPSecurity | | |--- Not Installed:IIS-ISAPIExtensions | | | | | |--- Not Installed:IIS-ASP | DRAFT - Pre RTM 29 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |--- Not Installed:IIS-ISAPIFilter | | |--- Not Installed:IIS-LoggingLibraries | | |--- Not Installed:IIS-ODBCLogging | | |--- Not Installed:IIS-RequestFiltering | | | | | |--- Not Installed:IIS-RequestMonitor | | |--- Not Installed:IIS-ServerSideIncludes | | |--- Not Installed:IIS-StaticContent | | |--- Not Installed:IIS-URLAuthorization | | |--- Not Installed:IIS-WindowsAuthentication | | |--- Not Installed:IIS-ASP | Not Installed:WindowsServerBackup Not Installed:WINS-SC 30 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Installing Server Roles Ocsetup.exe installs the available server roles and features in a Windows Server 2008 Core installation. One difference from using Servermanager from a regular install is there are not configuration options available in Ocsetup.exe. Configuration of a specific Role or Feature will require the use of additional command line tools to complete the installation for use. Note Ocsetup.exe tools is case sensitive for the Role and Features names. Figure :Ocsetup.exe syntax Parameter /? /h /help <component> [/uninstall] [/passive] [/unattendfile:<file>] [/quiet] [/norestart] [/log:<files>] /x:<parameters>] Description Displays the help screen for ocsetup.exe command Name of component to be installed or uninstalled. Uninstall the component. Installation is default Unattended mode, progress only. Non-default configuration parameters, implies /passive. See component documentation for details. Quiet mode, no user interaction. Do not restart the machine, even if required to complete setup. Non-default log file location Extra parameters to be supplied to the underlying installer. See component documentation for details. DRAFT - Pre RTM 31 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting Lesson 6: Features on Server Core In this section you will learn about the available features on a Windows Server Core 2008 install and how to configure them. Overview Once the installation is complete and the server is configured for use, you can install optional features. The server core installation of Windows Server "Longhorn" supports the following optional features: 1. Failover Clustering 2. Network Load Balancing 3. Subsystem for UNIX-based applications 4. Backup 5. Multipath IO 6. Removable Storage 7. Bitlocker Drive Encryption 8. Simple Network Management Protocol (SNMP) 9. Windows Internet Name Service (WINS) 10. Telnet client Note Failover Clustering is not available in Windows Server "Longhorn" Standard Edition. Prerequisites for installing an optional feature on a server running a Server Core installation The following optional features require appropriate hardware: 1. Failover Clustering 2. Network Load Balancing 3. Multipath IO 4. Removable Storage 32 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting 5. Bitlocker Drive Encryption 6. There are no prerequisites for the following optional features: 7. Subsystem for UNIX-based applications 8. Backup 9. Simple Network Management Protocol (SNMP) 10. Windows Internet Name Service (WINS) 11. Telnet client 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 1. At a command prompt, type: start /w ocsetup <featurename>. Where featurename is the name of a feature from the following list: 2. Failover Clustering: FailoverCluster-Core 3. Network Load Balancing: NetworkLoadBalancingHeadlessServer 4. Subsystem for UNIX-based applications: SUACore 5. Multipath IO: MultipathIo 6. Removable Storage: Microsoft-Windows-RemovableStorageManagementCore 7. Bitlocker Drive Encryption: BitLocker Note To install the remote administration tool for BitLocker, type the following at a command prompt: Start /w ocsetup BitLocker-RemoteAdminTool 1. Backup: WindowsServerBackup 2. Simple Network Management Protocol (SNMP): SNMP-SC 3. Windows Internet Name Service (WINS): WINS-SC DRAFT - Pre RTM 33 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting 4. Telnet client: TelnetClient Note To remove an optional feature, use start /w ocsetup with the appropriate role name and the /uninstall switch. 34 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Lesson 7: Managing a Server Core Installation In this section you will learn about additional configuration tasks for a windows Server Core install and how to perform them. Overview You can manage a server running Server Core installation in the following ways: 1. 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. 2. 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. Note Run the following command to allow terminalserver connections: netsh firewall set service remotedesktop enable 3. Remotely using Windows Remote Shell. By using another computer running W indows Vista or Windows Server "Longhorn", you can use Windows Remote Shell to run command-line tools and scripts on a server running a Server Core installation. 4. Remotely using an MMC snap-in. By using an MMC snap-in from a computer running Windows Vista or Windows Server "Longhorn", you can connect to a server running Server Core installation in the same way that you would connect to any computer running Windows. Note Run the following command to allow remote server administration: netsh firewall set services remoteadmin enable DRAFT - Pre RTM 35 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting Known issues for managing a server running a Server Core installation Not all tasks can be performed from the command line or remotely through an MMC snap-in. To allow you to configure these settings, there is a script included with the server core installation of Windows Server "Longhorn" that can be used to: 1. Enable automatic updates 2. Enable Remote Desktop for Administration 3. Enable Terminal Server clients on previous versions of Windows to connect to a server running a Server Core installation 4. Configure DNS SRV record weight and priority 5. Manage IPSec Monitor remotely The script is located in the \Windows\System32 folder of the server running the server core installation. After opening the folder at the command prompt, use the following command to display the usage instructions for the above options: Cscript scregedit.wsf /? Figure : Output of cscript scregedit.wsf /? Microsoft (R) Windows Script Host Version 5.7 Copyright (C) Microsoft Corporation. All rights reserved. Automatic Updates - Manage Automatic Windows Updates These settings can be used to configure how Automatic Updates are applied to the Windows system. It includes the ability to disable automatic updates and to set the installation schedule. /AU [/v][value] /v View the current Automatic Update settings value value you want to set to. Options: 4 - Enable Automatic Updates 1 - D isable Automatic Updates 36 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Terminal Service - Allow Remote Administration Connections This allows administrators to connect remotely for administration purposes. /AR [/v][value] /v View the Remote Terminal Service Connection setting value (0 = enabled, 1 = disabled) Terminal Service - Allow connections from previous versions of Windows This setting configures CredSSP based user authentication for Terminal Service connections /CS [/v][value] /v View the Terminal Service CredSSP setting value (0 = allow previous versions, 1 = require CredSSP) IP Security (IPSEC) Monitor - allow remote management This setting configures the server to allow the IP Security (IPSEC) Monitor to be able to remotely manage IPSEC. /IM [/v][value] /v View the IPSEC Monitor setting value (0 = do not allow, 1 = allow remote management) DNS SRV priority - changes the priority for DNS SRV records This setting configures the priority for DNS SRV records and is only useful on Domain Controllers. For more information on this setting, search TechNet for LdapSrvPriority DRAFT - Pre RTM 37 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting /DP [/v][value] /v View the DNS SRV priority setting value (value from 0 through 65535. The recommended value is 200.) DNS SRV weight - changes the weight for DNS SRV records This setting configures the weight for DNS SRV records and is only useful on Domain Controllers. For more information on this setting, search TechNet for LdapSrvWeight /DW [/v][value] /v View the DNS SRV weight setting value (value from 0 through 65535. The recommended value is 50.) Command Line Reference This setting displays a list of common tasks and how to perform them from the command line. /CLI Other Command Line configuration tools The following command show the list of available command line tools for managing a Server Core Installation. Figure :Output of cscript scregedit.wsf /CLI Microsoft (R) Windows Script Host Version 5.7 Copyright (C) Microsoft Corporation. All rights reserved. To activate: Cscript slmgr.vbs -ato To use KMS volume licensing for activation: Configure KMS volume licensing: 38 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting cscript slmgr.vbs -ipk [volume license key] Activate KMS licensing cscript slmgr.vbs -ato Set KMS DNS SRV record cscript slmgr.vbs -skma [KMS FQDN] Determine the computer name, any of the following: Set c Ipconfig /all Systeminfo.exe or Hostname.exe Rename the Server Core computer: Domain joined: Netdom renamecomputer %computername% /NewName:new-name /UserD:domain-username /PasswordD:* Not domain joined: Netdom renamecomputer %computername% /NewName:new-name Changing workgroups: Wmic computersystem where name="%computername%" call joindomainorworkgroup name="[new workgroup name]" Install a role or optional feature: Start /w Ocsetup [packagename] Note: For Active Directory, run Dcpromo with an answer file. View role and optional feature package names and current installation state: oclist Start task manager hot-key: ctrl-shift-esc Logoff of a Terminal Services session: Logoff To set the pagefile size: DRAFT - Pre RTM 39 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting Disable system pagefile management: wmic computersystem where name="%computername%" set AutomaticManagedPagefile=False Configure the pagefile: wmic pagefileset where name="C:\\pagefile.sys" set InitialSize=500,MaximumSize=1000 Configure the timezone, date, or time: control timedate.cpl Configure regional and language options: control intl.cpl Manually install a management tool or agent: Msiexec.exe /i [msipackage] List installed msi applications: Wmic product Uninstall msi applications: Wmic product get name /value Wmic product where name="[name]" call uninstall To list installed drivers: Sc query type= driver Install a driver that is not included: Copy the driver files to Server Core Pnputil i a [path]\[driver].inf Rename a Network Adapter: netsh interface set interface name="Local Area Connection" newname="PrivateNetwork" Disable a Network Adapter: netsh interface set interface name="Local Area Connection 2" admin=DISABLED Determine a files version: wmic datafile where name="d:\\windows\\system32\\ntdll.dll" get version 40 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting List of installed patches: wmic qfe list Install a patch: Wusa.exe [patchame].msu /quiet Configure a proxy: Netsh winhttp proxy set [proxy_name]:[port] Other important Server Core Configuration Information 1. Notepad is included with server core. 2. If you close all command prompt windows, to open a new command prompt window you can press CTRL-ALT-DEL, click Start Task Manager, click File, click Run, and type cmd.exe. Alternatively, you can log off and log back on again. 3. Any command or tool that attempts to launch Explorer will not work. For example, "start." will not work. 4. Runonce is not supported on server core. 5. There is no support for html rendering or html help in server core. 6. Server core does not support running managed code. Any management tools and utilities run locally on the server corebased computer must be written in native W in32 code. 7. On server core you will not receive any notifications for activation, new updates or password expiration because these notifications require the Explorer shell, which is not part of the server core installation. 8. If you need to write a script for managing server core that will require the secure inclusion of an administrator password, see "How Can I Mask Passwords Using an InputBox" on Microsoft TechNet (http://go.microsoft.com/fwlink/?LinkID=56421). 9. Server core supports Windows Installer in quiet mode so that you can install tools and utilities from Windows Installer files. 10. Windows Firewall may be configured from the command line using netsh advfirewall. 11. When installing Windows Installer packages on server core, it is recommended that you use the /qb switch to display the basic UI. DRAFT - Pre RTM 41 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting 12. To change the time zone on a computer running a server core installation of Windows Server "Longhorn", run control timedate.cpl. 13. To change international settings on a computer running a server core installation of W indows Server "Longhorn", run control intl.cpl. 1. 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 1. Control.exe will not run on its own. You must run it with either Timedate.cpl or Intl.cpl. 2. Winver.exe is not available in Server Core installations. To obtain version information use Systeminfo.exe. 42 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Part 2: Networking Roles and Features This lesson will cover Roles and Features available in a Windows Server 2008 Core installation specific to Networking. What You Will Learn After completing this lesson, you will be able to: 10. Install and configure DHCP Role 11. Install and configure DNS Role 12. Install and configure WINS Feature 13. Install and configure SNMP Feature 14. Install and configure File Services Role DRAFT - Pre RTM 43 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting Lesson 1: DHCP on Server Core In this section, you will learn more about installation of the DHCP role for a Windows Server 2008 Core Installation. Installation Installing the DHCP server role on a Windows Server 2008 Core installation uses a simple command. However, configuration of scopes and dhcp options requires a knowledge of netsh. To install the DHCP server role 1. At the command prompt, type: start /w ocsetup DHCPServerCore 2. Configure a DHCP scope from the command line using netsh or remotely using the DHCP M MC snap-in. 3. If the DHCP server is installed in an Active Directory domain it will need to be authorized in Active Directory. Note Typing start /w ocsetup DHCPServerCore /uninstall at the command prompt will uninstall the DHCP server role. Configuring DHCP The largest task in installing the DHCP role on a Windows Server 2008 Core installation is the configuration. Most administrators are used to configuring role based functions using the GUI interface. Because there is no GUI interface in a core installation, the use of command l ine tools to configure DHCP will have to be used. Alternatively an administrator could connect using MMC tools from a remote machine with the DHCP MMC. The list of commands shows common configurations an administrator would make: Table . DHCP Netsh commands Table Task Netsh commands 44 DRAFT - Pre RTM 2007 Microsoft Corporation. rights All reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Authorize a DHCP Server Adding a scope Adding Ranges Adding Exclusions Adding Options Netsh dhcp add server Netsh dhcp server <servername/IP> add scope <network ID> <Mask> <ScopeName> Dhcp Server <servername/ip> Scope <Scope Network ID> Add iprange <Beginning IP in Range> <Ending IP in Range> Dhcp Server <servername/ip> Scope <Scope Network ID> add excluderange <Beginning Exclusion IP> <Ending Exlucsion IP> Dhcp Server <Servername/IP> Scope <Scope Network ID> set optionvalue 3 IPADDRESS <Default Gateway IP> Dhcp Server <Servername/IP> Scope <Scope Network ID> set optionvalue 51 DWORD "<Lease Lifetime in seconds>" Dhcp Server <Servername/IP> Scope <Scope Network ID> set optionvalue 6 IPADDRESS "<Primary DNS Server IP>" "<Secondary DNS Server IP>" Dhcp Server <Servername/IP> Scope <Scope Network ID> set optionvalue 44 IPADDRESS "<Primary WINS Server IP>" "<Secondary WINS Server IP>" Adding Reservations Dhcp Server <Server Name/IP> Scope <Scope Network ID> Add reservedip <Reserved IP Address> <Reserved Machine MAC address> "<Display Name>" "" "<DHCP/BootP>" DRAFT - Pre RTM 45 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting Lesson 2: DNS on Server Core In this section, you will learn more about <briefly describe main subtopics>. Installation Installing the DNS role on a Windows Server 2008 Core installation is also done using ocsetup.exe. Using ocsetup.exe to install Roles on a Core installation doesnt configure the Role, it only installs the binaries required and starts the service. Configuration will require the use of dnscmd.exe. To install the DNS server role 1. At the command prompt, type: start /w ocsetup DNS-Server-Core-Role 2. Configure a DNS zone from the command line using dnscmd or remotely using the DNS M MC snap-in. Note Typing start /w ocsetup DNS-Server-Core-Role /uninstall at the commant prompt will uninstall the DNS server role. Configuration After successful installation of the DNS Role on a server core installation, the configuration will have to be done using dnscmd.exe or using another computer utilizing the DNS MMC from the remote computer. In the table that follows there will be a list of common configuration commands using dsncmd.exe Table . Dnscmd.exe commands Table Task Server Information Adding Zones Adding Records Creating Dnscmd.exe commands Dnscmd.exe <ServerName/IP> DnsCmd.exe <ServerName> /ZoneAdd <ZoneName> <ZoneType> [<Options>] Usage: DnsCmd <ServerName> /RecordAdd <Zone> <NodeName> [/Aging] [/OpenAcl] [/CreatePTR] [<Ttl>] <RRType> <RRData> DnsCmd <ServerName> /CreateDirectoryPartition <FQDN of partition> 46 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Directory Partition DRAFT - Pre RTM 47 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting Lesson 3: WINS on Server Core In this section you will learn how to install and configure the WINS Feature on a Windows Server 2008 Core installation. Installation WINS is a feature in Windows Server 2008. Installing WINS on a server core installation requires the use of ocsetup.exe. Ocsetup.exe installs the necessary binaries for WINS to operate, but doesnt have configuration options for the specific feature. Use of Netsh or remote management will be required to configure WINS. To install the WINS server feature 1. At the command prompt, type: start /w ocsetup WINS-SC 2. Configure WINS replication and options using netsh. Configuration Configuring WINS on a server core installation requires the use of the netsh command line tools or the use of a remote management machine with the WINS MMC installed. In the table that follows a list of command administrative task required for configuring WINS on a server core installation. Table . Simple Table Example Task Add Replication Partner Configure Push Replication Configure Pull Replication Show all database records from all owners Netsh commands netsh wins server add partner <Replication Partner IP> netsh wins server Set Pushpartnerconfig state=1 server=<Replication Partner IP> update=2 netsh wins server set pullpartnerconfig state=1 server=<Replication Partner IP> start=0 interval=1800 netsh wins server show database Server={ } 48 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting DRAFT - Pre RTM 49 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting Lesson 4: NLB on Server Core In this section, you will learn about installing and configuring NLB on Server Core. Installation Installing NLB on a Windows Server 2008 Core installation requires the use of ocsetup.exe. This will load the necessary binaries required to run the feature. Configuration To install an optional feature At the command prompt, type: 1. start /w ocsetup NetworkLoadBalancingHeadlessServer 2. Configure NLB using the nlb.exe command. Configuration After successful installation of the NLB feature, configuration will be done using the NLB.exe command or from a remote machine using the NLB MMC. The table that follows l ist common administrative tasks using the NLB.exe command line interface. Table . NLB.exe commands table. suspend [ {Cluster[:Host] | all { local | global} }] Suspends all cluster operations until the resume command is issued. Suspend temporarily stops cluster operations if they were previously started. The purpose of this command is to override any remote control commands that might be issued. A ll subsequent cluster-control commands except resume and query are ignored. The optional parameters allow the command to address a specific cluster, a specific cluster on a specific host, all clusters on the local computer, or all global computers that are part of the cluster. resume [ {Cluster[:Host] | all { local | global} }] Resumes cluster operations after a previous suspend command. This does not restart cluster operations, but enables use of cluster-control commands, including remote control commands. The optional parameters allow the command to address a specific cluster, a specific cluster on a specific host, all clusters on the local computer, or all global computers that are part of the cluster. start [ {Cluster[:Host] | all { local | global} }] Starts cluster operations on the specified hosts. This enables all ports that might have been previously disabled. The optional parameters allow the command to address a specific cluster, a specific cluster on a specific host, all clusters on the local computer, or all global computers that are part of the cluster. 50 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting stop Stops cluster operations on the specified hosts. The optional parameters allow the [ {Cluster[:Host] command to address a specific cluster, a specific cluster on a specific host, all | all { local | clusters on the local computer, or all global computers that are part of the cluster. global} }] drainstop [ {Cluster[:Host] | all { local | global} }] Disables all new traffic handling on the specified hosts. While draining, hosts continue to service opened connections and stop their cluster operations when there are no more active connections. Draining mode can be terminated by explicitly stopping cluster mode with the stop command or by restarting new traffic handling with the start command. The optional parameters allow the command to address a specific cluster, a specific cluster on a specific host, all clusters on the local computer, or all global computers that are part of the cluster. Enables traffic handling for the rule whose port range contains the specified port. The first set of optional parameters allow the command to address every virtual IP address (vip), or specific vips on a specific port rule or on all ports. The second set of optional parameters allow the command to address a specific cluster, a specific cluster on a specific host, all clusters on the local computer, or all global computers that are part of the cluster. All ports specified by the port rule are affected. If all is specified for the port, this command is applied to the ports covered by all port rules. This command has no effect if the specified hosts have not started cluster operations. Disables and immediately blocks all traffic handling for the rule whose port range contains the specified port. The first set of optional parameters allow the command to address every virtual IP address (vip), or specific vips on a specific port rule or on all ports. The second set of optional parameters allow the command to address a specific cluster, a specific cluster on a specific host, all clusters on the local computer, or all global computers that are part of the cluster. All ports specified by the port rule are affected. If all is specified for the port, this command is applied to the ports covered by all port rules. All active connections on the specified hosts are blocked. To maintain active connections, use the drain function instead. This has no effect if the specified hosts have not started cluster operations. Displays the current cluster state and the list of host priorities for the current members of the cluster. The possible states are: Unknown. The responding host has not started cluster operations and cannot determine the cluster's state. Converging. The cluster is currently attempting to converge to a consistent state. Prolonged convergence usually indicates a problem with cluster parameters. If this occurs, check the event logs on the cluster hosts for Network Load Balancing messages warning you about the source of the problem. Draining. The cluster has converged, and the responding host is draining active connections in response to a drainstop command. Converged as default. The cluster has converged, and the responding host is the current default (the highest priority host without a drainstop command in progress). The default host handles network traffic for all of the TCP/ UDP ports not covered by the port rules. Converged. The cluster has converged, and the responding host is not the default host. The optional parameters allow the command to address a specific cluster, a specific cluster on a specific host, all clusters on the local computer, or all global computers that are part of the cluster. enable { vip[{:Port | :all}] | all[{:Port | :all}] } { Cluster[: {Host]| all { local | global} } } disable { vip[{:Port | :all}] | all[{:Port | :all}] } { Cluster[: {Host]| all { local | global} } } query [ {Cluster[:Host] | all { local | global} }] DRAFT - Pre RTM 51 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting reload [ {Cluster | all}] (local only) Reloads the NLB driver's current parameters from the registry. Cluster operations on the local host are automatically stopped and restarted if necessary. If an error exists in the parameters, the host will not join the cluster, and a warning is displayed. If this should occur, open the NLB Properties dialog box to fix the problem. Displays extensive information about your current NLB parameters, cluster state, and past cluster activity. The last several event log records produced by NLB are shown, including the binary data attached to those records. This command is designed to assist in technical support and debugging. The registry information retrieved by the display command shows what the next state of NLB would be if a reload or some other operation that causes the driver to read the registry were to be performed. The registry information might or might not be the current state of NLB. display [ {Cluster | all}] (local only) params [ {Cluster | all}] (local only) Displays information about your current NLB configuration. This command is similar to the display command, however, instead of retrieving the information from the registry, the params command queries directly from the kernel-mode driver. The information displayed is therefore the current state of NLB. (The registry information retrieved by the display command shows what the next state of NLB would be if a reload or some other operation that causes the driver to read the registry were to be performed. The registry information might or might not be the current state of NLB.) In addition to the configuration information, nlb params displays state variables from the kernel, including the current number of connections being maintained by NLB and the number of dynamic allocations that have been necessary for connection tracking Remote Commands /PASSW Password /PORT Port Specifies the remote control password. Specifies the cluster's remote control UDP port. 52 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Lesson 5: File and Print Service on Server Core In this section, you will learn how to install and configure the File and Print Service Role on a W indows Server 2008 Core installation. Installation The file server role is installed by default to provide administrative share support for management tools. Configuration Configuration of the core File Service Role requires the use of additional command line tools. The table that follows list common administrative tasks for configuring the File Service role. Table . Simple Table Example Optional File Service Features To install additional file server features use the following procedures. To install file server role features For File Replication service, type: 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 Network File System, type: DRAFT - Pre RTM 53 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting start /w ocsetup ServerForNFS-Base Then type: start /w ocsetup ClientForNFS-Base For Single Instance Store, type: start /w ocsetup SIS Note Uninstall any file server role options using the commands listed above with the /uninstall switch. 54 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Part 3: Support and Troubleshooting <Text that introduces and provides an overview of the lesson>1 2. What You Will Learn After completing this lesson, you will be able to: 15. Lesson objective 1 16. Lesson objective 2 DRAFT - Pre RTM 55 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting Lesson 1: CBS.log When using a server core installation, logging of installation and removal of Roles and Features is tracked via the cbs.log. This is very useful for diagnosing problems installing or uninstalling roles, role services and features. In this section, you will learn more about the cbs.log and its output. Overview In a Windows Server 2008 Core installation, the cbs.log file is used instead of the servermanager.log. It provides information about the Roles, Role Services, and Features that have been installed on the server. When diagnosing and troubleshooting errors with installing and uninstalling the subset of Roles and Features within a Windows Server 2008 Core installation, the cbs.log is the most useful place to look. The cbs.log is stored at %windir %\logs\cbs directory. Example of cbs.log This example show the contents of the cbs.log at first boot of a server core installation. 2007-02-21 12:13:25, Info CSI 00000001@2007/2/21:20:13:25.371 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x730c0e15 @0x7346d7b3 @0x7344eb2c @0xd8204b @0xd81ed4 @0xd81939) 2007-02-21 12:13:25, Info CBS Could not load SrClient DLL from path: SrClient.dll. Continuing without system restore points. 2007-02-21 12:13:25, Info CSI 00000002@2007/2/21:20:13:25.434 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x730c0e15 @0x7349bacf @0x7348390c @0xd8204b @0xd81ed4 @0xd81939) 2007-02-21 12:13:25, Info CBS Loaded Servicing Stack v6.0.6001.16469 with Core: D:\Windows\winsxs\x86_microsoft-windowsservicingstack_31bf3856ad364e35_6.0.6001.16469_none_0927b982c772c773\cbscore.dll 2007-02-21 12:13:25, Info CSI 00000003@2007/2/21:20:13:25.496 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x730c0e15 @0x73431a0d @0x73431794 @0xd83367 @0xd829ca @0xd81939) 2007-02-21 12:13:25, Info 2007-02-21 12:13:25, Info 2007-02-21 12:13:25, Info 2007-02-21 12:13:25, Info 2007-02-21 12:13:25, Info CBS Startup: Begin processing, registering for winlogon notification. CBS Startup: Initializing driver operations queue. CBS Startup: Initializing advanced operation queue. CSI 00000004 CSI Store 4560576 (0x004596c0) initialized CBS Startup: Processing advanced operation queue, startupPhase: 0 56 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting 2007-02-21 12:13:25, Info CSI 00000005 I AdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000003, progress = NULL, phase = 0, pdwDisposition = disp 2007-02-21 12:13:25, Info necessary. 2007-02-21 12:13:25, Info CBS Startup: Driver operations queue is empty. No processing was CBS Startup: Processing complete. hr: 0x0 2007-02-26 12:29:08, Info CSI 00000001@2007/2/26:20:29:08.046 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x73d70e15 @0x740cd7b3 @0x740aeb2c @0xb4204b @0xb41ed4 @0xb41939) 2007-02-26 12:29:08, Info CBS Could not load SrClient DLL from path: SrClient.dll. Continuing without system restore points. 2007-02-26 12:29:08, Info CSI 00000002@2007/2/26:20:29:08.136 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x73d70e15 @0x740fbacf @0x740e390c @0xb4204b @0xb41ed4 @0xb41939) 2007-02-26 12:29:08, Info CBS Loaded Servicing Stack v6.0.6001.16469 with Core: C:\Windows\winsxs\x86_microsoft-windowsservicingstack_31bf3856ad364e35_6.0.6001.16469_none_0927b982c772c773\cbscore.dll 2007-02-26 12:29:08, Info CSI 00000003@2007/2/26:20:29:08.176 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x73d70e15 @0x74201a0d @0x74201794 @0xb43367 @0xb429ca @0xb41939) 2007-02-26 12:29:08, Info 2007-02-26 12:29:08, Info 2007-02-26 12:29:08, Info 2007-02-26 12:29:08, Info 2007-02-26 12:29:08, Info CBS Startup: Begin processing, registering for winlogon notification. CBS Startup: Initializing driver operations queue. CBS Startup: Initializing advanced operation queue. CSI 00000004 CSI Store 3484152 (0x003529f8) initialized CBS Startup: Processing advanced operation queue, startupPhase: 0 2007-02-26 12:29:08, Info CSI 00000005 I AdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000003, progress = NULL, phase = 0, pdwDisposition = disp 2007-02-26 12:29:08, Info necessary. 2007-02-26 12:29:08, Info CBS Startup: Driver operations queue is empty. No processing was CBS Startup: Processing complete. hr: 0x0 DRAFT - Pre RTM 57 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting Lesson 2: Additional Troubleshooting Tools This section will discuss some of the tools and techniques that aid in troubleshooting a Server Core installation. This information provides a foundation for troubleshooting Server Core without some of the traditional troubleshooting tools that would be used to troubleshoot a full installation of Windows Server 2008. Event Logs The Event Viewer MMC snap-in is not included on Server Core however the underlying event subsystem is the same as a full installation of Windows Server 2008. The following methods may be used to view events that have occurred on a Server Core server: 1. Remotely using the Event Viewer snap-in (eventvwr.msc) from Windows Vista or a full installation of Windows Server 2008. 2. Locally using the wevtutil.exe command line tool that was introduced in Windows V ista. Wevtutil.exe can be used to retrieve information about the event logs, execute queries, archive, sort, and clear event logs. Wevtutil.exe usage Wevtutil.exe supports the following commands: el (enum-logs) gl (get-log) sl (set-log) List log names. Get log configuration information. Modify configuration of a log. ep (enum-publishers) List event publishers. gp (get-publisher) Get publisher configuration information. im (install-manifest) Install event publishers and logs from manifest. um (uninstall-manifest)Uninstall event publishers and logs from manifest. qe (query-events) gli (get-log-info) epl (export-log) al (archive-log) cl (clear-log) Query events from a log or log file. Get log status information. Export a log. Archive an exported log. Clear a log. Note 58 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Each of the wevtutil.exe commands above support multiple context options. To view the options that are specific to the commands above, use wevutil.exe <COMMAND> /? . Examples of common wevtutil.exe commands are provided below: 1. Obtain a list of all of the available event logs by name: wevtutil el 2. To create a text file with all of the System log events, run: wevtutil qe /f:text /rd:true system > system.txt 3. To create a text file that lists only the last 100 events in the Application log, run: wevtutil qe /f:text /c:100 /rd:true application > application.txt Tip Due to the large number of events that may be displayed in the command shell when using wevtutil.exe, it is recommended to pipe the output to a text file for viewing. The event logs, with a .evtx extension, are located in the following folder: %WinDir%\System32\Winevt\Logs Wecutil.exe Wevtutil.exe does not support event subscriptions so the command line tool, wecutil.exe, is provided to create and manage subscriptions to events forwarded from remote event sources that support the WS-Management protocol. Since the Event Viewer MMC console is not available on Server Core, creating event subscriptions on a full installation of Windows Server 2008 that target the Server Core server(s) can be useful to simplify Server Core event viewing. Event subscriptions provide the ability to collect copies of events from multiple remote computers and store them locally. To specify which events to collect, a subscription to a remote computers event channel(s) must be created. Subscribing to a remote computers event channel(s) allows a user to access events from the remote channel(s) without the need to f irst connect to the remote machine using the Event Viewer console. Among other details, the subscription configuration specifies exactly which events will be collected and in which log they will be stored locally. Once a subscription is active and events are being collected, you can view and manipulate these forwarded events as you would any other locally stored events. DRAFT - Pre RTM 59 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting Wectutil.exe supports the following commands: es (enum-subscription) gs (get-subscription) ss (set-subscription) cs (create-subscription) ds (delete-subscription) rs (retry-subscription) qc (quick-config) List existent subscriptions. Get subscription configuration. Set subscription configuration. Create new subscription. Delete subscription. Retry subscription. Configure Windows Event Collector service. gr (get-subscriptionruntimestatus)Get subscription runtime status. Note Each of the wecutil.exe commands above support multiple context options. To view the options that are specific to the commands above, use wecutil.exe <COMMAND> /? . Before you can create a subscription to collect events on a computer, you must configure both the collecting computer (collector) and each computer from which events will be collected (source). To configure computers to forward and collect events, perform the following steps: 1. Log on to all collector and source computers. If the computers are members of a domain, it is a best practice to use a domain account with administrative privileges. 2. On each source computer, type the following at an elevated command prompt: winrm quickconfig FYI If you intend to specify an event delivery optimization of M inimize Bandwidth or M inimize Latency, using the set-subscription (ss) argument and context options, the above command must also be executed on the collector computer. 1. On the collector computer, type the following at an elevated command prompt: wecutil qc 60 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting 1. Add the computer account of the collector computer to the local Administrators group on each of the source computers. To add a computer account to the local Administrators group, use the following command: net localgroup Administrators /add <domain>\<computername>$ As an alternative to using the computer account to gain read access to the event logs on Server Core, or any event source computer, a Specific User, such as a domain administrator, can be specified as the account used for the subscription. The User Account option is available in the Advanced Subscription Settings dialog in the Subscription Properties in Event Viewer. Important Note the $ after the computer name in the net command above. This is needed to denote that the object being added is a computer, not a user. After performing the steps above, the computers are configured to forward and/or collect events. Event Viewer or wecutil.exe, for Server Core, may then be used to configure the event subscriptions. Performance Monitoring The Reliability and Performance Monitor (RPM) console is not available on Server Core, however, the Performance Logs and Alerts service and the underlying performance subsystem is the same as a full installation of Windows Server 2008. Performance Monitoring of a Server Core server can be accomplished using the following methods: 1. Remotely using Performance Monitor on a full installation of Windows Server 2008 or Windows Vista 2. Locally on Server Core using the following command line performance monitoring tools: Logman.exe Logman.exe can be used to perform the following tasks: 3. Locally and remotely manage performance counter and event trace log collections. 4. Configure a data collection on one computer and then copy that configuration to multiple computers from a central location. DRAFT - Pre RTM 61 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting 5. Query currently-running logs and event traces. Logman.exe supports the following commands: Usage: logman [create|query|start|stop|delete|update|import|export] [options] Verbs: Create - Create a new data collector. Query - Query data collector properties by name. Start - Start an existing data collector and set the begin time to manual. Stop - Stop an existing data collector and set the end time to manual. Delete - Delete an existing data collector. Update - Update an existing data collector's properties. Import - Import a data collector set from an XML file. Export - Export a data collector set to an XML file. Options: -? - Displays context sensitive help. -s <computer> - Perform the command on specified remote system. -config <value> - Settings file containing command options. -ets - Send commands to Event Trace Sessions without saving or scheduling. A common scenario for using logman.exe on Server Core is to create a Data Collector Set using Performance Monitor on a full installation of Windows Server 2008, or Windows Vista, and export the Data Collector Set configuration as an XML template. Then, use logman.exe to import and start the Data Collector Set on a Server Core server. After exporting the Data Collector Set XML template file, the following command can be used to import the XML template using logman.exe: logman import n <name> -xml <filename> Where: <name> = the desired name for the target Data Collector Set <filename> = the name of the XML template to import To start the Performance Monitor Data Collector Set after inporting the XML template, type the following command at the command prompt: logman start <name> 62 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Where: <name> = the name of the Data Collector Set to start Tip All of the configured Data Collector Sets may be listed using logman query . The Performance Monitor log file will be created in the following folder: %systemdrive%\PerfLogs Relog.exe Relog can be used to create new performance logs from data in existing performance logs by changing the sampling rate and/or converting the file format. Supports all performance log formats, including Windows NT 4.0 compressed logs. Relog.exe supports the following commands: Usage: relog <filename [filename ...] [options] Parameters: <filename [filename ...] Options: -? -a -cf <filename> Displays context sensitive help. Append output to the existing binary file. Counters to filter from the input log. File listing performance counters to filter f rom the input log. Default is all counters in the original log file. -f <CSV|TSV|BIN|SQL> -t <value> -o Output file format. Only write every nth record into the output f ile. Default is to write every record. Output file path or SQL database. the output file. -b <M/d/yyyy h:mm:ss[AM|PM] Begin time for the first record to write into Performance file to relog. -c <path [path ...]> DRAFT - Pre RTM 63 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting -e <M/d/yyyy h:mm:ss[AM|PM] End time for the last record to write into the output file. -config <filename> -q -y Settings file containing command options. List performance counters in the input file. Answer yes to all questions without prompting. Typeperf.exe Typeperf.exe can be used to perform the following tasks: 1. Write performance data to the command window or to a supported log file format (csv|tsv|bin|sql). 2. Display all of the counters that are currently available on a particular local or remote computer. Typeperf.exe supports the following commands: Usage: typeperf { <counter [counter ...]> | -cf <filename> | -q [object] | -qx [object] } [options] Parameters: <counter [counter ...]> Performance counters to monitor. Options: -? -cf <filename> -si <[[hh:]mm:]ss> -o <filename> -q [object] Displays context sensitive help. Output file format. Default is CSV. File containing performance counters to monitor, one per line. Time between samples. Default is 1 second. Path of output file or SQL database. Default is STDOUT. List installed counters (no instances). To l ist counters for one object, include the 64 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only -f <CSV|TSV|BIN|SQL> Module 9: Server Core Part 3: Support and Troubleshooting object name, such as Processor. -qx [object] List installed counters with instances. To l ist counters for one object, include the object name, such as Processor. -sc <samples> -config <filename> -s <computer_name> -y Note: Counter is the full name of a performance counter in "\\<Computer>\<Object>(<Instance>)\<Counter>" format, such as "\\Server1\Processor(0)\% User Time". Number of samples to collect. Default is to sample until CTRL+C. Settings file containing command options. Server to monitor if no server is specified in the counter path. Answer yes to all questions without prompting. Obtaining a Kernel memory dump file If a Kernel memory dump is needed for troubleshooting purposes, the following methods may be used: 1. Crash.exe both the command line and GUI versions of Crash.exe may be used to create a memory dump file on Server Core. 2. CrashOnCTRLScroll the CTRL+Scroll Lock+Scroll Lock keyboard sequence may be used to crash a server to create a memory dump file after editing the registry to add the CrashOnCTRLScroll DWORD value, set to 1, in the following key and restarting the server: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Par ameters Note The CrashOnCTRLScroll process is described in the following Knowledge Base article: 244139 Windows feature lets you generate a memory dump file by using the keyboard http://support.microsoft.com/default.aspx?scid=kb;EN-US;244139 DRAFT - Pre RTM 65 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting As with previous versions of Windows, prior to creating a memory dump, the paging file and memory dump type must be configured and the server must be restarted. To create a Complete memory dump, the paging file must be located on the System drive and sized to at least (installed memory + 50MB). The paging file may be configured using the steps discussed in the Configure the Paging File topic in the Initial Configuration of Server Core section of this module. By default, Windows Server 2008 is configured to create a Kernel memory dump when a Kernel exception occurs. The memory dump type is defined by the CrashDumpEnabled DWORD value in the following registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl The valid CrashDumpEnabled registry values are as follows: 0x0 = None 0x1 = Complete memory dump 0x2 = Kernel memory dump 0x3 = Small memory dump (64KB) The other settings that are available in the Startup and Recovery options on a full installation of Windows Server 2008 are also located in the CrashControl registry key, as follows: Startup and Recovery UI Option Write an event to the System log Automatically restart Write debugging information Dump file Overwrite any existing file Registry value (value range) Logevent (0, 1) AutoReboot (0,1) CrashDumpEnabled (see above) DumpFile (path\<dump file name>.dmp) Overwrite (0,1) With the large amounts of RAM that are present in modern servers, it may be impractical, or unnecessary, to create a Complete memory dump. It is important to assess the situation to determine and use the minimum memory dump size that is needed to diagnose an issue. Tip Many modern servers are equipped with Non-Maskable Interrupt (NMI) capabilities which can be used to force a STOP error by pressing a switch located on the server. In most cases, unless specific functionality is provided by the hardware vendor, the Windows memory dump and paging file configuration is used for creating a memory dump initiated by an NMI switch. To enable NMI functionality, the N MICrashDump DWORD registry value must be created, and set to 1, in the 66 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting following registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl Obtaining a user mode process dump file If a user mode process memory dump is needed for troubleshooting purposes, for a process that is unresponsive, terminating unexpectedly, or exhibiting high CPU utilization, for example, the following methods may be used: 1. Task Manager Task Manager on Windows Server 2008, including Server Core, includes the option to create a process dump file, as follows: 1. Open Task Manager using one of the following methods: 1. Run taskmgr.exe f rom the command line. 2. Press CTRL+Shift+Esc. 3. Press CTRL+Alt+Del and select Task Manager from the Windows Security page. 2. Click the Processes tab in Task Manager. 3. Locate and right-click the process that will be dumped. 4. Select the Create Dump File context menu option. 1. ADPlus the ADPlus tool that is included with the Debugging Tools for Windows may be used to obtain process memory dump files. To use ADPlus to create a process dump file, perform the following steps: 1. Using a comuter with a web browser, download the latest Debugging Tools for W indows package from the following location: x86: http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx x64: http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx 2. Install the Debugging Tools for Windows on the Server Core server from a network share or after copying the installation package to the Server Core server. 3. In the Server Core command shell, change to the directory where the Debugging Tools for Windows were installed and configure ADPlus for the appropriate scenario by using the following commands: DRAFT - Pre RTM 67 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting 1. Obtain a process dump when a process terminates unexpectedly: adplus.vbs crash p <PID> -o <path> or adplus.vbs crash pn <ProcessName> -o <path> Where: <PID> = the process ID for the process <ProcessName> = the process name for the process <path> = the location to create the process dump files Using this method, the process dump is created when the process terminates unexpectedly. 2. Obtain a process dump when a process becomes unresponsive, exhibits high CPU utilization, etc.: adplus.vbs hang p <PID> -o <path> or adplus.vbs hang pn <ProcessName> -o <path> Where: <PID> = the process ID for the process <ProcessName> = the process name for the process <path> = the location to create the process dump files Using this method, the process dump is created immediately after executing the command. FYI The Debugging Tools for Windows can be installed on Server Core and the Windbg.exe debugger may be used. There are limitations, however, such as Browse and Help functionality are not available on Server Core. Kernel Pool Memory Monitoring Kernel Pool tagging is enabled by default on all versions of Windows Server 2008, including Server Core installations. Tools such as Poolmon.exe, including the GUI version of Poolmon.exe, function properly on Server Core. 68 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Important It is recommended to spawn a new command shell on Server Core and then execute Pool monitoring tools from the 2nd command shell. Otherwise, some tools may monopolize the parent command shell, requiring termination, using CTRL+C, before the command shell can be used for other tasks. Use start cmd to spawn a new command shell from an existing command shell. Microsoft Diagnostic Tool (MSDT) Server Core includes the Microsoft Diagnostic Tool (MSDT), msdt.exe, to allow Microsoft Support Professionals to obtain diagnostic information from a customers server. MSDT on Server Core, including the GUI MSDT wizard, behaves the same as it does on Windows Vista and full installations of Windows Server 2008. MSDT information may be obtained using either of the following methods: 1. If the Server Core server can access the Internet, the MSDT passcode can be provided to the customer and they can run MSDT.exe on Server Core. When prompted, the customer will type the passcode and follow the MSDT wizard to collect and save the data. The customer can then choose to allow the compressed MSDT to be uploaded to Microsoft. They can also select the option to save the files locally, if desired. 2. If the Server Core server cannot access the Internet, the Support Professional can use the MSDT server to send an email to the customer with the URL to access the MSDT server from another computer that does have Internet access. The customer can then obtain the MSDT information by accessing the provided URL and selecting the The problem is on another computer option to obtain the MSDT-Portable.exe f ile that will be executed on the Server Core server to obtain the data. The customer would need to copy or move the compressed MSDT file that is created by MSDTPortable.exe to a computer that has Internet access and send the file to the Support Professional. Other Tools Many tools that work on full installations of Windows Server 2008 also work on Server Core, with some of the same application issues that have been discussed throughout this module. There are far too many tools to test and list within the scope of this document so the best practice is to test any tool for compatibility on Server Core. A few of the most common Sysinternals utilities that can be used on Server core are as follows: Handle - displays information about open handles for any process in the system. It can be used to see the programs that have a file open, or to see the object types and names of all the handles of a program. DRAFT - Pre RTM 69 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting Process Explorer - shows information about handles and DLLs that processes have opened or loaded as well as thread stack information. Process Monitor an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity. Combines and expands upon the functionality provided by Filemon and Regmon utilities. PsTools - includes command-line utilities for listing the processes running on local or remote computers, running processes remotely, rebooting computers, dumping event logs, and more. The Sysinternals tools are available at the following location: http://www.microsoft.com/technet/sysinternals/default.mspx 70 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Additional Reading Server Core Blog: http://blogs.technet.com/server_core/ Longhorn Server Product Site: http://www.microsoft.com/windowsserver/longhorn/ Command Line Reference A-Z: http://go.microsoft.com/fwlink/?LinkId=20331 Windows Management Instrumentation Command-line (WMIC): http://technet2.microsoft.com/WindowsServer/en/library/ea5d7f04-07e8-4b96-bda3a2b2cc15391e1033.mspx?mfr=true Managing DHCP from the Command-line: http://technet2.microsoft.com/windowsserver/en/library/a0bb93e9-2103-4edc-ad895da5b80e574c1033.mspx?mfr=true The following resources provide additional information about some of the commands used to configure Server Core and install and configure server roles: 1. Active Directory: (http://go.microsoft.com/fwlink/?LinkID=19802) 2. Backing Up and Recovering Data: (http://go.microsoft.com/fwlink/?LinkID=22347) 3. BitLocker Drive Encryption Overview: (http://go.microsoft.com/fwlink/?LinkID=62724) 4. Failover Clustering Services: (http://go.microsoft.com/fwlink/?LinkID=50520) 5. Performing an Unattended Installation of Active Directory: (http://go.microsoft.com/fwlink/?LinkId=49661) 6. Dynamic Host Configuration Protocol: (http://go.microsoft.com/fwlink/?LinkID=56423) 7. Dfscmd Overview: (http://go.microsoft.com/fwlink/?LinkId=49658) 8. Distributed File System (DFS): (http://go.microsoft.com/fwlink/?LinkId=58131) 9. Distributed File System Replication: (http://go.microsoft.com/fwlink/?LinkID=62725) 10. Windows Server 2003 Domain Name System (DNS): (http://go.microsoft.com/fwlink/? LinkID=56422) 11. Dnscmd Overview: (http://go.microsoft.com/fwlink/?LinkId=49656) 12. Dnscmd Syntax: (http://go.microsoft.com/fwlink/?LinkId=49659) 13. Dnscmd Examples: (http://go.microsoft.com/fwlink/?LinkId=49660) DRAFT - Pre RTM 71 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting 14. What is FRS?: (http://go.microsoft.com/fwlink/?LinkID=62726) 15. File and Storage Services: (http://go.microsoft.com/fwlink/?LinkID=26716) 16. Microsoft Storage Technologies - Multipath IO: (http://go.microsoft.com/fwlink/? LinkId=11264) 17. Netsh Overview: (http://go.microsoft.com/fwlink/?LinkId=49654) 18. Performance Tuning Guidelines for Microsoft Services for Network File System: (http://go.microsoft.com/fwlink/?LinkID=62727) 19. Removable Storage: (http://go.microsoft.com/fwlink/?LinkID=62728) 20. Welcome to Subsystem for UNIX-based Applications: (http://go.microsoft.com/fwlink/? LinkID=57768) 72 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Part 4:Review <Module level review points and/or questions> DRAFT - Pre RTM 73 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. Supporting Windows Server 2008 for Networking Part 3: Support and Troubleshooting Assessment <Compile questions and answers from lesson documents in Template Learning measures.xlsm, submit for entry into the online assessment system. When the assessment becomes available in the online system, update the URL below and delete this paragraph.> Now that you have completed all the course elements in this module, you are ready for the assessment. After you read the instructions below, click the link to begin the assessment: 1. 2. 3. 4. In the login box, type your alias and press Enter. For each assessment item, choose an answer and then click Next. When you have answered all the questions, click Proceed. Your score will be displayed. When you have completed reviewing your score, exit from the assessment. Click the link below to begin the course assessment: http://psswebextools.partners.extranet.microsoft.com/glslm/server/q/open.dll? session=7701712352061683 74 DRAFT - Pre RTM 2007 Microsoft Corporation. All rights reserved.Microsoft Confidential - For Internal and OEM Partner Use Only Module 9: Server Core Part 3: Support and Troubleshooting Instructor Notes This section provides additional information to assist instructors in course delivery. Instructor notes are numbered consecutively throughout the document. DRAFT - Pre RTM 75 Microsoft Confidential - For Internal and OEM Partner Use Only 2007 Microsoft Corporation. All rights reserved. 1 For lesson content examples, see _Sample_InnLnn_Lesson.docx. 2 This is an example of an Instructor endnote with a separate introductory sentence to highlight the endnote number. When viewing a document in Word, a PDF reader, or the browser window, endnote text such as this example is displayed in a pop-up when you pass your mouse pointer over the endnote reference number. You can also double-click the endnote number in the document text to jump to the endnote in the Instructor Notes section and then double-click the left margin number in the Instructor Notes section to return to the endnote location in the document text.

Textbooks related to the document above:

Find millions of documents on Course Hero - Study Guides, Lecture Notes, Reference Materials, Practice Exams and more. Course Hero has millions of course specific materials providing students with the best way to expand their education.

Below is a small sample set of documents:

University of Sydney - MCP MCSE M - MCP MCSE M
D R A F T - P rSupporting e RTMPublished: November 12, 2007 Microsoft Confidential - For Internal and OEM Partner Use OnlyWindows Server 2008 for NetworkingModule 8 Terminal Server GatewayNote: Documentation based on Pre-RTM code. Final product may be
University of Sydney - MCP MCSE M - MCP MCSE M
D R A F T - P rSupporting e RTMPublished: November 12, 2007 Microsoft Confidential - For Internal and OEM Partner Use OnlyWindows Server 2008 for NetworkingModule 7: Network Access ProtectionNote: Documentation based on Pre-RTM code. Final product may
University of Sydney - MCP MCSE M - MCP MCSE M
D R A F T - P rSupportin e RTMPublished: November 12, 2007 Microsoft Confidential - For Internal and OEM Partner Use Onlyg Windows Server 2008 for NetworkingModule 6: I PSec in Windows Server 2008Note: Documentation based on Pre-RTM code. Final produc
University of Sydney - MCP MCSE M - MCP MCSE M
D R A F T - P rSupporting e RTMPublished: November 12, 2007 Microsoft Confidential - For Internal and OEM Partner Use OnlyWindows Server 2008 for NetworkingModule 6: Network Policy and Access ServiceNote: Documentation based on Pre-RTM code. Final pro
University of Sydney - MCP MCSE M - MCP MCSE M
D R A F T - P rSupporting e RTMPublished: November 12, 2007 Microsoft Confidential - For Internal and OEM Partner Use OnlyWindows Server 2008 for NetworkingModule 4: DNSNote: Documentation based on Pre-RTM code. Final product may be different from wha
University of Sydney - MCP MCSE M - MCP MCSE M
D R A F T - P rSupporting e RTMPublished: November 12, 2007 Microsoft Confidential - For Internal and OEM Partner Use OnlyWindows Server 2008 for NetworkingModule 3: D HCPNote: Documentation based on Pre-RTM code. Final product may be different from w
University of Sydney - MCP MCSE M - MCP MCSE M
D R A F T - P rSupporting e RTMPublished: November 12, 2007 Microsoft Confidential - For Internal and OEM Partner Use OnlyWindows Server 2008 for NetworkingModule 2: Windows Server 2008 Configuration I nterfacesNote: Documentation based on Pre-RTM cod
University of Sydney - MCP MCSE M - MCP MCSE M
D R A F T - P r e Supporting RTMPublished: N ovember 12, 2007 M icr osoft Confident ial - For I nt er nal and OEM Par t ner Use OnlyW indows Server 2008 for N etworkingCou rse Overv iewNote: Documentation based on Pre-RTM code. Final product may be di
École Normale Supérieure - MTH - 718
Introduction to Probability Models Ninth EditionThis page intentionally left blankIntroduction to Probability ModelsNinth EditionSheldon M. RossUniversity of California Berkeley, CaliforniaAMSTERDAM BOSTON HEIDELBERG LONDON NEW YORK OXFORD PARIS SAN
Dominican School of Philosophy and Theology - INFOMATIC - 2
A Fast Fourier Transform CompilerMatteo Frigo MIT Laboratory for Computer Science 545 Technology Square NE43-203 Cambridge, MA 021394 3 ( &amp; $ &quot; 210)'%#! February 16, 1999Abstract The FFTW library for computing the discrete Fourier transform (DFT) has
FIT - ACCT 1 - EAC 2211
Financial Statement Case(20-30 min.) Financial Statement CaseReq. 1 (balances in millions at December 31, 2004)Accumulated Depreciation 177 Accounts Payable 1,142 Other Assets 42Req. 2 (amounts in millions)JournalDATE ACCOUNTS AND EXPLANATIONS POST
University of Texas - EE - EE 306
EE306 IntroductiontoComputingChapter7:AssemblyLanguageRameshYerraballi7-1Example01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 ; ; Program to multiply a number by six ; .ORIG x3050 LD R1, SIX LD R2, NUMBER AND R3, R3, #0 ; clear R3 ; ; T
University of Texas - EE - EE 306
EE306 IntroductiontoComputingChapter8:I/O(Input/Output)RameshYerraballi8-1I/OBasicsDefinitionsInput transferdatafromtheoutsideworldtothecomputer: keyboard,mouse,scanner,barcodereader,etc. transferdatafromthecomputertotheoutside:monitor, printer,LED
University of Texas - EE - EE 306
EE 306: Programming Assignment 2Department of Electrical and Computer Engineering The University of Texas at Austin Spring 2010 Due: Friday 2nd April 2010, 11:59 pm Instructor: Ramesh Yerraballi, TAs: Pratyusha Nidamaluri, Arvind Chandrababu You must do
Foothill College - PA - SE103
Major plc Balance sheet as at 31 December 20052005 000 Fixed assets Plant and machinery P&amp; M depreciation Current assets Stocks Debtors Prepayments Cash Total assets Current liabilities Overdraft Creditors Taxation Dividends Accruals 29,300 10,750 13,150
Acadia - ACC - 52639
Works Cited &quot;Consumer Debt Statistics.&quot; Careers, Finance and Investing : Money-zine.com. 2009. Web. 14 Mar. 2010. &lt;http:/www.money-zine.com/Financial-Planning/DebtConsolidation/Consumer-Debt-Statistics/&gt;. &quot;Credit-Card Fees: The New Traps.&quot; The Wall Street
Ashford University - PHIL - PHIL 107
You Earned it1Do we all deserve to drive fancy cars and live in huge mansions? Do we deserve to live in happiness and worry free? Many people would answer yes to the questions above. The finer things in life dont come to us by chance; they come from har
Aims Community College - ENVI SCI - 5460453
Environmental Science2002 AP ENVIRONMENTAL SCIENCE FREE-RESPONSE QUESTIONSENVIRONMENTAL SCIENCESECTION II Time90 minutes 4 Questions Directions: Answer all four questions, which are weighted equally; the suggested time is about 22 minutes for answering
Aims Community College - ENVI SCI - 5460453
AP Environmental Science 2007 Free-Response QuestionsThe College Board: Connecting Students to College SuccessThe College Board is a not-for-profit membership association whose mission is to connect students to college success and opportunity. Founded i
Aims Community College - ENVI SCI - 5460453
AP Environmental Science 2003 Free-Response QuestionsThe materials included in these files are intended for use by AP teachers for course and exam preparation; permission for any other use must be sought from the Advanced Placement Program. Teachers may
Aims Community College - ENVI SCI - 5460453
AP Environmental ScienceThe goal of this course is to provide students with the scientific principles, concepts, and methodologies to understand the interrelationships of the natural world, to identify and analyze environmental problems both natural and
Aims Community College - ENVI SCI - 5460453
AP Environmental Science 2008 Free-Response QuestionsThe College Board: Connecting Students to College SuccessThe College Board is a not-for-profit membership association whose mission is to connect students to college success and opportunity. Founded i
UNC - CHEM - 101L
Experiment 3 Density of Nonane Fall 2009Name TAType name Type TA's nameDay and Time Section Type section numberDocumentation List references here (Lab Partners, Lab Manual, Textbook, etc.)Grading RubricPossible Points Materials and Methods Reference
UNC - CHEM - 101L
Experiment 7ThermochemistryLab Goals1. Thermochemistry 2. Calorimetry 3. Hess' Law and Thermochemical Equations 4. Principals of exothermic and endothermic reactionsIntroduction to ThermochemistryThermochemistry the study of heat energy transfer resu
UNC - CHEM - 101L
Experiment 2 Scientific Measurement and Error Fall 2009Name TAType name Type TA's nameLab Day and Time SectionType day &amp; time Type section numberDocumentationList references here (Lab Partners, Lab Manual, Textbook, etc.)Grading RubricPossible Poi
UNC - CHEM - 101L
Experiment 5Conductometric TitrationLab Goals1. The Law of Conservation of Matter 2. Writing and balancing chemical equations 3. Conductivity as a means of following the progress of a chemical reactionThe Law of Conservation of MatterMatter (atoms) c
UNC - CHEM - 101L
Experiment 1 Software Tutorial Fall 2009Name TAType name Type TA's nameLab Day and Time SectionType day &amp; timeType section numberDocumentationList references here (Lab Partners, Lab Manual, Textbook, etc.)Grading RubricPossible Points Tutorial Pl
UNC - CHEM - 101L
Experiment 3Sensors and Chemical ReactionsLearning Objectives Define solution and understand its components Identify major classes of reactions Write chemical equations for various reactions Determine an appropriate sensor to monitor the course of a re
UNC - CHEM - 101L
Experiment 4Mass, Volume, and DensityLab Goals1. Understand the concepts of density 2. Measure the density of water at room temperature 3. Observe the effects of temperature on densityDo not plug immersion heater into the electrical outlet unless the
UNC - CHEM - 101L
Experiment 2Scientific Measurement and Experimental ErrorLearning Objectives Introduction to basic laboratory apparatus and manipulations associated with chemical measurements Identifying experimental error Using statistical analysis to quantify error
UNC - CHEM - 101L
Experiment 8 Beer-Lambert Law Fall 2009Name TA Brooke Hayden Zach Blanchard Lab Manual, Christina Miller Lab Day and Time Section Thursday, 2:00-5:50 432DocumentationPossible Points Introduction Hypothesis Purpose of report Goals of the experiment Mate
UNC - CHEM - 101L
Experiment 7 Spectroscopy Spring 2009Name TA Type name Type TA's name List references here (Lab Partners, Lab Manual, Textbook, etc.) Lab Day and Time Section Type day &amp; time Type section numberDocumentationPossible Points Introduction Purpose of repor
UNC - CHEM - 101L
Experiment 3 MASS, VOLUME AND DENSITYI. Learning Objectives To measure the density of a nonane at room temperature. To examine the effects of temperature on density.II.Background InformationAn important intensive property of every substance is its de
UNC - CHEM - 101L
Experiment 6 Thermochemistry Fall 2009Name TA Type name Type TA's name List references here (Lab Partners, Lab Manual, Textbook, etc.) Lab Day and Time Section Type day &amp; time Type section numberDocumentationPossible Points Introduction Purpose of repo
UNC - CHEM - 101L
Experiment 1 DATASTUDIO SOFTWARE TUTORIALI.Learning Objectives To introduce the basic concepts of data manipulation within the DataStudio software environment. To complete a step-by-step tutorial highlighting the major features of DataStudio.II.Backg
UNC - CHEM - 101L
Experiment 5 Conductometric Titration Fall 2009Name TA Type name Type TA's name List references here (Lab Partners, Lab Manual, Textbook, etc.) Lab Day and Time Section Type day &amp; time Type section numberDocumentationGrading RubricPossible Points Intr
UNC - CHEM - 101L
Experiment 8Beer's LawLearning ObjectivesUnderstand and use Beer's Law Gain experience with light absorption techniques (colorimetry) Utilize the reaction of iron with thiocyanate to determine iron content in foodChemical AnalysisWe want to determine
UNC - CHEM - 101L
Experiment 4 Sensors and Chemical Reactions Fall 2009Name TAType name Type TA's nameLab Day and Time SectionType day &amp; time Type section numberDocumentationList references here (Lab Partners, Lab Manual, Textbook, etc.)Grading RubricPossible Point
UNC - CHEM - 101L
Experiment 6 SpectroscopyLaboratory Goals To understand the relationships between wavelength, frequency, and energy of electromagnetic radiation To measure the energies of the photons emitted or absorbed by gases To use this spectral information to dete
University of Florida - SYG - SYG 2000
Social Class and Stratification Chapter 71. What is Social Stratification? 1. Social Stratification is the hierarchical arrangement of large social groups basedon their control over basic resources.2. Life Chances (Max Weber) extent to which individual
Keller Graduate School of Management - FINANCE - 100
The answers are highlighted in yellow Which of the following statements is correct?(Points: 10) One way to increase EVA is to achieve the same level of operating income but with more investorsupplied capital. If a firm reports positive net income, its EV
AIU Online - MATH - 133
Name:Lawanda Henderson the graph to enlarge it if it will make it easier for you to read. A MTH133 Unit 1 &amp; 2 Individual ProjectAName:1) Thefollowinggraphshowsthedepreciationforthecorporateairplanefrom2006to2009. Theplanewaspurchasednewin2006;therefore
LSU - SOCL - 2025
OUTLINES FOR BIOLOGY 1201 Section 002 Fall 2008 DR. STEVEN POMARICO 1DCHAPTER 4 CARBON AND THE MOLECULAR DIVERSITY OF LIFE Carbon Chemistry and Isomers 4.1.1 &gt;Aside from water, most biologically related molecules contain carbon. Organic chemistry is the
LSU - SOCL - 2025
Chapter 2: Outline Culture(material and nonmaterial aspects)Nonmaterial Normative Component (norms) Folkways Mores Cognitive components Knowledge Beliefs ValuesIdeal vs. Real culture Subcultures &amp; countercultures Global Culture Cultural Relativi
LSU - SOCL - 2025
Socialization: Outline Social Class socialization The Life Course Parents social class Sex vs. gender Gender and the Family Gender and Peer Groups Gender and Mass Media The family School Peer groups Mass mediaGender SocializationChildhood Adolesce
LSU - SOCL - 2025
Macrosociology Society Socialstructure StatusesandRoles Groups SocialsolidarityMicrosociology Dramaturgy Impression Socialinteraction PersonalSpacemanagement SavingFace SocialConstructionof Reality Macrosociologyanalysisofsociallifethatfocusesonbr
LSU - SOCL - 2025
Ch5:SocietiesandSocial NetworksSocial GroupsAggregates andSocial NetworksReference groups Dyads and Triads Group LeadersInstrumental and expressive leaders Authoritarian, democratic and laissez-faire leadersCategories Primary and Secondary groups In
LSU - SOCL - 2025
Chapter 1: Outline What is Sociology? The History of Sociology The Sociological Imagination Social Structures Three Revolutions Early Thinkers Micro Macro GlobalAugust Comte Karl Marx Max Weber Emile DurkheimTheoretical Perspectives Symbolic I
LSU - SOCL - 2025
Ch 3 Socialization OutlineSocializationhThe Functions of Socialization Nurture vs. Nature Cooley and the Looking Glass Self Mead and Role Taking3The Impact of BiologyhTheories about socialization:h hstages in the process of learningSocialization
LSU - SOCL - 2025
Ch6Deviance:Outline Ch6Deviance:Outline WhatisDeviance? WhatisCrime? SocialControl Competing SymbolicInteractionismExplanationsof Deviance Biological Psychological Sociological Functionalism Differential Association ControlTheory LabelingTheory 3mai
LSU - SOCL - 2025
Conflict TheoryTakes the perspective that deviance is a reflection or social inequality Links Deviance to Power in 3 ways:Norms reflect the interests of the powerful Those with power can resist a deviant label Laws may be unequalDeviance and Capitalism
LSU - SOCL - 2025
Social StratificationWhat do you think?Howextensiveisthegapbetweentherichandthe poorintheUnitedStates? Whatdifferencesdopovertyandwealthmakefor peopleslives?Forms of Social StratificationSlavery CasteSystem SocialClass GenderGlobal StratificationMos
LSU - SOCL - 2025
Regional Cultures of ViolenceCultural Deviance TheorySubculture- A segment of society that shares a distinctive pattern of norms and values that differ from the pattern of the larger society. Cultural transmission-(sub) cultural values are handed down f
American College of Gastroenterology - BIO - Bio311c
Phylum: Echindermata echinoderms (spiny-skin); sea stars, sea urchins, sea cucumbers, sea lilies A. All marine (poor osmoregulators), 6,000 or so extant species B. Deuterostomous, enterocoelous, triploblastic, eucoelomate C. Secondarily evolved radial sym
N.C. State - E - E115
N.C. State - E - E101
WILL NANCE 111 Friendly Drive Raleigh, NC 27605 919.555.88881 wbnance@ncsu.edu OBJECTIVE A summer internship where I can understand the daily tasks a civil engineer faces. EDUCATION North Carolina State University, Raleigh, NC College of Civil Engineering
N.C. State - E - E115
E115 Homework 2 Will Nance Section 028 1. Twisted pair cable Coaxial Cable 2. Coaxial Cable 3. The IEEE 802.11 group 4. Up to the speed of light 5. Switch 6. Switches deliver information that they are given to specific paths, routers can determine what pa
N.C. State - E - E115
Name Will Nance H omework 4 :Fall 2009Unity ID:wbnanceAFS Commands ContinuedUNIX CommandsFor this section you will need to log into your terminal as well as write the answers in the space provided. 1. Make a new directory called Homework4 in your home
N.C. State - E - E115
-Class 5Computer Hardware Summer 2009 This week in class you will be taking apart some very basic computers. We will be discussing what each major part of a computer does, so be sure to pay attention! 1. How many bits are in a byte? 8 2. In a plain ASCII
N.C. State - E - E115
Homework7 CompanyName CosttoRun(Monthly) TotalRevenue(Monthly) Popularity StreetSprinter $1,000 $1,200 Dull $5,000 $5,600 IAMM $2,200 $3,000 Blackkit $900 $1,800 Macrohard $3,500 $3,000 5040 5 2360 Profitability InvestmentAmount 400 2000 880 360 1400 1008
N.C. State - E - E115
UNIX Fall 2009 Commands I n-Class 4 The following questions will test intermediate knowledge of the *NIX terminal. 1. Write the command that would create a shortcut to the E115 course locker. eos% attach e115 2. After doing so, what would be the new pathn