I found two references, so far: http://blogs.msdn.com/jmazner/archive/2006/07/14/665973.aspx
or http://preview.tinyurl.com/2j2afn which says: Windows Activation Service (WAS) provides a central broker that can take incoming network requests and route them to the appropriate service or application, reducing the need for developers to write custom NT services to manage their own service activation. Having fewer services running with high local system privileges reduces the potential attack surface of the system. WAS also provides process health monitoring and failure recycling for a more robust system. Built-in support of poison queues for receiving messages that cannot be processed makes building fault-tolerant systems easier. And since IIS 7 is also a requirement for TS Gateway: http://technet2.microsoft.com/windowsserver/en/library/edd59c63-a12c-4990-b3 b7-dcf02067deca1033.mspx?mfr=true or http://preview.tinyurl.com/3auvfe Maybe Ken Schaefer can explain this for me. Webster > -----Original Message----- > From: Carl Webster [mailto:[EMAIL PROTECTED] > Subject: Server 2008 TS Gateway and Windows Activation Service > > Why does using TS Gateway require the use of the Windows Activation > Service? ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
