Latest Contributions by AngusHooper1

‎08-16-2021

Interestingly I cannot find anything listening on 8081 within our 10.8.1 Enterprise. As outlined in the microsoft doco, there is a bunch of best practise you can use to mitigate this risk. https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-firewall/best-practices-configuring. Ensure your security review considers mitigating mechanisms and is not clear-cut with compliant/non-compliant. As a FYI, I would recommend you install the ArcGIS software to the D drive and leave C to the OS. E drive can then store the site information (e.g. arcgis server directories).

‎08-15-2021

I was wary of doing this for obvious reasons. Is there a specific table or workflow?

‎08-04-2021

ArcGIS Enterprise Portal allows you to set showForgotUsername: false in the config.js and it also allows you to disable the ability for users to create built-in accounts via the portal organisation settings page. What is missing is the ability to disable the "forgot password" interface. Using this interface allows someone to confirm/deny the existence of accounts within the identity store even if that identity is within the built-in store or a 3rd party identity store (e.g. ldap). Is there a mechanism for disabling the ability to reset a password for an account in Portal?

‎08-04-2021

Unfortunately the locks cannot be easily cleared as the python tool errors out due to the scale of locks. It does clear some, but not all.

‎07-11-2021

What is the system locale time for the various VMs that support Portal, hosting server etc?

‎06-22-2021

We have an enterprise geodatabase (AWS Aurora, postgres) that has a significant number of sessions and locks (10,000+). These sessions and locks date back to 8+ months ago. These tables and feature classes are only accessed by cached map services from a multi-machine ArcGIS Server site. All of these map services have been set to use "shared services" in the pooling. Theoretically if everything maxed out we would expect to see 200 concurrent connections to the database via these services. We have tested these services in our dev environment using dedicated pooling and cannot replicate these persistent lock issues. Has anyone else noticed that shared services from a multi-machine ArcGIS Server site not dropping the connection to the database? Our assumption is that when the service is recycled it never truly drops the connection. This is somewhat justified by Aurora never showing 0 connections to the database as there is always the minimum threshold as indicated by our shared service pooling size. update We have been able to replicate the schema locks persisting after the service has been stopped in our dev environment. Only changing the number of shared instances for the ArcGIS Server site cleared the locks.

‎06-15-2021

That looks correct. Keep in mind that the rollback is quite easy, just change it back to machine name. Also, this only applies for Portal for ArcGIS. ArcGIS Server does not allow you to /edit the web adaptor endpoint. In order to achieve the same end result you'll need to reinstall the WA and ensure you access the configuration endpoint via the DNS alias from the local machine when configuring it. This may not be relevant for the recent releases though as the web adaptor config process has been tweaked by the looks of it.

‎06-01-2021

Sorry, yes it should be ALB. When we set the health check to use the web adaptor we generally have no issues and as you have suggested it should be a great way to ensure that both the web adaptor and the site are operational. Since we are using chef to deploy and configure the web adaptor we have certain instances where the web adaptor either doesn't configure at all or it takes a few attempts to configure. During this configuration time or when it doesn't configure at all, any requests that go to https://server.domain.com/webadaptorname/ * will receive an ArcGIS error page indicating that no server machines have been configured with the web adaptor. When viewing this page as a user through a browser it is obvious that it is an error message, however the web adaptor simply sees a 200 response from the ArcGIS error page and marks the instance as healthy. This has resulted in users seeing the above error page as the instance is then put into production. If we just hit the 6443/rest/info/healthcheck we have the same problem of the instance being marked as healthy before the web adaptor has configured. While we have not yet seen a web adaptor fail in our cloud deployment we could envisage a situation where the web adaptor drops its configuration and starts to show the no server associated with this web adaptor but still being marked as healthy as the Esri error page returns a 200 error.

‎05-31-2021

What is the most appropriate health check configuration for ArcGIS Server when using an application load balancer in AWS? The default guidance from Esri (e.g. cfn scripts) is to use the 6443:/arcgis/rest/info/healthCheck endpoint. However this does not take into consideration the web adaptor or issues within the web adaptor / web server tier. Another option would be to use the same endpoint but from :443/webadaptorName/rest/info/healthCheck. However, even if the healthCheck endpoint returns a broken response it is still code 200 and healthy. What would be the best option? I was thinking an export request against sampleWorldCities.

‎03-25-2021

https://support.esri.com/en/technical-article/000012876

Online Status	Offline
Date Last Visited	a week ago

My Ideas

Latest Contributions by AngusHooper1

Re: ArcGIS Server 10.8.1 and port 8081 running Apache Spark 2.4.4?

Re: Shared services and persisting database locks

Disable password reset functionality

Re: Shared services and persisting database locks

Re: Time Zone is incorrect when overwriting existing Feature Services

Shared services and persisting database locks

Re: Changing ArcGIS portal DNS alias post installation -

Re: ArcGIS Server - AWS NLB health check

ArcGIS Server - AWS NLB health check

Re: What causes the following Server Log: Unable to process request. java.io.IOException: Connection reset by peer