Latest Contributions by AngusHooper1

FYI - answered here https://community.esri.com/thread/239463-how-to-install-docker-desktop-on-windows-for-notebook-server-on-windows-2016. You need to use Docker Desktop 2.0.x not the current release of 2.1.x. ... View more

Unfortunately, installing Docker Desktop 2.1.0.1 on Windows 2016 fails as the docker installer reports 'Installation failed: one prerequisitie is not fulfilled. Docker Desktop requires Windows 10 Pro or Enterprise version 15063 to run.' This error message aligns with the Docker documentation that Desktop requires windows 10 to install. ... View more

So to confirm, Engine is required if you are deploying Notebook Server onto a windows 2016/2019 machine? ... View more

Just to expand on this point, if Docker for Desktop is documented (by Docker) as only being available/supported for Windows 10, how can we deploy ArcGIS Notebook Server on a Windows 2016/2019 server? The Esri documentation references Docker runtime 17.0+ as the supported version which does not align with "Docker for Desktop". ArcGIS Notebook Server system requirements—ArcGIS Enterprise system requirements | ArcGIS Enterprise  Then, the Esri documentation references Docker for Desktop as the avenue for getting Docker Engine which is required. Install Docker for ArcGIS Notebook Server—ArcGIS Notebook Server Installation Guide (10.7) | ArcGIS Enterprise  Docker for Desktop states that it is only supported for windows 10. https://hub.docker.com/editions/community/docker-ce-desktop-windows Docker Engine Enterprise states that it supports 2016+. Install Docker Engine - Enterprise on Windows Servers | Docker Documentation  So, do we use docker for desktop or docker engine enterprise when deploying Notebook Server onto a 2016/2019 server? ... View more

If you turn on automatic account creation, are accounts automatically created per a ldap user when they hit the portal home page?  ... View more

If this was not happening previously then it is likely that the certificate has expired. ... View more

Exactly. When dealing with the various stakeholders you need to make sure everyone understands the differences between multi-machine site, multiple sites with distinct functions, multiple sites in HA under a NLB etc. Some of these design options may give the desired 'HA' benefit that you are wanting without being a 'true HA' design. For example, a multi-machine site provides some clever workflows for upgrading the site, upgrading underlying OS' and dropping or adding VM's without a perceived outage. This, depending on some audiences, may be the primary reason for a HA design and yet I wouldn't call it actual HA. It's all semantics, but I find the tricky part is unpacking that requirement of 'HA' or 'fault-tolerant' or 'no outages' and then pointing that in the direction of an appropriate design. ... View more

As Moginraj Mohandas‌ said, a multi-machine site is not actually HA. When we talk about failover & HA, we need to talk about it in the context of risk. If you had two distinct AGS sites underneath a NLB, what risk are you trying to mitigate? If the network connectivity drops, failover means nothing. If the data tier drops, failover means nothing. Etc. Active-passive of AGS would only resolve an issue which is inherent to the AGS application tier. And, theoretically, both sites are identical so the issue could also occur in the passive site. I tend to find the argument for HA in the application tier is not strong enough to warrant the administrative overhead when considering how little risk it mitigates. Risk is only comprehensively mitigated when you have a passive site on a completely different domain/data centre with duplicate data holdings etc. ... View more

Just to clarify, this is a design where the hosting server would be active-passive (2 x VM's, 2 x sites)? Or, a hosting server site that is multi-machine (2 x VM's, 1 x site)? ... View more

Great post Scott. In my experience, the hiccup with these workflows is if your environment is fundamentally leveraging the federation & hosting configurations. This is particularly apparent when you have a system that has been in production for some time and you are dealing with old design niggles. As it currently stands, I cannot see how you could possibly migrate a GIS that has a hosting server from one environment to another without an outage. You would need to set the hosting GIS to be in read-only mode as you run a chance of orphaning objects/data edits during the migration proces (e.g. webgisdr). As your migration mechanism (e.g. webgisdr) creates a point-in-time backup of the GIS, no further changes can be made to the live GIS. If you only have a GIS services and registered database requirement, then you are probably fine as these can be static for a short period of time. With regards to old design niggles, something that is quite frustrating is how old server URL's can be baked into almost everything in the GIS. You could potentially get around this with DNS redirect logic, but I would suggest that this is a bandaid and you'll have to comprehensively edit items in the GIS via the python API to point to new URL's. In an ideal world, all your servers have been sitting behind a DNS or load balancer which would help you with the 'swap out' model of Join Site. This is potentially where my team will be moving to, but the first item to tick off is remediating legacy content that references FQDN's. You'll need to make sure that the federated server admin url is pointing through a DNS/load balancer for similar reasons. Any comments/advice for the above? Happy to be proven wrong. It's a topic that many in the GIS community are trying to solve it seems. ... View more

Unfortunately we are using notepad to edit the file, but that's a good line of questioning. Our local is English (Australia). As an FYI, the portal logs (debug) show no records which highlight that this error is occuring within the actual webgisdr executable logic rather than after the GIS is contacted by the tool via the REST api. ... View more

Shared_location has been \\myshare\webgisdr\backup (this fails the export due to escape character handling), \\\\myshare\\webgisdr\\backup (this fails on import with the above error) and //myshare/webgisdr/backup (fails with the above error). ... View more