I have been working remotely for over 10 year. However, as we all embrace the use of video/audio conferencing during the COVID-19 pandemic, I would like to remind all users the best practices and online meetings etiquette.

1. Use a Headset when possible: Wearing a headset in noisy, closed, crowded spaces can virtually eliminate distracting echoes and help other participants hear you more clearly. Even using a regular headphone (such as the one you use for your iPhone/Android) helps to minimize the echo and provide a better experience for all participants.
2. Mute yourself when you are not speaking: Mute yourself when you are not speaking (especially if you are on a call with more than two participants). This will significantly reduce background noise for everyone on the call. Learn where the mute button is in the Teams app or the phone.
3. Join only once the audio conference:  If you are using the Teams App for audio, refrain from dialing from your phone into the conference call at the same time. The audio will still come out via the computer speakers and feeding back into the phone creating a feedback loop.
4. Use the Phone Audio when needed: If you are on the road with no internet access, or if you are experiencing slow internet connections, or simply the computer audio system is not working properly during a video conference. Remember to use the dial-in options using your phone or get the Teams app to call your number to join the audio portion of the conference. But please, don’t join the audio conference twice.
5. Check you backlight and position: Having any backlight on a video call can negatively impact the quality by giving you a harsh silhouette effect. Whenever possible, try sitting with your back to a wall rather than a window or try lowering the shades.
6. Test your internet connection and hardware ahead of time: Every attendee should make sure that they can log on properly using the app and test the microphone, camera and equipment in advanced.
7. Resist to multitask: During a call, avoid multitasking at all costs. It’s professional video/audio etiquette to give all colleagues or participants your complete attention. Avoid the urge to check your email or phone while listening.

I personally use Microsoft Teams for all my conference calling and video conferencing. However, these best practices are applicable to any type of video conference system.

With Microsoft, security can be simple once again. Microsoft 365 provides an intelligent security hub that works seamlessly across platforms, going far beyond Microsoft to Linux, Mac and others — so you can manage mission-critical workloads with existing tools at your fingertips. Contact us to learn how Microsoft 365 helps keep your organization secure and productive.

Requirements

• Both the RD Web and RD Gateway endpoints must be located on the same machine, and with a common root
• You should already have deployed RDS
• You should have already deployed and enabled Application Proxy agent in your local network.
• This scenario only works with Internet Explorer on Windows 7 or Windows 10 desktops. I repeat ONLY INTERNET EXPLORER
• It is recommended to use the same internal and external FQDN. If the internal and external FQDNs are different then you should disable Request Header Translation to avoid the client receiving invalid links.
• On Internet Explorer, enable the RDS ActiveX add-on.

Publish the RD host endpoint

1. Publish a new Application Proxy application with the following values:

1. • Internal URL: https://remote.contoso.com/, where <remote.contoso.com> is the common root that RD Web and RD Gateway share.
   • External URL: This field is automatically populated based on the name of the application, but you can modify it. Your users will go to this URL when they access RDS.
   • Preauthentication method: Azure Active Directory
   • Translate URL headers: No
2. Assign users to the published RD application. Make sure they all have access to RDS, too.
3. Leave the single sign-on method for the application as Azure AD single sign-on disabled. Your users are asked to authenticate once to Azure AD and once to RD Web, but have single sign-on to RD Gateway.
4. 
5. Select Azure Active Directory, and then App Registrations. Choose your app from the list.
6. Under Manage, select Branding.
7. Update the Home page URL field to point to your RD Web endpoint (like https://remote.contoso.com/RDWeb).

Direct RDS traffic to Application Proxy

Connect to the RDS deployment as an administrator and change the RD Gateway server name for the deployment. This configuration ensures that connections go through the Azure AD Application Proxy service.

1. Connect to the RDS server running the RD Connection Broker role.
2. Launch Server Manager.
3. Select Remote Desktop Services from the pane on the left.
4. Select Overview.
5. In the Deployment Overview section, select the drop-down menu and choose Edit deployment properties.
6. In the RD Gateway tab, change the Server name field to the External URL that you set for the RD host endpoint in Application Proxy.
7. Change the Logon method field to Password Authentication.
8. 
9. Run this command for each collection:

Set-RDSessionCollectionConfiguration -CollectionName "QuickSessionCollection" -CustomRdpProperty "pre-authentication server address:s:https://remotedesktoptest-aadapdemo.msappproxy.net/`nrequire pre-authentication:i:1"

(Remember to use the ` on the previous command