![]() VMware support told me that this will be solved in the next release of UEM. By placing the DirectFlexTimeout1 value this “delay” is removed. In the UEM Fle圎flexngine 9.2 they added an “delay” of 60 seconds for using App-V applications combined with DirectFlex. Security Hotfixes - Released December 2021. So what does this setting do what solves the slow application response issue. For known issues in Horizon DaaS 9.1.2, see Known Issues below. In the Flex Profiles folder create an REG_DWORD with the name DirectFlexTimeout1 w ith an value of 1. Immidio and within this folder create the Flex Profiles folder. We created the following folders within the HKLM\SOFTWARE\Policies\ And yes, the application responds as it should be! This helped us in the troubleshooting process to sort things out.Īfter several days of troubleshooting and creating logs, I got called by VMware with the question if I could create an registry setting and test it again. With the Horizon View infrastructure we created two pools, one with UEM 9.1 and one with 9.2. What can I say about the support that I got, it was SUPERB! So now it was time to bring in the big guns, I created a support call with VMware. Internet Explorer starts en connects to an URL followed by opening an App-V package (sorry the screenshot is in Dutch). Below an screenshot of how the application works. What makes this application diffferent from the “other” applications like Outlook or Word which are starting quick? This application was using Internet Explorer combined with an App-V package. Also the application didn`t show any errorsīut then again, not all applications are suffering the slow responses.The Windows logging does not show any errors or logging at all.Turned on the Debug logging within UEM and analyzed the logging with no outcome.For example the application in the production evironment started in tree seconds and in Test this was almost three minutes… strange…Īnd the troubleshooting begun, what did I do? Not long after the testing begun we got the feedback from some users that ther were experiencingslow responses after starting applications. So we provisioned our desktops in the Test environment, and the testing begun. The Production and Acceptation VDI Desktops are running the 9.1 UEM Fle圎ngine. Note: at this point we got mixed versions in our environment.īoth the UEM Environment Manger and Test environment are running version 9.2. The User Environment Manager is running 9.2 and the Flexengine got replaced by the new 9.2 agent in the WIndows 10 ParentVM. We followed the upgrade Documentation and the upgrade went smooth and perfect! We created three environments which makes our life alot easier:Ī couple of weeks ago we upgraded the UEM 9.1 environment to 9.2. The fact that “all” configurations are written in xml files make it easy to export and backup. ![]() I must say that I like the simplicity of the product the most. ![]() The last couple of months I am working intensively with UEM. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |