Q: I received a notification of PB and EB v1.8 EOS PMB last December 2018. Does that mean I can no longer buy them?
This notice is giving you proper notice to be able to transition your customers to a current product. July 31, 2019 will be the last day to order the sku’s of the EOS product list. Currently, there is no planned support for EB 1.x or any additional fix releases on 1.X for Oreo. If the customer wishes to maintain software fixes and enhancements, an upgrade to EB 2.0 will be required for Oreo
Q: We have customers who have received V2.0 that still want to use V1.8 and customers that have received v1.8 that want to use V2.0. Can we cancel the v2.0 and redirect them to v1.8 and vice-versa? (PMB for EB)
We can always do an exchange, if necessary.
For customers who purchased v1.8 and want to have v2.0 instead, this is possible and no different to earlier process i.e. if v1.8 SW licenses are still NOT allocated, we can cancel the licenses and change the order with 2.0.
For customers who have received 2.0 and wishes to have v1.8, the process should be the same. If the V2.0 is not registered & customers wants 1.8 we can obsolete the order in Flexera & reissue the licenses through our old site. Once the SO# is cancelled and a credit note is generated for the customer, we can reference the cancelled SO# and obsolete the entitlement in Flexera. This is equivalent of the license being returned. We can then ask the customer to issue an SO for v1.8.
Q: Is it possible to transfer Enterprise Browser licenses from Windows devices to Android devices when there is a roll-out for Android ones?
Since May 2018 we have separated the Android and Windows binaries, hence there are separate SKUs BUT the capability to transition from legacy Windows to Android is still there to facilitate customers upgrade to Android. That has not changed.