Dell Client manager auto-generated package settings overwritten after each change to the root policy by default settings.
DCM BIOS settings policy, BIOS upgrade policy, and client monitoring policy. Administrators clones the original tasks to their own site folder under Tasks. Before enabling their own task, they go to Tasks > PlatformAdministration > Dell Client Manager > Dell BIOS policies > Internal Autogenerated Items > Task Name > x32 > Bios Settings 32-bit package; under the Package Server tab, they choose to only replicate packages to their own Package Server. When they go back to their own task and enable it, the packages still gets replicated to all Package Servers. Looking in the BIOS settings 32-bit package page, the setting to use individual Package Server was overwritten as soon as they enabled the task.
This is how the product is designed to function.
This is not a bug if the policy is enabled (or reapplied) afterwards as described. The packages are re-created on clicking Apply in the BIOS settings, update, and monitoring policies based on the template package settings. If you want to change package settings
after the policy is enabled you can do it in the internal autogenerated items. If you want any newly created or reapplied policies to use some newly defined default settings, then you need to change default template settings
As we used Software Delivery packages internally for BIOS tasks, BIOS flash, BIOS inventory, and alerts monitoring, we realized there might be a need sometimes for customers to modify package settings to tune it to specific needs customers may have in their environments. Internally we use a "template package" when we produce BIOS Settings and BIOS Update packages. So it should be enough to modify template package settings and from that moment all newly created and existing updated bios settings and bios update policies will generate packages using new settings.
We are hiding template package and generated by policies packages from the user but there are, anyway, many ways to access template package. Here are a couple of them:
As package is a resource, you can see it in resource manager. Here is a URL to access template package: