[p4] How do you handle this situation

[McKenna, Robert]

This sounds more like an accounting problem than a licensing problem,
given that license costs are per seat regardless of how many servers
there are. In our situation we buy a single license for multiple studios
and projects and let finance figure out how to distribute the cost.
There may not be as many users on a given server as are licensed and the
Perforce part of the problem is making sure that the number of unique
users across all servers does not exceed the license seats. One approach
which we use is to create user groups on each server that include all
users in the company regardless of they are using a particular server.
Active users are in other groups specific to the server.


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Ivey, William
Sent: Friday, January 11, 2008 9:44 AM
To: perforce-user at perforce.com
Subject: [p4] How do you handle this situation


We have multiple Perforce servers with their own licenses and user sets

for various teams.

 

The situation now is that some people have been moved from team

to team but are still required to support code they left behind.
Obviously

the old team isn't keen on paying for a license from their cost center
that

might be used for a couple of hours a week or month.

 

Just wondering what others have done in cases such as this before I have

a chat with Perforce licensing.

 

Consolidating all the licenses into one big 'un and using a single
server

to authenticate everyone doesn't appear to be practical at this time
though

it is an attractive idea. (I see P4AUTH is still on the undoc list,
though.)

 

-Wm

 

 

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user