Windows Terminal Server Licensing (Score 1)

I think that Codeweavers has a very good explanation regarding licensing considerations for a Linux TS server hosting MS apps, with many points that apply to your proposed environment. The most important thing they clarify is that application licensing is based upon device count (PC's, thin clients, pda's, whatever) that attach to the terminal server. http://www.codeweavers.com/products/cxofficeserver /mslicensing.php However, one significant difference between Netraverse (Win4Lin) and CodeWeavers (Terminal Server) is that Codeweavers are using their own Windows API's to run the programs and Netravers is using Microsofts. My understanding of MS licensing is that if you want to use MS's api's you need to ALSO buy a copy of Windows OS for each device (see above definition) that will attach to the server. Licensing proof is considered a Licensing Certificate, Electronic Licensing agreement (eMolp), serialized media, or invoice. Purchase orders could be challenged during a software audit unless they can be tracked back to an invoice number.