Microsoft Teams cache in a non-persistent environment
Hi all, My name is Koen and I am working with Microsoft Teams in a Dutch government organization. We like to offer our staff the ability to work from home, especially during the COVID-19 crisis. We already have enrolled Microsoft Teams in our desktop (it came out of nowhere and we are replacing the default web-downloader with the MSI file) For the record: We are using a non-persistent environment with VMWare Horizon Client and thin clients in the office, and mostly the web client when users are working from home. All of our users are having a profile where we store the temp files like caches and stuff. Also %AppData% is located in that profile. This data is presistent and will be availible on every boot, when they authenticate. But, we are looking for a way to change the Microsoft Teams cache location. We have limited disk space on the 'profile' disk. The problem is, that Microsoft Teams uses the folder %AppData%\Microsoft\Teams\Service Worker\CacheStorage as location of some caching files. The size of the folder is at least 200MB, and some other users are having a folder with at least 500MB cache. We have 200+ users, so when I calculate this ( 200(users)x200(MB) : 40.000MB/40GB for only the smallest caches. And the profile disk is only 100GB (for example) This is why we want to replace (or totally disable) the cache. I already looked in the newest Administrative Templates (for Office 365, 2016 and 2019) and the desktop-config.json - but I can't find the right way to do this. Does anyone know how to solve this issue?
User is offline for specific tenant
Hello dear colleagues, I have a some how mysterious problem. One of my customers is not able to write me on Teams. We both see each other as Skype user. I can write him, he can replay but only for a short moment. After som time he cannot write a message or call my anymore. Yesterday I created a new Tenant for a customer and I used this Tenant for some test. He can write to a user inside this Tenant, everything works normal. When This new user tries to write to my Teams account he get the same error message as my customer "This user is unavailable or offline. We've sent an email instead." (fun fact, I do not receive any mails). So I think it is an problem/miss configuration with our company Tenant. Any ideas? The attached picture is from the test users Teams With regards Alexander Asmußen
Microsoft Teams: Making web parts built with App Studio for MS Teams available in SharePoint
Hi everyone! Someone posted something similar as what I'm about to discuss in this post. Sadly, there wasn't any solution and several links that were included in the responses are broken. The post can be found here: https://techcommunity.microsoft.com/t5/microsoft-teams/is-it-possible-to-create-a-teams-webpart-and-display-it-on/m-p/110476. Now, on to my question: I'm in the process of converting several existing web parts (built in Visual Studio using the SharePoint Add-In project template) to work in Microsoft Teams. In a nutshell, there are 2 routes I could follow to accomplish this: (1) Using SharePoint Framework (SPFx), NodeJS, Typescript, Visual Studio Code and Yeoman Generator, OR (2) Visual Studio, HTML, Microsoft Teams SDK, Javascript, AppStudio for Microsoft Teams and NGROK (for testing). Following option (1) solves this whole issue completely, because it only involves these steps to make the app part available in both SharePoint AND Teams: Ensure that the supportedHosts config setting in <WebPart>.manifest.json has the "TeamsPersonalApp" and "TeamsTab" options included. Execute gulp bundle --ship in Command Prompt. Execute gulp package-solution --ship in Command Prompt. Drag-and-drop the resulting package onto the Sharepoint App Catalog and wait for the upload to complete. Click on the "Sync to Teams" menu item. However, option (1) does not work for me, because the web part uses DevExtreme controls that is built in JavaScript, and the DevExpress development/support teams are not familiar with using their controls in a web part that is being built in SPFx/TypeScript. In addition, the web part uses API calls to retrieve data. So, I completed the development of one of the web parts using option (2). These are the resources I referenced to do the development: https://www.rickvanrousselt.com/teams-ramp-up-part-3/ https://docs.microsoft.com/en-us/microsoftteams/platform/tutorials/get-started-dotnet-app-studio. As it stands, it works very nicely. However, this web part must be available in Sharepoint as well. The problem is that the schema of the manifest.json files of options (1) and (2) differs, so Sharepoint will not allow the .zip file that is generated with option 2 to be uploaded. I also posted about this exact issue on StackOverflow (https://stackoverflow.com/questions/62455352/microsoft-teams-making-web-parts-built-with-app-studio-for-ms-teams-available-i), but I didn't get any response there, so I'm hoping to get some answers here from all the Microsoft Teams developer geniuses! 🙂 If anyone could provide help with this (additional links, insights, etc), I'd really appreciate it!