http://msdn.microsoft.com/en-us/windows/dd203105.aspx
The new Windows 7 logo requirements are based on extensive analysis of error reports, input from domain experts and feedback from Microsoft’s OEM , ISV and IHV partners on the challenges they and their customers face. The logo toolkit targets specific, commonly identified application issues to help partners deliver a product that is compatible and reliable on Windows 7. Once in market, access to Windows built-in error reporting enables partners to monitor issues being experienced by their customers and respond pro-actively to improve their product.
Regardless of whether Canonical formally submits Ubuntu One to the Windows 7 Software Logo program, a QA pass should be made through the logo program requirements, including running the test toolkits against Ubuntu One and filing bugs for everything that does not comply. Where the non-compliance is caused by upstream software (Tomboy, Banshee) detailed bugs should be filed upstream along with information about how to reproduce and suggestions for how to fix the bug.
Not only your software, but also your setup must meet the Logo requirements. The Logo program captures your installation
If you use Wix's smoke.exe validation tool you will have the ICEs (Internal Consistency Evaluators) from the darice.cub file, which includes logo.cub (=logo requirements) that will check for that stuff.
Other way is to use Orca.exe, somewhere in the menu you will find a "Validate...".
For CLI fans there is also msival2.exe from the Windows (Installer) SDK (Tools)