VMware Horizon Community
jschwartz82
Contributor
Contributor
‎11-11-2020 04:07 AM

Profile doesn't archive during recompose

We have a specific user, without fail, whose profile fails to sync during recompose operations on his pool.

Looking at FlexEngine log, the process starts and then cuts off and nothing gets saved to his archive.  I thought maybe he had an application hanging at logoff and preventing FlexEngine from processing, so I enabled the Auto-End Tasks gpo to close hung tasks during logoff but that doesn't seem to have made a difference.

 

2020-11-10 19:20:35.603 [INFO ] Performing path-based export
2020-11-10 19:20:35.640 [DEBUG] User: <user>, Computer: <computer>, OS: x64-win10 (Version 1909, BuildNumber 18363.1082, SuiteMask 100, ProductType 1/4, Lang 0409, IE 11.1082.18362.0, VMware VDM 7.7.0, UEM 9.7.0.881, ProcInfo 1/1/4/4, UTC-06:00S), PTS: 36336/28388/1C
2020-11-10 19:20:35.643 [DEBUG] Policy "Always wait for the network at computer startup and logon" is enabled
2020-11-10 19:20:35.643 [DEBUG] Policy "Run logon scripts synchronously" is not configured
2020-11-10 19:20:35.684 [DEBUG] Redirected folders: Desktop, Favorites, Personal
2020-11-10 19:20:35.685 [DEBUG] Policy "Point and Print Restrictions" is configured for the computer (1/2)
2020-11-10 19:20:35.685 [DEBUG] User policy last applied at 2020-11-10 17:53:26.392 (took 3.215 s)
2020-11-10 19:20:35.687 [DEBUG] Boot time: 2020-10-24 07:18:35.178, Logon time: 2020-10-25 11:53:25.108
2020-11-10 19:20:35.687 [DEBUG] Recursively processing config files from path '\\server\config\general'
2020-11-10 19:20:35.687 [DEBUG] Using profile archive path '\\server\profile\user\Archives'
2020-11-10 19:20:35.687 [DEBUG] Profile archives will be compressed
2020-11-10 19:20:35.687 [DEBUG] Creating 2 backups (single backup per day) in path '\\server\profile\user\Backups'
2020-11-10 19:20:35.687 [DEBUG] Logging to event log for path-based import/export, asynchronous UEM, UEM refresh, DirectFlex refresh
2020-11-10 19:20:35.687 [DEBUG] Logging to file '\\cim-vdi-connect\profile\user\Logs\FlexEngine.log'
2020-11-10 19:20:35.687 [DEBUG] Log file will be overwritten when larger than 1024 kilobytes
2020-11-10 19:20:35.687 [DEBUG] If Flex config files path is not available at logon, log off automatically
2020-11-10 19:20:35.687 [DEBUG] If profile archive path is not available at logon, skip import but apply user environment settings

 

FlexEngine log cuts off there, and the next entry is for the subsequent logon processing.  If the user manually logs off of his machine, then the sync happens correctly and his profile gets archived.  Other users do not have this problem, it seems localized to this user.  

I'm not sure where else to troubleshoot this or how to ensure FlexEngine processes during recompose so that the users profile will always archive correctly.

 

Any troubleshooting advice is greatly appreciated.

 

0 Kudos
1 Reply
DEMdev
VMware Employee
VMware Employee
‎11-11-2020 06:19 AM

Hi @jschwartz82,

I'm not very familiar with Horizon: during such a recompose operation, I assume Horizon triggers a logoff?

Unfortunately, FlexEngine log messages aren't flushed to disk immediately, so the last line that made it to disk isn't necessarily an indication of what it was doing at the time it stopped running... Do you happen to know whether FlexEngine hangs or crashes when this happens for that particular user?

Would it be possible to replace your current logoff script with a batch file that does something like the following?

 

setlocal
set LogoffLog=%UEMProfileArchives%\LogoffLog.log
echo %DATE% %TIME% LOGOFF SCRIPT START >> "%LogoffLog%"
"C:\Program Files\Immidio\Flex Profiles\FlexEngine.exe" -s
echo %DATE% %TIME% LOGOFF SCRIPT END >> "%LogoffLog%"

 

If Windows is somehow terminating the logoff script before it can run to completion, that "LOGOFF SCRIPT END" message would not be logged. Not sure yet what our next troubleshooting step will be once we know this, but let's start there...

BTW:

2020-11-10 19:20:35.640 [DEBUG] User: <user>, Computer: <computer>, OS: x64-win10 (Version 1909, BuildNumber 18363.1082, SuiteMask 100, ProductType 1/4, Lang 0409, IE 11.1082.18362.0, VMware VDM 7.7.0, UEM 9.7.0.881, ProcInfo 1/1/4/4, UTC-06:00S), PTS: 36336/28388/1C

Official support for Windows 10 Version 1909 was introduced in DEM 9.10. I'm not aware of any issues with UEM 9.7, and can't imagine the logoff issue has anything to do with this version mismatch, but something to keep in mind.

0 Kudos