• A2.1 Desktop Client - Windows Compatibility
  • A2.3.1 - See A2.4.7 A2.3.2 - See A2.4.8
  • A2.4.2 DELETED A2.4.3 - See A1.4.12
  • A2.4.6 Windows XP Professional/Windows Server 2003: Expansion devices on desktop systems can be remotely managed
  • A2.4.7 See A1.1.4.13 A2.4.8 See A1.1.4.13
  • A1.R General System - Future Requirements




    Download 0.7 Mb.
    bet40/188
    Sana21.03.2017
    Hajmi0.7 Mb.
    #429
    1   ...   36   37   38   39   40   41   42   43   ...   188

    A1.R General System - Future Requirements

    A1.R.1 Announcement of additional future requirements will be published on the Windows Logo Program web site

    http://www.microsoft.com/winlogo/hardware/
    A1.R.3 – See A1.4.3

    A2.0 Desktop Client Requirements


    This section describes additional requirements or exceptions to the requirements defined earlier in Section A1.0.

    For Itanium-based desktop systems, all requirements in A5.0 are included by reference.


    A2.1 Desktop Client - Windows Compatibility


    See A1.1.

    A2.2 Desktop Client - Industry Standards

    A2.2.1 USB specifications and other USB requirements

    As defined in Section B2.6 in Appendix B, "Device Requirements Checklist."

    A2.3 Desktop Client - Quality


    See A1.3.
    A2.3.1 - See A2.4.7
    A2.3.2 - See A2.4.8

    A2.4 Desktop Client - Windows Experience

    A2.4.1 USB ports in all systems, with system BIOS boot support for USB input devices

    See A1.1.4.13

    If only two USB ports are provided, system provides at least one accessible USB port supporting end-user expansion when keyboard and pointing device are attached.


    A2.4.2 DELETED
    A2.4.3 - See A1.4.12
    A2.4.4 DELETED
    A2.4.5 If IEEE 1394 is included in a system, externally-accessible sockets are required

    If implemented, IEEE 1394 must meet the requirements defined in B2.2. Notably, externally accessible IEEE 1394 sockets are required when external access is provided. Internal-only IEEE 1394 implementations are also allowed.
    A2.4.6 Windows XP Professional/Windows Server 2003: Expansion devices on desktop systems can be remotely managed

    Devices provided as expansion devices must be capable of being remotely managed so that control and Total Cost of Ownership (TCO) policies can be realized. For example, for any implementation of a floppy disk drive on a system, the drive must be capable of being remotely disabled as a boot selection and provisions must be made for locking.

    Certain devices are not required to be capable of being remotely disabled, including the primary HDD, the network adapter, and any standard devices that use legacy connections, such as a keyboard or pointing device that uses a PS/2-compatible connection. However, it must be possible that permissions, policies, or other methods can be used to remotely manage capabilities such as hard disk access or to control end-user ability to change the MAC address or configuration settings for the network adapter.


    A2.4.7 See A1.1.4.13
    A2.4.8 See A1.1.4.13


    Download 0.7 Mb.
    1   ...   36   37   38   39   40   41   42   43   ...   188




    Download 0.7 Mb.

    Bosh sahifa
    Aloqalar

        Bosh sahifa



    A1.R General System - Future Requirements

    Download 0.7 Mb.