Office licensing

[Guest Dan]

We have a new Windows 2003 domain server that is acting as a TS for remote

access to our application. The app requires Microsoft Word. I believe that

we will need a volume license for each of the remote connections, but we also

have 4 local computers that are logging into the domain directly. will we

need additional licenses for these computers?

 

Thanks, Dan

[Guest Lanwench [MVP - Exchange]]

Re: Office licensing

 

Dan <Dan@discussions.microsoft.com> wrote:

> We have a new Windows 2003 domain server that is acting as a TS for

> remote access to our application. The app requires Microsoft Word.

> I believe that we will need a volume license for each of the remote

> connections, but we also have 4 local computers that are logging into

> the domain directly. will we need additional licenses for these

> computers?

>

> Thanks, Dan

 

AFAIK, you need as many licenses for MS Office as you have computers (or

sessions) that will be able to use it - so, one for each workstation, and

one for each potential TS session on that server. Call Microsoft or your

trusted reseller for any/'all licensing questions, though, rather than

relying on newsgroup myth and lore.

 

That said - you really shouldn't run TS on a domain controller or

install/run your desktop-type LOB apps on it - it's a very bad idea. Don't

let users log into a DC at all, whether at the console or via RD. You should

get a dedicated member server (even if it's virtual) to run TS. It's fine to

run TS licensing on your DC, though.

[Guest Dan]

Re: Office licensing

 

This is jaust a temporary configuration. Once we are weaned off of our old

system, I will be using one of our other servers as the TS.

 

"Lanwench [MVP - Exchange]" wrote:

> Dan <Dan@discussions.microsoft.com> wrote:

> > We have a new Windows 2003 domain server that is acting as a TS for

> > remote access to our application. The app requires Microsoft Word.

> > I believe that we will need a volume license for each of the remote

> > connections, but we also have 4 local computers that are logging into

> > the domain directly. will we need additional licenses for these

> > computers?

> >

> > Thanks, Dan

>

> AFAIK, you need as many licenses for MS Office as you have computers (or

> sessions) that will be able to use it - so, one for each workstation, and

> one for each potential TS session on that server. Call Microsoft or your

> trusted reseller for any/'all licensing questions, though, rather than

> relying on newsgroup myth and lore.

>

> That said - you really shouldn't run TS on a domain controller or

> install/run your desktop-type LOB apps on it - it's a very bad idea. Don't

> let users log into a DC at all, whether at the console or via RD. You should

> get a dedicated member server (even if it's virtual) to run TS. It's fine to

> run TS licensing on your DC, though.

>

>

>

[Guest Lanwench [MVP - Exchange]]

Re: Office licensing

 

Dan <Dan@discussions.microsoft.com> wrote:

> This is jaust a temporary configuration. Once we are weaned off of

> our old system, I will be using one of our other servers as the TS.

 

I'd make sure that happens immediately.

>

> "Lanwench [MVP - Exchange]" wrote:

>

>> Dan <Dan@discussions.microsoft.com> wrote:

>>> We have a new Windows 2003 domain server that is acting as a TS for

>>> remote access to our application. The app requires Microsoft Word.

>>> I believe that we will need a volume license for each of the remote

>>> connections, but we also have 4 local computers that are logging

>>> into the domain directly. will we need additional licenses for

>>> these computers?

>>>

>>> Thanks, Dan

>>

>> AFAIK, you need as many licenses for MS Office as you have computers

>> (or sessions) that will be able to use it - so, one for each

>> workstation, and one for each potential TS session on that server.

>> Call Microsoft or your trusted reseller for any/'all licensing

>> questions, though, rather than relying on newsgroup myth and lore.

>>

>> That said - you really shouldn't run TS on a domain controller or

>> install/run your desktop-type LOB apps on it - it's a very bad idea.

>> Don't let users log into a DC at all, whether at the console or via

>> RD. You should get a dedicated member server (even if it's virtual)

>> to run TS. It's fine to run TS licensing on your DC, though.