So we continued testing, with standard user accounts, admin accounts, and test/dummy accounts. We didn’t find any error logged for the photo upload or the configuration changes. However, the avatar photo then disappeared from the Skype4B client. Most of the configuration stayed in place, as it should. We’d log the user out and back in, to test the configuration. Here’s what happened: A photo upload would go through successfully. (We tried those steps just in case no luck.) Issue: Avatar Photos for User Accounts Disappear Following Logout The issue before us was different from that problem. See my post on making contacts photos display back in 2017. This isn’t the first time we’ve had issues with avatar photos. The photo itself lives in your Active Directory, whether local or on Azure, assigned to the user account. It’s the photo people see when they message you on Skype4B or Teams. The avatar photo has a few different names: profile photo, skype avatar, O365 avatar, contact photo, and so on. We had a problem with each user account’s Skype avatar photos. The digital equivalent of a fly buzzing around our heads. No, we got the “small but annoying” issue. We had no server crash, no hardware failure, no huge configuration snarl. Something has to go wrong.įortunately, the ‘something wrong’ wasn’t catastrophic. Now, if you’ve worked in IT for longer than 2 hours, you know what’s coming next. We set them up on a Hybrid configuration. Initial setup went smoothly…they had an existing Office 365 account, which they wanted to integrate. The other day, our Support team deployed a new Skype for Business Server for one of our mid-market customers.
0 kommentar(er)
