We're happy to announce that Dynamic Environment Manager 9.10 has been released, with the following new features:
It won't be brief, exactly, as it's a bit involved:
unfortunately I am unable to make sense of the process marked in yellow. Is the block "[DefaultApplications]" new in DEM 9.10? (I've never seen it before, but I can't add it manually either.). And: what is the function auf the "Process" in the next line?
Due to the fact that these default applications are also not "caught" in the DEM in the procedure you describe, no .xml file is generated.
Or did I miss something else?
Thank you for the answer:
"[DefaultApplications]" and "Process" are indeed new in DEM 9.10. They trigger the internal logic for managing default application settings. (You're not supposed to add them manually, which is why they don't show up in the menus or Intellisense .)
Your StandardBrowser_FTAs Flex config file should result in a StandardBrowser_FTAs.zip profile archive when your test user logs off. That zip should contain a Registry folder with a .REG file (which is irrelevant for now) and that Default Applications.xml file.
If that's not the case, can you share a FlexEngine log file, at log level DEBUG, covering the logoff of your test user?
Thank you for pointing out that the interop matrix between DEM 9.10 and Horizon is rather empty... I've informed the powers that be.
You can definitely use DEM 9.10 on Horizon 7.10.
We have set the default File Type Associations as described in the article.
Everything works fine so far, but when a user logs in for the first time (No DEM Profile available yet) this Pop Up shows up:
We can't find any way to suppress this. Do you have any idea.
There is a way to suppress this for every app like this for example:
But that's not an update save to resolve this issue.
Most of the time the issue is that the .xml with Default Associations that is used is missing entries.
To test this you could reset all default app associations to default. Then export the list to .XML using the following command in powershell:
Dism /Online /Export-DefaultAppAssociations:"c:\temp\temp.xml"
For more info see: Export or Import Default Application Associations | Microsoft Docs
After that compare the exported .xml with the file you use in DEM. Make sure that all the entries in the exported .XML are present in the .XML you use in DEM.
Always check this when switching/upgrading the client OS to a newer version as in almost every new build there are new built-in apps added that might need an entry in that .XML
One other possible cause could be that the .XML you are using is not valid (typos for example).
Would you mind starting a new topic for this, rather than piggybacking on the 9.10 announcement, and describe what exactly you have configured in DEM? Also, what "article" do you refer to in "as described in the article."?
I'm trying to follow your steps but I get stuck here: Extract the Registry\Default Applications.xml file from the test user's profile archive.
I don't see an XML file here, only a "Flex Profiles" registry key. How am I supposed to find this .xml file?