Washington DC Endpoint Management User Group

So I was working on uploading some software when I got around to uploading my SQL Standard and Enterprise software. I noticed that Symantec automatically discovered these and created it's own special managed software product. However it seems to include both Enterprise and Standard software packages. Since these are licensed differently, shouldn't they be split out to two different managed software products? I don't want to change anything yet because of that warning message that if I change the filter it will stop getting the updates from symantec on this product, but it doesn't seem right. I would need to track the licensing costs between both since the price is so much different. Thoughts?

I haven't split a product before and received that message.  A compromise would be adding both license purchases, despite the different costs, and allowing for an average number to appear for being over/under on licenses.  If you use this data to enforce license compliance, however, you should definitely create separate products and reassociate the components with the products.

What the warning tries to tell you:

- The system comes with (around 400) predefined product filters. (Stored in table Inv_SoftwareProductFilter)

- If you change the filter, _the filter_ will not get updated when you install a newer release of the Symantec Management Platform.

If the predefined product (filter definition) is not what you need:

- Change it, or (if you dont want to)

- Create a new product and select "Include components associated with other products"

I think I will change it. It might confuse our staff to see 2008, 2008 STD and 2008 ENT. Plus I plan to use the licensing feature for more stricked licensing compliance. Symantec should split these out. I will put in an "idea" later today.

I've logged this internally as well in our defect tracking database.