License ArcGIS 10.x for classified organizations

Summary

Procedure

1. ASR License File
   
   This is a classified file type intended for use with ArcGIS Desktop/Engine Single Use & Concurrent Use deployments. ASR files require a password, are not tied to any host machine, and can be authorized without limit on any system. That said, the actual data that is laid down on the system cannot be cloned or duplicated (a system authorized by an ASR when cloned will require a new authorization on any cloned systems.)
   
   • ASR 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.
   • ASR licenses are cumulative, and can be authorized against a single product to add authorizations to the product.
   
   Authorize ArcGIS Desktop/Engine with ASR File
   1. Run "C:\Program Files (x86)\Common Files\ArcGIS\bin\SoftwareAuthorization.exe"
   2. Choose: "I have received an authorization file from ESRI and am now ready to finish the authorization process."
   3. Click Browse...
   4. Select "All Files (*.*)" from the file type pull-down menu.
   5. Locate your *.asr file and click Open.
   6. Enter the password you have been provided for use with this ASR file.
   7. Click "Next" and "Yes" when prompted.
   
   Authorize ArcGIS License Manager with ASR File
   1. Run "C:\Program Files\ArcGIS\License10.0\bin\SoftwareAuthorizationLS.exe"
   2. Choose: "I have received an authorization file from ESRI and am now ready to finish the authorization process."
   3. Click Browse...
   4. Select "All Files (*.*)" from the file type pull-down menu.
   5. Locate your *.asr file and click Open.
   6. Enter the password you have been provided for use with this ASR file.
   7. Click "Next" and "Yes" when prompted.
   
   Verify an ASR is Valid
   An ASR file can be verified as valid by attempting to authorize the ASR file against the product (and version) it was intended for on one's own system (See above). Due to the nature of ASR files, they will not consume authorizations and such can be authorized without limit for testing.
   
   Some ASRs have embedded passwords that the user would need to provide to verify the validity of the license.
   
   ASR 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.
   
   
2. 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.
   
   Authorize ArcGIS Desktop/Engine with UFFC File
   1. Run "C:\Program Files (x86)\Common Files\ArcGIS\bin\SoftwareAuthorization.exe"
   2. Choose: "I have received an authorization file from ESRI and am now ready to finish the authorization process."
   3. Click Browse...
   4. Select "All Files (*.*)" from the file type pull-down menu.
   5. Locate your *.uffc file and click Open.
   6. Click "Next" and "Yes" when prompted.
   
   Verify an UFFC is Valid
   An 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.
   
   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.
   
   
3. 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.
   Authorize ArcGIS License Manager with UFFS File
   1. Run "C:\Program Files (x86)\ArcGIS\License10.0\bin\SoftwareAuthorizationLS.exe"
   2. Choose: "I have received an authorization file from ESRI and am now ready to finish the authorization process."
   3. Click Browse...
   4. Select "All Files (*.*)" from the file type pull-down menu.
   5. Locate your *.uffs file and click Open.
   6. Click "Next" and "Yes" when prompted.
   
   Verify an UFFS is Valid
   An 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.
   
   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.
4. Non-Classified License File Types
   
   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.
   
   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.
   
   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 a SCIF or other secured network that does not have internet access will FAIL. Obtain an ASR or an UFFS file instead.
   
   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.
   
   ECP File
   This is not a classified file type, it is a normal Server authorization file 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 a SCIF or other secured network that does not have internet access because an ECP file authorizes ArcGIS Server products without network transactions.
   
5. "Alternative" Offline Authorization
   Classified organizations needing to perform authorizations without the use of a classified license file have historically made use of a workflow known as the "Alternative" Offline Authorization. Recent updates to the licensing model have made this method all but impossible to perform and is not supported under any circumstances regardless of the nature of the organization.
   
   The workflow has been preseved under "Alternative" Offline Authorization for archival purposes only. This method of authorizing ArcGIS is not supported under any circumstances.