A reference for Designing Servers and Peripherals for the Microsoft® Windows® 2000 Server Family of Operating Systems Intel Corporation and Microsoft Corporation Publication Date—June 30, 2000
Manageability Baseline Requirements
Download 1.64 Mb.
|
- Navigate this page:
- General Manageability Baseline Requirements
- 228. Expansion devices can be remotely managed
- Manageability Component Instrumentation Requirements
- 229. System supports Windows Hardware Instrumentation Implementation Guidelines
- 230.1. IA-64 system uses Machine Check Architecture for error reporting and logging
- 230.2. IA-64 firmware implements support for Machine Check Architecture
- 230.3. IA-64 Machine Check Architecture supports code resources
- 231. IA-64 system supports event logging for critical events
Manageability Baseline RequirementsThis section presents server requirements related to the Wired for Management (WfM) initiative and the Zero Administration initiative for Windows. The WfM initiative seeks to raise the level of management capabilities on mobile, desktop, and server platforms. The Zero Administration initiative seeks to ensure a controlled, highly manageable enterprise. The baseline for these requirements is WHIIG 1.0, which also defines the Windows 2000-specific requirements of the WfM 2.0 specification for hardware instrumentation. Collectively, the items in this section represent the “Manageability Baseline” requirements.
General Manageability Baseline RequirementsThis section defines requirements related to centralized control and configurability and BIOS support for system manageability. 227. Remote new system setup and service boot support use DHCP and TFTPRecommended The complete mechanism for remote new system setup is defined in PXE 2.1 or later. If remote new system setup capabilities are implemented, there must be a way for this capability to be enabled or disabled by way of administrative control to maintain server security. See also the requirement for the preboot execution environment in guideline “#13. IA-32 BIOS boot system supports remote/network boot, USB boot devices, and firmware update,” and guideline “#14 IA-64 system complies with EFI 1.0 or later, with support for USB boot devices, firmware update, and PXE_BC, SERIAL_IO, and SIMPLE_NETWORK protocols.” 228. Expansion devices can be remotely managedRecommended Devices provided as expansion devices should be capable of being remotely managed, ensuring that control and TCO policies can be realized. The requirements for remote management capabilities are defined in “Manageability Component Instrumentation Requirements” later in this chapter. For example, for any implementation of a floppy drive, the floppy drive should be capable of being remotely disabled as a boot selection and should be able to be locked. Certain devices are not required to have remote disabling capabilities, including the primary hard disk drive, the network adapter, and any standard devices that use legacy connections, such as a keyboard or pointing device that uses a PS/2 connection. However, it must be possible to use permissions, policies, or other methods to remotely manage capabilities such as hard disk access or to control certain users’ ability to change the MAC address or configuration settings for the network adapter. If implemented, there must be a way to enable and disable this capability by way of administrative control to maintain server security. See also the requirement for the firmware to ensure secure preboot access to hardware components in guideline “#12. System firmware meets general boot support requirements.” Manageability Component Instrumentation RequirementsPlatform management information requirements are defined for two key areas:
229. System supports Windows Hardware Instrumentation Implementation GuidelinesRequired These guidelines are defined in WHIIG 1.0. 230. IA-64 hardware and firmware support IA-64 Machine Check ArchitectureRequired Many features of 64-bit Windows depend on platform support for IA-64 Machine Check Architecture. IA-64 systems must implement hardware and firmware that support IA-64 Machine Check Architecture. 230.1. IA-64 system uses Machine Check Architecture for error reporting and loggingThe IA-64 Machine Check Architecture has a complete method for reporting processor errors and many system errors. System designers must use the Machine Check Architecture for system-wide error reporting and logging. The Machine Check Architecture must be used to report platform errors, including errors within the system processors, memory, internal buses, and expansion buses. Note: Certain established interfaces, such as TCP/IP in the networking space and SCSI in the storage space, have extensive error reporting and recovery mechanisms in their protocol stacks. Some interfaces (for example, serial ports, LPC, and so on) may have limited or no hardware support for reporting errors. Subsystems such as this are excluded from this requirement. 230.2. IA-64 firmware implements support for Machine Check ArchitectureIA-64 system firmware must implement the IA-64 Machine Check Architecture. Using Machine Check Architecture, every firmware layer in the system may check for recoverable errors and log errors, and perform error recovery where possible. All machine check recovery code must use Machine Check Architecture firmware hooks. Discontinue use of Platform Management Interrupt (PMI) for doing machine check and recovery. 230.3. IA-64 Machine Check Architecture supports code resourcesAll IA-64 Machine Check recovery code must use Machine Check Architecture firmware hooks as specified in SAL 2.7 or later. Platform machine check hardware must provide relevant status bits for all sources of hardware errors that need to be handled in Machine Check Abort code. Discontinue use of PMI and NMI for performing machine check and error recovery. 231. IA-64 system supports event logging for critical eventsRequired The hardware, SAL, and firmware on IA-64 systems must provide the capability to log all critical events. It is required that an event log be made available that can be accessed by management software. Appendix A
This appendix summarizes all the requirements listed for server systems in this guide. If a recommended feature is implemented, it must meet the requirements defined in this guide for that feature. Directory: download download -> Performance Tuning Guidelines for Windows Server 2008 May 20, 2009 Abstract download -> Northern England’s set-jetting locations download -> Bbc archives: Beyond the programme download download -> Occupational health and safety download -> Dynatest 3031 lwd light Weight Deflectometer download -> Forth coming competitive exams download -> English Olympiad Tasks: 10 th form Аудіювання, 10 клас. Текст download -> Brush High School Morning Announcements Friday, September 05, 2014 all school download -> Year 9 The Arts — Music download -> Years 7 and 8 standard elaborations — Australian Curriculum: Music draft Download 1.64 Mb. Share with your friends:
|