POST
|
You can, but it takes some special configurations. It is documented here in the section called "Use an Esri basemap offline" Take web maps offline—Portal for ArcGIS | Documentation for ArcGIS Enterprise They key is that you must manually create an item "from URL" in Enterprise, connect to the AGO URL for the basemap, and then provide and store credentials to AGO using a built-in account. Share the new item to a group or your Org. Then, users of Enterprise will be able to connect to the AGO item using the credentials that you stored. They must be logged into Enterprise, no anonymous access allowed.
... View more
a week ago
|
0
|
2
|
81
|
POST
|
This makes a lot of sense to me. A non-admin user should not be able to control services they do not own.
... View more
2 weeks ago
|
1
|
0
|
143
|
POST
|
If you are using Azure AD (Entra) via SAML, this will be a setting in the application registration item in Azure. You, or your Azure admin, can choose what to send in the SAML assertion, which will include group membership information. I think it defaults to just security groups but you can tell it to include distribution groups too.
... View more
2 weeks ago
|
0
|
1
|
136
|
POST
|
You can install the web adaptor while the Portal is being upgraded, but you won't be able to configure the new web adaptor until the Portal configuration is completed.
... View more
2 weeks ago
|
0
|
0
|
235
|
POST
|
Thank you @ChrisUnderwood and @JoshuaBixby . None of those things happen on this server (site backups etc) I went to Esri support with this question and was told the temp files are created when a process fails but that there is no way to tell what process created them. While it would be useful to know that, I was hoping to find an answer as to why these "temp" files are persisting for so long. It seems like they should be automatically cleaned up by either ArcGIS Server or Windows OS. Apparantly that is not the case, though, and what we are seeing is expected behavior. So the lesson learned is to check your service account's appdata\local\ temp directory at least a few times per year and clean out the old stuff, or if your C drive suddenly fills up unexpectedly.
... View more
3 weeks ago
|
0
|
1
|
122
|
POST
|
It is the service account used to run the 'ArcGIS Server' service.
... View more
3 weeks ago
|
0
|
1
|
153
|
POST
|
In that case, would a collaboration 'by copy' with two way sync work for you? The feature layer will get copied to Portal, edited there with editor tracking, and the edits will be synced back to AGO by the collaboration.
... View more
3 weeks ago
|
0
|
1
|
203
|
POST
|
I would say that yes, what you want is possible, but not through a collaboration. A collaboration is best used when copying data from one place to another and keeping edits in sync. Sharing by Reference is just a way to add content to the guest that has been added to the host, but since it is by reference you are bound by the authentication and authorization of the host. Instead, you can manually add the AGOL item to your Portal and choose to store the credentials with the item. Then you should be able to edit the data without being prompted to log in. For the stored credentials, you will have to use a built-in account, it doesn't support enteprise authentication. Add a service or document from a URL—Portal for ArcGIS | Documentation for ArcGIS Enterprise
... View more
3 weeks ago
|
2
|
1
|
206
|
IDEA
|
A Distributed Collaboration should synchronize Item details on the guest Portals, not just the data from the feature service, web map, file, etc. A Collaboration will create a new item on the guest Portal and it will have the same Title, Summary, Description,Terms of Use, etc as that of the source item on the host. However, if any of those things change on the Host item, the Collaboration does not recognize it as a change. The Collaboration should sync the Item, not just the Data that the item references. This would be especially useful when using a By Reference workspace in which the Guest Portal item is using the same data service as the Host item.
... View more
4 weeks ago
|
1
|
0
|
122
|
POST
|
Instead of filtering the number of Occupants in the Web Map, you can create a View of your Occupants feature layer and add that to the space planner map. Place the filter at the View level and I think you will have better, more consistant results in Space Planner.
... View more
4 weeks ago
|
0
|
0
|
183
|
POST
|
Our conclusion is that the items do not stay in sync in a by reference Distributed Collaboration. They are only created or deleted. This is based on both direct observations of the behaviour and on a response from an Esri support analyst.
... View more
4 weeks ago
|
0
|
0
|
119
|
POST
|
Yes, that much is clear about the 'by reference' nature as far as the hosted feature layer data goes. Here is what I mean, more specifically. A hosted feature layer is an Item on AGO, with lots of properties like a summary, description, tags, etc., in addition to the URL to the feature service. The Collaboration will cause an identical item to be created on the Portal, pointing to the same feature service. If we change something about that Item in AGO, such as the description text, then the Collaboration should, presumably, see the item was modified and then update the description on the Portal's version of that item. Right? The Items in a collaboration aren't always data, they can be apps, web maps, even PDF documents. In those cases there is no "data" to update other than the properties of the Items being collaborated. This page describes what types of items can be shared in a colloration, and under "files" it calls out that "Item comments are not synced with collaboration participants." So my question, and hope, it that the other properties of the item will stay in sync? So far, when we change the description on the host item we are not seeing that reflected in the Guest's item's description.
... View more
a month ago
|
0
|
0
|
148
|
POST
|
We are protoyping a workflow in which a Distributed Collaboration between AGE and AGO is used to create items in our Portal that will reference the source hosted feature Views in AGO. Since we are doing this 'by reference' and not by copy, there is no sync trigger based on data edits. Besides Hosted Feature View items being added or deleted, what changes to those items will stay in sync? Early testing is suggesting changes in AGO to Summary, Description, Category, delete protection and authoritative badges are not picked up on the Portal side. Haven't tested Metadata changes yet, but that would be something we want, too. Do changes to the *item* properties in a colaboration get synced to the guest, or does the guest just get all of those properties the first time it is created and is then allowed to drift out of sync?
... View more
a month ago
|
0
|
3
|
175
|
IDEA
|
This is a great idea! Bonus points if we can customize the body of the calendar entry as well.
... View more
a month ago
|
0
|
0
|
74
|
POST
|
We are seeing .tmp files in the C:\Users\<account name>\AppData\Local\Temp that are not getting cleaned up. This directory has over 57 thousand files, dating back to Jan 2023. One tmp file has today's date and it over 100 GB in size. It set off monitoring alerts today for using so much space. Two questions, then. Why is the temp file so large and why arent temp files getting cleaned up?
... View more
a month ago
|
1
|
6
|
270
|
Title | Kudos | Posted |
---|---|---|
1 | 2 weeks ago | |
2 | 3 weeks ago | |
1 | 4 weeks ago | |
1 | a month ago | |
3 | a month ago |
Online Status |
Offline
|
Date Last Visited |
Thursday
|