Summary

What could cause UMN2 values to change in newer FNP versions 11.13.1 ?

Question

What could cause UMN2 values to change in newer FlexNet Publisher versions 11.13.1 ?

Example:

11.13.1 x64_n6
UMN1: 37136D8EAA1D118B621666C318022F01AB99AAAA
UMN2: CD09EF10B3AE3A432B325818B4CB8C2947052456

11.13.1 i86_n3
UMN1: D31F97C9F45AC408B2418039F20469A7699FA716
UMN2: CD09EF10B3AE3A432B325818B4CB8C2947052456

11.12.0 x64_n6
UMN1: 37136D8EAA1D118B621666C318022F01AB99AAAA
UMN2: C56DB8A77B69754792C1E9D4686A6C2F211984CB

11.12.0 i86_n3
UMN1: D31F97C9F45AC408B2418039F20469A7699FA716
UMN2: C56DB8A77B69754792C1E9D4686A6C2F211984CB

11.10.1 x64_n6
UMN1: 37136D8EAA1D118B621666C318022F01AB99AAAA
UMN2: C56DB8A77B69754792C1E9D4686A6C2F211984CB

11.10.1 i86_n3
UMN1: D31F97C9F45AC408B2418039F20469A7699FA716
UMN2: C56DB8A77B69754792C1E9D4686A6C2F211984CB

As you can see in the attached machine_ids.txt file...

UMN1 -- Consistent on i86 across all FNP versions. Consistent on x64 across all FNP versions. Not consistent across platforms.

UMN2 -- Seemed to be consistent across platforms and FNP versions at least until 11.13.1

Answer

In 11.12.1, we updated the mechanisms by which we extract ethernet information on Window to use WMI. In a small number of cases, this might cause UMN2 to change across a FNP upgrade.

We recommend producers typically allow for a small percentage of lifecycle operations being denied by FlexNet Operations (by having extra licenses available).