Latest Contributions by PaulDavidson1

The ...../arcgis is typically the default Web Adapter (WA) setting to the ArcGIS server rather than to Portal, but it depends on how your WA that Jonathan mentions is setup. The standard way to Portal is: https://your.FQDN/Portal/home We typically have an enterprise home page (SharePoint in our case, or whatever CIM you're using) and we just direct all users through that via links to a variety of GIS landing pages, including Portal, along with links to all our other apps, etc.. In this case, we don't really care what or how long the URL is because the end users could care less. We discourage them from creating any shortcuts and/or custom links. Teach them to click a standard access point and support headaches go down. This allows us to change actual URLs, such as when migrating to a new server with a new ArcGIS version. Keep both old and new going at once and once the new is ready, swap out the landing point and it's seamless to end users. Sounds like you want to use a shorthand for redirect to .../portal/home? If you're using the IIS WA, then it looks like Jonathan has provided nice links for that info. I imagine that works about as well as the above but it still means end users having to know a URL and get it right vs. just a click. Hope that helps. PS - one note, I have had issues with going back and forth between https and http in Portal.  Seems best to just pick https and use that. If you go back to http, it seems that you often still get redirect to the https at various time when in the admin/configuration sections of portal but it's been awhile since I've messed with that. This was in 10.4.1  Haven't pulled the 10.5.1 plug yet, too busy with other stuff.  But 10.5.1 features look so very useful. ... View more

My experience is that Portal handles this behind the scenes for you when you flip it into secure mode. To get to the server might require that it be in ssl only mode? -Paul Davidson ... View more

There is also the 64bit background processing library. I haven't used it yet but I probably should. Lot of overhead with Model Builder. You're inside ArcMap, then inside a Model, then calling out to Python, etc... In your case, maybe not a big difference since like you said, you're really just calling one tool. But if that we're available in 64bit, that might make a difference. Remember also that from Model Builder, you can export the Model to Python. Not the best code you'll ever see and doesn't always run first shot but it will give you a basic structure and all the function calls.  If you haven't done much or any Python, probably a decent way to get into it. The Esri Python course is also well worth it the $1200 or so. I'm like you, I've installed and played with Pro but that's about it. But the Utility Network requires ArcPro so we're going to have to introduce it. ... View more

That time seems "normal." We take about a week to process new flyover data ~ every two years. Jayanta could be right though that Python would speed it up. ModelBuilder seems to inject a lot of overhead. I've seen one big MB tool go from over 60 min to about 6 min when moved into Python. But that had a lot of calls across modules. But, like you say, it's really the one geoproc call for you so... But 64bit in ArcPro might make a difference. Regarding the Imagery Server, have you considered an ELA? Esri offers a Small Gov ELA.  If you can afford it, an ELA is the way to go in my mind. You can quit worrying over licensing (except for named users.) For us, it's money really well spent.  As a utility, we're blind without GIS. ... View more

Have you checked the permissions of the folder holding the linked files? If that doesn’t change anything, perhaps the file permissions of folders (temp and otherwise) in Portal and AGS? ... View more

Rather than 3 Portals, why not use Groups and security measures? There's also the GEO-Jobe tool, Mapfolio, that lets you build different landing pages for different groups. Your sharing the same server & datastore so it sounds like all you want to do is separate out access and sharing? -Paul Davidson ... View more

Luiz:  I have seen the problem of a full disk take down the DataStore server.  I worked a bit with Esri to try to recover the server but in the end, it was easiest to do a new re-install. DataStore can chew up space, especially with its default backup settings (at least in 10.4.1) I have since put monitors on the servers to alert when disks are reaching certain capacities. ... View more

Portal works well for what you want with the exception of fully public maps. But that's what AGOL is for. To let all users inside your firewalls access maps, you just share them to everyone and make sure you have anonymous access allowed.  Of course, any user inside your firewall should already be authenticated on your network.  And the general public shouldn't be allowed inside your firewalls so the term "everyone" on a Portal means everyone in the company. This get trickier if you really want to publish public maps for the general population. Your best bet is to publish those maps to AGOL.  Again, published to everyone with anon access allowed. And in this case, you're really publishing to everyone. If you're going to allow the general public inside your firewalls, chances are you're going to be up against it with your IT guys.  It would mean punching a hole in your firewalls that would destroy your security. I understand that you can do this by standing up a Portal out in a DMZ zone.  Then you have to deal with proxies, etc  in order to securely communicate with your internal Portal. This is not a trivial setup. Without a really compelling reason, it seems to me that AGOL is the obvious solution for any public facing maps. I have a hard time even thinking up a scenario where I'd want to publish for the general public and not do it on AGOL. Especially with the new 10.5.1 communication methods across Portals, AGOL, etc... Best of luck, hope this helped some. -Paul ... View more

Hi Colin: I would think that your idea of swapping Test and Prod back and forth via a DNS map could be very problematic. I would think you're better off using a migration tool like Jake has shown to move Test up to Prod. That is the standard development method.  Well, standard is typically Dev/Test/Prod with maybe an Acceptance box for some systems. If you're the only one ever using Portal, maybe you could make that work.  I couldn't, I'd forget where I was. But in a true Portal environment, you have lots of users doing things.  Before you swap that Prod box to test, you have to migrate that work to Test  so you can swap it to Prod, etc....  While you do that, more things can be going on in  Prod.  Seems problematic...  Maybe I didn't follow your intent? ... View more

Create a group for your feature content.  Add to the group what items you want shown. You have to set permissions for appropriate sharing of those items. Go to My Organization>Edit Settings>Gallery In Show in Gallery, select the new Group you created above. ... View more

Thanks, I wish more folks would share trials and tribulations.  Have you considered the Esri Chef Cookbooks for deployment and upgrades?  They have proven very useful for us.  Haven't, we haven't jumped 10.4.1 to 10.5.1 yet.  If you ever have the chance to move into a VM world for your servers, it could save you a lot of headaches.  You can snapshot before making changes so it's an easy recovery.  Easier to setup and rebuild servers, etc... and makes it easier to setup a Test environment so you hopefully work through these pains before upgrading Production.  Thanks again! ... View more

Google: esri portal config.js You may find some options there to do what you want. You won’t change the look and feel of the log in box, but you can set a header line that can help users distinguish where they are logging in. Make sure you have a backup, know what you’re doing in .js, etc…. I suspect this is a good way to really hose up your portal if you’re not really careful. Probably also a way to void a warranty with Esri. However the info is published in Esri’s help so…. ... View more

The timer indicates the page is still loading. Did you give it enough time to finish? Wait for a time out message. Did you log in using HTTPS? If not, try that. No or slow response can be many reasons. Assistant is a cloud based SAS. Could be a hiccup there, could be your end. Make sure you have other internet access. Try it again later in the day? -Paul Davidson ... View more

I'd imagine because a patch can sometimes be a lot easier to apply than doing an upgrade! ... View more

Thanks for the info Jonathan.  ... View more