Latest Contributions by JoshuaBixby

Yeah, changing the licensing level from Advanced to Basic was a bit excessive.  It is a trade-off going from Advanced to Standard, but going to Advanced to Basic really devalues the award/reward and personal use program. ... View more

I can't endorse/support this idea enough, any enterprise platform today needs to support multiple identity providers of the same type.   ... View more

@BrittanyLe , something the ArcGIS Pro Early Adopter program staff/teams do is send e-mails directly to former participants when new opportunities open.  That doesn't appear to happen with ArcGIS Enterprise, at least it never has with me.  Although I am regularly on Esri Community and usually see these kinds of announcements, relying solely/mostly on this announcement to notify folks isn't casting the widest net if engagement is what the product team wants during beta development and testing. ... View more

Are you using esriGeometryAny because you won't know ahead of time whether the geometry will be polygon?  For testing purposes, does the following work? IGeometry geometry = this.jsonConverter.toGeometry( jsonObject, esriGeometryType.esriGeometryPolygon, false, false ); ... View more

There are several registry entries related to licensing, not just AUTHORIZATION_TYPE.  My recommendation would be to delete the following registry keys under HKEY_CURRENT_USER, doing so will reset the CONCURRENT_USE licensing for that user and prompt a user to login to a Portal or arcgis.com to get a Named User license.  AUTHORIZATION_TYPE LICENSE_SERVER SEAT_PREFERENCE SOFTWARE_CLASS_FN All the keys but AUTHORIZATION_TYPE will be recreated for the user and set to default.  Since the AUTHORIZATION_TYPE default has been NAMED_USER for a while now, it likely won't even get re-created. NOTE:  Like anything involving registry changes, either backup the registry key involved or make sure you validate on test machines before deploying. ... View more

If you run into issues with vertical scaling, one area I have seen people run into problems is managing memory, both physical and virtual, at the OS level.  ArcSOC processes have a surprisingly large virtual memory footprint relative to their physical memory use, and when scaling RAM up to accommodate more services, I have seen virtual memory sizing and use become a problem.  Without knowing a lot more details about the application and OS configuration and spec's, I can't really offer any specifics.  ... View more

Another aspect of why vertical scaling makes sense more than horizontal is licensing.  I have always worked in large government organizations that deploy lots of what I refer to as "big brother" software, i.e., configuration management software, security software, monitoring software, etc....  Don't get me wrong, these types of applications are needed in today's environments whether they are small business or large government.  As needed as they are, they consume resources and increase the amount of resources a machine needs compared to an idealized, bare-bones OS. For a previous organization I worked for, the rule of thumb was the first 2 vCPU were basically throw-away vCPU to support running all the big-brother software.  This was more to do with poor management of the software by operations teams than the software itself.  So, if capacity planning shows you would want 4 vCPU for a VM, we always spec'ed 6 to ensure the application would always have roughly 4 vCPU worth of capacity available.  ArcGIS Server (not Portal, but Server itself) is licensed per core.  Unlike some enterprise software like SQL Server where the cores can be set in the application, ArcGIS Server licenses all the cores on a machine. For situations like the one I describe where a certain number of vCPUs are set aside for other operations software on the machine, and yet those vCPU are still licensed for ArcGIS Server, horizontal scaling drives up licensing costs much quicker than vertical licensing because each new machine has those marginally used but still licensed vCPUs whereas adding more cores to an existing machine allows having the application use all those new cores. Regarding @Scott_Tansley comment about segmenting workflows into other ArcGIS Server sites, I agree, at least for medium to large customers.  Each type of GIS service has its own unique patterns of use, both from the end-user consuming the service to the service consuming machine resources, and mixing them in large numbers often results in resource utilization and contention issues and capacity planning headaches. ... View more

I agree with @MichaelVolz .  ArcGIS 10.8.1 is fully retired in 2 months, 08/01/2026.  Besides the imminent retirement of that version, there are also practical issues you will run into.  Although it may technically work, trying to publish GIS services from ArcGIS Pro to older versions like ArcGIS 10.8.1 will lead to problems.  You won't be able to publish GP services, and there is risk of corrupt or unexpected results in map and image services. ... View more

I agree that ArcGIS Enterprise Functionality Matrix doesn't do a good job of explaining ArcGIS Enterprise Kubernetes functionality.  There are statements about ArcGIS Enterprise Kubernetes, but they are more along the lines of "see this" or "see that" for information rather than clearly stating how Kubernetes functionality relates. That said, it seems like a simple question being asked, but it is hard to answer without knowing more of what you are really after.  For example, since ArcGIS Enterprise on Kubernetes can federate with regular ArcGIS Server deployments, one needs to know whether someone's requirement is to only deploy in Kubernetes or whether a hybrid approach is allowed.  If hybrid is allowed, than a lot more functionality and features are possible. The other complication is that the underlying architecture of deploying ArcGIS Enterprise on Windows or Linux vs Kubernetes is fundamentally different.  Esri may make the REST APIs match, and the browser apps look and function the same, but under the hood they are very differently structured.  Because of this, Esri will sometime use terms like "equivalence" instead of "parity," and they focus more on describing outcomes and workflows than features and functionality when talking about the two types of architecture. Overall, I agree with the sentiment that Esri does not do a great job helping customers understand the difference.  Also, I really don't care for blogs as being "official" documentation, but the "Summary of Supported Functionality" in the What's New in ArcGIS Enterprise 12.0 on Kubernetes blog is about as authoritative as I have seen. ... View more

Browser-based, Web GIS apps built on JavaScript will not "see" fonts installed on servers or local computers.  These kinds of apps stream vector fonts over the web, so simply installing a new font on a machine doesn't make it available to them.  ArcGIS Pro is a desktop app that has direct permission to read standard font files installed on the local machine, so installing a font on a machine does make it available to ArcGIS Pro while not making it available to browser-based, web GIS apps. If you are interested in working with custom fonts for Esri's JavaScript-based apps, it would be good to read Font | References | ArcGIS Maps SDK for JavaScript.  It discusses the format fonts need to be in and where and how the apps look for and get fonts. ... View more

Can you describe your data schema and some examples in text here?  Can you also share the SQL that each query is generating?  A video is better than a screenshot, but I personally won't usually take the time to watch a video, and I am guessing there are plenty others on the forum that do the same, or don't in this case. ... View more

Assuming the context manager change with cursors was partially, or hopefully, driven by improving lock handling; I am a supported of the change.  Regarding resetting a cursor, although instantiating a new cursor may be the right decision, existing cursors can be re-used within a context manager.  That is, one doesn't have to create a new cursor if they want to reset a cursor and re-use with a context manager. ... View more