In this situation, the Security Profiles on the SMS contain filters that are known but also filters that are unknown to the TPS. If a security profile is distributed to the TPS, the TPS will configure the known filters. However, the configuration of the unknown filters cannot be used. Before the Security Profile is distributed, the SMS will inform you about the different DV-versions and ask if you want to proceed. If you confirm, after the distribution, the SMS will inform you about the filters the TPS was unable to configure using a Notification Window that contains a message like this:

Wed Aug 06 14:37:48 GMT+01:00 2008:
InstructorTPS (10.31.1.94) System Log Notification (error): parseOnePolicy: Invalid policy [d0af8c30-63bc-11dd-3120-81fae65bd922]

Wed Aug 06 14:37:47 GMT+01:00 2008:
InstructorTPS (10.31.1.94) System Log Notification (error): isValid:Signature [00000001-0001-0001-0001-000000006273] does not exist for policy [d0af8c30-63bc-11dd-3120-81fae65bd922]

The [00000001-0001-0001-0001-000000006273] message in this example tells you the filter that was unknown to the TPS: 6273.

The Digital Vaccine on the TPS is newer than the DV on the SMS:

In this situation, the SMS security Profiles do not contain all the filters the TPS knows about. Some filters on the TPS will not be configured by the SMS. The TPS will use the Category Settings for these filters. Before the Security Profile is distributed, the SMS will inform you about the different DV Versions and ask you if you want to proceed. If you confirm, after the distribution, there is no warning about this situation anymore.