I added to this post some time ago about my amazement that Pro was missing the same functionality that existed in ArcCatalog. Having now used Pro to publish my services, the publishing options appear to be missing the ability to define the service recycling time and the service timeout values. This means after publishing a new service from Pro to ArcGIS Server, I then have to open Server Manager, edit the service I've just published in order to set these values and cause the service to restart as it saves. I've just published 60 services on my new 11.1 ArcGIS Server and it's not been a fun process going into Server Manager after each publish to set some extra values. Why is this missing from Pro, this was a simple thing in ArcMap? If you can do it from Pro at the time of publishing and I've missed it, then it's very well hidden.
I'm going to miss this year's UC but those who go should go down to the ArcGIS Server island/desk and push the point. The UC is an opportunity to engage with some of the top ESRI people who probably aren't following this thread and consider their decision a done deal. Also, there is the Closing Session.
Having upgraded to AGS 11.1 we can not longer manage Map Services through ArcCatalog. This means we can no longer quickly stop and start map services. This really sucks. ESRI, please add this ArcCatalog functionality to ArcGIS Pro!
Those following this thread and going to the UC consider stopping by the appropriate ESRI area and pleading our case 🙂
We're well past the three-year mark on this Idea and it's still marked as "Open". Administering our map/feature/etc. services via the Server Manager webpage is clearly ponderous and time-consuming relative to the capabilities we had with ArcCatalog.
Esri, what's the status on this Idea? Why is it still marked as "Open"?
This is really important functionality for us. It is absolutely a waste of time to have to go out of the application to stop a service when managing the database. I believe future Pro development needs to be concentrate more on the DBA side of things, instead of the end-user.
Recently discovered this missing capability from Pro and your toolbox looks like it will fill the gap perfectly. Would you still be willing to share this toolbox?
