Microsoft Certifies New High-End Datacenter Configuration

Enterprise Datacenter configuration promises reliability, scalability, and security for back-end datacenter environments.

• By Stephen Swoyer
• 12/17/2002

Microsoft Corp. last week announced a new edition to its Microsoft Systems Architecture (MSA) certified configurations, Microsoft Systems Architecture for the Enterprise Data Center (EDC). The company describes its MSA configurations as “prescriptive architecture guides” for designing and rapidly implementing scalable, reliable, and secure Windows systems in various environments. The software giant certified the first MSA configuration, Internet Data Center (IDC), in February.

Since that time, says group product manager Alfredo Pizzirani, Microsoft’s customers have requested that the company make available additional MSA configurations. The result, he indicates, is EDC. “Our customers told us that there are more aspects of their infrastructure that they would like to design similar to what we did with IDC, so together with our partners we are coming back with a blueprint for their data centers.”

According to Pizzirani, the MSA guides describe a baseline configuration companies can use to rapidly design and deploy, for example, a variety of Windows operating systems and applications to support an EDC. The EDC guide provides a general overview of the framework and design philosophy of a Windows-based datacenter, along with specific architectural and configuration instructions. “These [MSAs] minimize the costs and the risks associated with implementing this kind of [enterprise data center] infrastructure. Together with our partners, we have already done most of the work.”

Microsoft’s partners include Avanade Inc., Brocade Communications Systems Inc., CommVault Systems Inc., Hewlett-Packard, Hitachi Data Systems Corp., McDATA Corp., NetIQ Corp., Nortel Networks and Unisys Corp. Microsoft says it will expand its partner base in the future.

Partnering is important, Pizzirani says, because almost all IT organizations will choose to customize certain aspects of the certified MSA configurations. “This is not going to be something that customers want to do on their own because there’s going to have to be some customization. No blueprint that we come up with would fit all users, so the partners that have been with us through the development process will help them with this.”

Lest someone charge that the software giant is merely puffing its chest, Pizzirani asserts that each of the system hardware and software configurations listed in the MSA books has been assembled and tested by Microsoft, by a group of its partner vendors, and by third-party integrators. “We bring it all into one place, and we actually build the configuration that we’re going to recommend and test it, so this is all actually pre-tested. We stand behind the guidance that we offer because we have thoroughly tested it.”

According to Mark Feverston, vice-president of platform marketing with long-time MSA partner Unisys Corp., the process is even more complicated than that. “You have to develop the prescriptive architecture, then you have to go ahead and build it out, test it, and make sure it works. Then you have to document it, then you tear it down, and then you try to rebuild it via your own documentation. Then you tear it down again, and this time you bring in a third-party who is going to certify you. Then they use your documentation to literally build your own system configuration on the floor.”