Derek:
Thanks for taking the time to help clarify all of this.
Would you say the following is accurate?
I have put a few questions I'm not 100% on in italics :
- Consider Portal and AGOL as two separate products requiring two separate sets of licenses.
Once you do that, it's much easier to get a grip on the licensing.
- Regarding Named Users (ELA exception below), you get a 1:1 Named User license for each Desktop seat.
Doesn't matter what Desktop level you are licensing, it's 1 seat = 1 Named User. (is this true?)
For example:
50 Advanced (ArcInfo) Concurrent seats = 50 Named Users
5 Basic (ArcView) Single Use seats = 5 Named Users
These Named Users are included in the cost of the Desktop licensing.
- Each Named User can be applied to Portal or to AGOL but not to both.
You can mix and match if you want.
Given 10 Named Users, you can assign them as X Portal and Y AGOL such that X+Y=10
i.e. A Named User license does not cross over across the two packages. (** see notes below)
- A Named User is for a Single User, there is no concept of Concurrent or Shared Named Users (**)
You can't create a generic Named User for some group of users.
If you need or want more Named Users then you buy them in packs of 5, 50 or 100
As an aside, in my mind: Unless you are having AGOL host your imagery or using it for massive geo processing, credits are an insignificant drop in the bucket.
- I assume Portal does not consume credits similar services since we're standing it all up? True as long as we're not going out to AGOL for Geocoding or similar AGOL hosted capability.
- If you're on an ELA, all bets are off and you have to talk with your account manager.
That shouldn't really be a surprise because ELAs tend to be unique and individually negotiated.
(**) Notes:
As many things Esri, there is some flexibility in all of this.
For example, you start off using AGOL then decide you need to be using Portal.
You probably have a pretty good chance of getting your AGOL Named User licenses transferred over to Portal.
Maybe you have a lot of Named Users in a Portal setup but need a few AGOL licenses to publish open maps? Best to be on good terms with your account rep.
The one exception to No Shared Named Users is if you are Accessing AGOL Services via custom code, say a Silverlight web site. Then you access AGOL via a token/authentication scheme. In a sense, your website is acting as the Named User. This will consume credits at the normal usage.
Accessing ArcGIS Online Services | ArcGIS for Developers
Regarding: You can't create a generic Named User for some group of users.
We could argue this licensing all day, but this is what it is.
I would like to have a generic login for certain classes of mobile users.
For example, line spotter and other field workers at our Utility.
There are a lot of them, they have turn over.
But each one of them requires a separate named user account.
C'est le Vie
===========
Does that cover the basics? 🙂
There is one area I'm still not clear on. (Actually, I think I am clear, I just don't like it.):
The 1:1 Named User licenses are designed to be given to desktop users.
The N licenses our ELA gave us with ArcPro's introduction can't be used for users who are strictly mobile.
These Named Users are for desktop users, for ArcPro.
