A customer (in the case 03903159) has upgraded successfully the satellite and capsules from 6.13 to 6.14. After upgrading they have had issues with the customs repositories, since from the version 6.14 the default policy for customs repositories is disable.

The customer uses two activation keys when registering the hosts, they put them in separated by comma. The first AK is with the customs repositories in disable, the second is with them in enable. In this situation when the client is registered the customs repos came in disable and was need manually put in enable, and inverting the AKs order we managed to register the client with the customs repos in enable by default. In the version 6.13 it didn't happened since the default policy was in enable.

The customer so asked if was possible put an option to define the default policy for customs repositories. It can continue in disable by default, but the WebUi in "Administer -> Settings"  maybe could be possible create an option to define it by default in enable.