Preparing to Earn the "Certified for
Effective March 31, 2013, the Windows Server 2008 R2 Logo Program will no longer be accepting submissions. Windows Server 2012 is the preferred platform for current Application Development Competencies and Certified for Windows Server Logo.
The "Certified for" and "Works with" programs require applications to be tested on Windows Server 2008 R2 in a Hyper-V environment.
The baseline for all Logo testing will be Windows Server 2008 R2 SP1:
The “Certified for Windows Server 2008 R2” logo designates applications that are independently tested to meet Microsoft-recommended standards for security, stability, availability, reliability and compatibility with the platform.
Test your application on the latest version of Windows Server 2008 R2 to verify compatibility with your applications. Download the latest build of Windows Server 2008 R2.
Download documents and tools:
Technical requirements of a server application and its client components must meet in order to be Certified for Windows Server 2008 R2.
Participate in the growing community that's developing applications on the new platform.
Correspond with the Windows Server 2008 R2 technical team to address technical issues.
Included in the Software Certification Toolkit is the same test framework and tool that the third-party test vendors will be using for final certification. You now have the ability to run the certification in-house prior to submitting the application to a test vendor for certification.
A high degree of automation built into the tool significantly reduces the time and resources required of your internal development team to run the tests.
Note: For self-testing purposes, you may either use the x86 version or x64 version of the Certification Tool. The x64 version of the Certification Tool will be used by the authorized test vendor during actual certification testing. Both 32-bit and 64-bit applications will be tested on 64-bit Windows Server 2008 R2 and 64-bit Windows 7 Ultimate operating system editions. For more details on the test environment and machine configuration, please see the Setup tab in the Certification Tool or the Windows Server 2008 R2 Software Test Framework document.
This document is ideal for technical managers and testers who are preparing software applications for qualification under the Windows Software Certification Program. The framework describes tests that verify an application's compliance with requirements. This document is also embedded into the Certification Tool (both x64 and x86 versions).
LoadGen is included with the Software Certification Toolkit and is a required tool for executing stress tests and long term reliability tests in the Certified for Windows Server 2008 R2 Logo Program.
Microsoft may occasionally grant limited waivers for specific test requirements on a case-by-case basis. Independent software vendors seeking waivers must justify the need for a waiver, document the application's behavior and impact on users, and agree to publish the information conspicuously for customers prior to installation. Microsoft reserves the right to publish waiver documentation for customers seeking information on certified software.
For minimal resource investment (between US$1,500 and US$3,000) you can outsource pretesting for Certified for Windows Server 2008 R2.
We recommend you take advantage of this service early in the application development cycle. Pretesting identifies common development challenges to meeting the Certified for Windows Server 2008 R2 requirements. The sooner these challenges are identified, the sooner they can be addressed at a lower development and test cost.
All SysDev accounts (formally Winqual) require a VeriSign Digital ID. A VeriSign Organizational Certificate allows Microsoft to identify your organization on the SysDev site. A VeriSign Microsoft Authenticode Code Signing Certificate identifies your organization and additionally allows you to sign executable files, drivers, and installation packages.
Use this tool to generate a Microsoft-recognized signature that uniquely identifies your application. This signature is required to complete the submission process on the SysDev site.
Use SysDev, the Windows Dev Center Hardware and Desktop Dashboard site to start the submission process and complete the steps for obtaining the Certified for Windows Server 2008 R2 qualification.
Sign in to the SysDev site and create a new Certified for Windows Server 2008 R2 submission package using your SysDev account.
Your company may already have a SysDev account. If so, check with your SysDev account administrator for your company's SysDev access credentials.
If you do not currently have a SysDev account, you will need to create one before starting the submission process. This requires a VeriSign Organizational Certificate (US$99) which allows Microsoft to identify your organization on the SysDev site. If your organization needs to sign executable files, device drivers, and kernel mode drivers, you should instead consider the VeriSign Microsoft Authenticode Code Signing Certificate available for US$399.
Please visit the SysDev site for the latest promotions and information about certificates.
This validation ensures that only you can communicate information about your products to Microsoft. It also ensures that the right information about your application is received. This allows Microsoft to share your application's certification status with Windows Server 2008 R2 customers.
All application drivers must pass Windows Hardware Certification testing (formally WHQL and Unclassified category) and be signed by Microsoft for R2 platform. From the Hardware Dashboard, you will then receive a Submission ID, which is required for Certified for Windows Server 2008 R2. Driver Signing Guidelines for ISVs.
Engage the authorized test vendor of your choice to receive instructions on how to submit your application for testing. You will receive documentation after completing the Certified for Windows Server 2008 R2 submission process on the SysDev site. This documentation is required by the authorized test vendors.
Note: Applications may be submitted in any language. However, the testing process and communication with the authorized test vendor may be conducted in English only.