Microsoft goes for the 'common' touch

Margie Semilof

How do you define what will be a common service?
The reason we call this a road map is because we see this as something evolving. We wanted a consistent experience across servers and that's what common engineering does. We asked customers what they needed. They said they need to be able to have

Requires Free Membership to View

MOM management extensions for monitoring all the products that are released. They want a common experience for patching, and the ability to uninstall patches. So we have evolved this list of criteria [for 2005 products] over the past year.

Moving forward, the group is focused on the common services we can deliver across Windows Server systems that can meet their needs. I'll be going out and asking what [customers] potentially need from an integrated server infrastructure.

One example [stems from] the Best Practices Analyzer for SQL Server. This is something we think will be common. We will also have a Windows Server System best practices analyzer. Will Microsoft be doing anything to older products to bring them into the fold?
The criteria will apply to all products with the 2005 name, such as MOM 2005 and Virtual Server 2005. We are looking at the potential for measuring older products against the criteria. We have criteria that say the enterprise edition needs to have support for high availability and scalability. Some products, such as the speech server, can't do clustering. They are PBXs. So we let customers [view materials] on the Windows Server site and they can see how a speech server implements high availability.

So we are looking at

For more information

Read about the extension of Microsoft's product life cycle


Find out why Steve Ballmer wants greater platform integration

2004 [products] and seeing if we can at least map them to the criteria. We haven't made a decision on that yet. So the plan is to have all server platforms support mostly the same criteria when they ship? All support 64-bit mode. All support virtualization. What else?
The essence of supporting it is to provide a consistent experience. You should expect certain things as they cut across all servers. Longer term, we want to move into common services. We want one set of reporting services, one common architecture. We see this as evolving, eventually moving more deeply into architectural changes. How hard was it to change the way the various groups within Microsoft develop their products?
We have a history where teams are driven to come up with new things. But when we talk about what customers need, everyone agrees [on one thing]. Customers have too much complexity to deal with. We have to think about that before we think up new features. Are there drawbacks to building products with common criteria? For example, won't it slow down the development process of individual products?
It's a development effort of its own. There is work that goes into meeting the criteria. For the MOM management packs, we have a small team in the management group that is good at building management packs. We can take that team and host it in different groups. We are looking to see if we can be more innovative here so we can get more efficiency out of the development process. In some cases, there will be trade-off decisions. We will have to look at shipping the 'nth' feature versus shipping common engineering.

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: