"This is the definitive resource for every network administrator, consultant, and architect who needs to maximize availability, scalability, and performance in Windows server environments." "Shapiro and Policht offer a clear, concise roadmap for keeping Windows servers running 24x7 and delivering on even the most challenging service-level agreement. They provide real-world case studies and easy-to-use instruction designed to help readers make better decisions more rapidly."--BOOK JACKET.

Building High Availability Windows Server™ 2003 Solutions About the Authors

Jeffrey R. Shapiro has worked in Information Technology for nearly 15 years. He is an industry-celebrated author and has published more than a dozen books on IT, network administration, and software development. Jeffrey has written for numerous publications over the years as well. He also regularly speaks at events and frequently participates in training courses on Microsoft systems.

Jeffrey has specialized in Microsoft technologies since 1989. From 1992 to 1998, he was CTO for a leading software development company specializing in telephony solutions for business and was credited with designing the architecture for one of the first Windows-based computer telephony platforms.

In early 2003 Jeffrey was selected to lead the Novell NetWare to Windows Server 2003 migration project for Broward County, Florida. His mandate was to design the architecture for an Active Directory network that would replace the hundreds of servers and Novell Directory Services (NDS) required to support more than 80 agencies. He was also in charge of designing the architecture for three mission-critical, high availability, high-performance data centers supporting thousands of public servants in one of the largest population centers in the United States.

In late 2004 Jeffrey turned his attention almost exclusively to systems and software architecture. He recently formed Normal Data, Inc., a company that specializes in architecting software for enterprise information technology solutions http://www.codetimes.com. Jeffrey can be reached on the Web at jshapiro@codetimes.com.

Marcin Policht has diverse experience in areas of scripting and programming, as well as system engineering and administration of large-scale, high availability, Windows-based environments. He has shared his expertise as a technical trainer and as a writer, authoring a number of books and Web articles on subjects varying from WMI scripting to Active Directory management.

© Copyright Pearson Education. All rights reserved.

Building High Availability Windows Server 2003 Solutions Building High Availability Windows Server 2003 Solutions Preface The year 2004 will long be remembered as the year that saw the beginning of a huge push by companies and government organizations to once and for all migrate to a Windows Server operating system underpinned by Active Directory and Windows Server 2003. What is also significant about this year is that it will be remembered as the year Microsoft finally ended all support for Windows NT 4.0, the grandfather of the current version of Windows Server that many IT professionals now regard as the Serengeti of the operating system jungle. In 2004, many companies have finally made the move to ditch Novell NetWare. However, it is not simply enough to trade one operating system for another. Many IT shops going to Windows Server 2003 need to install and configure high availability, high-performance Windows Server 2003 systems that can service their needs day in, day out, 365 days a year. At the same time, they are also striving to lower the cost of installing, operating, and maintaining these systems and the overall cost of ownership (TCO). Windows Server 2003 delivers on all these points. As companies migrate to the platform that is thede factowinner in the network and operating system wars, they face a huge learning curve and dilemma on how best to set up high-performance Windows Server networks for maximum availability and power. Their aspirations come down to one thing: service level--"How do we do it with Windows Server 2003?" Companies that have made the decision to migrate to Windows Server 2003 ask how they can keep systems up 24/7 or how they can achieve three, four, and perhaps even five times the availability with Microsoft technology. Network administrators ask, "Do we cluster, do we load balance, do we do both, do we invest in hot standbys, replication...what works?" This book gives you the answers to those questions. It will also go further than just failover and fault tolerance and discuss monitoring and operations management and choosing the right technology to accompany Microsoft's high-performance and high availability offerings. This is the book that caters to your needs. It is about achieving service level and keeping systems up 24/7 with the Windows Server 2003 platform. This book provides a clear and concise roadmap for how to go about using Microsoft Server 2003, (in some cases) with third-party add-ons, for scalability, uptime, performance, and management--and for how to avoid trouble at the same time. Many administrators and engineers find it hard to make decisions about what they need to do. They hear that clustering and using load balancing is a black art--extremely difficult and prone to disaster. Up until today, their only resources for architecting a high availability solution has been rare and expensive consultants and overzealous consulting services engineers, particularly from hardware vendors. If you are turned to Microsoft technology to achieve your SLA, this book will be the foundation to turn to, to bring it all together. Microsoft now offers a rich toolset for administration and monitoring, not only what is built into the server products, but also with collateral offerings such as Microsoft Operations Manager (MOM) and Systems Management Server. According to Gartner, Microsoft will own the systems administration market, and possibly surge ahead of IBM, in the coming years. Efforts in this area became very evident in 2003 and 2004 with the advent of new versions of MOM and Systems Management Server. We have thus devoted an entire chapter to monitoring and installing MOM as the essential operations platform for any high availability network. The book is divided into two parts: Part I,