Pcweek How to Implement Microsoft NT Server 4.0

Mark Twain once said that he did not have enough time to write short stories, so he was forced to write long novels. There seems to be a lot of Mark Twain wannabes writing computer books these days. Perusing the latest NT titles, one gets the feeling that there is an unwritten requirement that technical books must be at least 3 inches thick.Many NT books that claim to cover numerous topics come in at well over 1200 pages. Not only do such books kills a lot of trees, they also are rather difficult to read while standing on a bus or subway.How to Implement Microsoft Windows NT Server 4 humbly comes in at a rather modest 425 pages (or about 3 pounds). Rather than trying to cover every imaginable feature of NT, it assumes that the reader has a substantial level of NT knowledge and is geared for more of an advanced user, as opposed to one that needs 20 pages of screen shots on how to install a printer driver.The book is divided into 8 parts, compromising 39 chapters and 5 appendixes. As stated earlier, the book get to the heart of the technical issue at hand, rather than spending scores of pages on a relatively simply idea. Some chapters are as short as 2 pages, sparing you the often unneeded screen-captures than can add up to over 50% of a books page count.Parts 1 -2 (chapters 1-10) deal with the initial setting-up and configuration of an NT server. One of the enigmas of NT is that it is so easy to set-up, that inexperienced administrators can often set-up a system in a manner that later does not work or scale well. The authors write that no matter how good or easy Windows NT Server is to use, it still is a complex operating system. Given that caveat, throughout the book, it notes crucial areas in the installation and configuration process where utmost caution is required.An interesting point brought up in chapter six is about the infamous Intel Pentium bug. For the vast preponderance of NT Servers, the presence of a defective Pentium processor will have no effect. This obviously can not be said for a workstation, but for an NT Server, there is little point in attempting to fix the problem via software. For those users that somehow feel the need to perform this fix on a server, the author's write that the work-around may even harm system performance. The bottom line: Apply those patches carefully and selectively.Parts 3-4 of the book (chapters 11-25) accomplish in a little over 100 pages what other books take over 500 pages to state. These chapters detail the bulk of the configuration of an NT Server. Chapter 22 provides an excellent overview of the issues involved with directory replication. NT has the ability to replicate directories and data across servers. Replication is one of those little used, yet powerful features of NT. Don't get all excited and throw out your copy of ArcServe, replication is meant only to copy specific directories and was never meant to replace an enterprise-wide backup solution.Knowing that NT servers