https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# citrix-vad
s
This message was deleted.
n
I've had to address similar issues with other apps. Others set FTA using WEM (there's a recent conversation in the WEM channel on this), but I create a new OEMDefaultAssociations.xml file and save it in my image, then release that new image. This is for PVS non-persistent W10 VDAs.
⬆️ 1
j
Yep, OEMDefaultAssoications.xml is your friend here
n
And FWIW, I've routinely had to use the "ApplyOnUpgrade" setting to get some of them to work. So your second screenshot, the line may be something like this (replace the ProgId with the one for Edge Chromium)
Copy code
<Association Identifier="ms-xbl-3d8b930f" ProgId="AppXdn5b0j699ka5fqvrr3pgjad0evqarm6d" ApplicationName="Microsoft Edge" ApplyOnUpgrade="true" OverwriteIfProgIdIs="AppXdn5b0j699ka5fqvrr3pgjad0evqarm6d"/>
👍 2
a
thanks guys! ok so we upgraded wem to 2003 which seems to work much better w/ FTA. so for these 3 specific pop ups maybe i just need to figure out what the progID's are for all 3 and what they currently are set to and set that in WEM if i'm following right? definitely something i can mess with then if thats the case. unfortunately we had to set IE as the default browser (legacy crap) so i wonder if these 3 all are things for browser and now its going back to edge after this update
n
That's definitely worth a shot, since it's the easiest to accomplish.
a
so would that actually suppress those 3 pop ups though? i know wem processes this later in the long on process so wouldnt it kind of be a timing thing? thankfully it only does it the first logon after i push edge out but of course nicer if i can make it not show at all
n
Only one way to find out...
a
i figured that would be the case....what i was hoping for was YES it will make everything work perfect and it will even make things faster 🙂 j/k . thanks guys for the help! gives me something to dig into!
so the OEMDefaultAssoications.xml, would that work for existing profiles or only new ones after you'd make the change to include these?
j
The XML file is what is used to reset the associations when it detects a problem, so should work for old and new
a
awesome! so just add in those 3 app identifier's, and progIDs for the 3 pop ups i'm getting into the oemdefaultassociations.xml under c:\windows\system32 in my image and may take care of it? i tried setting those 3 in wem but didnt seem to make a difference yet
n
Backup the current OEMDefaultAssociations.xml before doing anything. You can either modify the file directly, or run dism /Online /Export-DefaultAppAssociations:"C:\AppAssociations.xml" to export the XML, and then modify that one.
Some people use dism to apply it. I copy it directly to C:\Windows\System32 in my image. You can also apply it via GPO.
a
i actually have done that in my image already w/ dism to set things how i wanted (for default browser, pdf handler , etc) export and then import so this does make sense now that i think of it. just wasnt sure if i can just manually add these in there . thanks guys!
n
Just make sure you keep copies of your old XML files. Definitely makes troubleshooting issues easier.
a
yup for sure! i've gotten paranoid over the years w/ those things so always backup first
n
We have two sites, and actually restored from backup on the first site. Our DBA at first told us that he couldn't find the backup, and the rest of us were ready to jump through the phone and strangle him.
Fun times.
a
been there man!
so if we still have a small subset of persistent desktops on 7.15.5000 vda, i assume i should probably NOT upgrade the Catalog & DG until they are updated to 1912 right?
n
I don’t think it would affect them; they’d likely just not be able to make use of the newer features. But yeah, I wouldn’t upgrade them until everything is on 1912.
a
cool thanks thats what i was thinking.
alright so the file association deal i tried editing that xml in a new image and added the following entries at the bottom (took them from my setup system exporting and copy/pasting in the bottom) but same 3 pop ups looks like. not a huge deal really i guess since it just the first logon after deploy but was hoping i could suppress ....not the end of the world
ok i think i'm dumb on this one and this may be what i need going back to your original suggestion 🙂 . i'll do some testing tomorrow .
n
If I were you, I'd try replacing those three lines with these:
Copy code
<Association Identifier="microsoft-edge-holographic" ProgId="MSEdgeHTM" ApplicationName="Microsoft Edge" ApplyOnUpgrade="true" OverwriteIfProgIdIs="AppX3xxs313wwkfjhythsb8q46xdsq8d2cvv" />
<Association Identifier="ms-xbl-3d8b930f" ProgId="MSEdgeHTM" ApplicationName="Microsoft Edge" ApplyOnUpgrade="true" OverwriteIfProgIdIs="AppXdn5b0j699ka5fqvrr3pgjad0evqarm6d" />
<Association Identifier="microsoft-edge" ProgId="MSEdgeHTM" ApplicationName="Microsoft Edge" ApplyOnUpgrade="true" OverwriteIfProgIdIs="AppX7rm9drdg8sk7vqndwj3sdjw11x96jc0y" />
The only thing you may want to do before is this, though: 1. Run SetUserFTA.exe get within one of your VDAs that does not have Edge Chromium to see what the ProgID is set to for ms-xbl-3d8b930f. I say this because I see two different IDs when I check my own machines, depending on the build 2. Replace the OverwriteIfProgIdIs entry for that if it's different than what I posted above
a
awesome thanks dude! i'll give that a check this morning!
ok yup the ms-xbl-3d8b930f on a pre-edge system theres only 1 entry and all 3 of those entries seem to match a post edge so sounds like i just need to tweak that sheet to the OverwriteIfProgIDIs so i'll give it a whirl. thanks man
👍 1
damn no dice.....same 3 pop ups. ahh well maybe i'll just leave them and tell people this might happen and ignore it
g
Was anyone able to fix this?
a
not that i was able to find.......it only happened on that first login after Edge updated so i just sent a notice out to users and moved on.
Open in Slack
PreviousNext
Powered by