Open pcsswamin opened 2 years ago
Hi @pcsswamin,
With -Mode InstallLicense
and -Mode InstallLicenseConfigure
the ArcGIS Module passes in the provided license file from ConfigData.Server.LicenseFilePath to the ArcGIS Server software authorization wizard which performs a silent authorization. For example:
<System disk drive>\Program files\Common files\ArcGIS\bin\SoftwareAuthorization.exe /S /Ver 10.8 /LIF <path to .prvc authorization file>authorizationfile.prvc
I suspect this very well could be a limitation with .prvc license files. You may need to instead use a .ecp license file.
Thanks, Cameron K.
@cameronkroeker - Could you confirm that internally? Lot more customers are probably facing the same as well.
@cameronkroeker - Could you confirm that internally? Lot more customers are probably facing the same as well.
Hi @pcsswamin,
Yes, I have confirmed this is a limitation with the software authorization wizard and .prvc files.
Thanks, Cameron K.
Hi - @cameronkroeker also just hit this using a .prvc file - can the license path be updated to an array so multiple prvc files can be authorised? Thanks
Possible duplicate ? https://github.com/Esri/arcgis-powershell-dsc/issues/131
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Community Note
Module Version
3.3.1
Affected Resource(s)
ArcGIS_Server
Configuration Files & Actual Behavior
This is a request that could possibly be satisfied by more clarifying documentation or may result in an enhancement request if there is a functionality gap.
In past versions of the ArcGIS module, I have found that if I use a single license file that contains the license codes for certain roles/ extensions for Stand-Alone ArcGIS Server (like Image Server or Network Analyst), only the base ArcGIS Server is licensed or more precisely only the first license code is used. I have had to run the licensing configuration again to get the role or extension to be activated on the same node.
It adds several additional steps to create separate license files for each role/extension? and doing it for several environments makes it quite onerous.
Is this still true?
Expected Behavior
All licensed features in a license file for ArcGIS Server should be detected and activated on the concerned node when the license mode of the DSC configuration is invoked.