KNOWN ISSUE: Dell Client manager auto-generated package settings overwritten after each change to the root policy by default settings

Article:TECH36821  |  Created: 2007-11-06  |  Updated: 2007-11-06  |  Article URL http://www.symantec.com/docs/TECH36821
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution

Issue



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 > Platform Administration > Dell Client Manager > Dell BIOS policies > Internal Autogenerated ItemsTask 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.


Environment



Notification Server 6.0 SP3 R4
Dell Client Manager 2.x
Windows* 2003 Server Enterprise, SP1
Microsoft SQL* 2000 SP3

Cause



This is how the product is designed to function.

Solution



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:
    1. As package is a resource, you can see it in resource manager. Here is a URL to access template package:

      http://localhost/Altiris/Resource/ResourceManagerConsole.aspx?ItemGuid=138F1507-DF28-47b2-A4FD-FDB2E7159C6B

    2. Template package, all created packages and some other internal items are created in the folder which is hidden by default. You still can access and view folder content by running a URL like this:

      http://localhost/Altiris/NS/ItemListView.aspx?ConsoleGuid={524C9C33-EE22-4a48-8B20-050120021DB6}&TabGuid=F2F5CD2C-DEAE-43E3-8A34-6E0B86AD9A9A&TreeGuid=8913A0C3-6408-41fd-9367-E179B8EAF8E3&ItemGuid=0D09693F-BAD9-4fab-8AA6-76E83D6AFA5F

From that view, you can double-click on needed package and modify settings. Here are the item GUIDs for the package templates:

  • BiosSettingsTemplatePackageItem32: {138F1507-DF28-47b2-A4FD-FDB2E7159C6B}
  • BiosSettingsTemplatePackageItem64: {7CE32C6F-3CED-4f52-9FF9-20FD99B41E9E}
  • BiosUpgradeTemplatePackageItem32: {9FAF6DF4-E6DA-4e1a-986F-C3827D8D2C19}
  • BiosUpgradeTemplatePackageItem64: {070B0F88-D5AF-44ec-89FF-84BAA03C0489}
  • Monitoring policy: {0D234AD8-786C-4a09-92E1-E76E35FEDD49}

Supplemental Materials

SourceDEFECT
ValueTLN 24676
DescriptionLogged in tlndev (Altiris - Talinn) database

Legacy ID



39120


Article URL http://www.symantec.com/docs/TECH36821


Terms of use for this information are found in Legal Notices