I don't like finding typos, but hey--if someone points one out it means that they're reading. On page 53 of the TS Resource Kit, an alert reader found the following confusing statement:  

 "32-bit Windows can't see more than 4 GB of virtual addresses no matter what you do, but you can use up to 64 GB of physical memory with 32-bit Windows Server 2008 (standard edition) or up to 2 terabytes with enterprise or datacenter editions."

This is an typo. The RAM support statements are documented on http://download.microsoft.com/download/e/6/3/e63cf2f6-7f71-450b-8e4a-dace88e99456/readme.htm#EFE
·         Maximum (32-bit systems): 4 GB (for Windows Server 2008 Standard) or 64 GB (for Windows Server 2008 Enterprise or Windows Server 2008 Datacenter)
·         Maximum (64-bit systems):32 GB (for Windows Server 2008 Standard) or 2 TB (for Windows Server 2008 Enterprise, Windows Server 2008 Datacenter, or Windows Server 2008 for Itanium-Based Systems)

Thanks for checking in! 

When you connect to a terminal server or remote desktop using RDP, the endpoint is ultimately made to an IP address, not to a machine name. I've written a new Terminal Services team blog entry explaining how DNS errors can manifest when making remote connections, and how you can diagnose and resolve them.

With apologies to the late, great, Douglas Adams... 

I was commissioned by Microsoft Press to write the Resource Kit for Terminal Services, and I accepted after I'd lined up my co-author, Kristin Griffin, who accepted in a moment of weakness. After a lot of procrastination and hiding and inventing excuses and having baths, I managed to get about two-thirds of it done. At this point Microsoft Press said, very pleasantly and politely, that I had already passed ten deadlines, so would I please just finish the page I was on and let them have the darn thing.

The trouble with writing a book is that at some point it's got to end. This is especially true when you have an editor. (Hi, Vicky!) You write, and you write, and you write, and eventually it become the day when you can no longer avoid turning the book over to the publisher because your editor works on the same campus less than a mile from you and you can't avoid your office forever. Besides, we were going to go out for a beer when we finished the book, and I wanted to go. So we finished.

I'm kidding, but not entirely. The thing about Terminal Services in Windows Server 2008 is that it's really big. It has expanded massively in scope from its form in Windows Server 2003. It now does a whole bunch of cool new things and touches the rest of the server ecosystem in cool new ways, and telling the story of both takes a while. I think we've done a really good job of telling it, and the cooperation of the rest of the Terminal Services team and other Terminal Services experts at Microsoft has been invaluable in getting us to this point. We just keep wanting to tell more.

One way to tell more is to write a second edition, and we hope to do just that. That takes a while, though, and new things come up far in advance of a second edition. The faster way is to post updates as they occur to us, and that's what we plan to do here. Look for more updates after the book's available in November of 2008, or sooner if we can't wait.