Windows Server Certification and Application Compatibility

  • Getting Started with Microsoft Hyper-V

    Introduction

    Windows Server 2008 Hyper-V is the next-generation hypervisor-based server virtualization technology that allows you to make the best use of your server hardware investments by consolidating multiple server roles as separate virtual machines (VMs) running on a single physical machine. With Hyper-V, you can also efficiently run multiple different operating systems in parallel, on a single server, and fully leverage the power of x64 computing. A feature-complete version is now available for download as a release candidate (RC). You can download the RC update for Hyper-V here to learn more about Microsoft and virtualization; please visit the Virtualization Web site, or the Virtualization TechCenter. To be eligible in the Windows Server 2008 Logo program for the Hyper-V designation, tests must be conducted on the latest available version of Hyper-V.

    Hardware requirements

    Hyper-V requires an x64-based processor, hardware-assisted virtualization, and hardware data execution protection. The Windows Server catalog, which can be found at the Microsoft Web site (Windows Server Catalog), lists systems that are certified for Windows Server 2008. Systems supporting the x64 architecture and supporting Hyper-V can be identified by the additional qualifier under the text “Certified for Windows”.

    NoteWeb Note:
    If you try to boot the hypervisor on an Intel VT-enabled machine with Execute Disable Bit disabled in the BIOS, the hypervisor does not boot. The issue is recorded in the System Event log as:
    • Hypervisor launch failed; at least one of the processors in the system does not appear to support the features required by the hypervisor”

    To fix this issue, enable the following Bios settings:

    1. Assure Hardware virtualization assist in enabled
    2. Assure DEP is turned on. Also known as NX or XD
    3. Power off the machine and then restart (just a reboot is not sufficient)

    Install Hyper-V

    You can install Hyper-V on either a Full Windows Server 2008 installation or a Server Core installation. You can use Server Manager to install Hyper-V on a full installation, as described in the following procedure.

    Install Hyper-V on a full installation of Windows Server 2008
    1. Click Start, and then click Server Manager
    2. In the Roles Summary area of the Server Manager main window, click Add Roles
    3. On the Select Server Roles page, click Hyper-V
    4. On the Create Virtual Networks page, click one or more network adapters if you want to make their network connection available to virtual machines
    5. On the Confirm Installation Selections page, click Install
    6. The computer must be restarted to complete the installation. Click Close to finish the wizard, and then click Yes to restart the computer
    7. After you restart the computer, log on with the same account you used to install the role. After the Resume Configuration Wizard completes the installation, click Close to finish the wizard
    Install Hyper-V on a Server Core installation of Windows Server 2008

    To install on a Server Core installation, you must perform the installation from a command prompt by running the following command:

    Start /w ocsetup Microsoft-Hyper-V

     NoteWeb Note:
    To manage Hyper-V on a Server Core installation, you can use the Hyper-V management tools to manage the server remotely. The management tools are available for Windows Server 2008 and Windows Vista Service Pack 1. For more information on Hypervisor updates, see article 949219 (Hyper-V updates for Windows Server_2008) and for more information on Hyper-V Management Tools, see article 949758 (Windows Vista Service Pack 1 management tools for Hyper-V) in the Microsoft Knowledge Base.

    Create and set up a virtual machine

    After you have installed Hyper-V, you can create a virtual machine and set up an operating system on the virtual machine.

    Before you create the virtual machine, you may find it helpful to consider the following questions. You can provide answers to the questions when you use the New Virtual Machine Wizard to create the virtual machine.

    • Is the installation media available for the operating system you want to install on the virtual machine? You can use physical media, a remote image server, or an .ISO file. The method you want to use determines how you should configure the virtual machine
    • How much memory will you allocate to the virtual machine?
    • Where do you want to store the virtual machine and what do you want to name it?
    Create and set up a virtual machine
    1. Open Hyper-V Manager. Click Start, point to Administrative Tools, and then click Hyper-V Manager
    2. From the Action pane, click New, and then click Virtual Machine
    3. From the New Virtual Machine Wizard, click Next
    4. On the Specify Name and Location page, specify what you want to name the virtual machine and where you want to store it
    5. On the Memory page, specify enough memory to run the guest operating system you want to use on the virtual machine
    6. On the Networking page, connect the network adapter to an existing virtual network if you want to establish network connectivity at this point
     NoteWeb Note:
    If you want to use a remote image server to install an operating system on your test virtual machine, select the external network.
    1. On the Connect Virtual Hard Disk page, specify a name, location, and size to create a virtual hard disk so you can install an operating system on it.
    2. On the Installation Options page, choose the method you want to use to install the operating system:
      • Install an operating system from a boot CD/DVD-ROM. You can use either physical media or an image file (.iso file)
      • Install an operating system from a boot floppy disk
      • Install an operating system from a network-based installation server. To use this option, you must configure the virtual machine with a network adapter connected to the same network as the image server
    3. Click Finish.
    Install the operating system and integration services

    In the final step of this process, you connect to the virtual machine to set up the operating system. As part of the setup, you install a software package that improves integration between the virtualization server and the virtual machine.

     NoteWeb Note:
    The instructions in this step assume that you specified the location of the installation media when you created the virtual machine. The instructions also assume that you are installing an operating system for which integration services are available.
    To install the Operating System and Integration Services
    1. From the Virtual Machines section of the results pane, right-click the name of the virtual machine you created in step 2 and click Connect. The Virtual Machine Connection tool will open
    2. From the Action menu in the Virtual Machine Connection window, click Start
    3. Proceed through the OS installation
     NoteWeb Note:
    • When you are at the point where you need to provide input to complete the process, move the mouse cursor over the image of the setup window. After the mouse pointer changes to a small dot, click anywhere in the virtual machine window. This action "captures" the mouse so that keyboard and mouse input is sent to the virtual machine. To return the input to the physical computer, press “Ctrl+Alt+Left Arrow” and then move the mouse pointer outside of the virtual machine window
    • To install the latest version of the Integration Services for x86 & x64-based versions of Windows Server 2008, you must install this package in the virtual machine and on computers that are running the x86 or x64-based version of Windows Server 2008
    • To install the latest version of the Integration Services for Windows Server 2003, for Windows Vista SP1, and for Windows XP SP3, click Insert Integration Services Setup Disk on the Action menu in the Virtual Machine Connection dialog box

    Network Access for VM

    You can configure networking for virtual machines by adding, removing, and modifying their network adapters as necessary. Each network adapter can be connected to one of the virtual networks available on your virtualization server. Virtual Network Manager enables you to add, remove, modify, and manage virtual networks. The Virtual Network Manager is available from Hyper-V™ Manager.

    To create a virtual Network connection
    1. Open Hyper-V Manager. Click Start, point to Administrative Tools, and then click Hyper-V Manager.
    2. From the Action pane, click New, and then click Virtual Machine.
    3. From the Create Virtual Network pane, select External and then click on Add
    4. In the next screen, enter the Name of your new virtual network
    5. Under Connection Type, select External: and select the desired network adapter from the drop down list
    6. Click on Apply and then OK to close the window
    7. From the Virtual Machines list in Hyper-V Manager, select the Virtual Machine you wish to add a Virtual network Connection to
    8. Right click the virtual machine and select Settings
    9. Select Add Hardware from the hardware list in the right pane
    10. Select Legacy Network Adapter in the Devices list in the right pane and click on Add
    11. From the Legacy Network Adapter screen, select the Network you created earlier from the drop down list
    12. Click on Apply and then OK to add the Virtual Network Connection to the virtual machine

    Working with Snapshots and Saved States

    A Snapshot is a point in time of the state of the running or non-running VM that you can revert to anytime. They consist of a memory save state file, a Difference disk (.avhd), and a copy of the VM configuration xml file. When you revert to a snapshot, you are loading that configuration, that memory state, and using that Diff disk.

    To Create a Snapshot

    Right-click on the Virtual Machine name in Hyper-V Manager, and choose 'Snapshot'. You can do this when the VM is still running, or when the VM is turned off. You can also do this on a brand new VM that has never been started before.

     NoteWeb Note:
    Snapshots are very convenient and useful, but they have a performance cost; if you exceed the snapshot depth to more than three, then you may experience performance degradation depending on the resources available and allocated.
    Applying a Snapshot

    When you apply a snapshot, you are reverting to the state of the VM at that point in time, including the VM configuration at that time (such as total RAM, total cores, etc).

    NoteWeb Note:                                                                                                                                            Applying a snapshot can mean data loss. When you apply a snapshot you are prompted with if you'd like to Take Snapshot Then Apply?
    • If you ignore this and just Apply, you will forever lose the current system state
    • If you choose to Take Snapshot Then Apply, your current system state will be saved
    Deleting a Snapshot
    • When you delete a snapshot, you are saying that you do not want to revert back to that point in time again.
    • You can delete a snapshot at any time (i.e. guest can be running or turned off)
    • Data loss may occur when deleting a snapshot in the sense that you will lose the system state for that snapshot and the ability to revert to that VM state in time.
    Saved State

    A Saved State is a point in time of the state of a running VM, much like a snapshot; however, a Saved State can only be performed on a running VM and it can only be restored ounce, provided that no other snapshot has been applied since the System State has been saved.

    To create a Saved State, right-click on the name of a running Virtual Machine in Hyper-V Manager, and choose Save. This will save the system sate and the VM will appear to be shutdown. To resume from a saved state right-click on the name of the saved Virtual Machine in Hyper-V Manager and choose Start.

     NoteWeb Note:
    Applying a snapshot can mean data loss. If you apply a snapshot after you have saved a system state; Any data and/or system changes specific to the Saved State, will be lost.

    Written By:

    Scott Lanphear

    Posted Wednesday, June 18, 2008 6:21 PM by Logoteam | 3 Comments

  • Welcome to the Works with Tool for Windows Server 2008 R2

    You will use the Works with Tool to:

    • Test your application and earn the Works with Windows Server 2008 R2 Logo.
    • Test internal line-of-business and mission-critical applications for compatibility
    • Test third party software prior to platform adoption, purchase, or consideration
    • Milestone testing during development cycle
    • Partner Program tests

    Works with Tool is:

    • Completely a Wizard based tool. No learning curve.
    • Testing can be run on a virtual machine, a physical box or through remote access.
    • Test Server and Client components for compliance and compatibility in under 2 to 4 hours.
    • View comprehensive report and logs at any time during and after testing.

    Server and Client components can be tested with the Works with Tool on x64 versions of:

    • Windows Server 2008 R2 Enterprise
    • Windows Server 2008 Enterprise
    • Windows 7
    • Vista Ultimate or Enterprise

    Install all application prerequisites, prior to testing:

    • Applications
    • .NET
    • IIS
    • Devices and Storage depots
    • Server Features and Roles
    • etc.

    The current Works with Tool is installed with the Software Certification Toolkit from the Works with Windows Server landing page, where you can:

    • Download the Works with Specifications
    • Download the Works with Test Framework
    • Learn about Windows Server 2008 R2 and how to get started in the Logo Program
    • Learn about other free tools and resources to use during your development cycle

     

    Ready to begin testing

    Follow the simple guides of the Wizard to name your Server or Client component. Click the appropriate component type radio button. Click Next. Etc.

    Note any yellow highlighted textboxes throughout wizard with important information regarding requirements in other logo programs.

    The Works with Tool has many uses and may show configuration status as a failure on the Prerequisite screen. Depending on level of testing being performed, the tool will allow you to continue test and ignore error warnings.

    Focus of the following is the Works with Windows Server 2008 R2 Logo Program, and how to interpret your results.

    When submitting an application for Windows Server 2008 R2 Logo, the Prerequisite screen must show all status as green, unless otherwise noted in yellow textbox.

    Assure that the following status show as passing or are enabled for Windows Server 2008 R2:

    • 64-bit Windows Server 2008 R2 or Windows 7
    • Virtual Machine Status must show “Microsoft Hyper-V R2”
    • Firewall
    • IPv6
    • Windows Error Reporting

    Note: If Windows Error Reporting is listed as Disabled, do not click Next. In Windows Taskbar, Start/Search, type services.msc and hit Enter. Click through any UAC to launch Services Manager. On Right pane, Name column, locate Windows Error Reporting Service, and double click. Change Startup type: to Automatic or Manual. Click OK to close, then close Services Manager. On Prerequisite screen, click the F5 link to refresh.

    Assure an Antivirus program is installed and running.

    The Works with Tool performs all testing in the background, including monitoring the above prerequisites.

    On Installer Information screen select either an MSI package, or setup executable. Alternately, if the application under test does not include an installer, you may select the appropriate radio button and include requested information.

    At any time during the following screens, you may click View Report link to see current testing status and logs.

    The tests performed are outlined in the Works with Windows Server 2008 R2 Test Framework.

    Important: To qualify for Works with Windows Server 2008 R2 Logo, the Works with Tool must be used.

    The Works with Tool will inform when to install, test, and uninstall the application. Rebooting may be necessary. The Works with Tool will allow you to resume a test at launch. Select this radio option, Select the proper test, and you will return to the last page prior to rebooting.

    Between steps the tool may take a snapshot of the system. This may take a up to 15 minutes depending on speed, capacity, and resources of the system.

    If your application contains drivers, you may be prompted to reboot to set up special driver testing during boot up and during primary functionality testing.

    Client components: If the application contains client components, assure the Server components are operational, then follow the above steps on another machine to test Client components using Works with Tool. If client components were designed to run on a Server, then another Server can be used, otherwise run client components on Windows 7 64-bit. The client components will be used to exercise the Server components. Note that testing on a virtual machine is optional for clients running on Windows 7.

    When testing is nearly complete, you will be presented with a series of quick, but important questions about the testing.

    When testing is complete, a quick report will launch presenting the results of the tests, and testing status achieved.

    If all tests show as a pass for the Logo Program desired, you will now create a Submission package which includes the test results from the Server components and any Client components from another machine. This can be created from the Finish screen or by launching the Works with Tool and selecting the Create Submission Package option.

    These test results may now be submitted to the test vendor.

     

    If submitting test results to a test vendor...

    If you are ready to submit your test results to a test vendor for independent validation:

    • Assure all tests are listed as Pass or documentation exists for each failure.
    • Establish a Winqual Account that identifies your company with the Windows Logo Program.
    • If the application contains drivers, then all Drivers must have passed separate WHQL testing as well. Please submit your WHQL Submission ID.
    • Provide Microsoft Pre-approved Waivers. (Only granted on a limited basis.)
    • Provide documentation for 3rd party file failures to test vendor. Include all failing 3rd party file names installed found by Works with Tool and file owners in publicly facing documentation. Waivers not required.
    • See the Works with page for details on above steps and on how to select a test vendor.

    When submission package has been validated by test vendor, you will be granted the use of the Works with Windows Server 2008 Logo artwork. See the Innovate On web site for benefits associated with each Logo Program.

     

    Interpreting the Logs from Works with Tool

    Since the Works with program is one of self testing, you will be interpreting the test logs generated.

    Help can be had on the dedicated MSDN Forum for Windows Server 2008 Application Compatibility and Certification issues. There you will find Windows experts, as well as a community of developers and Independent Software Vendors helping each other with the new operating system and Logo program requirements.

    Below are the most common issues encountered when attempting to interpret your own logs. Most are common to many of the test case logs, so they do not bear repeating for each log. The Works with Tool has built in intelligence to automatically remove noise from the logs and allowed failures.

     

    Interpreting log failures:

    3rd party files

    Definition: Any file not part of your build process, and not owned by your Product group or Company.

    If these files do not have signatures or valid file properties, these files will fail the test case, but will NOT block achieving Works with designation.

    Do not sign files that do not belong to your Product group or Company.

    Do not assign file properties to files that do not belong to your Product Group or Company.

    Document, no waiver required.

    Documentation must include all 3rd party file names and owners which appear as failing the test cases.

    Documentation must be publicly facing for the use and convenience of your Customers: ReadMe, FAQ, Product manual or webpage

    Documentation must be provided to test vendor upon submission.

     

    Temporary files

    Files in all temp folders that are expected to be deleted by Windows can be safely ignored.

    Temp folders:

    • Temp IIS, ASP, ASP.NET folders (transient files, or created on the fly, and expected to be deleted)
    • Temp .NET folders
    • Temp Java folders
    • Temp Windows Installer folders (example: x:\Windows\Installer, many icon files appear here as 16 bit executables.)

    Any temp files not automatically ignored by the Works with Tool may fail the test case, so must be documented as temporary files on which the application does not have a dependency. No waiver required.

     

    Interop files

    Interop files do not contain file properties, by design.

    This known by Microsoft, no documentation required, and ignored by the Works with Tool.

    If built and owned by Product group or Company, Interop files should be signed as a best practice, but will not fail the Works with test.

     

    Files using known binary extensions

    Some (text, log) files used by application using known binary extensions must document these extensions. (Example, .sys, .bat, .com, etc.)

    For instance, a text log file extension of .com may be improperly labeled a 16 bit binary.

     

    Internal Consistency Evaluators (ICE) Errors or Warnings in MSI packages

    ALL ICE Errors appearing on logs must be fixed.

    See ICE Error reference MSDN page for guidance on fixing.

    ICE Warnings do not require a fix. All Warnings should be investigated, and as a best practice, should be fixed.

    These are the ICE errors being validated in Works with Tool:

    • (ICE) 1-2, 4-7, 9-15, 17-24, 27-29, 31, 33-36, 38, 40-42, 44-56, 59, 61-63, 65, 67-71, 74-78, 81-84, 86-87, 89-94, 96-105 

     

    Package Identity

    Windows Installer packages must comply with ICE validation as well as identify installer package and properly prepare for upgrade.

    To Pass this test case the Property Table and the Upgrade Table must contain:

    Property Table:

    • Manufacturer
    • ProductCode
    • ProductLanguage
    • ProductName
    • ProductVersion (major and minor)

    Upgrade Table:

    • UpgradeCode
    • VersionMin   (Major.minor.build)
    • VersionMax  (Major.minor.build)

    The UpgradeCode in the Upgrade table must be identical to the UpgradeCode in the Property table.

    VersionMin and VersionMax: BOTH cannot be null. 

     

    Custom Actions

    Custom table starting with MSI : MsiSFCBypass or MsiDriverPackage

    • These can be safely ignored. No Waiver required. These are allowed MSI Prefixed Standard Tables.

     

    16 bit files found

    Some installer programs create an icon file with an .exe extension. These will be flagged as failures, and appear as 16 bit files to Work with Tool.

    If these are found in the C:\Windows\Installer directory or similar User redirected folder, these are considered to be installed into a temporary directory and will be automatically ignored by the Works with Tool.

    Be sure you do not own any files you list as 3rd party.

     

    No Installer, No Windows executables

    The Windows Server Logo Program will evaluate on a case by case basis any application which has no installer, and installs no Windows executables.

    The Logo Program requires a Waiver be filed for failure in the Works with 2008 R2 Report labeled: “Were any binaries installed for this Component?”

    The ISV must document:

      • All major components installed
      • Their interaction with specific hosted application(s) or Windows feature(s)
      • Any other prerequisite software installed and versions
      • Submit waiver to wslogofb@microsoft.com

    With no other failures in the Works with logs, there should not be any issues in achieving the Works with Logo.

    The Logo Program will review only complete waivers and respond with Microsoft approval to proceed with submission.

     

    Waivers

    As mentioned earlier, there will be very limited Waivers granted.

    Examples: Logo Tool errors, Windows limitation, or technical documentation exists why no other workaround existed for exemption (very limited).

    When Waiver is necessary, it must be sent to Microsoft for pre-approval, prior to sending submission package to test vendor. R2 Waiver document can be downloaded from Works with web site.

    Waivers are not required when only documentation is sufficient to detail test case issues as mentioned above.

     

    Hope the above is helpful,

    -PaulS

     

    Posted Wednesday, February 27, 2008 11:58 PM by Logoteam | 2 Comments

This Blog

Syndication

Tags

No tags have been created or used yet.

© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Microsoft
Page view tracker