antonpaloka
Enthusiast
Enthusiast

FLX###.tmp files causing long logon times

Jump to solution

Hello,

We've been increasing our logon times over the course of our Horizon View rollout, and it's mostly due to UEM. In working with our AV vendor (who is now owned by VMware) we noticed locks on files which were named FLX###.tmp where ### seems to be a random number. I believe these to be owned by FlexEngine, and very limited number of results. Adding a unique filter for this brought our logon times down by an alarming amount.

Is there any info on these files, and possibly any further?

1 Solution

Accepted Solutions
DEMdev
VMware Employee
VMware Employee

Hi ap_idb,

Any item that we extract from a profile archive is first written to a local temp file. Whether it contains registry information or represents a file from the user profile does not matter – it first is written to FLXrandom.tmp. Either in the user's temp folder (for registry information), or in the "real" file's destination folder (so we only have to move it to its real file name once successfully extracted.)

View solution in original post

5 Replies
DEMdev
VMware Employee
VMware Employee

Hi antonpaloka,

Indeed, those FLX*.tmp files are created by DEM/UEM (at logon and during DirectFlex imports.) When we import a file from a profile archive, we first write it to such a temp file. Once we have successfully extracted the file, we move it to to its real name.

If AV triggers on those files, that can definitely slow things down. Have the guidelines from the Antivirus Considerations in a VMware Horizon 7 Environment document been implemented?

0 Kudos
Shreyskar
VMware Employee
VMware Employee

Hi antonpaloka,

I suspect you are using carbon black security software in the environment.

Adding to what DEMdev has mentioned, here is the KB which talks about excluding these files from your AV scan: VMware Knowledge Base

antonpaloka
Enthusiast
Enthusiast

The known AV article is mandatory reading but yes, the settings have been implemented. But those TMP files are not mentioned in the article. I do think those tmp files should be added to the document as making writes from a tmp file and possibly overwriting files could easily be flagged by any AV. Are there any other files of this sort that may do these types of writes?

Shreyskar Yes, Carbon Black Defense.

0 Kudos
ap_idb
Enthusiast
Enthusiast

Hey DEMdev​ is that .tmp file just for appdata or is it for any zip in the archives folder (HKCU, appdata, etc)?

0 Kudos
DEMdev
VMware Employee
VMware Employee

Hi ap_idb,

Any item that we extract from a profile archive is first written to a local temp file. Whether it contains registry information or represents a file from the user profile does not matter – it first is written to FLXrandom.tmp. Either in the user's temp folder (for registry information), or in the "real" file's destination folder (so we only have to move it to its real file name once successfully extracted.)