An ArcGIS administrator executes a script to silently upgrade all components of ArcGIS Enterprise version 10.6.1 to version 10.9.1. The upgrade completes without logging any errors.
When the administrator logs in, the following message appears: "Members in your organization were assigned the Standard (Temporary) or Lite (Temporary) user types. No users can log in to the Portal."
What is causing these issues?
During the upgrade from ArcGIS Enterprise 10.6.1 to 10.9.1, user type licensing is enforced. If the new license file includes more than one compatible user type (e.g., Creator and GIS Professional), existing members without a specified user type may be assigned temporary user types like 'Standard (Temporary)' or 'Lite (Temporary).' These temporary assignments prevent users from logging in until valid user types are manually assigned.
This issue is not related to internet access (Option B) or the need to restart services (Option C).
Reference Source: ArcGIS Enterprise documentation on user type licensing during upgrades
An organization wants to use the standard feature analysis tools available in ArcGIS Enterprise to create hosted feature layers for planning and design.
Which data store is required for this work?
The standard feature analysis tools in ArcGIS Enterprise (e.g., buffer, overlay, aggregate points) require hosted feature layers, which depend on the relational data store (a component of ArcGIS Data Store). The relational data store is the default location for hosting feature layers.
From ArcGIS Enterprise documentation:
''To use the standard spatial analysis tools and create hosted feature layers, the ArcGIS Data Store (relational) must be configured and set as the default hosting location.''
Option A (spatiotemporal big data store) is used for real-time and big data feeds, not standard analysis.
Option C supports cached tiles, not feature layers.
ArcGIS Enterprise -- Configuring the Relational Data Store for Hosting Feature Layers
=====================
A GIS administrator publishes a feature service that references user-managed data. The administrator wants users to add new features. Users should not make changes to attributes of existing features or delete features.
Which feature service operations should be set?
To allow users to add new features without the ability to modify or delete existing ones, the feature service should have the 'Create' and 'Query' operations enabled. The 'Create' operation permits users to add new features, while the 'Query' operation allows them to view existing features. By not enabling the 'Update' and 'Delete' operations, users are restricted from making changes to or removing existing features. This configuration is ideal for workflows where data integrity is crucial, and only the addition of new data is permitted.
Enabling 'Update and sync' (Option A) would allow users to modify existing features and synchronize changes, which is not desired in this scenario. 'Extract and create' (Option C) is not a standard combination of operations for controlling editing permissions in feature services.
Reference Source: ArcGIS Server documentation on editor permissions for feature services
An organization recently upgraded Portal for ArcGIS. The organization must reduce the number of named users to the maximum allowed by the authorization file and delete members in bulk.
Which action should the administrator perform?
An organization's portal license file provides for 30 Editor user type and 15 GIS Professional user type licenses. After performing a needs assessment, the GIS administrator discovers that the organization requires 10 Viewer, 40 Editor, and 20 GIS Professional user type licenses.
When downloading a new license file, how many of each user type license should the administrator specify?
When downloading a new license file from My Esri to accommodate the organization's user needs, administrators should request the exact quantities identified in the internal needs assessment:
10 Viewer
40 Editor
20 GIS Professional
These quantities will be used to generate the new license file, which reflects the actual number of entitlements needed. Esri licensing is flexible in this regard, and the administrator can request different counts per type within their entitlements.
From the ArcGIS Enterprise Licensing documentation:
''When generating a new license file for your deployment, you can specify the number of each user type and role needed. The license file will reflect these values, and must match the needs of your organization.''
Option A provides insufficient licenses.
Option B omits the necessary Viewer licenses.
Option D reflects original entitlements, not the updated requirement.
ArcGIS Enterprise Administration -- User Types and Licensing Model
Gennie
4 days agoRueben
11 days agoReita
19 days agoIvette
26 days agoLashandra
1 month agoLang
1 month agoAshlee
2 months agoCassie
2 months agoSkye
2 months agoWhitney
2 months agoTijuana
3 months agoYvonne
3 months agoErnie
3 months agoSelma
3 months agoScarlet
4 months agoDenise
4 months agoXochitl
4 months agoElouise
4 months agoGlendora
5 months agoShaquana
5 months agoLang
5 months agoClaudia
5 months agoGlory
5 months agoLizbeth
5 months agoMabelle
6 months agoIrma
6 months agoIlene
6 months ago