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.

comments powered by Disqus

Reader Comments:

Wed, Dec 8, 2010 Bert B, St. Louis

What about Cario? It went into Windows Server correct?

Wed, Dec 8, 2010 AJ Seattle

You missed my favorite: Project Origami eventually turned into "Ultra-Mobile PC". The initial buzz for Origami was very positive; the buzz for UMPC didn't exist because nobody noticed it had been released.

Tue, Dec 7, 2010

Indigo instead of WCF

Mon, Dec 6, 2010

dont forget sync , they should have kept that over mesh as a name !

Add Your Comment Now:

Your Name:(optional)
Your Email:(optional)
Your Location:(optional)
Please type the letters/numbers you see above

Redmond Tech Watch

Sign up for our newsletter.

I agree to this site's Privacy Policy.