EMA Files not working on larger folders on v1.12.1.0

[Jack_S]

We installed EMA 1.10.0 last year and deployed the agent to ~15k devices. Last month we updated to 1.12.1 and this process appeared to complete successfully. All functionality is working as before except for the remote files view.

We're able to use the remote files to browse folders with smaller numbers of files/folders within them, but as soon as we attempt to navigate to a folder with more than approximate 500 items, the names of all the items are either blank or random characters, and none of them can be interacted with in any way.

Here are examples of folders with 450 and 500 items on the same client device:

450 items in the folder - ok500 items in the folder - no names and we cannot interact with any of them

We don't have the automatic client upgrades enabled so most of our clients are currently still running 1.10.0 however we have also tested upgrading some clients with 1.12.1 and that makes no difference. 

Is this a known issue with 1.12.1? Is there a workaround? We often use this for collecting log files from client devices which sometimes involved navigating through folders with more than 500 items. Presently we're using the remote terminal to copy the files to a directory with fewer items but this can be rather cumbersome.

[Victor_G_Intel]

Hello Jack_S,

Thank you for posting on the Intel® communities.

Please let me review this information internally, and kindly wait for an update.

Once we have more information to share, we will post it on this thread.

Regards,

Victor G.

Intel Technical Support Technician 

[Victor_G_Intel]

Hello Jack_S,

We hope this message finds you well.

This communication is to inform you that we are working on replicating your findings and characterizing the scope of what needs to be addressed. We will be in touch as soon as possible.

Best regards,

Victor G.

Intel Technical Support Technician

[Victor_G_Intel]

Hello Jack_S,

Thank you for your patience.

At this time, our recommendation for will be to keep your EMA server up to date, you should see this issue resolved in an upcoming release. In the meantime, we encourage to keep using your workaround.

Best regards,

Victor G.

Intel Technical Support Technician