Doctor Deploys Blog

In recent multi-blog conversations between Windows Installer experts Aaron Stebner, Christopher Painter, and Stefan Krueger, it was noted that my statement that ‘Windows Server 2008 logo would require Windows Installer’ in the Channel 9 video Application Compatibility - MSI Installer Issues was out of sync with the published requirements.

Sure enough, the Windows Server 2008 Logo team demoted this from a requirement to a recommendation.  Unfortunately the Windows Server 2008 Logo didn’t let me know they had decided to do this.  Still, the mistake is mine and I humbly apologize for this unfortunate misinformation.  I do sincerely appreciate the community Windows Installer experts efforts in catching and correcting my mistake. ;^)

Back Story
For the back story, I’ll start by observing the underlying conflict here is in picking the right point in the ubiquity/quality spectrum

• Weaken the quality requirements so that any ISV that is willing to pay the fee can get the brand on their box (optimize for the ubiquity of the logo)


• Strengthen the quality requirements so that any software consumer can use the presence of the brand as synonymous with excellence (optimize for the quality of the logo)

I’ll further observe that the Logo program a marketing program and not a standards program.  This means that the engineering experts are simply consultants to their requirements and test cases.  As a marketing program to ISVs, there is significant feedback to push toward the “make it easy” end of the spectrum.

As was pointed out in the insightful conversation among the Windows Installer experts, there is ubiquitous presence of Windows Installer in corporate environments and particular those that need leverage client software distribution tools.  Putting aside the recent virtualization trends for a bit, any corporate customer research will find very quickly that Windows Installer is the de facto standard for desktop application packaging.  For servers, the Microsoft presence and costs of management is still evolving thus a de facto standard is not yet present.

Ultimately, Windows Server 2008 Logo is marketing’s program so they get to make the final decision.  If this choice bothers you as a software consumer, please let your software provider know.

[Author: Robert Flaming]
This posting is provided “AS IS” with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm.

Original post by Windows Installer Team

In recent multi-blog conversations between Windows Installer experts Aaron Stebner, Christopher Painter, and Stefan Krueger, it was noted that my statement that ‘Windows Server 2008 logo would require Windows Installer’ in the Channel 9 video Application Compatibility - MSI Installer Issues was out of sync with the published requirements.

Sure enough, the Windows Server 2008 Logo team demoted this from a requirement to a recommendation.  Unfortunately the Windows Server 2008 Logo didn’t let me know they had decided to do this.  Still, the mistake is mine and I humbly apologize for this unfortunate misinformation.  I do sincerely appreciate the community Windows Installer experts efforts in catching and correcting my mistake. ;^)

Back Story
For the back story, I’ll start by observing the underlying conflict here is in picking the right point in the ubiquity/quality spectrum

• Weaken the quality requirements so that any ISV that is willing to pay the fee can get the brand on their box (optimize for the ubiquity of the logo)


• Strengthen the quality requirements so that any software consumer can use the presence of the brand as synonymous with excellence (optimize for the quality of the logo)

I’ll further observe that the Logo program a marketing program and not a standards program.  This means that the engineering experts are simply consultants to their requirements and test cases.  As a marketing program to ISVs, there is significant feedback to push toward the “make it easy” end of the spectrum.

As was pointed out in the insightful conversation among the Windows Installer experts, there is ubiquitous presence of Windows Installer in corporate environments and particular those that need leverage client software distribution tools.  Putting aside the recent virtualization trends for a bit, any corporate customer research will find very quickly that Windows Installer is the de facto standard for desktop application packaging.  For servers, the Microsoft presence and costs of management is still evolving thus a de facto standard is not yet present.

Ultimately, Windows Server 2008 Logo is marketing’s program so they get to make the final decision.  If this choice bothers you as a software consumer, please let your software provider know.

[Author: Robert Flaming]
This posting is provided “AS IS” with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm.

Original post by Windows Installer Team