Citrix or Terminal Services Licensing related to Project Server

A

Adam Hodgson

My client is located across a number of States. We have two server set up in
one State that is not having any issues with performance, except when Project
Managers are opening files, saving files and using Build Team from Enterprise
from other States - that is the performance issues relate to network speed.
I have read in many places that Microsoft recommends using Terminal Services
to address this issue.

We were ready to trial Citrix when I was warned that you need to be careful
of licensing when implementing Terminal Services. I called a MS rep and they
said that I would need to license all staff in the organisation with MS
Project Professional if I was to implement this solution (over 3000 people).
Is this correct? We are happy to purchase licenses for those who use MS
Project Pro. Any suggestions how to set things up so that we comply with MS
licensing requirements?

Regards,

Adam
 
R

Rolly Perreaux

My client is located across a number of States. We have two server set up in
one State that is not having any issues with performance, except when Project
Managers are opening files, saving files and using Build Team from Enterprise
from other States - that is the performance issues relate to network speed.
I have read in many places that Microsoft recommends using Terminal Services
to address this issue.

We were ready to trial Citrix when I was warned that you need to be careful
of licensing when implementing Terminal Services. I called a MS rep and they
said that I would need to license all staff in the organisation with MS
Project Professional if I was to implement this solution (over 3000 people).
Is this correct? We are happy to purchase licenses for those who use MS
Project Pro. Any suggestions how to set things up so that we comply with MS
licensing requirements?

Regards,

Adam

That's incorrect Adam.

Here is the License Terms for Project 2003 Professional and Standard
Editions

A. Standard License Terms. You have the rights below for each license
you acquire.
I) Installation and Use Rights.
a) Licensed Device. The licensed device is the device on which
you use the software. You may install and use one copy of
the software, any component product of the software, and any
prior Microsoft version of the software on the licensed
device. Except in the case of remote assistance, only one
user at a time may use these copies.
b) Portable Device. You may install another copy on a portable
device for use by the single primary user of the licensed
device.
c) Network Device. You may also install one copy on a network
device. You may only use that copy as described in the
Remote Access section below.
II) Additional Licensing Requirements and/or Use Rights.
a) Remote Access. You may access and use the software remotely
from another device as described below.
* Primary user. The single primary user of the device
hosting the remote desktop session may access and use
the software remotely from any other device. No other
person may use the software under the same license at
the same time except to provide support services.
* Non-primary users. Any user may access and use the
software remotely from a separately licensed device.
* Remote assistance. You may allow other devices to
access the software to provide you with support
services. You do not need additional licenses for this
access.

You can download the Microsoft Licensing Product Use Rights document at:
http://download.microsoft.com/download/a/5/f/a5fc3270-2fe6-4536-b228-
6b333ab8569d/PUR_Oct2005.doc
OR
http://tinyurl.com/cq254

Here's some additional licensing info on Terminal Server you'll need to
know:

There are two types of Terminal Server Client Access Licenses are
available: TS Device CAL or TS User CAL.

From the FAQ About Terminal Services:

Q. What license do I need for non–Microsoft products such as Citrix
MetaFrame?
A. You need a Terminal Services CAL for each device; in addition, each
server must have a Windows CAL for each connection. Because
non–Microsoft products run on top of Terminal Services, you need the
same licensing as always, plus any additional licensing for the third-
party software.

http://www.microsoft.com/windowsserver2003/community/centers/terminal/te
rminal_faq.mspx#ERF
OR
http://tinyurl.com/66ef7


Here's a list of Microsoft links that describe the licensing issues with
Windows Server 2003 Terminal Server:

Licensing Terminal Server in Windows Server 2003
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/ts2003.msp
x
OR
http://tinyurl.com/feu4

Windows Server 2003 Terminal Server Licensing (Whitepaper)
http://www.microsoft.com/windowsserver2003/techinfo/overview/termservlic
..mspx
OR
http://tinyurl.com/npz4

Windows Server 2003 Terminal Server licensing issues and requirements
for deployment (Good KB Article)
http://support.microsoft.com/default.aspx?scid=kb;en-us;823313

Good Luck

--
Rolly Perreaux, PMP
Project Server Trainer/Consultant

IT Summit Series
Advanced Microsoft Technology Training
http://www.itsummitseries.com
 
A

Adam Hodgson

Thanks for the fast response Rolly!

I will read through all the links ... but if I read this correctly, as long
as the users of the MS Project Professional (accessing through Terminal
Server) have a license then that is all that is required (plus appropriate TS
CALS).

Regards,

Adam
 
R

Rolly Perreaux

Thanks for the fast response Rolly!

I will read through all the links ... but if I read this correctly, as long
as the users of the MS Project Professional (accessing through Terminal
Server) have a license then that is all that is required (plus appropriate TS
CALS).

Regards,

Adam

That's my take on it Adam
Good Luck!

--
Rolly Perreaux, PMP
Project Server Trainer/Consultant

IT Summit Series
Advanced Microsoft Technology Training
http://www.itsummitseries.com
 
A

Adam Hodgson

I read it the same way. Thanks again Rolly.

Is there anyone from Microsoft that reads this forum that can confirm? I
do not want to head down the track, only for my client to be slugged with a
big bill later.
 
R

Rolly Perreaux

A

adam.hodgson

We did not read it the way Microsoft does. After many emails to try
and get a straight answer in writing, this is what I got


"Dear Adam,

Thank you for your response.

Any device that could potentially access the software via Terminal
Services requires a license.

Please feel free to contact us again if you require further assistance
relating to licensing of Microsoft products.

Alternatively for immediate assistance you can contact the Microsoft
Licensing Hotline on 13 20 58 from Monday to Friday, 8.30 a.m. - 5.30
p.m. Australian Eastern Daylight Time).


Thank you again for contacting Microsoft,

Victoria Connell | Microsoft Licensing Specialist | Microsoft
Licensing Hotline | 13 20 58 | (e-mail address removed) "

It makes it impossible for most organisations install TS and comply
with the licensing. Absolutely amazing!! We will not be doing TS.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top