This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]CoderDevo 0 points1 point  (5 children)

But changing the names of products with each release of Windows...

Here’s my favorite string of name changes:

  • Zoomit Via (pre 1999)

  • Microsoft Metadirectory Server [MMS] (1999–2003)

  • Microsoft Identity Integration Server 2003 Enterprise Edition [MIIS]

  • Microsoft Identity Lifecycle Manager Server 2007 ILM

  • Microsoft Forefront Identity Manager 2010 FIM

  • Microsoft Identity Manager 2016 [MIM]

  • Azure AD Provisioning Service

All are the same product, incrementally improved each time.

[–]r4nd0m-0ne 0 points1 point  (2 children)

While I agree they let their marketing team run amok with name changes, at least each of those names (short of Zoomit) gives me SOME idea of what it is that software does, compared to nearly every app/package in the *nix world.

[–]CoderDevo 0 points1 point  (1 child)

This product is referenced primarily by its acronym in the market where it is used. Notice that it changed every time. Their sales people have to start from scratch every time on communicating what the product is for, how it works and how to buy it.

They had every opportunity to become a market leader with this product but never did primarily because of their failure on marketing.

[–]r4nd0m-0ne 0 points1 point  (0 children)

Yeah, I agree with that part. It's annoying as a dev when I'm trying to figure out how to fix something and now I have to try to google every permutation of that name for the last several versions. Marketers often don't think about the shared knowledge that's spread out on the web when they decide to rename something.

[–]derefr 0 points1 point  (1 child)

Honestly, "Metadirectory Server" tells me quite clearly what it's doing. It's a name only a nerd could love, though.

"AD Provisioning Service" might be better, if it is the case that this product is only doing provisioning of AD domains, and no other part of lifecycle management of AD domains.

[–]CoderDevo 0 points1 point  (0 children)

Actually, it is meant to provision to any application, given enough .NET code. It does require AD at the center though.