Comments on: How Microsoft Office is licensed in a Terminal Services Environment http://blogs.virtualizationadmin.com/conger/2007/08/10/how-microsoft-office-is-licensed-in-a-terminal-services-environment/ Welcome to the Blog of Jason Conger. Here, we will focus on Server Based Computing environments including Microsoft Windows Terminal Services and Citrix Presentation Server, Application and Server virtualization, Application streaming and delivery technologies such as Microsoft Softricity, and many other server-centric topics. Also, I will point out tools and tips to help you with your Terminal Services environments. Tue, 6 Jan 2009 13:16:50 +0000 http://wordpress.org/?v=MU by: What is Open Office? http://blogs.virtualizationadmin.com/conger/2007/08/10/how-microsoft-office-is-licensed-in-a-terminal-services-environment/#comment-26805 Tue, 09 Oct 2007 11:38:15 +0000 http://blogs.virtualizationadmin.com/conger/2007/08/10/how-microsoft-office-is-licensed-in-a-terminal-services-environment/#comment-26805 Want a simpler license? To avoid possible litigation, here at work we’ve all switched to Open Office. Not only is it easier to use, but it cost us nothing to setup and install. The $12400 that was saved went right into our pockets: every employee got an Open Office bonus of $250 in their paycheck last August, with an additional $1650 used to refurnish the office kitchen. And we don't worry about Microsoft barging down the door with a software audit. All our software has always been legal, but we don't need the bother of proving it. Want a simpler license? To avoid possible litigation, here at work we’ve all switched to Open Office. Not only is it easier to use, but it cost us nothing to setup and install. The $12400 that was saved went right into our pockets: every employee got an Open Office bonus of $250 in their paycheck last August, with an additional $1650 used to refurnish the office kitchen. And we don’t worry about Microsoft barging down the door with a software audit. All our software has always been legal, but we don’t need the bother of proving it.

]]> by: Nick Smith http://blogs.virtualizationadmin.com/conger/2007/08/10/how-microsoft-office-is-licensed-in-a-terminal-services-environment/#comment-22320 Wed, 22 Aug 2007 16:01:01 +0000 http://blogs.virtualizationadmin.com/conger/2007/08/10/how-microsoft-office-is-licensed-in-a-terminal-services-environment/#comment-22320 Which suggests that if you have Office on the PC, you would also have the right to connect to a TS from that PC and use Office on the TS? I've been told this fairly confidently by People Who Ought to Know. Which suggests (And I have indeed been told this is so) that if you have a legitimate OEM licence for the PC which is connecting to the TS then that works OK too. Which suggests that if you have Office on the PC, you would also have the right to connect to a TS from that PC and use Office on the TS?

I’ve been told this fairly confidently by People Who Ought to Know. Which suggests (And I have indeed been told this is so) that if you have a legitimate OEM licence for the PC which is connecting to the TS then that works OK too.

]]> by: Eric Ligman http://blogs.virtualizationadmin.com/conger/2007/08/10/how-microsoft-office-is-licensed-in-a-terminal-services-environment/#comment-22218 Tue, 21 Aug 2007 22:48:36 +0000 http://blogs.virtualizationadmin.com/conger/2007/08/10/how-microsoft-office-is-licensed-in-a-terminal-services-environment/#comment-22218 As my post on the Blog states, you need (1) Office license per client device running/accessing Office, since it is actually the client devices accessing the Office software on the server. You do not need an Office license for the server itself, unless you have someone sitting at the server and using Office on it directly. (Which is highly discouraged since servers should not be used as client devices). So if you have (10) devices using Terminal Services to run Office from the server, then you need (10) Office licenses (with network storage and use rights). As my post on the Blog states, you need (1) Office license per client device running/accessing Office, since it is actually the client devices accessing the Office software on the server. You do not need an Office license for the server itself, unless you have someone sitting at the server and using Office on it directly. (Which is highly discouraged since servers should not be used as client devices). So if you have (10) devices using Terminal Services to run Office from the server, then you need (10) Office licenses (with network storage and use rights).

]]> by: Ben Lipman http://blogs.virtualizationadmin.com/conger/2007/08/10/how-microsoft-office-is-licensed-in-a-terminal-services-environment/#comment-22216 Tue, 21 Aug 2007 20:20:34 +0000 http://blogs.virtualizationadmin.com/conger/2007/08/10/how-microsoft-office-is-licensed-in-a-terminal-services-environment/#comment-22216 Ok, so does this mean you need exactly one additional license per terminal server since it is the device using Office instead of the workstation or does this imply that you need no additional licensing for the TS box itself? This is all assuming the licensing in question is Volume. Ok, so does this mean you need exactly one additional license per terminal server since it is the device using Office instead of the workstation or does this imply that you need no additional licensing for the TS box itself? This is all assuming the licensing in question is Volume.

]]>