Frequently asked question

What are different licensing files?

Last Published: April 25, 2020

Answer



** Internal Publish Only! This article may contain information that is not intended for external circulation. **



UFFC (Unbound) License File
This is a classified file type intended for use with ArcGIS Desktop/Engine Single Use deployments. UFFC files that do not require a password, are not tied to any host machine, and can be authorized without limit on any system. These files are self-contained authorizations that never communicate to ESRI or consume activations.

UFFC files do not communicate on the network to perform authorization and as such will function within a SCIF or other secured environment without an internet connection.
Unbound authorizations are non-cumulative and will destroy any previous ArcGIS authorizations on a system if applied.
[edit] Authorize ArcGIS Desktop/Engine with UFFC File
Run "C:\Program Files (x86)\Common Files\ArcGIS\bin\SoftwareAuthorization.exe"
Choose: "I have received an authorization file from ESRI and am now ready to finish the authorization process."
Click Browse...
Select "All Files (*.*)" from the file type pull-down menu.
Locate your *.uffc file and click Open.
Click "Next" and "Yes" when prompted.
[edit] Verify a UFFC is Valid
A UFFC file can be verified as valid by attempting to authorize the UFFC file against the product (and version) it was intended for on one's own system (See above). Due to the nature of UFFC files, they will not consume authorizations and such can be authorized without limit for testing.

Some UFFS files have embedded passwords that the user would need to provide to verify the validity of the license.
[edit] UFFC Invalid - What now?
Provide the file(s) to Badri Lakkur (mailto:blakkur@esri.com), cc Gregory Ponto (Implementation Technical Lead) mailto:gponto@esri.com including the details of what you are seeing when you perform your testing on the file(s). Badri can re-generate the licenses if needed.

[edit] UFFS (Unbound) License File
This is a classified file type intended for use with ArcGIS License Manager deployments. UFFS files do not require a password, are not tied to any host machine, and can be authorized without limit on any system. These files are self-contained authorizations that never communicate to ESRI or consume activations.

UFFS files do not communicate on the network to perform authorization and as such will function within a SCIF or other secured environment without an internet connection.
Unbound authorizations are non-cumulative and will destroy any previous authorizations on a system if applied.

[edit] Authorize ArcGIS License Manager with UFFS File
Run "C:\Program Files (x86)\ArcGIS\License10.0\bin\SoftwareAuthorizationLS.exe"
Choose: "I have received an authorization file from ESRI and am now ready to finish the authorization process."
Click Browse...
Select "All Files (*.*)" from the file type pull-down menu.
Locate your *.uffs file and click Open.
Click "Next" and "Yes" when prompted.
[edit] Verify a UFFS is Valid
A UFFS file can be verified as valid by attempting to authorize the UFFS file against the product (and version) it was intended for on one's own system (See above). Due to the nature of UFFS files, they will not consume authorizations and such can be authorized without limit for testing.

Some UFFS files have embedded passwords that the user would need to provide to verify the validity of the license.
[edit] UFFS Invalid - What now?
Provide the file(s) to Badri Lakkur (mailto:blakkur@esri.com), cc Gregory Ponto (Implementation Technical Lead) mailto:gponto@esri.com including the details of what you are seeing when you perform your testing on the file(s). Badri can re-generate the licenses if needed.

[edit] PRVC File
This is not a classified file type, it is a normal Provisioning Client file for use with Single Use ArcGIS Desktop or ArcGIS Engine deployments. Provisioning files are the first step in the authorization process. Provisioning Client files are handled through normal support channels.

Any attempts to use a Provisioning Client file within a SCIF or other secured network that does not have internet access will FAIL. Obtain an ASR or UFFC file instead.
[edit] RESPC File
This is not a classified file type, but instead a "response file" provided by Esri automatically when a PRVC file is uploaded to https://service.esri.com/drm. Once a RESPC file is received, it can be used to complete the authorization process but be aware that RESPC files are node locked to the system that the original PRVC file was used with, and can only be used to authorize that system.

[edit] PRVS File
This is not a classified file type, it is a normal Provisioning Server file for use with Concurrent Use ArcGIS License Manager deployments. Provisioning files are the first step in the authorization process. Provisioning Server files are handled through normal support channels.

Any attempts to use a Provisioning file within an SCIF or other secured network that does not have internet access will FAIL. Obtain an ASR or a UFFS file instead.
[edit] RESPS File
This is not a classified file type, but instead a "response file" provided by Esri automatically when a PRVS file is uploaded to https://service.esri.com/drm. Once a RESPS file is received, it can be used to complete the authorization process but be aware that RESPS files are node locked to the system that the original PRVC file was used with, and can only be used to authorize that system.

[edit] ECP File
This is not a classified file type, it is a normal Server authorization file for ArcGIS Server products. ECP files do not require special intervention, can be authorized on any system an unlimited number of times and can be handled easily through normal support channels.

ECP files can be authorized within an SCIF or other secured network that does not have internet access because an ECP file authorizes ArcGIS Server products without network transactions.

Article ID:000011446

Software:
  • ArcMap

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options

Discover more on this topic