Common Engineering Criteria for Products shipping in FY2005
(Foundation criteria) 
.NET Connected Logo ProgramTo ensure that businesses can connect with employees, customers, and partners using Web services, Windows Server System products will qualify for the .NET Connected logo. Microsoft has developed the .NET Connected logo program in an effort to help customers easily identify products designed to assist their creation of connected solutions. By choosing .NET Connected products, organizations gain the advantage of flexible, standardized ways to integrate systems and collaborate across the value chain from suppliers to customers. For more on the .NET Connected logo program, please see http://www.microsoft.com/net/logo/.
64-Bit Support
To give businesses the ability to take advantage of the improved price/performance of the 64-bit platform, all server products will support one or both of the following:
- Fully support 32-bit emulation on 64-bit architectures (Windows on Windows 64 [WOW 64]).
- Support X64 native execution in a 64-bit architecture. IA64 support is required for Windows Server and SQL Server only.
With this support built into Windows Server System, businesses gain the flexibility to upgrade to 64-bit hardware as desired. Businesses will be able to take advantage of 64-bit computers' larger address space and improved performance. The result: improved infrastructure productivity and greater value from their IT investment.
Support for Multicore Processor Technology and Licensing
Multicore processor technology provides increased computing power from each processor, allowing servers, workstations, and PCs to perform more functions simultaneously. All Windows Server System products will support multicore processor technology, enabling customers to take advantage of this increased computational power. Further, Windows Server System products that are currently licensed on a per-processor model will continue to be licensed per processor, not per core, for hardware that contains multicore processors. This criterion will enable customers to create additional business value by lowering the price/performance ratio of Windows Server System Solutions.
Core Training and Training Roadmap at Launch
To help organizations put their servers to work creating new business value sooner, all Windows Server System products will make core training available at launch, which generally includes deployment planning as well as basic operational training. Further, a training roadmap will be available at launch, and non-core training will be available 90 days after launch.
Adopt Secure Software Development Guidelines
To improve the security of Windows Server System products, all products will adopt Microsoft's Trustworthy Computing initiative practices. These practices fortify the development process to include security milestones at every phase of product development, resulting in products that are more secure by design, in development, and in deployment. Hot Patch Technology SupportMicrosoft continues to focus on reducing the number of restarts required when computers are patched. Windows Server System products support "hot patching" technology that can update server software components in place, without requiring a restart for some patches. Although not all fixes can benefit from hot patching, it will further reduce restart scenarios. With the hot patching technology, Microsoft expects customers to be able to install 30 percent of critical updates without restarting their computers. The support of hot patching technologies in all Windows Server System products will provide customers with a more reliable and secure platform to support uninterrupted business operations. Windows/Microsoft Update SupportAll Windows Server System products will provide updates in standardized packages, enabling customers to easily keep their IT environments current. - The package will follow consistent naming conventions.
-
The package will be digitally signed.
- Products must add an entry into the Control Panel Add/Remove Program.
- Symbols used for the software update must be archived.
- Microsoft Security Response Center security update policies must be followed.
Product Implemented in Production Prior to LaunchTo ensure the highest level of quality, all server products will be subject to demanding core scenario testing and implementation in production prior to the product's final release. Where applicable, server products will be implemented in production first within the Microsoft IT department, and then at a minimum of four customer sites prior to final release. These implementations will cover a core scenario to representative scale, and at least one implementation must be outside the United States of America. Windows Server 2003 Logo CertificationTo ensure that our server products take full and correct advantage of Windows features, all products will be Windows Logo Certified. Products with Enterprise Editions must obtain the Enterprise level of Certified for Windows Server 2003 certification. Customer Feedback LoopAll Windows Server System products will provide the capability to collect customer input to improve product quality. Each of the Windows Server System products must be enabled to capture and send crash analysis data to either a Corporate Reporting Server (CRS) or directly to Microsoft (user configurable during product installation and when enabling feature in product). Further, products must allow customers to rate the quality of the content and provide suggestions to improve our products. Products will enable customers to join product-related user communities from their management user interface. MOM 2005 Management Pack Support at LaunchTo help businesses reduce the cost of managing infrastructure, all server products will have a MOM Management Pack available at launch. The management pack will be serviced on the same schedule as the core product. MOM packs will provide: - Event and performance processing alerts.
- Basic views that graphically map performance and event trending information.
- State Monitoring view (green/yellow/red) state for managed entities.
- Tasks.
Scripting Support for OperationsTo lower the cost of installing and configuring products across an enterprise, Windows Server System products will support command-line scripting and/or be Windows Management Instrumentation (WMI)-enabled. This requirement enables administrators to automate and customize server deployment and operations, enhancing administrative efficiency. Virtual Server SupportTo help customers improve the utilization of hardware resources, all server products will support Microsoft Virtual Server 2005. Each product must be capable of running from within a virtual instance. Exemptions will be granted if: -
The operating system required for the product is not supported as guest virtual machine (VM) operating system.
- The product requires hardware that is not currently supported in the VM environment.
- Core product scenarios fail because of virtualization performance or scaling-related issues.
Standardized InstallerTo provide consistent product installation and Windows/Microsoft Update support, all Windows Server System products will use a standardized installer. In addition: -
The Windows Installer service must be used for installation and uninstallation.
- The MSI package must pass package validation without errors.
- All MSI custom actions must have compensating rollback and uninstall custom actions, where possible. Nonreversible actions, such as data conversion, should be clearly documented so that customers know to back up configuration changes that cannot be undone.
- Windows Installer 3.0 is not required but recommended for install.
- Windows Installer 3.0 must be used for an update (patch).
Product Upgrade Roadmap and GuidanceTo enable organizations to plan for product upgrades, product upgrade roadmaps and prescriptive guidance will be available for each Windows Server System product. Further, whenever possible, feature deprecation will be announced and staged over several product releases to minimize customer issues. Standardized Packaging and LicensingTo provide a consistent product experience, licensing for all products will be either CPU-based or Server/CAL/Connector-based. For products with more than one edition, a standard set of category names (for example, Express, Workgroup, Standard, and Enterprise) will be applied. |