MS Office on Terminal server Andrew Mallette <andrewm270[ at ]aol.com> 12.07.2007 02:18:08 excuse my ignorance but i am so confused by the licensing that i only want to get it right. A client has a Terminal Server with 5 user cal's, each person has MS office 2003 on their own computer. They want Office 2003 (same version) on the terminal server. What must be done to keep in line with the proper licensing for Microsoft.

Re: MS Office on Terminal server "Vera Noest [MVP]" <vera.noest[ at ]remove-this.hem.utfors.se> 12.07.2007 12:16:01 In principle, you don't have to buy more Office licenses, because you already have one for each device which uses Office. It doesn't matter if Office is used locally or through a terminal services connection. BUT: it depends on how you bought your current Office licenses. If it's OEM (which came with the PC hardware), then you are not allowed to install that on any other machine. The best thing you can do is to contact your local Microsoft Sales Representative (NOT a reseller/VAR) and get an evaluation of what you need to purchase to be compliant. _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___ Andrew Mallette <andrewm270[ at ]aol.com> wrote on 12 jul 2007 in microsoft.public.windows.terminal_services: [Quoted Text] > excuse my ignorance but i am so confused by the licensing that i > only want to get it right. > > A client has a Terminal Server with 5 user cal's, each person > has MS office 2003 on their own computer. > > They want Office 2003 (same version) on the terminal server. > What must be done to keep in line with the proper licensing for > Microsoft.

Re: MS Office on Terminal server "paulc" <paulc[ at ]mmcwm.com> 12.07.2007 17:08:55 Here's a slightly OT question for you, Vera. Perhaps you ran across an answer. I understand about OEM but lately we've been getting new HP's desktops in with Office 2007 installed but not activated. This isn't something we ordered but appears to be pre-installed on all the HP's we get. So, would you consider that OEM? In my mind, it wouldn't be considered OEM since we still have to pay to activate the software. "Vera Noest [MVP]" <vera.noest[ at ]remove-this.hem.utfors.se> wrote in message news:Xns996B9121F7868veranoesthemutforsse[ at ]207.46.248.16... [Quoted Text] > In principle, you don't have to buy more Office licenses, because you > already have one for each device which uses Office. It doesn't matter > if Office is used locally or through a terminal services connection. > BUT: it depends on how you bought your current Office licenses. If > it's OEM (which came with the PC hardware), then you are not allowed > to install that on any other machine. > > The best thing you can do is to contact your local Microsoft > Sales Representative (NOT a reseller/VAR) and get an evaluation of > what you need to purchase to be compliant. > > _________________________________________________________ > Vera Noest > MCSE, CCEA, Microsoft MVP - Terminal Server > TS troubleshooting: http://ts.veranoest.net > ___ please respond in newsgroup, NOT by private email ___ > > Andrew Mallette <andrewm270[ at ]aol.com> wrote on 12 jul 2007 in > microsoft.public.windows.terminal_services: > >> excuse my ignorance but i am so confused by the licensing that i >> only want to get it right. >> >> A client has a Terminal Server with 5 user cal's, each person >> has MS office 2003 on their own computer. >> >> They want Office 2003 (same version) on the terminal server. >> What must be done to keep in line with the proper licensing for >> Microsoft.

Re: MS Office on Terminal server "Vera Noest [MVP]" <vera.noest[ at ]remove-this.hem.utfors.se> 12.07.2007 19:23:51 I really can't answer that, Paul. I've personally only dealt with software bought under a Volume Licensing Agreement, which doesn't have to be activated. I would contact your reseller and a Microsoft representative. _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___ "paulc" <paulc[ at ]mmcwm.com> wrote on 12 jul 2007 in microsoft.public.windows.terminal_services: [Quoted Text] > Here's a slightly OT question for you, Vera. Perhaps you ran > across an answer. I understand about OEM but lately we've been > getting new HP's desktops in with Office 2007 installed but not > activated. This isn't something we ordered but appears to be > pre-installed on all the HP's we get. So, would you consider > that OEM? In my mind, it wouldn't be considered OEM since we > still have to pay to activate the software. > > "Vera Noest [MVP]" > <vera.noest[ at ]remove-this.hem.utfors.se> wrote in message > news:Xns996B9121F7868veranoesthemutforsse[ at ]207.46.248.16... >> In principle, you don't have to buy more Office licenses, >> because you already have one for each device which uses Office. >> It doesn't matter if Office is used locally or through a >> terminal services connection. BUT: it depends on how you bought >> your current Office licenses. If it's OEM (which came with the >> PC hardware), then you are not allowed to install that on any >> other machine. >> >> The best thing you can do is to contact your local Microsoft >> Sales Representative (NOT a reseller/VAR) and get an evaluation >> of what you need to purchase to be compliant. >> >> _________________________________________________________ >> Vera Noest >> MCSE, CCEA, Microsoft MVP - Terminal Server >> TS troubleshooting: http://ts.veranoest.net >> ___ please respond in newsgroup, NOT by private email ___ >> >> Andrew Mallette <andrewm270[ at ]aol.com> wrote on 12 jul 2007 in >> microsoft.public.windows.terminal_services: >> >>> excuse my ignorance but i am so confused by the licensing that >>> i only want to get it right. >>> >>> A client has a Terminal Server with 5 user cal's, each person >>> has MS office 2003 on their own computer. >>> >>> They want Office 2003 (same version) on the terminal server. >>> What must be done to keep in line with the proper licensing >>> for Microsoft.

Re: MS Office on Terminal server Andrew Mallette <andrewm270[ at ]aol.com> 12.07.2007 23:39:20 I have found out that 4 of the 5 are retail versions, and 1 is oem. They are all the same level (2003 Professional). So that would seem to me that i could install the retail version on the TS but only allow 4 out of the 5 to use it? Unless i purchase one more retail license for the OEM versioned PC? Vera Noest [MVP] wrote: [Quoted Text] > In principle, you don't have to buy more Office licenses, because you > already have one for each device which uses Office. It doesn't matter > if Office is used locally or through a terminal services connection. > BUT: it depends on how you bought your current Office licenses. If > it's OEM (which came with the PC hardware), then you are not allowed > to install that on any other machine. > > The best thing you can do is to contact your local Microsoft > Sales Representative (NOT a reseller/VAR) and get an evaluation of > what you need to purchase to be compliant. > > _________________________________________________________ > Vera Noest > MCSE, CCEA, Microsoft MVP - Terminal Server > TS troubleshooting: http://ts.veranoest.net > ___ please respond in newsgroup, NOT by private email ___ > > Andrew Mallette <andrewm270[ at ]aol.com> wrote on 12 jul 2007 in > microsoft.public.windows.terminal_services: > > >>excuse my ignorance but i am so confused by the licensing that i >>only want to get it right. >> >>A client has a Terminal Server with 5 user cal's, each person >>has MS office 2003 on their own computer. >> >>They want Office 2003 (same version) on the terminal server. >>What must be done to keep in line with the proper licensing for >>Microsoft.