Oct 08 2019 03:46 AM
Hi,
When I'm switching Teams current account to guest account then below changes happening and skype addin gets disabled , sometimes both skype and teams addin disabled from outlook.
HKEY_CURRENT_USER\Software\IM Providers – String value is changing from Lync to Teams
HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\UCAddin.LyncAddin.1 – Dword value is changing from 3 to 0
Is there anyway to keep the below value unchanged or constant in regedit?
IM Providers should be always Lync
UCAddin.LyncAddin.1 - Loadbehavior value should be always 3
Oct 08 2019 04:14 AM
Oct 08 2019 04:41 AM
Oct 08 2019 11:17 AM
Oct 08 2019 12:34 PM
Nov 08 2019 03:24 AM
Nov 08 2019 03:28 AM
Nov 11 2019 07:31 AM
@Rob Ellis Ok thank you
Dec 12 2019 07:44 AM - edited Dec 12 2019 07:45 AM
I think it's pretty simple, because, when you switch to a guest account, as mentioned in article guest user does not have permission to schedule a meeting. Since the guest account does not have permission to schedule a meeting, Outlook might be disabling the add-in. Another reason could be, in SFB you needed same account in Skype and Outlook to schedule a meeting. Same would be carried over in Teams. Since the user account in Teams and Outlook are different, add-in is disabled.
Jan 13 2020 03:25 AM
@Chris Webb
But this do not explain why Skype addIn is removed from Outlook right? It doesn't make sense when in another tenant in Teams will disable the possibility to create a Skype meeting from outlook in your tenant?
Jan 13 2020 05:40 AM
@Markus Johansson If the add-in is still there, you won't be able to create a Skype meeting, when Skype sign in is different than Outlook primary SMTP, and that is known behavior for long time.
Jan 13 2020 05:44 AM
@Tejas_Haria Agree, but if you are in Island mode you can easily be logged in to your home tenant in Skype and Outlook but as a guest in Teams. Then it should be possible to create a Skype meeting in your tenant right?
Jan 13 2020 06:01 AM
@Markus Johansson Yes, skype meeting creation should work.
Jul 11 2022 08:46 AM - edited Jul 11 2022 09:07 AM
Hi @Say_Much
Running this PowerShell script will add an access rule to DENY the current user the right to SetValue on this registry key. Then Teams (running in current user's context) won't be able to change the value anymore and the Outlook-plugin stays enabled.
$regPath = 'Registry::HKCU\Software\Microsoft\Office\Outlook\Addins\UCAddin.LyncAddin.1'
Set-ItemProperty $regPath -Name LoadBehavior -Value 3
$acl = Get-Acl $regPath
$acl.Access | FT *
$idRef = [System.Security.Principal.NTAccount]([System.Security.Principal.WindowsIdentity]::GetCurrent().Name)
$regRights = [System.Security.AccessControl.RegistryRights]::SetValue
$inhFlags = [System.Security.AccessControl.InheritanceFlags]::None
$prFlags = [System.Security.AccessControl.PropagationFlags]::None
$acType = [System.Security.AccessControl.AccessControlType]::Deny
$rule = New-Object System.Security.AccessControl.RegistryAccessRule ($idRef, $regRights, $inhFlags, $prFlags, $acType)
$acl.AddAccessRule($rule)
$acl | Set-Acl -Path $regPath
$acl = Get-Acl $regPath
$acl.Access | FT *