In-Depth

10 Microsoft Product Code Names That Should've Stuck

Often, Microsoft's code names are better than its resulting product names. Here's 10 examples that Microsoft should have at least considered keeping.

You've read about many products in development years before they finally arrived. Sometimes we become so familiar with the code names that the final names are often bewildering. Here are 10 code names that Microsoft should have slapped on the final releases.

Code Name Final Name
Hydra Windows Terminal Services
Blackcomb (eventually changed to Vienna) Windows 7
Lone Star Windows XP Tablet PC Edition 2005
Bobcat and Cougar SBS 2003 and SBS 2008
Centro Windows Essential Business Server
Red Dog Windows Azure
Titan CRM 4.0
Metro Windows Phone 7
Katmai SQL Server 2008
Chicago Windows 95

About the Author

Doug Barney is editor in chief of Redmond magazine and the VP, editorial director of Redmond Media Group.

Featured

  • Azure Cost Management Now Commercially Available for Some Tenancies

    Microsoft on Monday announced that its Azure Cost Management feature had reached the "general availability" release stage for both Azure "pay-as-you-go" customers and Azure Government tenancies.

  • Microsoft Bringing Files Restore Capability to SharePoint Online and Teams

    Microsoft on Monday announced that it's delivering its Files Restore feature for SharePoint Online and Microsoft Teams to Office 365 tenancies as early as this month.

  • Microsoft Nabs IoT Platform Provider Express Logic

    As part of its plan to invest $5 billion in IoT technologies, Microsoft this week acquired Express Logic, which provides real-time operating systems for industrial embedded and IoT devices.

  • Dealing with Broken Dependencies in SCVMM

    Brien shows you how to resolve some broken, template-related dependencies in Microsoft's System Center Virtual Machine Manager.

comments powered by Disqus

Office 365 Watch

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.