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

  • Office 365 Attack Simulator Now Supports Attachments

    The Attack Simulator in Office 365 tool has been updated and now has the ability to include message attachments in targeted campaigns, according to a Friday Microsoft announcement.

  • How To Disable Touch Input in Windows 10

    When the touchscreen on your Windows 10 laptop goes bad, there's no reason to throw that baby out with the bath water.

  • Microsoft Previews Windows VM Authentications via Azure Active Directory

    Microsoft on Thursday announced a preview of remote authentications into Windows-based Azure virtual machines (VMs) using Azure AD credentials.

  • Windows Server 20H1 Getting Smaller Containers and Faster PowerShell

    Microsoft is promising to deliver a smaller container size and improved PowerShell performance with its next release of Windows Server.

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.