We are testing Windows 10 with a separate environment and for some reason i am not getting any printer maps, drive maps, desktop or mydocuments redirects.
There is no errors in the normal user log and there is no logs-async to be found.
Any ideas?
I've attached a log file to have a look at.
Hi AlexLSx7,
Your problem is not limited to async items not working – none of your user environment settings are processed... That's because the Central location of Flex config files Group Policy setting isn't quite correct: it should include the General folder:
2019-03-21 15:00:29.203 [DEBUG] Recursively processing config files from path '\\cspulsuem01\UEMWindows10'
[...]
2019-03-21 15:00:29.312 [WARN ] Found 'General' subfolder in configured 'Flex Config Files path' '\\cspulsuem01\UEMWindows10'. It is generally advised to change this setting to '\\cspulsuem01\UEMWindows10\General'.
There's also something not quite right with the configuration of your logoff script(s), as the path-based export runs three times at logoff:
2019-03-21 14:14:39.772 [INFO ] Starting FlexEngine v9.5.0.832 [IFP#c4b8590e-145784>>]
2019-03-21 14:14:39.772 [INFO ] Performing path-based export
[...]
2019-03-21 14:14:46.585 [INFO ] Done (6812 ms) [<<IFP#c4b8590e-145784]
2019-03-21 14:14:46.710 [INFO ] Starting FlexEngine v9.5.0.832 [IFP#a6a80eb7-145784>>]
2019-03-21 14:14:46.710 [INFO ] Performing path-based export
[...]
2019-03-21 14:14:46.757 [WARN ] Previous import not marked as successful -- skipping export
2019-03-21 14:14:46.757 [INFO ] Done (45 ms) [<<IFP#a6a80eb7-145784]
2019-03-21 14:14:46.866 [INFO ] Starting FlexEngine v9.5.0.832 [IFP#e6280e73-145784>>]
2019-03-21 14:14:46.866 [INFO ] Performing path-based export
[...]
2019-03-21 14:14:46.913 [WARN ] Previous import not marked as successful -- skipping export
2019-03-21 14:14:46.913 [INFO ] Done (45 ms) [<<IFP#e6280e73-145784]
It does not do any real harm, as we pick up on the fact that the export has already run, but still good to take a look at.
Hi AlexLSx7,
Your problem is not limited to async items not working – none of your user environment settings are processed... That's because the Central location of Flex config files Group Policy setting isn't quite correct: it should include the General folder:
2019-03-21 15:00:29.203 [DEBUG] Recursively processing config files from path '\\cspulsuem01\UEMWindows10'
[...]
2019-03-21 15:00:29.312 [WARN ] Found 'General' subfolder in configured 'Flex Config Files path' '\\cspulsuem01\UEMWindows10'. It is generally advised to change this setting to '\\cspulsuem01\UEMWindows10\General'.
There's also something not quite right with the configuration of your logoff script(s), as the path-based export runs three times at logoff:
2019-03-21 14:14:39.772 [INFO ] Starting FlexEngine v9.5.0.832 [IFP#c4b8590e-145784>>]
2019-03-21 14:14:39.772 [INFO ] Performing path-based export
[...]
2019-03-21 14:14:46.585 [INFO ] Done (6812 ms) [<<IFP#c4b8590e-145784]
2019-03-21 14:14:46.710 [INFO ] Starting FlexEngine v9.5.0.832 [IFP#a6a80eb7-145784>>]
2019-03-21 14:14:46.710 [INFO ] Performing path-based export
[...]
2019-03-21 14:14:46.757 [WARN ] Previous import not marked as successful -- skipping export
2019-03-21 14:14:46.757 [INFO ] Done (45 ms) [<<IFP#a6a80eb7-145784]
2019-03-21 14:14:46.866 [INFO ] Starting FlexEngine v9.5.0.832 [IFP#e6280e73-145784>>]
2019-03-21 14:14:46.866 [INFO ] Performing path-based export
[...]
2019-03-21 14:14:46.913 [WARN ] Previous import not marked as successful -- skipping export
2019-03-21 14:14:46.913 [INFO ] Done (45 ms) [<<IFP#e6280e73-145784]
It does not do any real harm, as we pick up on the fact that the export has already run, but still good to take a look at.
Dammit! I knew it would be something stupid. Thanks again for your help!
This is the login script, is it incorrect?
C:\Program Files\Immidio\Flex Profiles\FlexEngine.exe -s
Hi AlexLSx7,
This is the login script, is it incorrect?
C:\Program Files\Immidio\Flex Profiles\FlexEngine.exe -s
That's the logoff script, yes. Maybe you have multiple logoff scripts configured in Group Policy?
Sorry, yes logoff script!
I think i know why its doing that as there is another policy for the Windows 7 Environment probably causing it to run.
Everything is working now, thanks again for your help
Hey AlexLSx7, happy to hear that everything is working now – thanks for confirming!