So in my particular case these settings have to be added to the registry: Skype for business 2019 MSO (6.20002) 32bitĪfter working for weeks with microsoft, they came back with a solution. When I press connect in the skype for business client, a pop up window appears for our 3rd party sso and I can enter windows credentials, click submit, pop up disappears and the skype for business client logs in. On the base image, (it's not joined to the domain), i can log in as local administrator, and with any user account in our AD, that's licensed for office365 and skype for business, log into the skype for business client. But with skype for business, when a user connects, no pop up for the 3rd party sso appears and i get an error that skype cannot retrieve an ssl certificate. Both the office 2019 and products on each desktop in the pool work fine with the sso. One thing to note is that we have a 3rd party sso provider leveraging authentication with our AD with Microsoft office 365. Users logging into these desktops will not be able to log into skype for business. The pool is also a dedicated, full desktop. The pool is created with the virtual center customization script to generate a new SID (sysprep).
I have created different base images based off windows 1803 Enterprise and windows 1903 Enterprise.
0 kommentar(er)
