hi,
Have you tried with a manual import: "C:\Program Files\Immidio\Flex Profiles\FlexEngine.exe" -r after the session is opened ?

Hi,

no, I couldn't do this. The user did already a logoff and a logon again.
This is normally what our servicedesk is doing, too. 

Is it always the same users who experience with behavior ?

No, everytime (4 times yet) another user. But they all use the same VDI-Pool. But again there are more than 500 users which use the same pool without any issues yet. And it happened only onces for these user. It's not reproducable for me. There is also nothing special for these users. We didn't have this kind of issue in the last 3 years. 

Hum, well, without DEBUG logs at minimum, hard to check... I would try to ask user to manually import with the provided command when it happens again if possible before they close session. Just to check if it's the profile itself that is no able to load or if any other side effect at logon period.

I would also ensure that there is no double flexengine start (as GPO + Logon script for example) or any double logoff export.

Hello,

same issue.

there is already a solution for this?

DEM Enterprise Version 10.8.0.1064

Hi @VMHero4Ever,

That "verification value still has initial data" message means that registry settings were not (completely) imported correctly, but without DEBUG logging it will be hard to pinpoint the problem any further. Sometimes there's anti-malware software that gets in the way of DEM imports; might something have changed in that regard in last 3 months that could have contributed to this?

@Andreé,

When you say "same issue", what issue do you mean exactly? Profile archives failing to import, seeing that "verification value still has initial data" error message, ...?

Hi @DEMdev ,

yes thats right. "verification value still has initial data"  is the Error..

the logs look something like this

30 08:15:27.914 [FATAL] Importing registry information failed (verification value still has initial data)
30 08:15:27.914 [FATAL] Error importing archive '\\profile.*******\benutzer\swa\archive\Windows Settings\Typed History.zip'
30 08:15:27.946 [FATAL] Importing registry information failed (verification value still has initial data)
30 08:15:27.947 [FATAL] Error importing archive '\\profile.*******\benutzer\swa\archive\Windows Settings\Wallpaper.zip'
30 08:16:08.304 [FATAL] Importing registry information failed (verification value still has initial data)
30 08:16:08.304 [FATAL] Error importing archive '\\fs1.*******\benutzervorlagen\UEM_Konfiguration\general\FlexRepository\Settings\MUI\Sprache.zip'
30 08:16:08.305 [ERROR] Error importing settings ('Sprache.xml')
30 08:16:08.331 [FATAL] Importing registry information failed (verification value still has initial data)
30 08:16:08.332 [FATAL] Error importing archive '\\fs1.*******\benutzervorlagen\UEM_Konfiguration\general\FlexRepository\Settings\Reg\BO License.zip'
30 08:16:08.332 [ERROR] Error importing settings ('BO License.xml')
30 08:16:08.357 [FATAL] Importing registry information failed (verification value still has initial data)
30 08:16:08.357 [FATAL] Error importing archive '\\fs1.*******\benutzervorlagen\UEM_Konfiguration\general\FlexRepository\Settings\Reg\Numlock.zip'
30 08:16:08.357 [ERROR] Error importing settings ('Numlock.xml')

anti-mailware has not been change.

ok, i can understand that without sufficient logs debugging is not possible.
I have increased the loglevel and will report as soon as the error occurs again. (with logs)

Kind regards,

Andree

any news on this? we also have the same problem but it is totaly random: 3 or 4 users a day (we have about 600 VDI) are affeted. We don't want to increase log level for all users...

Hi @VMHero4Ever, @Andreé, @doninside,

Please find attached an ADMX template for the advanced Prevent export for failed import policy setting. For NoAD, add SkipExportForFailedImport="1" in NoAD.xml.

With this setting enabled, a profile archive that failed to import successfully will not be overwritten at logoff (or, in the case of DirectFlex, at application exit.)

This works well if such import failures are temporary. However, if a profile archive has become corrupted somehow, each and every import will fail, the corrupt profile archive will not be overwritten at export, and this cycle will continue forever.
It can only be straightened out by resetting the profile archive or restoring a profile archive backup using the Self-Support Tool or the Helpdesk Support Tool.

This setting is supported in all non-EoGS DEM versions.

Hello,

I have reinstalled the DEM Manager , as well as DEM Agent in the VDI. Since then, the problems no longer occur.

Thanks a lot

KD,

Andreé