HI All,
Not completely sure this should be in the App Volumes or UEM forum.
I have a strange issue with App Volumes 2.12 and UEM 9.1 implementation at a customer site.
When i attach a Appstack (created on W10 1607) on my Dynamic desktop pool (also Windows 10 1607), some of the shortcuts which are created with UEM are not clickable.
Without UEM with appstack, shortcuts from the system are working just fine.
Without the appstack, shortcuts from UEM are working fine.
On other Windows versions like Windows 7, everything is working ok. Seems an issue that only occurs when combining Windows 10, UEM and App Volumes.
Does anyone have an idea?
Regards,
what apps are included in the AppStack? Are they shortcuts to modern/universal apps? Where are the shortcuts located: Start Menu / Desktop?
Hi Pim,
Just a few demo applications are included within the Appstack, such as Filezilla, Chrome , notepad++ etc nothing special.
All shortcuts are located within the Startmenu.
.
Create a batch script "allvolattached_shellstarted.bat" and update the appstack with batch script.
@echo off
if not exist "c:\temp\uem_refresh.txt" (
echo > "c:\temp\uem_refresh.txt"
"C:\Program Files\Immidio\Flex Profiles\FlexEngine.exe" -UemRefreshshortcuts
)
This will help to solve the issue
Yes I had the same Problem found a solution there are two things you need to do
Find a Service called Application Identity and start it (do not change to Automatic)
Then Go to a Powershell run as an Administrator
and paste this line in :
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
And it will be fixed, I put this into an Group policy that runs in the background as this always happens when I attach a App Volume Container
The why is to long to write but will If people are intrested
Dennis, any update on this?
Did the suggested solutions work for you?
Hi Pim,
This was a short PoC implementation with limited time to troubleshoot.
It seemed it had something to do with the time between the machine boot time and the user login action. If this was very short, because we had a very small test pool with dynamic desktops, the issue seems to occur. When giving the VM's more time to become idle after reboot the issue wasn't there.
also, you have to make sure this key is excluded and not included in the startmenu INI.
[ExcludeIndividualRegistryValues]
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\StartMenuInit
