Hi, Could you please update this script to support Skype for business server 2015? - we used this script for our former Lync-environment but we have upgraded to Sfb2015. Thx! //Mattias
In my company, we use lync2010 and lync2013 client. When I add the photo for a user with lync 2013 client, it works for all other users with a 2013 client. But all users with a 2010 client could not see the photo. Have you an idea how to solve it? Thanks
Lync 2013, Federated with another company. For Exchange/AD, we import the photo thumbnail using the Exchange 2010 import method. This works for Exchange/Outlook 2010 and Lync 2013. Your script is great so Federated users can see each other via URL thumbnail. I deploy and the URL goes into user xml and users on each side of the Federation can see photo thumbnails. However, if a user goes offline, the photo will go away until your script is run again. If a user stays online (never logs off their PC or Lync Client) the photo thumbnail remains visible. We are Global -DisplayPhoto AllPhotos (site settings too). How can we make sure the photo thumbnail remains up and stable, never goes away or needs the script re-run? Are there other potential settings which might override the photo thumbnail URL at logoff/login and force the ADPhoto only (which prevents Federated users from seeing thumbnails)? thank you, David
Thanks for your feedback & question! Yes, there might be potentials that the URL photos are overridden. There's one thing I'd like to confirm. does the user using URL photo also has AD photo as well? And after the user logout/login, URL photo disappeared and AD photo came back? Could you please run the following cmdlet againt this user and search if the URL is still exists in the exported xml file? Export-CsUserData -PoolFqdn <poolFqdn> -FileName <c:\***.xml> -UserFilter <user sip> -LegacyFormat Thanks,
When using the script and specifying a the folder attribute, if the folder does not exist, get nothing but a bunch of errors and uncaught exceptions. Could you adjust the code, to A) use a default folder of C:\temp or similar if no folder attribute used? B) Check if the folder exists on the provided attribute, and if not create it? Oh, and C) When using a CSV file make it so Yes to All actually runs for each users, instead of having to say Yes to update every users pic in the CSV file? Great script thanks for sharing!
Thanks for your feedback & advice! I'll try to add more exception handling and consider using/creating a default folder in the next version. for the Yes to All, I think it's already in the current version. the parameter -noConfirm does the same thing. Hope it meets your needs. Thank you again for your advice! Best regards,