devices
103 TopicsTeams Room "Cannot Fetch Calendar"
Good day, I have just finished setting up our Lenovo ThinkSmart Hub500. Creating the room and users account as per MS instructions is all done and Teams Room is logged in. I can start a new meeting and project but no meetings are showing up. At the top it says "Cannot Fetch Calendar". What are we doing wrong? Thanks.137KViews0likes46CommentsPolycom RealPresence Trio 8800
I'm looking at using the Polycom RealPresence Trio 8800 as a replacement for some of our smaller conference rooms. We are currently using a combined traditional conference phone with a Surface tablet with SfB connected for video and chat. It is messy and people cling to their dialtone devices. The goal would be to eliminate the surface tablet and phone for the RealPresence Trio 8800. Is anyone using these who would be willing to share their experience?27KViews0likes43CommentsPolycom VVX 600 and MFA
Has anyone had any luck with the Polycom VVX 600 and signing into S4B when you have MFA enabled on your account? Or for that matter any polycom device? I've tried app passwords and those don't seem to work either. I haven't seen any documentaiton anywhere if this is supported or not, so just curious if anyone has any inforamtion about it and if it's not supported, when it might be.Solved23KViews1like38CommentsSkype call issues - Bad device state
Hi all, during past two weeks I have noticed increased number of incidents regards Skype for business calls. Users are complaining that suddenly the other end stops hearing them. We have Skype for business is running on premises, Skype client version 15.0.4927.1000 While digging in the Skype for business server reporting I find something like this: Capture device: Headset Microphone (5- Microsoft LifeChat LX-6000) Capture device driver: Microsoft: 6.1.7601.18208 Render device: Headset Earphone (5- Microsoft LifeChat LX-6000) Render device driver: Microsoft: 6.1.7601.18208 Microphone glitch rate: 1 per 5 minutes Speaker glitch rate: 291 per 5 minutes Microphone timestamp drift: 0,01126528% Speaker timestamp drift: 0,00931025% Microphone timestamp error: 0,0355660505592823 ms Speaker timestamp error: 0,17209330201149 ms Echo event cause: Voice switch cause: Bad device state Echo percent send: 3,09% Echo percent microphone in: 11,04% Send signal level: -26 dBov Receive signal level: -21 dBov Send noise level: -62 dBov Receive nosie level: -57 dBov Echo return: Initial signal level RMS: 125,749099731445 Capture device: Transmit (Plantronics D100-M) Capture device driver: Microsoft: 6.1.7601.18208 Render device: Receive (Plantronics D100-M) Render device driver: Microsoft: 6.1.7601.18208 Microphone glitch rate: 14 per 5 minutes Speaker glitch rate: 618 per 5 minutes Microphone timestamp drift: 0,00761747% Speaker timestamp drift: 0,00914335% Microphone timestamp error: 0,0629489421844482 ms Speaker timestamp error: 0,107901096343994 ms Echo event cause: Voice switch cause: Bad device state Echo percent send: 1,55% Echo percent microphone in: 1,55% Send signal level: -19 dBov Receive signal level: -21 dBov Send noise level: -70 dBov Receive nosie level: -57 dBov Echo return: Initial signal level RMS: -53,501651763916 I notice that each time speaker and microphone are glitching which ends in the result Voice switch cause: Bad device state According to MS explanation Voice switch cause: Reason why a call had to be placed into half duplex mode in order to prevent echo. In half duplex mode, communication can travel in only one direction at a time, similar to the way users take turns when communicating with a walkie-talkie. Select one of the following: [All] None Bad timestamp Echo DNLP (dynamic nonlinear processor) Low complexity Bad device state Post-AEC echo (acoustic echo cancellation) This explains why the user "drops out" from the call and others stop hearing him, but this not help to resolve the issue. Each time users were using headsets certified for Skype for business (Plantronics SAVI W410, Microsoft LifeChat LX-6000), we tried updating Skype for business client, headset firmware if available, audio drivers, but the next day users return saying that problem continues to exist. Any ideas on how to resolve this? It would be easy to say to change the headset for the user, but when you buy certified device for $100+, then you expect things to work.Solved20KViews1like19CommentsSurface Hub acoustics and satellite microphone options
We are finding that we will likely need satellite microphones in our conference spaces. While the built-in microphone pickup is good in a relatively small space, we are getting complaints about audio pickup in anything bigger than a 6-8 person conference room, or in rooms with not-so-great accoustics. Has anyone tested any USB satellite microphones, or tried using a USB a/v bridge to connect Surface Hub to existing room audio systems? I've been looking at some Vaddio and Polycom options, but would prefer not to purchase until more data is available. Echo cancellation and ease of use will be key factors.17KViews3likes19CommentsChange Language on Skype Room System v 2
I can´t find any information on how or if it is possible to change display language for the local "Skype" account on a Skype Room System. I can download a second language when I´m loged in as Admin and change the display language for that account. But I can´t seem to find a way to do it for the "Skype" local account. Do I need to reinstall my SRS and prepar my ISO with a second language like described in this articel: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-language-interface-packs-to-windows Will this help or will the "Skype" local account always be installed with English?15KViews1like14CommentsSkype Room System shows calendar info but can't sign in
We have 2 Logitech SRS systems that we are testing before a wider rollout (over 70 in total) We have one kit working perfectly, but the other gives an error saying: "We can't sign you in because the server couldn't be reached" However, it does pick up the meeting info for anything the room account has been invited to To me, both room accounts, hardware, network and build (1703/3.0.16.0) are identical so I can't see why this one device is failing? I've tried using both the working room account and a normal user on the device but it has the same issue. I can also sign in to the Windows Skype for Business 2016 client using the room account Any pointers as to where I should look? I've sent myself the logs using the "Give Feedback" feature but not sure what I should be looking forSolved14KViews0likes13CommentsExperiences with SRS/Logitech SmartDock
David Phillips asked me to share out experience with the Logitech SmartDock and SRSv2 in another thread, I thought I would start a new post to collect other people's experience. We are refurbishing our head office buildings, the first floor of the first building went live 3 weeks ago, so our experience is limited at this point. This floor has about 250 desks, and now a new collection of collaboration booths, high tables, etc. For the meeting rooms we installed :- 3 x 5 person Rooms with 46" screen, SmartDock, Logitech C930E and Senheisser ML20 Speaker 1 x 9 person Room with 65" screen SmartDock and Logitech Group 2 x 14 person room with 75" screen SmartDock, Logitech Group with extension mic, extron amp and ceiling speakers 3 x 55" Surfacehubs in a variety of different settings We bought the SmartDocks separate to the Surface Pros inside them, didn't find any issue in following the instructions to create the build, and to configure the accounts in Skype Online. We manage them in Intune, but not in OMS (too expensive!). We've configured them with E1, CloudPBX, PSTN Conferencing and a UK Domestic DialPlan. They have wired connections to our direct internet connection, not through the corporate lan, they arent domain joined. Out staffs response has been great, it's a big step up from the ugly collection of speakerphones and TVs we had before. Sound clarity is great, Video and screen sharing are very good. At the moment I would say about 40% of our meetings are using skype, and perhaps an equal number dialing into a legacy audioconferencing provider, the balance is shifting as people discover how much clearer the audio is in Skype. Having a quality solution in every bookable space makes a huge difference, we no longer need to think much about which site a user is at when booking a meeting, just find a point where people and a room are available and let them figure out where they want to be. The Logitech Dock seems pretty good, lots of screws but we don't want something that users will take to bits. Solid feeling, very good swivel function. It would perhaps have been easier with a line out option inside the cable section. There lots of cables going in/out of the dock but our installers have done a good job of making it neat and unmovable. We understand that we've bought into a very new product but its been remarkably stable. We are aware of 3 devices that reached a point where they needed a reboot as they became unresponsive (we schedule a reboot each night), this typically seems to be related to connecting local devices to the hdmi in. We've had quite a lot of difficulty getting hdmi switch boxes working reliably on the hdmi input, we wanted to provide autoswtching between hdmi and mini-dp inputs. Forcing the switch to set an appropriate Edid seems to be helping, but I'm not convinced we've totally figured it right yet. Users have raised 2 areas in the software that could be improved. 1. when dialing out to an external conference provider they cant then connect a laptop into the screen locally. 2. They would like to be able to cancel meetings that don't show up from the device, ideally we would like them to timeout like on a meeting room system. We're now just over 3 weeks away from our second floor going live, 15 SRS and 4 Shubs. I'll update back here with any new expereinces. Looking forward to seeing what happens as the SRSv2 app updates. DM me if you want any recomendations for installers in th UK.14KViews7likes43CommentsRe-Image your Surface Hub the easy way
[This is a copy of an article I wrote for my blog. you can find it over here including inline video http://www.skype4badmin.com/re-image-your-surface-hub-the-fast-and-easy-way/ ] I don't know about you, but I roll out a fair few Surface Hub devices for clients and the main issue is. Every time I pull them out of the box they are on a really old build of Windows Team. These older versions have some issues with certain scenarios and the newer builds change the look at feel of the device a little. So I always try to have the device on the latest version when commissioning a new unit for a customer. The issue was there was only two supported ways of doing this. Sign the device in to my test account online, force it to update and wait a few hours Re-image the device by "turning it off" during the boot process and forcing an online recovery (overnight) Both of these options are really frikken slow and have to be done onsite at the customers office. So our solution has been to carry some "Pre-imaged" SSD's with us to swap out when we arrive onsite. But the issue was we either needed to re-image these in our Surface Hub in the office, or use my dodgy hacked together CloneZilla server to prepare disks. So when I saw Y0av post this on his LinkedIn this morning I was really excited His post links to the first public build of the Surface Hub Recovery Tool from the Microsoft website. Download the SurfaceHub_Recovery_v1.4.137.0.msi (version number may change) file and install it on a PC with; Windows 10 1607 or better At least 10 GB free disk space on C: Some method of connecting a SATA disk that doesn't mask the drive ID, a list of tested USB to SATA cables is below. Here are the official requirements from help.txt included in the package Introduction: This tool was designed to help reimage your Surface Hub Solid State Drives (SSD) in a timely manner without calling for support or replacing the SSD itself. This will not fix physically damaged SSDs. You will need to call support if this reimaging tool does not restore your factory image. Time to download the recovery image is dependent on internet connection speeds. On an average corporate connection, it can take up to an hour to download a 10GB file. Requirements: Host computer running Windows 10 “Version 1607” or higher. Internet access USB -> SATA cable 10 GB of free disk space on the host computer SSDs shipped with Surface Hub or an SSD provided by Support as a replacement. Other SSD’s are not supported. Recommendations: High-speed Internet connection USB 3.0 or higher USB -> SATA cable Tested Make and model of cables: Startech USB312SAT3CB Rosewill RCUC16001 Ugreen 20231 Now we know we are good, we can install the tool by firing up the MSI and following the bouncing ball. Once the tool is installed, it pop up in your start menu as Microsoft Surface Hub Recovery Tool Launching the app will ask for admin rights and show a welcome screen. The Learn More link simply takes you to this PDF on how to remove and replace the SSD in the Surface Hub or you can watch the video below. Clicking on start will ask if you want to download the image for the Surface Hub. This gets stored in C:\Program Files\Microsoft Surface Hub Recovery Tool\install.wim and as Y0av reminded me, you can then just copy this WIM file between machines if you don't want to download it again. The download took me about 6 Hours on a 100mbit connection but once you have it, you have it right? Whilst you wait for that to download. Go shutdown your Surface Hub, turn off the AC power, remove the SSD and connect it to your PC/USB Adapter 30 Sec Howto here "http://www.skype4badmin.com/wp-content/uploads/2018/05/Imaging.webm" Once you have the drive connected to your PC using a supported method the tool should change from this To this; Note: The tool does do some sort of checking to see if its a Surface Hub drive, it seems to be looking specifically for a Lite-On SSD. I tried popping a generic disk in and it never showed up, so don't expect to make a fleet of spare disks to carry with you using this tool. Make sure your Surface Hub SSD is selected and hit Start. (No seriously. Make sure its the Surface Hub drive. This tool formats whatever you select, so if you don't want to lose your My Little Pony collection watch out) It gets stuck for a little while at a few different places. Don't worry, its still copying. If you really think its stuck, restarting it wont break the SSD, but it will be unusable until you re-image it. Once that's done, Pull the disk out and pop it in your Surface Hub. Then continue your build as per normal. 30 second how to here "http://www.skype4badmin.com/wp-content/uploads/2018/05/Imaging2.webm" Hope this helps. Thanks to Y0av and the Surface Hub team for making this available for us.13KViews1like0Comments