Tip

What you need to know about .NET Server



IT administrators who have already sweated through a Windows 2000 upgrade and have installed Active Directory can relax knowing that upgrading to .NET Server won't require much in terms of additional staff training.

But even though the learning curve from Windows 2000 to .NET Server may be small, many companies that wish to move servers still running NT 4.0 up to .NET Server -- bypassing Windows 2000 entirely -- could run into trouble if they don't learn the ins and outs of changes that take place within

Requires Free Membership to View

Active Directory, security and administration. The .NET Server release candidate 1 shipped in late July and the first release should become available in early 2003, Microsoft executives have said.

In .NET Server, there is a new partition inside of Active Directory that is specifically geared for replicating DNS records. "If you're not familiar with Active Directory or with DNS, you won't know what to check on or where to put those records, said Bill Boswell, principal at the Windows Consulting Group, a Glendale, Ariz. consulting firm.

There are other changes. The directory uses Stub Zones, which replicates only the names of a master zone rather than an entire zone. There is also conditional forwarding, which makes it easier to implement extranet connections. Conditional forwarding helps resolve the problem of having multiple server names behind a firewall for various business subsidiaries. Also helpful is the ability to have cross-forest trusts, so various business divisions on separate servers in separate forests can access each other's resources.

Beyond Active Directory, most of the big changes are in the security department, since .NET Server is using new technology offered in Internet Information Services (IIS) 6.0. In this vein, what makes .NET Server more flexible is also what makes it more complex, according to Paul Hinsberg, chief executive at CRSD Inc., a Pleasanton, Calif., consulting firm.

As one example, the number of configuration items that are inside the Group Policy objects has tripled within .NET Server. These are the items that govern what people can do and their experience once on the network. "There are now many more different options you can use to manage the users' desktops, and a tool for managing those desktops," Hinsberg said.

There are also changes to the VPN and remote access application. Users are no longer tied to a particular domain when using a VPN, Hinsberg said.

IIS 6.0 adds a new thread-handling model so Web sites can be grouped into application pools, Boswell said. For someone hosting Web sites for 15 different internal customers, the advantage is they can have separate application pools for different customers so they never talk to one another. Microsoft has also added security lockdown in IIS, so administrators who are not familiar with how security works need to understand what the lockdowns are doing, Boswell said.

One trial user of .NET Server said an area that often gets overlooked in terms of changes is scripting and programming. Until Windows 2000, there wasn't much an IT administrator could do with Java scripting. Now, however, these scripts can be used to automate a number of management administration tasks within .NET Server, said Dustin Sauter, a system architect at Wells Fargo & Company, San Francisco.

Microsoft has expanded the type of data on clients and servers that customers can reach using .NET Server and in the Windows Management Instrumentation [WMI] model. Active Directory can also do more with the data it gets from WMI. Though WMI was a part of Windows 2000, there are more items in .NET Server that are exposed to that interface such as processor speeds and temperature. "You can write scripts to grab information about a particular machine," Souter said. "They've enhanced the type of data you can get to on a server and on a client."

Of course, for customers insisting on making the jump from NT 4.0 to .NET Server, Sauter warns Windows administrators not to underestimate the work involved.

"It's important that people get trained before they make this move," Sauter said. "Not only will you reduce your mistakes but you will also do a better job leveraging the technology."

MORE ON THIS TOPIC:

>> The .NET Info Center
Trying to get up to speed on .NET and what it means for you? Visit the .NET Info Center for the latest .NET news and development tips. Plus, get one-stop access to the most important Visual Studio.NET resources direct from Microsoft.

>> Web Services Decisions (March 19-21, Atlanta)
This free conference will feature critical tech sessions including Implement Essential Web Services Security Tactics; Understand the Key Role that XML Plays in Web Services; Rate the Vendor: An Unbiased Analysis; Gain the Highest ROI from Web Services; How to Survive the Web Services Platform Wars; and much more. View full sessions and apply to attend today.

This was first published in August 2002

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:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.