Hi eball1221,
6-12 seconds is ok, but preferable would be to cut down the login times as much as we can for user experience. All help has been appreciated as user printers complaints have subsided, now I believe further tuning with async mapping and roaming the default printer. Is there an article that points to the configs for that?
As mentioned earlier in this thread, roaming the user's preferred default printer is a bit tricky when mapping printers asynchronously. We need to make sure that the profile archive containing the user's printing preferences is imported only after the printers have been mapped. That works fine for printers that are mapped synchronously, as that happens before profile archive import, but that's no longer the case once the printer mappings are changed to async.
The workaround is as follows:
- Configure the printer mappings to be synchronous. (This is necessary to make sure that step 3 works correctly.)
- Configure the advanced configuration setting Disable DEM Printer Mappings during logon.
- Create a script that "refreshes" the printer mappings (effectively mapping them for the first time in that session, as they were skipped during logon), followed by an import of the user's printer-related profile archive.
Because the printer mappings were configured as synchronous (as per step 1), we can be sure that they have completed by the time the printer mapping refresh finishes. - Launch that script.
Step 1 is simple, as printers are already being mapped synchronously in your current setup.
Step 2– Configure the Disable DEM Printer Mappings during logon policy setting (available in the advanced ADMX template), or the NoAD equivalent: UEMActionPrinterMappingDuringLogon="0". Be sure to pick the "during logon" variant:
![]()
Otherwise, printer mapping will be disabled completely.
Step 3– The script could be something like this:
@echo off
setlocal
set FlexEngine="C:\Program Files\Immidio\Flex Profiles\FlexEngine.exe"
set PrinterArchive="%UEMProfileArchives%\Printers.zip"
%FlexEngine% -UEMRefreshPrinters
if exist %PrinterArchive% %FlexEngine% -r %PrinterArchive%
You would need to make sure that the path to the profile archive mentioned on line 4 is correct for your environment.
Step 4– To launch the script, you have a few options. You could run it as a custom command once App Volumes has attached all AppStacks:
![]()
Or you could launch it as soon as File Explorer has started, by creating a shortcut in the Startup folder.
Or you could launch it as an After profile archive import Logon Task, although I would suggest adding a delay to the start of the script then, so as not to compete for resources with the logon process.
