Posts
Well, this is odd. I was helping a customer in an Office 365 Hybrid Deployment. They decided to go with S4B on prem and Exchange in the cloud. The customer tested scheduling a S4B Meeting and noticed the following: ( Dial-In Conferencing Numbers are blacked out, but trust me, they're the same. ;) ) Why is this a thing? I wasn't for certain, however, my best guess was this was either being caused by the O365 Pro Plus Client or Exchange. Time to troubleshoot! I checked S4B Technet Forums and found a post from another user regarding this same issue. I followed the advice in the post above and had the customer schedule a meeting through OWA rather than through their client. Low and behold, scheduling the meeting through OWA listed the dial-in conferencing number once. Alright, now I'm getting somewhere, but what's going on with the client? The customer was running the most recent O365 First Release Deferred Channel Version (v 1701 as of June 2017)...
Sometimes, PowerShell will truncate your command output: Uggh... how annoying. Why do you hide things from me, PowerShell? Thankfully, this is easy to correct. There is an environment variable in PowerShell for 'EnumerationLimit' (i.e. the number of items enumerated to the screen during a session): Setting this variable to -1 essentially allows for unlimited enumeration. I hope you find this helpful.
