Filter your discovery models to publisher Adobe and you will find many sitting at Partially Normalized. This is usually not a bug. Adobe normalizes differently because Adobe only sells subscriptions.

 

Five Adobe behaviours to know

1. Creative Cloud versions roll up to one generic version starting with  CC. These products are sold only inside a CC subscription, so they reconcile against the subscription, not a point release.
2. No version at all → Partially Normalized.
3. Version missing in the discovered version field but present in the discovered product → the product's version is used.
4. Two different versions (one in product, one in version) → if both are Creative Cloud, the discovered version wins. If they clash, the model goes to Partially Normalized.
5. Version  1.0.000 → this normalizes to the installer or uninstaller product. It is a component, not a real install. Leave it alone.

Field note: Acrobat names with a stray number

You will see names like Adobe Acrobat 200 <version> or Adobe Acrobat (64-bit) 300 <version>. That number is the edition, not the version. From what I have seen across engagements: 200 = Standard, 300 = Pro, 7760 = Pro.

 

 

No Package Map rule covers these strings, so edition stays blank — and that matters, because Acrobat Standard and Pro are licensed separately.

 

Fix: export the models as XML and raise a content request so the Content Team creates the Package Map rules centrally. Do not edit them by hand. Manually Normalized models cannot be reverted, and future content updates stop reaching them.

 

What happens after you send the XML

You will get a confirmation email from the Content Team. It looks like this:

 

Software Discovery Models:

• Total discovery models requested: XX
• Discovery models normalized: XX

Data curated has been scheduled for the upcoming shipment, and is expected to be available for download by DD MMM, YYYY.

 

The shared Discovery Models were partially normalized. We have therefore normalized the applicable rules accordingly.

 

Two things to note:

• The rules do not appear immediately. They arrive in the next content shipment. Track the promised date, then confirm the download landed before you re-check your models.
• Compare "requested" against "normalized". If the two numbers do not match, some models were not actioned — usually incomplete data in the export or a genuinely unrecognised product. Go back on the same request rather than opening a new one.

After the shipment lands, run SAM — Normalize discovery models using content library rules so the new rules are applied to your existing models.

 

 

Abby (https://www.linkedin.com/in/abhishek-singh786/)