Licensing Question

[dc]

I have tried to figure out what I need to run Project 2003, it seems
the more I read the more 'notes' appear saying i need something extra.

My understanding is thus :

Project Professional 2003 - for setting up / main control of the
projects. Includes 1 CAL for connecting to Project Server

Project Server 2003 5 CAL - so I can publish the projects from above,
and allow 5 people to connect via Project Web Access 2003.

Now I get a bit confused.

I was planning on having a DB server with Windows 2003 Server Standard
and an web server with Windows Server 2003 Web Edition.

The DB server to have SQL Server 2000 installed (standard).

Would I have to install Project Server onto the DB server and therefore
give access to the DB server to people using 'Project Web Access', or
can the 'Project Web Access' go to the web server, with Project Server
installed on the DB server?

Do I need any extra CALs for either of the Windows Server machines or
the SQL Server 2000 installation? ie one for each Project 2003 user?

Thanks in advance
Dave

 

[JackD]

The web server talks to the db. The clients do not.
The Web Server and DB server do not need licenses to "talk to each other".
Basically you need one CAL for each person who are using Project Web
Access.

You can run both the web and database servers on the same machine if
necessary.

 

[DC]

Thanks for your reply. On this page :
http://www.microsoft.com/office/project/prodinfo/faq.mspx it says :

The EPM Solution consists of the following Project 2003 products, each
of which is sold separately:

·Project Professional 2003 (includes one Microsoft Office Project
Server 2003 Client Access License [CAL])
·Project Server 2003 (includes five Project Server 2003 CALs through
retail)
·(Optional) Project Server 2003 CALs-User or Device (to use Project
Web Access, which is enabled by Project Server 2003)
·(Optional) Project Server 2003 External Connector

Note The solution also requires:
·Windows Server 2003 and Windows Server CALs.
·Windows SharePoint Services (a component technology of Windows
Server 2003) for file management, and issue and risk tracking.
·Microsoft SQL Server 2000 and SQL Server CALs.

It's this last bit that I am confused about. We have a single CPU SQL
Server 2000 license, and a standard Win2003 Server instalation. When
it says I need SQL Server CALs, does it just mean I need the licensed
software installed, or does it mean that if I have 5 users connected to
Project Server, which is hooked into SQL Server 2000, then I need 5
CALs for SQL Server 2000 ?

 

[JackD]

I'm fairly certain that if you have a licenced SQL and Windows Server
software and the correct CAL's to access it before installing Project
Server, that adding Project Server will not require additional CAL's. If you
are in doubt, contact Microsoft directly for a clarification. I do not speak
for them.

--
-Jack ... For project information and macro examples visit
http://masamiki.com/project

..
Thanks for your reply. On this page :
http://www.microsoft.com/office/project/prodinfo/faq.mspx it says :

The EPM Solution consists of the following Project 2003 products, each
of which is sold separately:

·Project Professional 2003 (includes one Microsoft Office Project
Server 2003 Client Access License [CAL])
·Project Server 2003 (includes five Project Server 2003 CALs through
retail)
·(Optional) Project Server 2003 CALs-User or Device (to use Project
Web Access, which is enabled by Project Server 2003)
·(Optional) Project Server 2003 External Connector

Note The solution also requires:
·Windows Server 2003 and Windows Server CALs.
·Windows SharePoint Services (a component technology of Windows
Server 2003) for file management, and issue and risk tracking.
·Microsoft SQL Server 2000 and SQL Server CALs.

It's this last bit that I am confused about. We have a single CPU SQL
Server 2000 license, and a standard Win2003 Server instalation. When
it says I need SQL Server CALs, does it just mean I need the licensed
software installed, or does it mean that if I have 5 users connected to
Project Server, which is hooked into SQL Server 2000, then I need 5
CALs for SQL Server 2000 ?

 

[John Sitka]

SQL if licenced by way of one of the 'per device' or 'per user schemes' needs additional CALS
even if the only connection is by the web. Each web user needs an SQL CAL,
One might speculate (price dependent) on a break even point of say 25 users of an SQL enabled web for
single processor SQL or 50 users of an SQL enable web for dual processor SQL machine to provide
SQL services to an enterprise.
Most SQL servers providing data to web servers will get an SQL processor licence as hopefully your web is
being used by many people to the point where you don't even know how many!

Another way to look at it is for each device/user that gains functionality from SQL.
there is a needed SQL CAL
"OR"
a processor(s) licence.

Web server talks to SQL but if SQL is "NOT" 'per processor licenced' Then each SQL CAL must
be in place for each web user, and I don't mean IUSER.

The SQL per processors licence allows any number of unknown devices or users
in whatever fashion.

I've poured throught this a lot and hopefully I'm not misleading.
Basically unless you can gaurentee a very limited web access base on an SQL backed
web site you need 'per processor' licencing.
In a brick and mortar situation you can look around and see that "only these folks"
derive any kind of SQL functionality. If the number is small then SQL CAL licencing can work.

I'm fairly certain that if you have a licenced SQL and Windows Server
software and the correct CAL's to access it before installing Project
Server, that adding Project Server will not require additional CAL's. If you
are in doubt, contact Microsoft directly for a clarification. I do not speak
for them.

--
-Jack ... For project information and macro examples visit
http://masamiki.com/project

.
Thanks for your reply. On this page :
http://www.microsoft.com/office/project/prodinfo/faq.mspx it says :

The EPM Solution consists of the following Project 2003 products, each
of which is sold separately:

