|
This newsletter contains archived content. No warranty is made as to technical accuracy of content or currency of URLs.
The Windows Logo Program Newsletter provides up to date information about Winlogo hardware testing issues/submissions and the Windows Logo Program. Did you get this newsletter from a friend? Subscribe to the Windows Logo Program Newsletter.
Top Story
Windows Server 2008 Logo for Printing and Imaging Devices
Partners interested in certifying their devices for the Windows Server 2008 Logo may now do so. The Windows Server 2008 Logo provides similar testing to that of our current Windows Vista Basic Logo program, but exposes drivers to the rigors of running in a Windows Server environment. Any Windows Vista Premium Logo features implemented on the device or device driver will also be tested in this environment.
Logo testing for Windows Vista and Windows Server 2008 are separate DTM test runs. The logo requirements, the tests, minimum system requirements for the operating system, and minimum capabilities of the system used for testing devices for the Windows Vista and Windows Server 2008 Logos are different. The generated submission package from a DTM test run is specific to an operating system.
If a completed Winqual Submission Tool submission package includes more than one operating system, each operating system must contain passing results; otherwise, the entire WST submission package will fail Winqual validation.
Windows Server 2008 Printing and Imaging Test Release Notes
When testing for logo submission, please ensure you implement the following release notes.
Issue: Printing kit requires additional setup for Windows Server 2008 testing.
DEVFUND-0017 -- Server Device functions properly before, during, and after a Microsoft Terminal Services session -- Added Server to the beginning of the title
DEVFUND-0009 -- Client device functions properly before, during, and after fast user switching or a Microsoft Terminal Services session -- Added Client to the beginning of the title
Storage-0005 -- Devices that implement the NV-Cache command set support industry Microsoft standards -- Changed; Random 1MB block write scenario throughput : 16 MBs to 10MB/s; Boot/resume scenario, 512 byte read IO latency requirement : 1 second to 3 seconds
Imaging-0004 -- Network-connected device implements Windows network connected Web Services for Devices (WSD) properly for their device type -- Clarified what MultiFunctionPrinters and Scanners need to support under this requirement
Imaging-0038 -- Scanning device sends device status messages correctly -- Added references to the Design Notes
Imaging-0040 -- Driver supports TWAIN 1.7 if TWAIN support is implemented -- Retired this requirement
Connect-0096 -- Devices which support Bluetooth must implement the Bluetooth 2.1 requirements -- Updated effective date to June 01, 2009
DEVFUND-0014 -- Device drivers support x64 versions of Windows -- Additional clarifications added to the requirement regarding the implementation, based on partner feedback. Exemption clause for Windows Server 2008 added. Clarified IA-64 exception.)
Description: Due to the default configuration of Windows Server 2008, many components needed for the Print kit are not available unless installed.
Workaround: The Printing kit must be run with the following configuration:
• Use Windows Server 2008 Datacenter Edition
• Network discovery must be turned on in the firewall if testing a WSD Device
• Add Print Services server role via Server Manager
• Add Microsoft .NET Framework 3.0 server feature via Server Manager
• Add Desktop Experience server feature via Server Manager before creating a Scanner submission
Windows Logo Program Requirement Update
The Windows Logo Program would like to inform partners of the following requirement updates
The following are new requirements and policies being proposed. Please provide any feedback through LogoPoint on these new requirements by March 18, 2008.
Input-0039 -- Keyboards reflect user selected language and layout at login screens
Input-0041 -- The Windows key remains visible to the user
Input-0044 -- Non-Mechanical input devices support Selective Suspend
Busport-0027 -- 1394b host controllers must provide at least one customer accessible nine pin 'bilingual' port
Connect-0028 -- 1394 devices must pass all required 1394 Trade Association compliance tests
Connect-0093 -- USB device is USB IF certified
Connect-0102 -- USB Host Controller needs to be USB IF certified
Connect-0103 -- 1394 host controllers must pass all required 1394 Trade Association compliance tests
Imaging-0042 -- Print drivers support Driver Sandboxing
Imaging-0043 -- Printer driver components run with Data Execution Protection enabled and with User Account Control enabled as a non administrative user
Imaging-0045 -- Printer, Scanner, Fax, and MFP driver components include an authored device metadata document
Imaging-0046 -- Enterprise Scan Devices implement Enterprise Scan protocols correctly
Imaging-0047 -- Print driver support Driver Side by Side
Imaging-0048 -- Network attached Printers, Scanners, and MFPs implement the Windows Rally Technologies
Connect-0109 -- Attached USB devices must be functional after resuming from system power states
Connect-0110 -- Wireless Host Controller Interface (WHCI), Host Wire Adapters (HWAs), and Device Wire Adapters (DWAs) must work without any additional non Microsoft software
Connect-0114 -- Devices making use of Web Services for Devices (WSD) comply with Device Profiles for Web Services (DPWS) specification
Connect-0116 -- Devices making use of Web Services for Devices (WSD) implement WS-Discovery
Connect-0117 -- Devices making use of Web Services for Devices (WSD) support metadata exchange
Connect-0118 -- Devices making use of Web Services for Devices (WSD) populate metadata required by Microsoft
Input-0045 -- IR Receiver/Transceiver interfaces with the Windows Media Center class driver (Future Requirement)
Systems without TPM chips fails BitLocker Drive Encryption BIOS Interface Logo Test
A known issue has been found in the WLK 1.1 System test titled "BitLocker Drive Encryption BIOS Interface Logo Test;" it intermittently fails on machines without TPMs. If your platform does not have a TPM and the test fails, Microsoft will manually pass the test after confirming your platform does not have a TPM. Please be sure to include DTM Errata ID 779 in your readme.doc file.
|
