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....
See more...
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.
Prevent-export-for-failed-import-ADMX-template.zip