This is a test, please join in

Microsoft has finally crystallized its .Net philosophy into what's supposedly going to become the crowning jewel of this once-nebulous initiative: the .Net Server. I've been charged with the task of testing the final, or "gold code," version of this yet to be released product for Network World.

There are four versions of the operating system: Web, Standard, Enterprise and Datacenter. The Enterprise edition supports the highest common denominator feature set, and it's likely that we'll test that set of code.

Microsoft promises to deliver the final code soon, so I need your help now.

To continue reading, register here and become an Insider. You'll get free access to premium content from CIO, Computerworld, CSO, InfoWorld, and Network World. See more Insider content or sign in.

Microsoft has finally crystallized its .Net philosophy into what's supposedly going to become the crowning jewel of this once-nebulous initiative: the .Net Server. I've been charged with the task of testing the final, or "gold code," version of this yet to be released product for Network World.

There are four versions of the operating system: Web, Standard, Enterprise and Datacenter. The Enterprise edition supports the highest common denominator feature set, and it's likely that we'll test that set of code.

Microsoft promises to deliver the final code soon, so I need your help now.

Here's the dilemma. Because .Net is a huge code set with feature listings that are pages long, I need to determine which of those features are important to you as an enterprise network professional - and your organization - and perhaps the individual that will make use of the test results information.

I've developed a Web form comprising the feature sets of .Net Server. I need to know your insights on what our test of this new product should entail in a prioritized manner. The form is simple, but the operating system is not.

Microsoft's .Net server message issued in the early-beta versions of .Net is that .Net has incremental changes over Windows 2000 Server editions, with the exception of highly evolved Web services in the .Net API sets. There also are changes to Active Directory, Microsoft's successor to its domain management model, that underpin in the .Net strategy. New services anchored on Active Directory include those based on Universal, Description, Discovery and Integration specification and authentication services for Web applications.

Microsoft wants to play and ostensibly be a good neighbor on every network. Redmond engineers have added new management APIs to .Net, and features that are supposed to allow heretofore difficult manipulation of managed domains, users and services - or so we must test if you tell us to do so. These changes also are rooted (if you'll excuse the pun) in Microsoft's initiatives toward interoperability with third-party management and directory services infrastructures. Is interoperability as important to test as increased management features? Tell us on the form.

The .Net Web services additions are seen as a key ingredient to the .Net mantra. While some organizations maintain file-and-print servers separate from those that manage Web applications, others want to integrate not only the aforementioned services, but additional Microsoft and third-party applications such as Exchange and Oracle. I need to know if centralized or distributed services matter to you.

And so I need your help. Fill in the form, and click submit. The information will remain private between Network World, you and me. In addition to the form, you can send your extended comments to gta@nww.com.

In the name of collecting a valid data set for this project, I'll be tracking IP addresses for unique entries. Thanks in advance for your time.

Read more about software in Network World's Software section.