Jump to content

Benzini00

Members
 View Profile  See their activity

  • Posts

    30

  • Joined

  • Last visited

Reputation

10 Good

About Benzini00

Personal Information

  • Location
    Liverpool
  1. Benzini00
    Hello everyone, A bit of a weird one, I'm hoping one of you have come across this before because I'm drawing a blank. We deploy a couple of add-ins for Outlook via the admin centre in Microsoft 365, 'FindTime' and 'Translate Message', we believe the add-in's were working fine before Christmas but now fail to load giving the following error: This add-in could not be started. Close this dialogue to ignore the problem or click "Restart" to try again. When clicking 'Restart' the add-in gives the impression of attempting to load but nothing actually happens. The strange thing is, the 'Insights' add-in loads without any issue. I've trawled the web and followed all the troubleshooting steps I can find, such as, ensuring protected mode is enabled in IE11 settings, ensuring the Office desktop apps and the add-in's are up-to-date, but I can't seem to get the add-in's working or pinpoint the cause of the issue. It feels a bit like a connection error or web rendering issue, we replaced Edge Legacy with Edge Chromium last summer but we're fairly certain the add-ins were still functioning after that change, and with the Insights add-in working I assume that rules out a rendering issue, unless of course the Insights add-in renders differently? Here's what we're running: Windows 10 2004 / Office 13628.20528 (Microsoft 365 Apps for enterprise) / Edge Chromium 89.0.774.57 / Google Chrome 89.0.4389.90 Any suggestions or thoughts will be gratefully received. Many thanks
  2. Benzini00
    Hi Garacesh, The furthest we got was Microsoft admitting that UWP apps are pretty much broken when it comes to the use of roaming profiles. During lockdown I investigated our options and found that using FSLogix pretty much resolved the issue due to the way it captures the entire profile rather than just the 'Roaming' aspect, after configuration & testing we took the decision to deploy across our desktops for staff & students, it's all working perfectly so far! ... For mobile/laptop devices we decided to go for local profiles as using FSLogix off-network was too slow across DirectAccess/VPN, the majority of 'important' folders are already redirected to OneDrive and the people using mobile devices typically use the same device on a long term basis and rarely have need to use a desktop device on campus. If you're licensed for FSLogix and have a decent amount of network storage to provision it (typically around 5Gb per user profile, although de-dupe and compression is giving us over 50% savings at the moment) then I'd highly recommend it!
  3. Benzini00
    Hi turnerr12, I've pretty much resigned myself to the fact this will never get fixed unless it's taken out of the hands of 1st & 2nd line support, in this case MS seem to have farmed support out to Convergys, unfortunately they're more interested in closing the ticket than resolving it, no doubt because they want their support stats to look good for Microsoft ... I keep being told the issue is with the 'backend team' and then shortly after the ticket is closed and marked as resolved, obviously it's not resolved, so I re-open the ticket and the process repeats. It's now been over a year and the whole experience has been abysmal to say the very least. Please feel free to report your experience to Microsoft and reference our case number, if more people report this hopefully it'll get the attention it requires, our case number is: 119060524001140
  4. Benzini00
    Hello everyone, We're currently doing some proof of concept testing around delivering open days during the current restrictions. We decided to use Teams Live Event and it looks like it will do the job perfectly, however, we don't appear to be able to use an external encoder or vision mixer if we choose 'Public' under the event permissions, if we choose 'Org-Wide' or 'People and Groups' we can then choose 'An external app or device' and successfully use an encoder or vision mixer. Does anyone know a way around this? Is this a hard limitation? Many thanks, Benzini00
  5. Benzini00
    Hi @Gio_W, Apologies for the delay responding, thanks for posting the code again, it was a formatting issue on my side, doh! The scripts appear to work in terms of allowing the UWP apps to at least open on subsequent logins/different devices when using roaming profiles, however, all UWP apps get reset which means the user will experience first-run conditions, not a deal breaker but it could be annoying if certain UWP apps are used regularly ... I guess this is what happens when UWP app settings aren't stored within the 'Roaming' folder of the users profile though, thanks Microsoft! When using the scripts we're experiencing a long delay during user logon, the user is presented with a black screen for a minute or so before finally seeing the desktop, has anyone else observed this behaviour too? In other news, still nothing back from Microsoft about the roaming profile / UWP issue, has anyone else logged this issue with Microsoft, if so would you mind sharing your case numbers?
  6. Benzini00
    Hi all, Still trying to get this issue resolved over 8 months later, Microsoft support keep closing the case and marking it as resolved when it clearly isn't! @LeonC I can't seem to get the second part of your powershell to work, would you mind checking and re-posting? $items = Import-CSV C:\Support\MicrosoftApps.csv foreach ($item in $items) {$foldername = $item.Name Write-Host $item.Name Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\$foldername\AppxManifest.xml"}
  7. Benzini00
    Having not heard anything from MS support for a number of months, despite sending regular emails requesting an update on the ticket, I'm sure you can all imagine my surprise having downloaded build 1909 only to find this issue still exists!
  8. Benzini00
    Hello Jessica, I keep regularly chasing Microsoft about this, spoke to them last Thursday, no further news, they keep telling me it's with the 'backend team' and there's no timeline for a fix ... appalling, to say the least. I'll post here as and when their response changes.
  9. Benzini00
    Hi jpbp200, Could you detail how you're running both the PS and delprof2.exe in a single script? I think you mentioned earlier on in this thread that you had trouble doing this via GPO, or that it didn't work? Maybe I misread that? Sounds like this would be a good workaround until the Microsoft fix makes an appearance and would mean we can start deployment of 1903.
  10. Benzini00
    The 'back-end' team at Microsoft have confirmed they are working on a fix for this issue, no timeline or method of fix delivery is available at this time, one assumes it will get bundled in with one of the monthly Windows Updates. More as and when I hear anything.
  11. Benzini00
    I've been testing a few deployments over the last 2 days based upon the findings in the reddit post, at first I was hopeful that the removal of Microsoft Solitaire Collection or the use of DISM to remove unwanted UWP apps from the .wim was causing the issue but sadly that doesn't appear to be the case. Here's what we've tried thus far: 1. Un-modified 1903 .wim - Removed our usual unwanted UWP apps using DISM and left Microsoft Solitaire Collection installed - Deployed with MDT LiteTouch - Same issue, UWP apps open on first login but fail to do so on subsequent logins. 2. Un-modified 1903 .wim - Deployed with MDT LiteTouch - Used a Task Sequence item to run a script to remove UWP apps during 'State Restore' phase leaving Microsoft Solitaire Collection installed - Same issue, UWP apps open on first login but fail to do so on subsequent logins. 3. Un-modified 1903 .wim - Deployed with MDT LiteTouch - Previous Task Sequence script disabled so all UWP apps install - Same issue, UWP apps open on first login but fail to do so on subsequent logins. Having re-read the reddit post it appears the OP was unable to launch UWP apps at all when using a new account, whereas we can launch all UWP apps during the initial session but not during subsequent sessions. Testing continues ...
  12. Benzini00
    Oh wow ... I feel the pain of 'kr0k0f4nt' from the reddit post! Right, time to test removing apps during the MDT task sequence rather than directly from the .wim I'm going to follow this as it was mentioned in the comments on the reddit post: https://www.scconfigmgr.com/2019/05/03/remove-built-in-apps-for-windows-10-version-1903/ More shortly ...
  13. Benzini00
    Hi BOOT3988, Yes, we've removed it from every build since first deploying Windows 10. Has something changed with that app that you're aware of, dependencies or otherwise?
  14. Benzini00
    Hi all, Microsoft are slowly working through the issue, lots of basic troubleshooting which we had already carried out prior to opening our support call, but they obviously need to check for themselves. I mentioned that others were experiencing the same/similar issue, the support engineer, Shipra Singh, told me to share the case number and description so that others can log a call and reference it, this should help speed up resolution as Microsoft will then be able to see it's not an environment, device or build issue specific to ourselves. 119060524001140 In-built UWP apps not working with roaming profiles in Windows 10 1903 I'll post further information as and when progress is made. Many thanks, Benzini00
  15. Benzini00
    Hi BOOT3988, Thanks for the link, it's a brutal fix but I can confirm this resolves the issue of UWP apps not opening in 1903. Unfortunately the way the script works is to reset UWP apps on every logon, thus the user will see a black screen for around 10-15 seconds after 'Preparing Desktop' completes whilst it resets the apps, and due to the UWP apps being reset any changes the user makes to those apps during their session will be lost when they next log in. I'm starting to see other reports of issues with the Start Menu/UWP apps so it appears something has definitely changed or is broken in 1903. Still waiting to hear back from Microsoft regarding the ticket I've raised, I'll post here when I've got more information.
×
×
  • Create New...