Summary
In Flexnet Connect 2015, changes were made to how an update type is identified. The product/update type is now identified at the update level, rather than at the product level.. If the update is not flagged with the correct type, then it will not be displayed correctly by the client.Symptoms
In Flexnet Connect 2015, changes were made to how an update type is identified. The product/update type is now identified at the update level, rather than at the product level.. If the update is not flagged with the correct type, then it will not be displayed correctly by the client.Cause
Typically, this will be caused by flagging the update with the wrong Delivery type.Resolution
There are three possible Delivery Types:1. Multi-Platform Client
2. Windows Agent
3. Java Agent
The default value for any new update is the Multi-platform Client type, The Windows and Java Agents are legacy client types. If the Delivery Type is not set to the client type which is checking for updates, then the update will never be received..
If the Multi-Platform Client is specified, then the client should be either the XT client or the Client UI. If the Windows Agent is being used to check for updates, then set the Delivery type to Windows Agent. If the Java Agent is being used, then the Delivery type should be set to the Java Agent.
The following screen capture shows the location of the Delivery Type setting, when creating a new update:
