Got this figured out. I utilized username and password in the server field as work around; I then downloaded the .bin file and installed it and it worked correctly. So the proper configuration to import into the phone prior to exporting the .bin file is the following:
Code:
#!version:1.0.0.1
static.features.custom_factory_config.enable = 1
static.auto_provision.server.url = https://<UN>:<PW>@<SERVER>.com:<PORT>/<FOLDERNAME>/
Upon factory reset I have it grab an updated configuration that contains the following values:
Code:
#!version:1.0.0.1
static.auto_provision.server.url = https://<SERVER>.com:<PORT>/<FOLDERNAME>/
static.auto_provision.server.username = <UN>
static.auto_provision.server.password = <PW>
auto_provision.reboot_force.enable = 1
This then provisions to the correct username/password combination and directory that you'd like it to pull from. The force reboot makes sure that the phone reboots upon successful provision of this file. After this, it grabs its' new configuration from it's proper directory.
The reason I adjusted it from putting the username:password in the URL instead is for readability; using the same format should still work, just don't set values for the the username and password fields.
For phones that are out in the field already, utilizing the following configurations should work, but keep in mind that you do have to have the file in place already for it to grab after a scenario of a factory reset.
The following configurations do a factory reset of the phone to install the factory configuration file.
Code:
static.features.custom_factory_config.enable = 1
custom_factory_configuration.url = https://<UN>:<PW>@<SERVER>:<PORT>/<FOLDER>/config.bin
Customers that accidentally factory reset phones should be a thing of the past with this! Thanks for all of your guy's hard work with these phones!
Regards,
Zach