Unfortunately, I wasn't able to find a configuration parameter for DTLT itself but if you disable paging for the affected clients, this may speed up fallback to the applet. If a client is configured to be non-pageable, the MCS won't try to connect to it on port 28002.

I'd recommend running a quick test:

1. Disable paging for a test client (you can use the GUI or run the command mccli client edit --domain= --name= --pageable=false on the utility node of the Avamar server)
2. Open the DTLT interface on the client and test if the applet comes up immediately.

If this works, you could create an mccli script that disables paging for the affected clients.

Hi ianderson,

I tried to execute the command and I got this output: "0,22211,Client was updated".

Unfortunately nothing happened. DTLT always attempts with the normal method and then the Java applet.

This is a serious problem, not only form me, but also for my customers.

Moreover loading of Java applet is not always done neither with Google Chrome nor with Firefox. Internet Explorer in this case works better.

In you opinion, are there other solutions?

Thanks a lot!

I apologize for the delay. I spoke with my team on this and it does not appear that there is an option to force immediate failover to the applet. I would recommend filing a request for enhancement through PowerLink for this functionality.