WebAppInstallForceList not adding shortcuts to the desktop

%3CLINGO-SUB%20id%3D%22lingo-sub-2144204%22%20slang%3D%22en-US%22%3EWebAppInstallForceList%20not%20adding%20shortcuts%20to%20the%20desktop%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2144204%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20trying%20to%20test%20deploying%20a%20PWA%20using%20the%26nbsp%3BWebAppInstallForceList%20policy%20on%20Edge%2088%20with%20the%20following%3A%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-json%22%3E%3CCODE%3E%5B%7B%20%22create_desktop_shortcut%22%3A%20true%2C%20%22default_launch_container%22%3A%20%22window%22%2C%20%22url%22%3A%20%22https%3A%2F%2Fservice.example.com%2F%22%7D%5D%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3EThe%20problem%20is%20that%20the%20PWA%20gets%20installed%20but%20its%20not%20creating%20a%20desktop%20shortcut.%20Manually%20trying%20to%20pin%20the%20desktop%20shortcut%20at%26nbsp%3Bedge%3A%2F%2Fapps%2F%20also%20does%20nothing.%3C%2FP%3E%3CP%3EWhen%20the%26nbsp%3BWebAppInstallForceList%20policy%20is%20disabled%20and%20the%20PWA%20is%20installed%20manually%20I%20can%26nbsp%3Bpin%20the%20desktop%20shortcut%20at%26nbsp%3Bedge%3A%2F%2Fapps%2F%20just%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20would%20I%20go%20about%20troubleshooting%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2144593%22%20slang%3D%22en-US%22%3ERe%3A%20WebAppInstallForceList%20not%20adding%20shortcuts%20to%20the%20desktop%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2144593%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F970097%22%20target%3D%22_blank%22%3E%40EliLoewen%3C%2FA%3E%26nbsp%3BHi!%26nbsp%3B%20I%20compared%20your%20code%20snippet%20to%20our%20documentation%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fmicrosoft-edge-policies%23compact-example-value-13%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fmicrosoft-edge-policies%23compact-example-value-13%3C%2FA%3E%26nbsp%3Band%20I%20did%20notice%20there%20is%20an%20additional%20space%20at%20the%20beginning%20of%20your%20example.%26nbsp%3B%20After%20the%20%7B%20and%20before%26nbsp%3B%22create_desktop_shortcut%22.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHopefully%20it%20just%20needs%20that%20little%20change.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAfter%20trying%20that%2C%20if%20it%20is%20still%20not%20working%20as%20expected%20can%20you%20please%20submit%20feedback%2Fdiagnostic%20data%20through%20the%20browser%3F%20(%22...%22%20menu%20%26gt%3B%20Help%20and%20feedback%20%26gt%3B%20Send%20feedback).%26nbsp%3B%20Thanks!%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E-Kelly%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2249432%22%20slang%3D%22en-US%22%3ERe%3A%20WebAppInstallForceList%20not%20adding%20shortcuts%20to%20the%20desktop%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2249432%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20our%20testing%2C%20after%20the%20policy%20is%20installed%2C%20the%20user%20must%20open%20Edge%20for%20the%20shortcut%20to%20be%20added%20to%20the%20desktop.%20Is%20this%20the%20intended%20behavior%3F%20It's%20an%20issue%20for%20us%2C%20as%20many%20of%20our%20users%20don't%20use%20Edge%20as%20their%20default%20browser%20and%20wouldn't%20normally%20open%20it%2C%20in%20which%20case%20they%20would%20have%20no%20idea%20the%20PWA%20existed.%20We%20played%20around%20with%20adding%20a%20script%20to%20the%20GPO%20that%20would%20open%20and%20close%20Edge%20but%20this%20is%20unexpected%20for%20the%20user%20and%20in%20our%20testing%20Edge%20had%20to%20be%20opened%20for%20up%20to%2010%20seconds%20before%20the%20shortcut%20appeared.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I'm trying to test deploying a PWA using the WebAppInstallForceList policy on Edge 88 with the following:

 

[{ "create_desktop_shortcut": true, "default_launch_container": "window", "url": "https://service.example.com/"}]

 

The problem is that the PWA gets installed but its not creating a desktop shortcut. Manually trying to pin the desktop shortcut at edge://apps/ also does nothing.

When the WebAppInstallForceList policy is disabled and the PWA is installed manually I can pin the desktop shortcut at edge://apps/ just fine.

 

How would I go about troubleshooting this?

5 Replies

@EliLoewen Hi!  I compared your code snippet to our documentation https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#compact-example-value-13 and I did notice there is an additional space at the beginning of your example.  After the { and before "create_desktop_shortcut".  

 

Hopefully it just needs that little change.  

 

After trying that, if it is still not working as expected can you please submit feedback/diagnostic data through the browser? ("..." menu > Help and feedback > Send feedback).  Thanks! 

 

-Kelly

In our testing, after the policy is installed, the user must open Edge for the shortcut to be added to the desktop. Is this the intended behavior? It's an issue for us, as many of our users don't use Edge as their default browser and wouldn't normally open it, in which case they would have no idea the PWA existed. We played around with adding a script to the GPO that would open and close Edge but this is unexpected for the user and in our testing Edge had to be opened for up to 10 seconds before the shortcut appeared.

@TriangleSolDev Hello!  Yes, that is the expected behavior.  The browser needs to run at least once after a change to the WebAppInstallForceList to either install or remove the apps in that list. 

 

-Kelly

I can confirm the same, if I take the same gpo and configure it for chrome I can confirm it works normally.

I can create a shortcut manually after the gpu applies, however, the GPO fails to create the shortcut automatically if I specify the value to true when it is applied to edge.

@bwitzigFH Hello!  It looks like we recently released a fix for a similar issue which is available in MS Edge Canary Channel Build 93.0.939.0+.  Would you be able to test on the new build and see if your issue is resolved?  Thanks! 

 

-Kelly