DEMdev's Posts

The ViewClient_Launch_ID environment variable typically isn't be available yet when UEM runs at logon, so that's to be expected. Checking 'Pool name' using the Horizon client property should work... See more...
The ViewClient_Launch_ID environment variable typically isn't be available yet when UEM runs at logon, so that's to be expected. Checking 'Pool name' using the Horizon client property should work, though... What version of Horizon are you using, and how are you running UEM at logon?
In addition to techguy129​'s response, just wanted to make sure that is indeed set for that particular shortcut. If that's not set and the shortcut is created initially (for whatever reason... See more...
In addition to techguy129​'s response, just wanted to make sure that is indeed set for that particular shortcut. If that's not set and the shortcut is created initially (for whatever reason), a UEM refresh will not delete it.
Hi Jasper, Did you by any chance use the VMware OS Optimization Tool (OSOT) when creating your mandatory profile?
Thank you for the log file and screenshots, VDINinja311​. Looking at the FlexEngine log file, there is no difference between the Horizon Smart Policies settings that are applied during logon, ... See more...
Thank you for the log file and screenshots, VDINinja311​. Looking at the FlexEngine log file, there is no difference between the Horizon Smart Policies settings that are applied during logon, and the settings that are applied during the UEM refresh. In both cases we see [INFO ] Applied Horizon Smart Policies settings, without any warnings or errors. I think the next step in troubleshooting this would be to review the Horizon-related logs for the components that take their config through Horizon Smart Policies. Unfortunately, I don't know where to find these logs, how to enable them, or how to interpret them – I only know about the UEM side of Horizon Smart Policies
Although UEM creates ZIP files that can be extracted by any standard ZIP tool, it can only import ZIP files that have been created by UEM. The Reader::VMFN: Incorrect length message strongly s... See more...
Although UEM creates ZIP files that can be extracted by any standard ZIP tool, it can only import ZIP files that have been created by UEM. The Reader::VMFN: Incorrect length message strongly suggests that Taskbar.zip has been modified outside of UEM. Maybe by antivirus software, or maybe it's just a network/storage fluke that prevented UEM from reading the ZIP correctly...
The issue of pinned items I'll leave for Ivan and Pim to address , as they have way more experience with tweaking .INI settings. I'm afraid that there's no good answer for dealing with scena... See more...
The issue of pinned items I'll leave for Ivan and Pim to address , as they have way more experience with tweaking .INI settings. I'm afraid that there's no good answer for dealing with scenarios where settings randomly do not persist, other than checking the log file for clues around the time the issue occurs. I also checked the log file you attached to update #19, and just like Ivan and Pim already stated, pretty much everything seems to work fine. I have a few minor notes and comments, but none of the issues I highlight below will result in settings not persisting... 2017-05-09 13:34:36.660 [DEBUG]    Logging to file '\\...\uemprofiles\...\logs' Not a problem at all, but unlike the Flex config files path and the profile archive path settings (which should point to a folder), the log file path should include a file name. With this configuration, you'll end up with a log file called "logs". Again, not a technical problem, but probably easier to specify something like \\...\uemprofiles\...\logs\FlexEngine.log instead. 2017-05-09 13:34:37.207 [ERROR] AdmxActions: Invalid <Key> 'Software\Microsoft\Office\Outlook\Addins\zzz.SafeSend' ('SafeSend.xml')[/SafeSend Email Security for Outlook][Enabled] ADMX-based settings only support actual policies, that is, settings that live under HKCU\Software\Policies\... registry locations. Settings under the non-policy HKCU\Software\Microsoft\Office\Outlook\Addins\... location can be managed through UEM "Registry Settings" instead. I'm surprised to see that the UEM Management Console allowed the creation of the SafeSend.xml config file based on this ADMX template. Thank you for bringing that to our attention. 2017-05-09 13:34:51.606 [DEBUG] ImportRegistry::Import: Calling '"C:\Windows\REGEDIT.EXE" /S "C:\Users\...\AppData\Local\Temp\FLX7125.tmp"' (RPAL: l=0 (D/E), r=0) 2017-05-09 13:34:55.356 [DEBUG] Read 1 entry from profile archive (size: 2590110; compressed: 218070) Regedit.exe needing nearly 4 seconds to import a .REG file is rather slow (even though the file is 2.5 megabytes), so Pim's remark about antivirus settings is definitely something to check from a performance perspective. 2017-05-09 13:34:56.883 [DEBUG] Running post-import task asynchronously ('"C:\Program Files\Immidio\Flex Profiles\FlexEngine.exe" -UemRefreshshortcuts') ('UEM-Refresh.xml') Any particular reason why you're launching this at the end of the path-based import? The shortcuts have just been processed (actually, 10 of them are still scheduled to be created asynchronously), so this refresh will probably not achieve much (under most circumstances this will just result in an "Async UEM actions or UEM Refresh in progress" error message in the log file (actually, most probably in a "-1" log file, as the main log file will be in use)).
Hi VDINinja311​, UEM 9.1 fully supports WIndows 10 v1607, and I think Horizon 7.0.2 does as well. Can you provide a FlexEngine log file at log level DEBUG? And, just as some general backgro... See more...
Hi VDINinja311​, UEM 9.1 fully supports WIndows 10 v1607, and I think Horizon 7.0.2 does as well. Can you provide a FlexEngine log file at log level DEBUG? And, just as some general background information for anyone following this thread, UEM's Horizon Smart Policies feature is basically just a fancy name for "provide configuration settings for certain Horizon components" Not intended as "blame shifting" or anything like that, but after UEM has applied its Smart Policies settings, it's up to the corresponding Horizon components to pick up those settings and act on them. That also means (as was seemingly the issue in one of the earlier posts in this thread) that for instance setting Client drive redirection to Allow all through UEM Smart Policies does not magically give you client drive redirection – for the actual functionality we fully depend on that feature to be installed and enabled in the Horizon agent and client.
Hi Erossman​, By all means, feel free to file this as a feature request. Not trying to be difficult or bureaucratic here, but that official channel will give product management some more info ... See more...
Hi Erossman​, By all means, feel free to file this as a feature request. Not trying to be difficult or bureaucratic here, but that official channel will give product management some more info than just "some user on the forum wants this". As for the difference between PCoIP and Blast: that has to do with the way those two protocols are implemented. They both read their settings from HKCU\Software\Policies\... indeed, but Blast will interpret any settings it finds there dynamically, whereas PCoIP only re-evaluates its configuration under certain circumstances. That means that I can probably come up with a workaround that would allow you to dynamically control settings like MaxFPS and MaxBandwidthKbps as you initially requested, but that would only work for Blast...
Hi Erossman​, Can you provide a FlexEngine log file (at DEBUG log level) that illustrates what isn't working for you?
Sorry, dbrutus​, that's something I can't comment on.
I agree with Ivan: can you provide a FlexEngine log file (at DEBUG level)?
Yes and yes, respectively
Thanks Ivan! This will be part of the upcoming UEM 9.2 release as a Windows Common Setting, although without that MRU entry. Nice touch
Just to clarify Ivan's response a bit (as it may not be obvious unless you click that link), "environment" isn't used in the generic sense of the word, but refers to the UEM feature with that nam... See more...
Just to clarify Ivan's response a bit (as it may not be obvious unless you click that link), "environment" isn't used in the generic sense of the word, but refers to the UEM feature with that name: UEM environments can be managed from within a single UEM management console. You can switch between environments, and you can import and export configuration files between them (to "promote" a config file from Test to Acceptance, for example).
Given that users get that message about the option being locked by the admin, UEM probably won't be able to help you here. I'd suggest checking with ProcMon to see what exactly is going on her... See more...
Given that users get that message about the option being locked by the admin, UEM probably won't be able to help you here. I'd suggest checking with ProcMon to see what exactly is going on here. Maybe it's something you can fix in the AppStack?
I certainly understand the request, but I'm not sure whether this is possible (or, possible in a way that is officially supported...) First, the bandwidth profiles you can choose between in UE... See more...
I certainly understand the request, but I'm not sure whether this is possible (or, possible in a way that is officially supported...) First, the bandwidth profiles you can choose between in UEM's Horizon Smart Policies are fixed, and cannot be tweaked. Furthermore, as far as I know, PCoIP only re-evaluates its configuration if it's set through Smart Policies, so I think you won't be able to tweak that. Blast will dynamically re-evaluate some parts of its configuration, but I don't know whether that is officially supported... You'd have to check this in the Horizon/PCoIP/Blast/... forums, I'm afraid. If it turns out to be supported, I'd be happy to help deploy such settings using UEM, of course!
Glad to hear it works! And, errm, cheers?
The tricky thing with Always wait for the network at computer startup and logon not having been configured is that UEM does get to run at logon, but only at every other logon... So, I'd still sug... See more...
The tricky thing with Always wait for the network at computer startup and logon not having been configured is that UEM does get to run at logon, but only at every other logon... So, I'd still suggest to double-check that that policy setting is configured correctly.
As none of the "custom config files [...] appear to be getting applied": does your logoff script run correctly? Does anything appear in the FlexEngine log file at logoff?
Would that be for Blast or PCoIP? What aspects of the profile would they like to tweak?