World of EUC

WEM - File Type Associations - HTTP/HTTPS for ServerFTA.  Has anyone been able to get this to work since MSEDGE became a thing?  Currently we use Default Association files and that works correctly.  But have had MSEdge still taking over occassionaly.  When we use WEM to attempt to set the default association, Windows throws an error and resets it back to MSEdge.

Not seen any issues since we set it.  Prior to using the FTA option we used to use setdefaultbrowser.exe from <http://kolbi.cz|kolbi.cz> but it kept upsetting CS, and so our CS Admins..

We were using that as well.  It's odd, everything else on WEM is working great, but when we attempt to refresh WEM it isn't re-applying the FTAs when they change.

<@U06AW5RU9JA> are you running into this maybe?
<https://kolbi.cz/blog/2024/04/03/userchoice-protection-driver-ucpd-sys/?sfw=pass1751078424|https://kolbi.cz/blog/2024/04/03/userchoice-protection-driver-ucpd-sys/?sfw=pass1751078424>

Well actually now that I think about it, WEM FTA part wouldn't work if that was it 

Saw that article.  Unfortunately thats not installed on this image.  Updated to 2503 agent on the image, and WEM still doesn't enforce on refresh.   And there is still something, somewhere in the image where it will work fine, then out of nowhere, boom Edge is set to default.  Tracking it in the Shell-Core app logs and you can watch, as long as sfta is last applied to the user it works fine.  If it applies before whatever else is setting the default, msedge wins.

So I was reading some more on this, and it might be an issue that serverftahtml is not on the accepted browser list in the WEM documentation.  I did find 3 other MS URIs that might have been triggering msedge to re-register.  More testing to continue.

Yup, can confirm.  ServerFTA is not a supported browser in WEM.  Using MSEdge works.  To fix the overarching issue, I had to add 3 additional MSEDGE uris to the DefaultAssociation to keep MSEDGE from taking over with the mandatory profiles.

&lt;DefaultAssociations&gt;
  &lt;Association Identifier="http" ProgId="ServerFTAHTML" ApplicationName="Citrix FTA Launcher" /&gt;
  &lt;Association Identifier="https" ProgId="ServerFTAHTML" ApplicationName="Citrix FTA Launcher" /&gt;
  &lt;Association Identifier="microsoft-edge" ProgId="ServerFTAHTML" ApplicationName="Citrix FTA Launcher" /&gt;
  &lt;Association Identifier="microsoft-edge-holographic" ProgId="ServerFTAHTML" ApplicationName="Citrix FTA Launcher" /&gt;
  &lt;Association Identifier="ms-xbl-3d8b930f" ProgId="ServerFTAHTML" ApplicationName="Citrix FTA Launcher" /&gt;
  &lt;Association Identifier=".pdf" ProgId="AcroExch.Document.DC" ApplicationName="Adobe Acrobat Reader DC" /&gt;
&lt;/DefaultAssociations&gt;

Seems when any of those are not defined, then MSEDGE takes over ALL of them.  So in our environment we set all those in the default association, and then for the anonymous users that we don't want them to redirect local, we use WEM to set their HTTP and HTTPS entries to MSEDGE.  I think Citrix really should make WEM support their own configuration, but that's just me.  /sips tea.

<https://www.jeffriechers.com/blog/wiki/citrix-sfta-and-the-battle-against-msedge/>

Worked for the weekend, and then somehow Edge took over again.  Setting up a scheduled task hourly to re-import the default associations as a work around.  But getting a call with Microsoft going to find out what it is doing.