If you mean that you're not sure whether -UEMRefreshPrinters is a valid command-line option: it is indeed ( Additional Fleångine Operations). ![]() Not sure if this last option also works, but could solve two problems at once for us. The UEM logon task would run with the same problematic token, and (less important) you'd end up with a Fleångine -1.log log file, as the main log file would still be in use by the UEM agent.Īs for the printer mapping problem: are the drivers for that printer available in the image, or are they installed dynamically? Having printer drivers in the base image is definitely a best practice, as it will speed up printer mappings and generally prevent printer mapping issues. ForFiles.exe does not support UNC paths as the starting directory to start searching from, thus you have to temporarily map a : to the network path.Instead of using a UEM logon task, I would strongly recommend to go the "shortcut in the Startup folder" route. Not that it really matters, but what's the output of whoami /groups /priv? I am also puzzled why we have the split token in Windows 10. I will let you know if this solved our problems for now. ![]() We did not know about this option, but we will try this.Īs we currently also sometimes have a problem with the printer mapping: Error 87 trying to map printer '\\srv-uniflow\Canon' ('Canon MFC.xml') for a workaround we will now try the UEM logon task: C:\Program Files\Immidio\Flex Profiles\Flexengine.exe -UEMRefreshDrives -UEMRefreshPrinters Well, it seems the drive mapping problem is Windows 10 UAC related.Īnd the command Fleångine.exe -UEMRefreshDrives does seem to work for us to get the drive mappings! The only thing is that we get (A/F) in the log instead of (F). I did a test earlier where I made this account member of the local admins group, but it did not make any difference with the drive mapping problem. The user account GC\test-rene is not local admin, nor is this account member of one of "special" groups. Why can we only get the drive mappings appear with Fleångine.exe" -uemrefresh -r or the triggered task (User Environment refresh / Drive Mappings) and not at first login. "C:\Program Files\Immidio\Flex Profiles\Fleångine.exe -r" the network drives do appear.Īlso when we lock the desktop and login again the drives appear, because of the triggered task (User Environment refresh / Drive Mappings). The standard flexengine refresh "C:\Program Files\Immidio\Flex Profiles\Fleångine.exe -uemrefresh" does also make no difference, but if we do We tried many different settings, and we also the setting "Special Drive Mapping Logic" (admx flexengine advanced settings), but there are no network drive mappings at the startup of Windows 10. On the Windows 10 desktops the log file shows that the mapping was succesful but the drive letter does not appear. With the Windows 7 desktops we had no problem with the UEM network drive mappings, but the Windows 10 desktops do not show the network mappings at startup. We use UEM 9.1 and are migrating the desktops from Windows 7 to Windows 10.
0 Comments
Leave a Reply. |