Error during USB Flash Drive Provisioning - Remote Configuration Enable

[idata]

During recent attempt to load our corporate root ca thumbprint onto Dell OptiPlex 755 AMT 3.2.20 systems using USB Flash Drive method via the USBFile.exe utility we enoucntered a failure error during the process referring to a 'Remote Configuration Enable' parameter. The command line used to prepare the setup.bin file loaded onto the flash drive was:

USBFile.exe -create admin /mailto:N3wP@ssw0rd N3wP@ssw0rd -amt -ztc 1 -hash rootca.cer "Corporate Root CA"

The USBFile.exe version was latest publicly available version, v2.1, from the v5.1.1 SDK

In order to get around this problem and load the PKI thumbprint we had to restart the system, enter the MEBx changing the MEBx password, disable the Remote Configuration Enable/Disable** via the menu, wait for unprovisioning, then restart the system and use a new setup.bin containing the new password. This takes almost as long as it does to manually type in and save a new PKI hash.

Is there an easier way around this problem?

[idata]

ChrisF wrote:

During recent attempt to load our corporate root ca thumbprint onto Dell OptiPlex 755 AMT 3.2.20 systems using USB Flash Drive method via the USBFile.exe utility we enoucntered a failure error during the process referring to a 'Remote Configuration Enable' parameter. The command line used to prepare the setup.bin file loaded onto the flash drive was:

USBFile.exe -create admin /mailto:N3wP@ssw0rd N3wP@ssw0rd -amt -ztc 1 -hash rootca.cer "Corporate Root CA"

The USBFile.exe version was latest publicly available version, v2.1, from the v5.1.1 SDK

In order to get around this problem and load the PKI thumbprint we had to restart the system, enter the MEBx changing the MEBx password, disable the Remote Configuration Enable/Disable** via the menu, wait for unprovisioning, then restart the system and use a new setup.bin containing the new password. This takes almost as long as it does to manually type in and save a new PKI hash.

Is there an easier way around this problem?

It turns out that the "-ztc 1" parameter was causing the error to popup. Removing that command parameter resolves the error.