%3CLINGO-SUB%20id%3D%22lingo-sub-1539064%22%20slang%3D%22en-US%22%3ETeams%20setup%20rapidly%20grows%20my%20profile%20disk%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1539064%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there%2C%20Gonzalo%26nbsp%3Bagain%20here.%20We%20have%20many%20customers%20that%20contact%20us%20with%20the%20same%20request%3A%20When%20Teams%20it%20is%20installed%2C%20profile%20disk%20rapidly%20grows%20around%204%20to%205%20GB%20in%20size%2C%20but%20the%20data%20contained%20there%20is%20just%20about%20a%20few%20MBs.%20This%20issue%20it%20is%20only%20observed%20when%20you%20are%20using%20the%20default%20disk%20type%20(Dynamic).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20would%20like%20to%20clarify%20something%20before%20moving%20forward%3A%20This%20is%20not%20bug%20in%20Teams%20nor%20FSLogix.%20As%20any%20software%2C%20during%20setup%2C%20Teams%20will%20write%20temporary%20data%20that%20will%20be%20deleted%20when%20setup%20completes%2C%20and%20the%20good%20news%20is%20that%20there%20is%20a%20way%20to%20avoid%20this.%20After%20some%20research%20conducted%20by%20our%20product%20group%2C%20they%20shared%20with%20us%20a%20way%20to%20avoid%20this%20situation%20by%20adding%20an%20exclusion%20to%20the%20redirections.xml%20file.%20You%20will%20need%20to%20add%20the%20following%20exclusion%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22lia-align-center%22%3E%3CEXCLUDE%20copy%3D%22%26quot%3B0%26quot%3B%22%3EAppData%5CRoaming%5CMicrosoft%5CTeams%5CService%20Worker%5C%3C%2FEXCLUDE%3E%3C%2FP%3E%0A%3CP%20class%3D%22lia-align-center%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%20note%20that%20this%20will%20be%20beneficial%20to%20you%20if%20you%20add%20this%20line%20before%20installing%20Teams.%20If%20you%20already%20installed%20Teams%20and%20you%20want%20to%20remove%20all%20those%20empty%20blocks%20from%20the%20profile%20disk%2C%20please%20review%20the%20options%20described%20in%20this%20other%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Ffslogix-blog%2Fmy-storage-is-running-out-of-space-because-of-fslogix%2Fba-p%2F1333170%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eblog.%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20can%20get%20more%20information%20about%20the%20use%20of%20redirections%20by%20looking%20at%20our%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Ffslogix%2Fmanage-profile-content-cncpt%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eofficial%20documentation%3C%2FA%3E%20and%20more%20in%20depth%20in%20the%20following%20technical%20%3CA%20href%3D%22https%3A%2F%2Fsocial.msdn.microsoft.com%2FForums%2Fen-US%2F029e130e-5892-4d1f-88a7-f8046d78f3b0%2Fusing-redirectionsxml-to-configure-what-to-copy-to-a-profile-with-fslogix%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Earticle%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1539064%22%20slang%3D%22en-US%22%3E%3CP%3ETeams%20setup%20can%20cause%20your%20profile%20disk%20to%20rapidly%20grow%2C%20and%20here%20we%20will%20discuss%20how%20to%20avoid%20this%20situation.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1542067%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20setup%20rapidly%20grows%20my%20profile%20disk%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1542067%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F613357%22%20target%3D%22_blank%22%3E%40Gonzalo_Reyna%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegarding%20scenarios%20where%20Non-Persistent%20setups%20are%20used%2C%20could%20we%20delete%20files%20out%20of%26nbsp%3B%3CSPAN%3EAppData%5CRoaming%5CMicrosoft%5CTeams%5CService%20Worker%5C%20for%20all%20profiles%20once%20this%20exclusion%20is%20specified%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1542173%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20setup%20rapidly%20grows%20my%20profile%20disk%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1542173%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F228093%22%20target%3D%22_blank%22%3E%40Timothy%20Balk%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20non-persistent%20environments%2C%20official%20documentation%20published%20by%20the%20Teams%20product%20group%20can%20be%20found%20here%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fteams-for-vdi%23non-persistent-setup%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fteams-for-vdi%23non-persistent-setup%3C%2FA%3E.%20There%20is%20mentioned%20the%20following%20items%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E.txt%20files%3C%2FLI%3E%0A%3CLI%3EMedia-stack%20folder%3C%2FLI%3E%0A%3CLI%3Emeeting-addin%5CCache%20(%25appdata%25%5CMicrosoft%5CTeams%5Cmeeting-addin%5CCache)%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3ERight%20now%2C%20FSLogix%20does%20not%20have%20the%20capability%20to%20exclude%20file%20types%2C%20so%20you%20can%20only%20exclude%20the%20last%20two%20items.%20My%20recommendation%20is%20to%20open%20a%20support%20ticket%20form%20the%20Microsoft%20365%20portal%20and%20ask%20the%20Teams%20support%20team%20about%20that%20particular%20folder.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

Hi there, Gonzalo again here. We have many customers that contact us with the same request: When Teams it is installed, profile disk rapidly grows around 4 to 5 GB in size, but the data contained there is just about a few MBs. This issue it is only observed when you are using the default disk type (Dynamic).

 

I would like to clarify something before moving forward: This is not bug in Teams nor FSLogix. As any software, during setup, Teams will write temporary data that will be deleted when setup completes, and the good news is that there is a way to avoid this. After some research conducted by our product group, they shared with us a way to avoid this situation by adding an exclusion to the redirections.xml file. You will need to add the following exclusion:

 

<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\Service Worker\</Exclude>

 

Please note that this will be beneficial to you if you add this line before installing Teams. If you already installed Teams and you want to remove all those empty blocks from the profile disk, please review the options described in this other blog.

 

You can get more information about the use of redirections by looking at our official documentation and more in depth in the following technical article.

2 Comments
Frequent Contributor

Hi @Gonzalo_Reyna,

 

Regarding scenarios where Non-Persistent setups are used, could we delete files out of AppData\Roaming\Microsoft\Teams\Service Worker\ for all profiles once this exclusion is specified?

 

Thanks

Microsoft

Hi @Timothy Balk 

 

For non-persistent environments, official documentation published by the Teams product group can be found here https://docs.microsoft.com/en-us/microsoftteams/teams-for-vdi#non-persistent-setup. There is mentioned the following items:

 

  • .txt files
  • Media-stack folder
  • meeting-addin\Cache (%appdata%\Microsoft\Teams\meeting-addin\Cache)

Right now, FSLogix does not have the capability to exclude file types, so you can only exclude the last two items. My recommendation is to open a support ticket form the Microsoft 365 portal and ask the Teams support team about that particular folder.