Please keep in mind that the use of the "Persist across cold boot?:" option has always been discouraged for a number of reasons.  This is reflected in the MSP 3.3.1 Online Help for the Network.WLAN.FusionPublic Settings, as shown below:

    Note:

    This mechanism is generally is not the recommended     way to make WLAN configuration Persistent.     The recommended method to make a Settings     Object Persistent across a Restore Boot     is to include it in a Bundle Object, as described     in Chapter 7 - Understanding Persistence. Begining with MSP 4.0, this option has been completely removed and can no longer be used.  Ths is reflected in the MSP 4.0 Online Help for the Network.WLAN.FusionPublic Settings, as shown below:

Cold Boot

    The Fusion Public setting used to provide an option     called "Persist Across Cold Boot". It is no longer     available due to the fact this mechanism is not the     recommended way to make a WLAN configuration     Persistent. The recommended method to make     a Settings Object Persistent across a Restore Boot     is to include it in a Bundle Object, as described     in Chapter 7 - Understanding Persistence.     If you use an existing Fusion Public setting with     the "Persist Across Cold Boot" set to TRUE     and it is saved in MSP 4.0 or later then the     Cold Boot Persist option will not be visible and it     will be automatically set to FALSE. This means     that the settings will not be persistent when     applied to a device unless the recommended     method is used as described in     Chapter 7- Understanding Persistence. For more explanation on why the "Persist across cold boot?:" is a poor choice and why the recommended approach is better, see the referenced chapter. In short, the recommended approach is to NOT select the  "Persist across cold boot?:"  and to instead apply the WLAN Settings via a Bundle, which will cause them to be reapplied automaticallty following a cold/clean reboot.  And, since the Fusion Plug-In will power on the WLAN Adapter if it is powered off when Fusion Settings are applied, it will also elliminate the need for the Registry setting.

Sorry for this late reply. As a follow up, if you are using an MC9190 it has Fusion 3.x.  In order to configure a Fusion 3.x unit WLAN setting using MSP , you should be using the Fusion30 Public setting (although the Fusion Public will still work). The Fusion30 Public setting does not have the "Persist across cold boot" parameter.

Justin, you should always try to mitigate the number of cold boots performed on a device. That being said if you put the setting in a bundle and have it installed as a setting it should be reapplied after a cold boot. If you are still having issues or need further assistance please open a case with the support center and we can assist you further.

Hi David Thanks for the response. Always try to educate the end user on boot procedures, but unfortunately there are going to be cases when they don’t listen J

I made a mistake on the original post. The WLAN profile is persistent, however with the MC9190 and 3190 upon a cold boot the WLAN adapter is disabled and you have to apply the following registry key.

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WLAN]

"InitialState"=dword:0

It would be good if the Cold Boot persistence in MSP automatically applied this registry instead of having to add in another step in the process. When I have tried to build using the package registry template that contains the key above it copies to the Application\Airbeam folder and sends an abmerge.exe command from the Temp folder, but the registry key does not get applied.

Further testing today and we have now resolved this issue. Regards Justin