DEMdev's Posts

Hi fborges555​, I'm still not clear on where exactly you see the error. Can you provide a screenshot? After logging on, does HKCU\Software\Policies\Immidio\Flex Profiles\Arguments contain r... See more...
Hi fborges555​, I'm still not clear on where exactly you see the error. Can you provide a screenshot? After logging on, does HKCU\Software\Policies\Immidio\Flex Profiles\Arguments contain registry values (IniFilePath, ProfileArchivePath, LogFileName...) referencing paths in your new environment?
Hi @fborges555, can you provide a bit more detail? What exactly did you change? Where do you see this error message?
I don't know much about PowerShell, but it seems that Get-TimeZone and Set-TimeZone were introduced in Windows 10 (or the PowerShell version that comes with Windows 10)? At least, they don't see... See more...
I don't know much about PowerShell, but it seems that Get-TimeZone and Set-TimeZone were introduced in Windows 10 (or the PowerShell version that comes with Windows 10)? At least, they don't seem to exist on Windows 8.1. Looking at TimeZone_Export.ps1, the HKCU\TimeZone key would still be created in this case, but the Id value would not. Vkmr, what OS are you using? And what output do you get if you open a PowerShell console and run Get-TimeZone?
Hi dbrutus​, the OSOT issue was not caused by its "Change Explorer Default View" setting, but by "Remove Windows Desktop Update Setup" in the "Improving Login Time" group. Could you please tes... See more...
Hi dbrutus​, the OSOT issue was not caused by its "Change Explorer Default View" setting, but by "Remove Windows Desktop Update Setup" in the "Improving Login Time" group. Could you please test again, making sure that "Remove Windows Desktop Update Setup" is not checked? Thanks!
Hi atoerper​, Sorry, no. The UEM agent is backwards compatible with configuration files created with older Management Consoles, but it will not understand certain configuration settings from n... See more...
Hi atoerper​, Sorry, no. The UEM agent is backwards compatible with configuration files created with older Management Consoles, but it will not understand certain configuration settings from newer ones. The Upgrade User Environment Manager topic in the docs provides more information on the order in which to upgrade the different components.
Thanks @jmatz135! I'm not a storage guy either :-), so I'll try to read up a bit on oplocks and related topics. I did read something about oplock timeouts which default to 35 seconds. Do any o... See more...
Thanks @jmatz135! I'm not a storage guy either :-), so I'll try to read up a bit on oplocks and related topics. I did read something about oplock timeouts which default to 35 seconds. Do any of you happen to see 35-second delays between subsequent lines in UEM log files?
Imitkov17​: Just wanted to let you know that I just fixed the "Startup" bug (instead of creating the shortcut in a "Startup" sub folder of the (possibly redirected) Programs Menu, we'll create it... See more...
Imitkov17​: Just wanted to let you know that I just fixed the "Startup" bug (instead of creating the shortcut in a "Startup" sub folder of the (possibly redirected) Programs Menu, we'll create it in the actual "Startup" folder). This bug goes all the way back to the initial implementation of the shortcut creation feature which is now more than five years ago, so: good find I can't make any statements regarding release dates, but you already found a functioning workaround for now. I've also filed your feature request about folder redirection for the Startup folder. As for brainstorming on your other questions: by all means! But indeed, please start a separate thread for that (or maybe even multiple ones?), just to keep things clear. (And, most important, to be able to score some more Correct Answer points
Thanks for the additional info, JohnTwilley​. UEM isn't doing anything special w.r.t. accessing or locking files. It just asks Windows to enumerate files from a folder, read files, write files... See more...
Thanks for the additional info, JohnTwilley​. UEM isn't doing anything special w.r.t. accessing or locking files. It just asks Windows to enumerate files from a folder, read files, write files, etc, without doing anything special.
SummaCollege​, The fact that the UEM management console also freezes when your logon hangs is a strong indication that this is related to storage. The UEM agent has no dependency on the manage... See more...
SummaCollege​, The fact that the UEM management console also freezes when your logon hangs is a strong indication that this is related to storage. The UEM agent has no dependency on the management console, but they both depend on the configuration share. Can you share a UEM log file for a slow logon? Alternatively, do you see any big "time gaps" between subsequent lines in the UEM log file for a slow logon?
Although we use official API calls to configure folder redirection, tweaking the registry directly has pretty much the same effect. Just didn't want to suggest that, as it's slightly hacky It ... See more...
Although we use official API calls to configure folder redirection, tweaking the registry directly has pretty much the same effect. Just didn't want to suggest that, as it's slightly hacky It should work just fine, though. I'll pass your feature request along to PM, and I'll file a bug for the underlying issue.
Thank you for finding this bug... Not sure yet how we will address this in the product, but we'll definitely pick this up in a future release. The Startup folder is its own separate entity w.r... See more...
Thank you for finding this bug... Not sure yet how we will address this in the product, but we'll definitely pick this up in a future release. The Startup folder is its own separate entity w.r.t. folder redirection (even though it's a sub folder of the programs menu). When it comes to UEM's shortcut creation, any sub folder you entered in the Programs folder text field will just be appended to the effective location of the programs menu folder. If the programs menu is redirected, we'll create your startup shortcut in <redirectedlocation>\Programs\Startup. But unless you also redirected your Startup folder (using GPO, as UEM does not support that) to that particular folder, Windows will look in the original %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup location... For now, my suggestion would be to add a value under HKCU\Software\Microsoft\Windows\CurrentVersion\RunOnce. Thanks again, and apologies for the issue.
Happy to hear it now works, Imitkov17​! I can't think of any relevant changes in this behavior between UEM 9.0 and 9.2... Could it be that with UEM 9.0 you were maybe running it from a logon scri... See more...
Happy to hear it now works, Imitkov17​! I can't think of any relevant changes in this behavior between UEM 9.0 and 9.2... Could it be that with UEM 9.0 you were maybe running it from a logon script instead of as a Group Policy client-side extension? You can't use UEM logon tasks to launch "interactive" applications; this functionality is meant for scripts or tools that don't need to show any UI, as we launch these tasks before the shell has started. Creating a shortcut in the startup folder should still work just fine for this, though. Can you provide the relevant bit of FlexEngine logging at DEBUG level?
Hi Imitkov17​, Indeed, UEM runs before the ViewClient_ env vars are available. However, you can achieve what you're looking for by using the Horizon Client Property condition, which does have ... See more...
Hi Imitkov17​, Indeed, UEM runs before the ViewClient_ env vars are available. However, you can achieve what you're looking for by using the Horizon Client Property condition, which does have access to the relevant information at the right time. Something like the following should do the trick: (Just be sure to leave out the ViewClient_ prefix in the property text box...
You mean the "OSOT issue that breaks some things around folder redirection" has been solved, right? On a more serious note, this OSOT update won't magically fix this issue on existing syste... See more...
You mean the "OSOT issue that breaks some things around folder redirection" has been solved, right? On a more serious note, this OSOT update won't magically fix this issue on existing systems, of course. It just means that the new OSOT release won't break folder redirection anymore when you apply it on a clean user profile (unless you re-enable the Remove Windows Desktop Update Setup OSOT setting, which you shouldn't).
Hi deep184​, Can you show us how exactly you configured that setting for user-installed applications, and the relevant bit of the FlexEngine log file (at DEBUG log level) that shows that that ... See more...
Hi deep184​, Can you show us how exactly you configured that setting for user-installed applications, and the relevant bit of the FlexEngine log file (at DEBUG log level) that shows that that configuration was applied?
Configuring the Helpdesk Support Tool consists of two parts: Creating the Immidio Flex+ Helpdesk Support Tool.xml configuration file Creating a GPO that tells the Helpdesk Support Tool where t... See more...
Configuring the Helpdesk Support Tool consists of two parts: Creating the Immidio Flex+ Helpdesk Support Tool.xml configuration file Creating a GPO that tells the Helpdesk Support Tool where to find that configuration file The error message you quoted indicates that that GPO is either not configured, or not applied to the system you're trying to run the Helpdesk Support Tool on.
Could you try if recreating the REG_SZ StubPath value under HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{89820200-ECBD-11cf-8B85-00AA005B4340}, and setting it to U (without the quot... See more...
Could you try if recreating the REG_SZ StubPath value under HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{89820200-ECBD-11cf-8B85-00AA005B4340}, and setting it to U (without the quotes) fixes the issue? That's the registry value that's removed by OSOT, which results in these symptoms.
Hi Jasper, Just wanted to make sure: did you indeed use OSOT in your environment?
2018-01-25 UPDATE: This post used to describe a workaround from the UEM side, which has the side effect of breaking Horizon Smart Policies. In the mean time, changes have been made on both the... See more...
2018-01-25 UPDATE: This post used to describe a workaround from the UEM side, which has the side effect of breaking Horizon Smart Policies. In the mean time, changes have been made on both the UEM and Horizon side (for different variants of the issue), so this workaround no longer applies, as long as you're on Horizon 7.3+ and UEM 9.2.1+.
> The shortcuts option in UEM adds but doesn't remove shortcuts unless its during logoff. Unless I'm mistaken. If so configured, shortcuts (and all the other "refreshable" items) are also remo... See more...
> The shortcuts option in UEM adds but doesn't remove shortcuts unless its during logoff. Unless I'm mistaken. If so configured, shortcuts (and all the other "refreshable" items) are also removed during a UEM refresh, if the conditions for a previously-created item no longer match. The OP stated that they have a "UEM Shortcut refresh set to run on startup". However, your hunch that the shortcut is put there (or left there) through some other mechanism is more probable.