March 30th, 2019 by Skype for Business News Aggregator
Charles is an HTTP proxy / HTTP monitor / Reverse Proxy that enables a developer to view all of the HTTP and SSL / HTTPS traffic between their machine and the Internet. This includes requests, responses and the HTTP headers (which contain the cookies and caching information).
For a full version you will need to buy a license. (It’s worth the $)
Install the Charles Proxy Root Certificate in the trusted root certification authorities.
Charles uses its own Root SSL certificate for SSL requests through Charles to hosts enabled for SSL Proxying. The Root certificate is generated automatically for each Charles installation.
Because Charles has signed the Root certificate itself, it won’t be trusted by your browsers or applications. In order to use the SSL Proxying feature in Charles you therefore need to add the Root certificate for your copy of Charles to the trust-store on your OS, and perhaps in your browser (ie: FireFox).
Go to the Help menu, SSL Proxying, Install Charless Root Certificate.
Click Install Certificate.
Choose Local Machine and click Next.
Select Place all certificates in the following store and click Browse. Select Trusted Root Certification Authorities as store, Click OK.
In the UAC click OK and click Finish.
The root certificate is now installed.
Set Proxy Settings
Enable the Windows Proxy from the Proxy Menu.
Click the Proxy menu > Proxy Settings.
Enable HTTP Proxy and SOCKS Proxy like the image below.
From the Proxy Settings Menu go to SSL Proxy settings.
Enable SSL Proxying and Click Add.
Add * for host and * for port.
Click OK to exit settings.
Close your Microsoft Teams Client and Click the broom icon to clear logging.
Startup your Microsoft Teams Client and start debugging!
March 29th, 2019 by Skype for Business News Aggregator
Hey all! I just got back from visiting the beautiful country of Belgium on a trip to learn more about how the Belgian Federal Police take advantage of Microsoft 365.
The story of how Wim Liekens and his team at the Belgian Federal Police force implemented Microsoft 365 E3 is an inspiring one. Trying to secure and modernize a workplace of over 55,000 employees not only requires a sound strategy, but also the right tools for the job.
Officers have been able to leverage Yammer to respond to questions investigators pose about ongoing cases. They take advantage of Office 365’s powerful online meeting capabilities to quickly convene and solve emergencies while out of the office. Members of the Belgian Federal Police have even been able to use Microsoft Teams to support dispatched units in the field (like their special canine units)!
One would think using liquid nitrogen to freeze ice cream is something that was discovered recently, but that is not the case! In 1901, British cookbook author Agnes Marshall, known as the Queen of Ice Cream, proposed the use of “liquid air” to freeze ice cream. Herve This further developed the technique by using liquid nitrogen to free the ice cream, almost instantly. This process helps make the ice cream smoother and more delicious!
Just like nitrogen ice cream, a lot of Office 365 and records managers have requirements about information being properly stored or “frozen”. With the NARA mandate coming this year, be sure to check out all our resources around NARA compliance to make sure you’re on the right track today!
You would probably get no argument, even from practitioners, in saying that the responsibility of driving and enforcing records management practices within organizations is seen as a fairly un-glamourous job.
There’s the rigorous time spent designing and planning an end-to-end records management strategy for the organization, laborious work to implement and train on the business processes and workflows necessary to identify, capture and manage records, and the inherent “chasing” of users and business units who either don’t understand or don’t comply with their responsibilities (which are often the last mile of records management within organizations).
And yet the goals of a proper records management implementation couldn’t be more important to an organization. These usually include:
Ensuring the capture and proper handling of the organization’s most important information,
Limiting the exposure (legal or otherwise) of information that is no longer relevant, necessary or required but may present risk to the organization,
Achieving provable compliance with legal or auditory requirements that ensure regulated content can be discovered and produced as appropriate.
These are lofty goals given the amount of data produced, stored and shared in today’s modern world of work and the many collaborative systems and services that are currently in use by organizations.Take, for example, the NARA 2019 and 2022 guidelines and mandates for the handling of permanent electronic records by US federal government agencies. To do this kind of work properly and effectively requires a combination of the right people, processes, and technology within the organization.
Another key element is required for a successful program: the support of an executive sponsor.In our work with many regulated organizations in both the commercial and public sector, we have seen the full spectrum of engagement in records management programs by the executive team. Over timesome common strategies, symptoms, and remedies have emerged.
Have questions about records management at the executive level? Check out this post: Click To Tweet
When It’s Working Right
The guidance from industry organizations such as AIIMon the executive sponsorship issue is clear. AIIM’s 2010 ECM toolkit states: ”To be successful, records management must start at the top. A senior executive must be held accountable. There is a growing but not yet universal understanding of this fact within the business community.”
Furthermore, guidance from AIIM suggests“Framing the initiative and confirming commitment needs a variety of key stakeholders: business, legal, executive, records, and IT. And don’t forget some representation from the people who will actually have to use all this technology!”The obvious value of an executive sponsor is to create motivation within the organization at large to actually comply with the goals and processes the program requires.
Records management initiatives that are properly funded, resourced and broadly visible within the organization are often sure signs of good executive buy-in. I’ve seen extremely effectiveimplementations where an executive sponsor was actually the face of the initiative and the one whose persona was used for all important communications around strategy and user impacts of the new processes.
Executive sponsors also have the luxury of not living in the granular details of the program, so they’re effective advocates of staying focused on big-picture goals (such as how the program’s controls and processes will be communicated to and received by regulators and auditors). In essence, goodexecutive sponsorship allows records management teams to borrow authority and influenceand help deliver the message that this really is important and vital work for the organization as a whole.
Symptoms That Executive Support May Be Lacking
As you would logically expect, symptoms of records management initiatives that are lacking executive sponsorship look a lot like the opposite of those listed above. Funding for these initiatives can be problematic if they are not seen as strategically important and, without funding and resources, these initiatives can have problems fulfilling their vision.
For example, the NARA 2019 and 2022 mandatesare driving US federal agencies to re-examine their existing processes and technology. Those examinations often reveal the need for more effective methods of the identification, handling, and disposition of records. Where they have previously heavily relied on manual, user-driven processes, automation through technology is now seen as the proper way forward. That said, if there isn’ta tight alignment between the records management teamand the executive level, the engagement and commitment to these technology evaluations can stall or lack priority against other IT procurement priorities.
Another telltale sign of lack of executive sponsorship is when records management teams have to constantly chase business units for the information required to formalize their program or for compliance with the policies once the program is launched. Simply put, the lack of the ability to borrow the authority and influence mentioned in the last paragraph can the level of change that is possible in the organization.
How to Encourage and Engage an Appropriate Sponsor
By now we’ve established why executive sponsorship for records management initiatives is so important. But how do you get there? If you’re leading a records management program, what can you do specifically to get the high-level buy-in you need? Here are a few best practices.
Be clear and detailed about the strategic value for your objective.Before you can gain buy-in, you need to understand for yourself why your program or initiative has value or urgency beyond solely the records management team. Again, AIIM has some great guidance here for building your business case justification. The good news here is that some of the same justifications you land on for selling your program up the chain will also help you communicate the importance of the program down to your business units.
Align with a compelling event or regulation.Nothing drives like a driver that is mandated from the outside. NARA’s 2019 and 2022 mandates are great examples here for the US federal agencies. Be ready to communicate both the detailed requirements of the driving event as well as the path you are laying out to get there.Not all compelling events will be date driven, of course. There’s always a looming driver for regulated organizations, though changes in the way the organization collaborates and the systems they use can be a good reason to re-evaluate and engage your executive sponsors at a deeper level.
Align with a key business initiative. Records management is the end of a larger information management strategy in organizations. Information management initiatives can be closely aligned with multiple strategic goals of an organization. A side benefit is that the better and more formalized the organization’s information management policies are (i.e. document templates, metadata/classification, data ownership, etc.), the more prepared they’ll be for implementing effective end of life strategies for that content. Where possible, identify and align with these deeper organizational goals.
Attaining executive sponsorship–and constructing effective records management policies as a whole–isn’t easy, but it also doesn’t have to be a major issue for your organization. If you’re looking for more insight into common issues and gray areas in the space, take a look at our Best Practices Guide for Records Management for the Digital Era.
March 28th, 2019 by Skype for Business News Aggregator
This is second part of the topic: ‘enhancing Skype for Business environment’. In case you miss, check part 1 to get the full picture. This one will be shorter and quick to read. It’s about authentication of your user accounts.…
March 28th, 2019 by Skype for Business News Aggregator
Microsoft Whiteboard Integration (commercial preview)
Microsoft Whiteboard in Teams meetings empowers meeting attendees from the same tenant to participate in the conversation regardless of the device you use or where you are. Whether joining from the meeting room or remotely, you can start a new board in the Teams meeting (currently supported on desktop, web and Surface Hub – coming soon to mobile). The board is automatically shared with meeting attendees. Users can ink together in real-time on the board. On Surface Hub, Users can launch the native Whiteboard app to enable an even richer collaboration experience with features such as sticky notes, images, and gridlines. To enable Whiteboard in a Teams meetings on Surface Hub, please turn on feature here
Note: For richer collaboration, please download the latest Microsoft Whiteboard App from the Store (requires User sign-in).
Switch cameras automatically
Microsoft Teams on Surface Hub now supports switching cameras automatically. The camera will use sound and motion detection to focus on who's talking. A light appears under each camera.
Note: In this update, Users will have to manually change settings to "Auto" while in a Teams meeting via Settings.
These updates provide user experience and reliability improvements.
Reduced echo emitting from speakers in meetings
Improved error handling when account is not licensed
Fixed layout issues for preview video in meetings
Fixed an issue to dismiss notifications when incoming calls are declined
Disabled dial pad when Enterprise Voice is not available
March 28th, 2019 by Skype for Business News Aggregator
At EC19, Yealink announced a partnership with Ribbon to deliver PSTN survival with Microsoft Teams for their Teams Phones. I don’t have a Yealink, but I do have a few VVX’s lying around my home office, so I thought I would give it a shot and see if I can get this working on other handsets. Turns out I can and that means I do not have to invest in new hardware for this disaster event solution. Better still it works for Skype for Business On-Prem and Online as well as Microsoft Teams!
So, how does it work conceptually? Basically the VVX phone registers to both Skype for Business Online (Teams via SIP Gateway) and to the SBC at the same time. When registration fails to Skype for Business / Teams, the phone will failover the active registration to the SBC and become essentially a basic SIP phone for making and receiving calls.
In order to facilitate this functionality, there are a couple of per-requisites.
The SBC must have local SIP registrar licenses to cover the number of phones you want to have this capability
The VVX phones must be running UCS 5.8 onwards
To set this up I will say right now is not that easy, or scale-able. This solution is really meant for mission critical phones that must survive a failure and not every phone in your business. Why, will become apparent as you read on. But basically, you would provide this capability maybe for your senior execs, inbound sales / support teams and main office reception type scenarios.
First we need to configure a Cloud IP Phone Policy in the tenant. This is so we can disable the management of firmware by Office 365. The reason for this is we need UCS 5.8 or higher, and Microsoft will force a rollback to UCS 5.6 if managed by Office 365. As there is only the global policy, this would mean that all phones would be affected.
Set-CsIPPhonePolicy -Identity Global -EnableDeviceUpdate $False
Now update your VVX to UCS 5.8 either by Phone Web UI or on-prem provisioning server.
Before we touch the phone any further, we now need to set up the SBC to support this. Assuming you now have the required Local Registrar license installed.
First on the SBC go to SIP > Local Registrars and create one. I’ve called mine “Teams Fallback SIP”
Now from SIP > Local / Pass thru Auth tables create an auth table. I’ve called mine “Teams Local Fallback”.
In this auth table, create an account for the phone that you want to survive. Note it is important that the address URI is the same as the DDI assigned to the user in Teams. The username and password can be anything. But for simplicity sake, the username is the DDI and I’ve set the password to 12345
Now we have the account set up, we need to catch registrations, so we need to create a signalling group. Under signalling groups create a SIP SG, I’ve called mine “Teams Fallback Phone”
The settings of the SG should be:
Call Routing Table (select any for now – we will come back to this)
SIP Profile: Default
SIP Mode: Local Registrar
Registrar: Teams Fallback SIP
Media List: Default
Listen Ports: 5060 TCP/UDP
Federated IP: <your network range>
Now create a call route table to handle outbound calls from phones when they are in a fallback mode.
Go back to the Signalling Group and set the call routing table to this and apply the settings.
Now we have the bones of the configuration we need. Now to configure the outbound call route. From the routing table we created, add a route to your ITSP. You can use the same transformation tables created for your Teams -> ITSP if it is compatible
This is now outbound calling configured. Now let’s configure inbound.
For inbound we need to ensure that the fallback route is only tried if the primary (via Microsoft Teams Direct Routing) is unresponsive. There are a few ways in which to achieve this, but I am going with the simple way. Rather than using cause code re-routes, I am simply going to add my fallback signalling group to the existing ITSP -> Teams route entry as a second possible destination for calls.
The way that this works is destination SGs are attempted on a first to last basis. As the Teams SG will almost always be up, the calls will always route via that. In an outage, which is what we want, it will not be available so the 2nd SG is tried and this is to our local SIP registrar table.
The SBC configuration is now complete. Now we need to configure the VVX phone.
You will need to add the following configuration to your phone’s cfg file
Where 192.168.1.252 is the IP address of your SBC, the userId is the sip user we created in the local auth table and it’s password.
Now the solution is ready the last note of interest is the experience.
By default, phones register to Office 365 for a period of 10 minutes. usually the phone re-registers when the time gets to 50% or 5 minutes. The phone is a single line, therefore, can only have one active registration for calls at any one time.
During a failure event, there may be a period of 10 minutes where no calling is possible until the registration with Office 365 times out, the phone will then automatically mark the backup registration active. Calls during this time inbound will receive a busy tone, and the message back from the phone will be a SIP 486 “Busy Here” message.
Once the phone realises that it can no longer register to Office 365 calls will proceed as normal, but the phone will be in a basic mode, which is nothing more than a landline type service.
As you can see, the solution would be quite hard to scale beyond the few critical phones you need and it is quite limited, but its giving your critical users something rather than nothing in a time where you need to be focused on restoring a service, not providing an ad-hoc workaround on a case by case basis.
March 27th, 2019 by Skype for Business News Aggregator
“Mobility”, as an industry term, refers to any application developed for a mobile device that facilitates business outside of a typical office environment. By using the portable power found in modern smartphones, a lot of the work that just a few years ago could only be done on a PC can be done in the palm of your hand.