Microsoft Press is proud to announce the publication of the following book on January 9, 2008:
Windows Server® 2008 Networking and Network Access Protection (NAP)
By Joseph Davies and Tony Northrup with the Microsoft Networking Team
This book describes how to plan, deploy, operate, and troubleshoot networks with Windows Server 2008. This book includes detailed instructions for all major networking and network security services including Internet Protocol version 4 (IPv4) and IPv6, Dynamic Host Configuration Protocol (DHCP), Windows Firewall, Internet Protocol security (IPsec), quality of service (QoS), scalable networking, Domain Name System (DNS), Windows Internet Name Service (WINS), network authentication infrastructure, protected wired and wireless connectivity, virtual private network (VPN) connections, and the new Network Access Protection (NAP) platform.
The NAP section of this book contains 6 six chapters and over 200 pages of detailed technical information and instructions for deploying and troubleshooting the IPsec, 802.1X, VPN, and DHCP enforcement methods.
You can pre-order this book from the following online booksellers:
Windows Server 2008 Networking and Network Access Protection (NAP) comments and corrections
PingBack from http://geeklectures.info/2007/12/20/microsoft-press-says-nap-the-world/
This post has inspired my curiosity into the lack of user manuals with just about every microsoft product over the past decade. Understandable that you can't really make a comprehensive "HOWTO" for every scenario of every technology in a server product and since every feature and common use is covered somewhere online.
Still, I sometimes long for the good old-fashioned user manual. Even a link-enabled .doc/xps/pdf does wonders for me when I have to deal with 3rd party products that I'm not so farmiliar with.
Does product complexity and feature creep mean the tech writers can no longer adequately instruct their customers without using more than a thousand words? Are the products too complex for them to understand without using analogies from the software developers? Will user manuals ever make a comeback at microsoft? Just some random ideas I was pondering.
Rob, you pose a very valid question. I appreciate you taking the time to post it here. I don’t get a ton of comments on the NAP blog, and I always cheer when I get one! :->
NAP in Server 2008 is a version 1 product. Over the course of the "Longhorn" beta cycle, while the overall NAP architecture was very stable, the user interface was a bit of a moving target. I noticed that just when the User Assistance team (aka doc writers) got a great handle on how all the knobs and buttons function, we would change it based on customer feedback so that what was in the docs no longer made any sense.
Our NAP step-by-steps from Longhorn Beta 3 demonstrate this. We spent a GREAT deal of time creating new wizards so that customers didn’t have to reverse engineer the complex Network Policy Server (NPS) MMC. Prior to Beta 3 our #1 piece of feedback from customers was that it was too easy for NAP to fail because of mistakes in the NPS MMC. We did extensive research and usability studies and created the wizards you see in the product today. What we didn't leave much time for was a little thing called documentation! :->
The UA team is in a constant "catch-up" mode, to keep pace with the darn product team who just loves to change the code. What ends up happening is we don't want to further delay the product release, so we put on the DVD what we have time to get right, and everything else hits the web very close to product release.
I know for a fact that we have extensive guidance releasing via the web (for free) on deploying NAP. I am helping Greg Lindsay, our genius UA dude, by reviewing all the great stuff he is writing. Joe Davies (the Cable Guy) who authored this book was ahead of the curve and beat us by releasing first.
I agree with you, the trend today is to not have a nice set of text, glued together with a binding, when you buy software. One of my favorite things to do when I buy a car for instance, is to sit down and pour over the manual. Software is a fast paced business. Hang in there with Microsoft. We are always trying to improve the quality of our work - I promise we will do better!
E' davvero da tanto che non vi parlo di Network Access Protection (NAP) e questo è male: questa