Open tomy983 opened 1 year ago
E:\iotprovision-bin-2.5.16.140.35>iotprovision-bin.exe -c aws -m mar --force usage: iotprovision-bin.exe [-h] -c {google,aws,azure} [-m {sandbox,custom,jitr,mar}] [-a AWS_PROFILE] [-P PORT] [--fca] [--fdev] [--faws] [--fwinc] [--sprov] [--org ORGANIZATION_NAME] [--rcn ROOT_COMMON_NAME] [--scn SIGNER_COMMON_NAME] [--ssid WIFI_SSID] [--psk WIFI_PSK] [--auth {open,wpa-psk,wep,ieee802.1x}] [--prov CELLULAR_PROVIDER] [--roam] [--bands CELLULAR_FREQUENCY_BANDS] [--cipher CELLULAR_CIPHERSUITES] [--privkey {ecc,sequans}] [-s SERIALNUMBER] [--verify] [-v {debug,info,warning,error,critical}] [-V] [-R] [{all,account,debuggerupgrade,wincupgrade,certs,provision,application} ...] iotprovision-bin.exe: error: ambiguous option: --force could match --force-ca-certs, --force-device-cert, --force-aws-cloudformation, --force-wincupgrade
Figured it out.
this link and also at the bottom of the page point to an older release of the provisioning tool.