·Project Professional 2003 (includes one Microsoft Office Project
Server 2003 Client Access License [CAL])
·Project Server 2003 (includes five Project Server 2003 CALs through
retail)
·(Optional) Project Server 2003 CALs-User or Device (to use Project
Web Access, which is enabled by Project Server 2003)
·(Optional) Project Server 2003 External Connector

Note The solution also requires:
·Windows Server 2003 and Windows Server CALs.
·Windows SharePoint Services (a component technology of Windows
Server 2003) for file management, and issue and risk tracking.
·Microsoft SQL Server 2000 and SQL Server CALs.

It's this last bit that I am confused about. We have a single CPU SQL
Server 2000 license, and a standard Win2003 Server instalation. When
it says I need SQL Server CALs, does it just mean I need the licensed
software installed, or does it mean that if I have 5 users connected to
Project Server, which is hooked into SQL Server 2000, then I need 5
CALs for SQL Server 2000 ?

 

[John Sitka]

-->>If the number is small then SQL CAL licencing can work.

wrong turn of phrase above. All schemes work, I meant in the terms of
proper adherence to the EULA in the most economic fashion.

SQL if licenced by way of one of the 'per device' or 'per user schemes' needs additional CALS
even if the only connection is by the web. Each web user needs an SQL CAL,
One might speculate (price dependent) on a break even point of say 25 users of an SQL enabled web for
single processor SQL or 50 users of an SQL enable web for dual processor SQL machine to provide
SQL services to an enterprise.
Most SQL servers providing data to web servers will get an SQL processor licence as hopefully your web is
being used by many people to the point where you don't even know how many!

Another way to look at it is for each device/user that gains functionality from SQL.
there is a needed SQL CAL
"OR"
a processor(s) licence.

Web server talks to SQL but if SQL is "NOT" 'per processor licenced' Then each SQL CAL must
be in place for each web user, and I don't mean IUSER.

The SQL per processors licence allows any number of unknown devices or users
in whatever fashion.

I've poured throught this a lot and hopefully I'm not misleading.
Basically unless you can gaurentee a very limited web access base on an SQL backed
web site you need 'per processor' licencing.
In a brick and mortar situation you can look around and see that "only these folks"
derive any kind of SQL functionality. If the number is small then SQL CAL licencing can work.

I'm fairly certain that if you have a licenced SQL and Windows Server
software and the correct CAL's to access it before installing Project
Server, that adding Project Server will not require additional CAL's. If you
are in doubt, contact Microsoft directly for a clarification. I do not speak
for them.

--
-Jack ... For project information and macro examples visit
http://masamiki.com/project

.
Thanks for your reply. On this page :
http://www.microsoft.com/office/project/prodinfo/faq.mspx it says :

The EPM Solution consists of the following Project 2003 products, each
of which is sold separately:

·Project Professional 2003 (includes one Microsoft Office Project
Server 2003 Client Access License [CAL])
·Project Server 2003 (includes five Project Server 2003 CALs through
retail)
·(Optional) Project Server 2003 CALs-User or Device (to use Project
Web Access, which is enabled by Project Server 2003)
·(Optional) Project Server 2003 External Connector

Note The solution also requires:
·Windows Server 2003 and Windows Server CALs.
·Windows SharePoint Services (a component technology of Windows
Server 2003) for file management, and issue and risk tracking.
·Microsoft SQL Server 2000 and SQL Server CALs.

It's this last bit that I am confused about. We have a single CPU SQL
Server 2000 license, and a standard Win2003 Server instalation. When
it says I need SQL Server CALs, does it just mean I need the licensed
software installed, or does it mean that if I have 5 users connected to
Project Server, which is hooked into SQL Server 2000, then I need 5
CALs for SQL Server 2000 ?

 

[DC]

I e-mailed microsoft, they told me it was too complicated to answer by
e-mail and told me to call the licensing department. After several
bouts of "I'll just go check..." I got an answer.

Project Professional (1 CAL - to connect to Project Server )
Project Server (5 CALs - for web access)
Web server : Windows Server 2003 Web Edition (needs nothing)
DB server : Windows Server 2003 Standard Edition (needs 1 CAL for each
user of Project Server)
MS SQL Server 2003 - is ok with the single cpu license.

So basically you pay for Project Server, which needs Windows Server but
you have to pay for extra CALs for that as well.....

Conclusion - too expensive, look elsewhere!

Thanks for your help.

 

[John Sitka]

Good luck in your search, I've listened to soooo
much vendor talk, found some products out there
with big commitments (user and money) and distributed updates
are at the BIG END of big.

It's the SQL processor licence and multiple Project Pro client purchases
that are expensive.

If you have the SQL licence already on a capable server and an existing Windows Domain.

then these are the rough additional costs

Pro is about $800 comes with 1 CAL (evaluate who really needs one)
Project Server is $2500 with 5 CALS

= (1 project manager 5 team/executive members)


additional PWA CALS $30 per web user
2003 Web edition under $800

Not seen anything even slightly close to that anywhere, basically the
only distributed updates (other vendor team/collaboration concepts all come
at substantial add-on cost and footprint.) If you need and are looking for
distibuted updates please post back when you find something.
I looked for almost a year now.

 

[John Sitka]

I'd like to clarify something.
honestly I don't know what the situation is with PWA, it might be an exception to the general SQL specific
treatment of single unauthenticated user providing service to many others.

That is... maybe a single CAL is all that is needed for the PWA to SQL connection??? This only really matters
if your SQL server is NOT licensed per processor. But the more I dig into this stuff the worse it gets.

Sorry for any misdirection.