Additional features, settings, or issues not covered by specific Microsoft Teams categories
$file = 'c:\windows\system32\fixTeamsBreakoutButton.txt'
#If the file does not exist, create it.
if (-not(Test-Path -Path $file -PathType Leaf)) {
try {
Remove-Item "HKLM:\Software\Citrix\PortICA" -Recurse
Get-ChildItem C:\Users |%{Remove-Item -Path "C:\Users\$_\AppData\Roaming\Microsoft\Teams\*" -Force -Recurse}
$null = New-Item -ItemType File -Path $file -Force -ErrorAction Stop
}
catch {
throw $_.Exception.Message
}
}
Hi Alan. In your script above, what is the purpose of creating "FixTeamsBreakoutButton.txt"? My thought is that if the removal of Teams AppData is successful, the file exists. Is that correct? I am curious why it's being created in the system32 folder.
We are looking into pushing this out via SCCM to run at startup. I am just wondering if we could place the output of the command in that file, though I don't know if SCCM can do anything with it. Possibly instead, it could write a line into a file on a network drive that would include a timestamp, the machine name and the result.