Forum Discussion
Edge: PDF files are opened with drawboard by default
When you hit that 'forceRefresh' URL, the response that comes back will be what is in the cache before forcing refresh.
So, please hit that URL twice with 3-5 seconds apart to leave enough time for the system to do the refresh and post the JSON of the second time to the forum - as it will reflect the real value of the cache after forcing refresh.
Without this it is not clear what the error is, that you had. If the first pdf opened fine, there should no reason for the second one to fail because of Drawboard.
The server cache should be cleared by now.
We think it is client cache that is problematic.
It is important to clear browser cache, close and re-open the browser.
Regards
Krishna
Thanks Krishna
Everything is good. I concur, in that client cache is problematic. Especially with 350 users of differing levels of IT tech skills. The client cache journey has been my week thus far. I am seeing a mix of user experiences between those who experienced the problems, and the problem went away on its own (cache element expiration I assume), and those still getting redirected to Drawboard application interaction. What we found early Monday was to take the user through Spent a couple hours trying to build a script that would target just "Cookies and other site data" option in Edge cache clearing, but soon discovered through too many powershell script examples that do not work, that it is near impossible to clear certain aspects of Edge cache (like cookies), outside of nuking the /Default directory, which if done takes you back in time to when you opened a fresh new install of Edge.
I and the IT support team have relinquished to handling these users on a case by case. I attached a Word doc I put together to take the users through the fix that we have proven to work. If someone from this thread knows how to programmatically (powershell, cmd line, anything) to surgically clear certain categories of MS Edge cache (specifically, "Cookies and other site data", would love to chat.
Krishna, sorry you are going through this. We here realize it could happen to any company. For us internally, it has resulted in a lot attention to permissions around access to Entra enterprise applications, and how, if even possible, to safeguard oneself against a situation like this.
As expressed earlier, thank you for your transparency. You don't see this, especially from the C suite, usually. I can honestly tell you how relieved I was Monday am, when I saw your post. I spent super chunk time Sunday trying to arrive at something that would solve this issue. No luck. Monday am, prepping for the MS call at 7am, getting the two discussion threads readied in my browser, I saw your post. Quite a relief it wasn't an issue in our farm. So thank you again.