All Posts

Unfortunately this particular site does use agent based AV in their gold image, rather than offloading it to the hypervisor, so it wouldn't be a stretch to say this could be the overarching reason for sub-par logons. I've been assured in the past that the necessary exclusions are in place, but I've sent them over again including the ones above, and am just waiting on confirmation. Unfortunately, I don't have access to their AV solution to confirm one way or the other. In terms of when a config file is decompressed, it was always my assumption that it would be done locally on the desktop - otherwise it would be copying the uncompressed data over the network, which I'd suspect could lead to some serious congestion during peak logon periods.

I understand what you say. What I am not really sure about is how/when decompression is done. Either directly from profile archive location (share) to temp user folder, or is the archive zip first copied over to the local system (user's profile), than decompressed to the temp user folder? Maybe UEMdev​ can elaborate on that? Anti-virus can also have huge impact on profile archives. Do you have exclusions in place on both file server and/or VDI for UEM? Extract from: https://techzone.vmware.com/sites/default/files/horizon-7-antivirus-view-app-volumes-thinapp-user-environment-manager.pd… User Environment Manager Scan Exclusions VMware User Environment Manager delivers personalization and centrally managed policy configurations across virtual, physical, and cloud-based Windows desktop environments. User Environment Manager allows IT to control which settings users are allowed to personalize, and also maps environmental settings such as networks and location-specific printers. On servers, exclude the FlexEngine log path from real-time scans. For example: \\server\FlexArchiveShare\%username%\Logs On clients, as with other network paths, exclude the following paths from real-time scans: • VMware User Environment Manager configuration share path For example: \\server\FlexConfigShare\general • Profile archive path For example: \\server\FlexArchiveShare\%username%\Archives • Profile archive backup path For example: \\server\FlexArchiveShare\%username%\Backups Additionally, in nonpersistent desktop pools that have a clean master image, you can exclude these User Environment Manager executables from real-time scans because they are known to be virus free: • FlexEngine.exe • FlexSyncTool.exe • Flex+ Helpdesk Support Tool.exe • Flex+ Self-Support.exe

It's a good call - that particular user's Windows Explorer config file is only 129kb compressed, and 1.69mb when extracted, so there is no reason for it to take more than a second to extract / import. In terms of the infrastructure, the profile server and VDI desktops are both stored in the same geographic location with a full 10GB backbone. Neither the vsphere clusters, profile server, or vdi desktops show any stress or contention from a resource perspective. For ref, the desktops are W7 linked-clones with 2 vCPU's / 6GB mem and are hosted on a all flash vSAN deployment.

One thing that stands out is Windows Explorer.zip 2018-01-16 08:26:55.643 [INFO ] Importing profile archive 'Windows Explorer.zip' (\\domain.com\UEM\UEMProfiles\user.name\Archive\Windows Settings\Windows Explorer.zip) 2018-01-16 08:26:55.830 [DEBUG] ImportRegistry::Import: Calling '"C:\Windows\REGEDIT.EXE" /S "C:\Users\user.name\AppData\Local\Temp\FLXD0E8.tmp"' (RPAL: l=0 (D/E), r=0) 2018-01-16 08:27:02.190 [DEBUG] Read 6 entries from profile archive (size: 1563998; compressed: 130956) This one alone already takes about 6-7 seconds. I my current customer's environment, it takes less than a second.

+1 on Ivan's request for a full log file. 35 seconds is quite slow, so we should definitely take a look at what's going on. (And now I'm wondering whether I should try and add timing information to the "Processed N settings" stats dump

Can you post the full FlexEngine.log for this user/session? Regarding DirectFlex and Office, I think it depends. It is always finding the balance between swift logon and swift application launches. For those applications that are started/closed a lot of times in a session, like Office apps, I import those settings during logon/logoff, rather than importing them at launch/closure of the application (DirectFlex). This means taking the "pain" once during logon and having the benefit of not needing to import/export at application launch/closure for those applications.

Oh wow, 5 Days later, 100 views but no reply... Guess the question is too delicious.. We have not really solved the issue. so If anyone feels like he has a suggestion.. Please write Thanks

Here's an example from a user with the highest logon time this morning from vrealize: 2018-01-16 08:27:13.940 [DEBUG] Processed 74 Flex config files (18 successful, 13 skipped, 38 added to DirectFlex cache, 1 disabled, 4 retired) 2018-01-16 08:27:13.940 [DEBUG] Processed 8 UEM import tasks (7 successful, 1 skipped) 2018-01-16 08:27:13.940 [DEBUG] Processed 89 UEM drive mappings (6 scheduled, 82 skipped, 1 disabled) 2018-01-16 08:27:13.940 [DEBUG] Processed 5 UEM printer mappings (1 scheduled, 4 skipped) 2018-01-16 08:27:13.940 [DEBUG] Processed 15 UEM settings imports (13 successful, 1 skipped, 1 disabled) 2018-01-16 08:27:13.940 [DEBUG] Processed 1 UEM drive hiding setting (1 successful) 2018-01-16 08:27:13.940 [DEBUG] Processed 2 UEM ADMX-based settings (2 successful) 2018-01-16 08:27:13.940 [DEBUG] Processed 131 UEM shortcuts (3 successful, 25 scheduled, 100 skipped, 3 disabled) 2018-01-16 08:27:13.940 [DEBUG] Processed 4 UEM folder redirection settings (2 successful, 2 skipped) 2018-01-16 08:27:13.940 [DEBUG] Processed 1 UEM application blocking setting (1 disabled) 2018-01-16 08:27:14.581 [DEBUG] Started DirectFlex injection 2018-01-16 08:27:14.627 [DEBUG] Launched FlexEngine in DirectFlex mode 2018-01-16 08:27:14.627 [INFO ] Done (35113 ms) [<<IFP#00e843da-3e7] What are people's thoughts on Direct Flex for the office applications? At the moment I tend to leave this as default, but is there any reason not to enable it on these as well?

Hi alsmk2, Where about would I see that statistic out of interest? Would that be mentioned in the UEM logs or somewhere else? Indeed, that's logged in the FlexEngine log file, like 2018-01-03 18:40:59.879 [INFO ] Done (119 ms) [<<IFP#f80a71f8-2a01a] As for your question about Horizon's V4V Helper process: that's probably a question for the Horizon forum.

Just to echo what Ray has already said. If you go to 2.13.1 you also get the benefit of being able to mix user & computer assignments. If you have any appstacks that everyone in the business needs access to, you can assign them to the computer objects instead. That means the appstacks are already attached before the user even logs on, and it will only be their specific user assigned stacks that will need processing during logon. It's knocked a decent chunk of time off logons where implemented, and has improved overall user experience as most apps are ready to go as soon as they hit the desktop, rather than waiting for a random amount of time after the desktop is already visible whilst the various apps trickle in.

The other thing I failed to mention is that since going to View 7.3, we've noticed that a script runs for V4V Helper (the helpdesk tool) at logon - this seems to take around 10 - 15 seconds to run, and appears to hold up the logon process. I'm pretty sure if we hadn't upgraded View and had just done AV to 2.13.1, that logon times would have seen a bigger decrease because of the lack of the v4v script running. It appears there is no way to stop it running, and in all honesty, the helpdesk tool is too useful to try and stop it anyhow. Has anyone else noticed the same thing?