Once the 'invoke' command is executed, the user's client with sign out and back in very quickly. I was trying to use an account that didn't and received an 'access denied' error message. After the policy was assigned, I issued a 'Invoke-CsUcsRollback' command with a '-identity' switch for the specific test account (ex: Invoke-CsUcsRollback -identity step #2: it's crucial that the account you run the command with on your on-prem Lync/S4B server has global admin rights on the tenant. I then assigned the policy to a test account I had.Ģ. Rather than modify the global policy, as a test, I created a new policy that set 'AllowUCS' to 'false'. The global UserServices Policy had 'AllowUCS' set to 'true'.
If someone else finds something to contradict this statement, please share.ġ. It doesn't appear that UCS is supported with Lync/S4B on-prem and Exchange in the cloud.
0 kommentar(er)
