The connection to Microsoft Exchange is unavailable, Outlook must be online or connected

Microsoft Outlook, at times, is known to give an error saying — The action cannot be completed. The connection to Microsoft Exchange is unavailable, Outlook must be online or connected to complete this action. In this post, we will show how you can fix this problem and get back it to working as usual.

The connection to Microsoft Exchange is unavailable, Outlook must be online or connected to complete this action

The connection to Microsoft Exchange is unavailable, Outlook must be online or connected to complete this action

The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action

There are two ways to fix tjis issue. First, create a new default profile. Second, Delete the default profile. Not many have multiple Outlook profiles is not always an option. So use the second method as follows:

  1. Delete Default Profile
  2. Create a New Outlook Profile
  3. Update or create your Outlook profile with RPC encryption
  4. Disable the encryption requirement on all CAS servers
  5. Deploy a Group Policy setting to update existing Outlook profiles with RPC encryption

The first, three can be configured by the end-user, while the last two are only for Servers.

1] Delete Default Profile

Change Default Outlook Profile Windows 10

  • Launch Outlook, and then click on Info > Account settings dropdown > Manage Profile
  • It will open the Mail Setup window. Click on Show Profiles button.
  • Delete the default profile by clicking on the Remove button.
  • Restart Outlook.

When you remove the profile, all offline cached content for its account will be removed. However, you can backup the OST profile to reuse it.

When you relaunch Outlook, you will have to create a new profile, and then go through the setup process again.

2] Create a New Outlook Profile

Create New Outlook Profile Windows 10

If you do not want to delete, you can create a new default profile. At the Mail Setup > Profiles section, you can click on the Add button, and then give a name to the profile. Next, you need to add the email accounts you want to add. Make sure to properly configure the email account, so the error doesn’t reappear. Also, make sure to set that as the default profile.

3] Update or create your Outlook profile with RPC encryption

create your Outlook profile with RPC encryption

Most of the users have all email accounts under one single profile. One of the email accounts may be having trouble with that is running Microsoft Exchange Server 2010, Microsoft Exchange Server 2013, or Microsoft Exchange Server 2016. These are usually corporate accounts that haven’t been configured properly.

  1. Launch Outlook, and then click on Info > Account settings dropdown > Manage Profile
  2. Click on E-mail Accounts > select the email which is configured with Exchange Server, and then click on Change > More Settings
  3. In the Microsoft Exchange window, switch to Security tab
  4. Select Encrypt data between Microsoft Office Outlook and Microsoft Exchange.
  5. Click Ok and exit

It should fix the issue if it were because of RPC encryption error.

4] Disable the encryption requirement on all CAS servers

This part is specifically for IT admins who can disable encryption requirements. Microsoft warns that it should be only used where you cannot immediately deploy the necessary RPC encryption settings on your Outlook clients. Run the following command in the Exchange Management Shell:

Set-RpcClientAccess –Server <Exchange server name> –EncryptionRequired:$False

You must run this cmdlet for all Client Access servers that are running Exchange Server 2010 or later version. Rerun this command for each Exchange server that has the Client Access Server role. Also, make sure to disable RPC encryption, which we talked about in the above step.

However, make sure to enable it back again after deployment with changes to the RPC requirement on the Outlook.

5] Deploy a Group Policy setting to update existing Outlook profiles with RPC encryption

Enable RPC Encryption Policy Settings

You can also change RPC settings on the server-side by using Group Policy. Navigate to User Configuration > Administrative Templates > Microsoft Office “Version number” > Account Settings > Exchange. Locate policy Enable RPC encryption and disable it.

We hope these methods helped you to resolve Outlook connected issues with Microsoft Exchange.

SD Times news digest: Microsoft’s AI for Accessibility grants, Hyperledger Sawtooth 1.2, and …

Microsoft announced that it is offering a grant to ObjectiveEd, the makers of the Braille Tutor app, which incorporates AI-based speech recognition to help students practice reading Braille with personalized learning plans. The grant is part of Microsoft’s AI for Accessibility program to help people using AI-powered technology.

The Braille Tutor app was created because currently, only 13% of blind or visually impaired students know Braille and in most public schools, teachers who know Braille only come to the schools once a week to teach personalized lessons, the company explained. The app aims to fix that by helping to teach Braille.

“We have a huge opportunity and a responsibility to be making technology smarter and more useful for people with disabilities,” said Mary Bellard, Microsoft senior architect lead for accessibility. The aim of the AI for Accessibility program, which began in 2018 and now has 32 grantees, is to help people “build something really useful at the intersection of AI, accessibility and disability.”

MIT researchers develop algorithm to give robots a better grip

Researchers at MIT developed a new algorithm that speeds up the planning process that robots use to adjust their grip on objects, thereby giving them a better, faster grasp.

Whereas traditional algorithms would require tens of minutes for planning out a sequence of motions, the team’s new approach shaves this pre planning process down to less than a second, according to a post.

“Seemingly simple variations, such as how hard robot grasps the object, can significantly change how the object moves in the grasp when pushed,” Rachel Hollada, a graduate student in electrical engineering and computer science at MIT, explained. “Based on how hard you’re grasping, there will be a different motion. And that’s part of the physical reasoning that the algorithm handles.”

Hyperledger Sawtooth 1.2

Hyperledger Sawtooth 1.2 is now available, adding full support for the PBFT consensus engine and for mobile application development with new SDKs for iOS and Android.

“Now, Sawtooth PBFT 1.0 is the preferred consensus for small-to-medium networks — it’s leader-based, non-forking, and fast. PBFT also provides the safety and liveness guarantees that are necessary for operating a blockchain network with adversarial trust. This makes PBFT an excellent option for smaller consortium-style networks,” the Hyperledger Foundation wrote in a post.

The release also contains transaction family compatibility with Sawtooth Sabre, enhanced performance and stability, improved documentation, better support for consensus algorithms, and overall platform refinements for a better developer experience.

Accusoft announces Barcode Xpress .NET Core

Accusoft released Barcode Xpress .NET Core, which offers support for 1D and 2D barcodes, recognition of over 30 barcode types and support for damaged and broken barcodes.

“Developers can integrate Barcode Xpress into their application with just a few lines of code,” said Steve Wilson, VP of product at Accusoft. “This new development environment enables developers from a variety of programming backgrounds to integrate leading barcode technology into their applications.”

Barcode Xpress is now available in Node.js, .NET, C/C++, ActiveX, Java, and .NET Core. The full details are available here.

Related:

  • No Related Posts

Fix Mailbox does not exist error in Microsoft Teams

If you’re using Microsoft Teams, then maybe you have come across a particular error in recent times. It’s nothing out of the ordinary, but annoying nonetheless. The issue we are talking about here is when the mailbox in Microsoft Teams is empty. You may see an error message – Mailbox does not exist.

An empty mailbox, or one that doesn’t exist, would be a surprise to anyone that had content within it before this problem. The big question right now is what caused this to happen, and whether or not if there is a way to fix it once and for all. Now, we can’t say for certain what caused the mailbox to go empty, but we can say the problem can be solved.

Mailbox does not exist error in Microsoft Teams

From what we have gathered, the mailbox does not exist error tends to happen when Microsoft Exchange is in use. Yes, many users of Microsoft Teams take big advantage of Exchange, which should come as no surprise to anyone at this point.

OK, so let’s look into how we can solve the no mailbox error, and hopefully, it will never show its ugly head ever again

Microsoft Teams – Mailbox does not exist

Fixing this problem is super easy, at least from our point of view, so don’t be discouraged because we will make it easy to understand.

  1. Check the O-auth setting
  2. Verify that Exchange Online can successfully connect

1] Check the O-auth setting

The first thing you’ll need to do is run the Test-OAuthConnectivity tool to see if things are working as they should. The idea here is to make sure your organization can successfully connect to Exchange Online because this is a very important aspect.

To get this done, please launch Windows PowerShell by right-clicking on the Start menu button, then select Windows PowerShell from the menu. We suggest choosing the admin version for a better chance of this working.

After launching the tool, please copy and paste the following into PowerShell then hit the Enter key on your keyboard:

Test-OAuthConnectivity -Service EWS -TargetUri https://outlook.office365.com/ews/exchange.asmx -Mailbox <On-Premises Mailbox> -Verbose | Format-List

2] Verify that Exchange Online can successfully connect

The next step, then, is to test if the connection is working, and yes, the task is easy to accomplish. You see, simply follow the steps above to launch Windows PowerShell, then copy and paste the following, and as usual, hit the Enter key:

Test-OAuthConnectivity -Service EWS -TargetUri <external hostname authority of your Exchange On-Premises deployment>/metadata/json/1 -Mailbox <Exchange Online Mailbox> -Verbose | Format-List

That should get the job done, 100 percent. So, go ahead and check the mailbox to see if its back to its regular setting.

All the best.

Microsoft Windows Security Updates September 2019 overview

It is September 10, 2019 and Microsoft has just released security and non-security updates for its Microsoft Windows operating system and other company products.

Our overview of the September 2019 Patch Day provides system administrators and home users with information on the released updates. It features some stats at the beginning, provides links to all support articles and direct download options, lists known issues and security advisories, and provides other relevant information.

Check out the August 2019 update overview in case you missed it.

Microsoft Windows Security Updates September 2019

Here is a handy Excel spreadsheet that lists all released security updates for Microsoft products in September 2019. Please download it with a click on the following link: Microsoft Windows Security Updates September 2019

Executive Summary

  • Microsoft released security updates for all client and server versions of the Windows operating system that it supports.
  • The following non-Windows products had security updates released as well: Internet Explorer, Microsoft Edge, Microsoft Office, Adobe Flash Player, Microsoft Lync, Visual Studio, .NET Framework, Microsoft Exchange Server, Microsoft Yammer, .NET Core, ASP.NET, Team Foundation Server, Project Rome.
  • Microsoft fixed the high CPU usage issue from SearchUI.exe in Windows 10 1903.
  • The Microsoft Update Catalog website lists 215 updates.

Operating System Distribution

  • Windows 7: 32 vulnerabilities: 4 rated critical and 28 rated important
    • CVE-2019-0787 | Remote Desktop Client Remote Code Execution Vulnerability
    • CVE-2019-1280 | LNK Remote Code Execution Vulnerability
    • CVE-2019-1290 | Remote Desktop Client Remote Code Execution Vulnerability
    • CVE-2019-1291 | Remote Desktop Client Remote Code Execution Vulnerability
  • Windows 8.1: 33 vulnerabilities: 5 rated critical and 28 rated important
    • same as Windows 7 plus
    • CVE-2019-0788 | Remote Desktop Client Remote Code Execution Vulnerability
  • Windows 10 version 1803: 46 vulnerabilities: 5 critical and 41 important
    • same as Windows 8.1
  • Windows 10 version 1809: 45 vulnerabilities: 5 critical and 40 important
    • same as Windows 8.1
  • Windows 10 version 1903: 45 vulnerabilities: 5 critical and 40 important.
    • same as Windows 8.1

Windows Server products

  • Windows Server 2008 R2: 31 vulnerabilities: 3 critical and 28 important.
    • CVE-2019-1280 | LNK Remote Code Execution Vulnerability
    • CVE-2019-1290 | Remote Desktop Client Remote Code Execution Vulnerability
    • CVE-2019-1291 | Remote Desktop Client Remote Code Execution Vulnerability
  • Windows Server 2012 R2: 31 vulnerabilities: 3 critical and 28 important.
    • same as Windows Server 2008 R2.
  • Windows Server 2016: 39 vulnerabilities: 3 critical and 36 important
    • same as Windows Server 2008 R2.
  • Windows Server 2019: 43 vulnerabilities: 3 critical and 40 are important.
    • same as Windows Server 2008 R2.

Other Microsoft Products

  • Internet Explorer 11: 4 vulnerabilities: 3 critical, 1 important
  • Microsoft Edge: 7 vulnerabilities: 5 critical, 2 important
    • CVE-2019-1138 | Chakra Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1217 | Chakra Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1237 | Chakra Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1298 | Chakra Scripting Engine Memory Corruption Vulnerability
    • CVE-2019-1300 | Chakra Scripting Engine Memory Corruption Vulnerability

Windows Security Updates

Windows 7 SP1 and Windows Server 2008 R2 SP1

Monthly Rollup: KB4516065

Security Only: KB4516033

  • Provides protections against a new subclass of speculative execution side-channel vulnerabilities, known as Microarchitectural Data Sampling, for 32-Bit (x86) versions of Windows
  • Security Updates

Windows 8.1 and Windows Server 2012 R2

Monthly Rollup: KB4516067

Security Only: KB4516064

  • Same as Windows 7 and Server 2008 R2

Windows 10 version 1803

Cumulative Update: KB4516058

  • Provides protections against a new subclass of speculative execution side-channel vulnerabilities, known as Microarchitectural Data Sampling, for 32-Bit (x86) versions of Windows.
  • Security updates.

Windows 10 version 1809 and Windows Server 1809

Cumulative Update: KB4512578

  • Same as Windows 10 version 1803.

Windows 10 version 1903 and Windows Server version 1903

Cumulative update: KB4515384

  • Same as Windows version 1803 plus
  • Fixed the high CPU usage issue caused by SearchUI.exe.

Windows 10 version 1903 and Windows Server 1903

Other security updates

KB4516046 — Cumulative security update for Internet Explorer: September 10, 2019

KB4474419 — SHA-2 code signing support update for Windows Server 2008 R2, Windows 7, and Windows Server 2008: August 13, 2019

KB4516655 — 2019-09 Servicing Stack Update for Windows Embedded Standard 7, Windows 7, and Windows Server 2008 R2

KB45171342019-09 Servicing Stack Update for Windows Server 2008

KB4512938 — 2019-09 Servicing Stack Update for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2

KB4512939 — 2019-09 Servicing Stack Update for Windows Embedded 8 Standard and Windows Server 2012

KB4511839 — 2019-09 Servicing Stack Update for Windows 10 Version 1703

KB4512573 — 2019-09 Servicing Stack Update for Windows 10 Version 1507

KB4512575 — 2019-09 Servicing Stack Update for Windows 10 Version 1709

KB4512576 — 2019-09 Servicing Stack Update for Windows Server Version 1803 and Windows 10 Version 1803

KB4512577 — 2019-09 Servicing Stack Update for Windows 10 Version 1809 and Windows Server 2019

KB4515383 — 2019-09 Servicing Stack Update for Windows 10 Version 1903

KB4512574 — 2019-09 Servicing Stack Update for Windows Server 1903 RTM, Windows 10 Version 1903, Windows Server 2019, Windows 10 Version 1809, Windows Server Version 1803, Windows 10 Version 1803, Windows Server 2016, Windows Server Version 1709, Windows 10 Version 1709, Windows 10 Version 1703, Windows 10 Version 1607, Windows 10 Version 1511, Windows 10 Version 1507, and Windows 10

Server / Embedded

KB4516026 — 2019-09 Security Monthly Quality Rollup for Windows Server 2008

KB4516051 — 2019-09 Security Only Quality Update for Windows Server 2008

KB4516055 –2019-09 Security Monthly Quality Rollup for Windows Embedded 8 Standard and Windows Server 2012

KB4516062 — 2019-09 Security Only Quality Update for Windows Embedded 8 Standard and Windows Server 2012

Microsoft .NET

KB4514330 — Security Only Update for .NET Framework 4.8 for Windows Server 2012

KB4514331 — Security Only Update for .NET Framework 4.8 for Windows 8.1 and Server 2012 R2

KB4514337

KB4514338 — Security Only Update for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 8.1 and Server 2012 R2

KB4514341 — Security Only Update for .NET Framework 4.5.2 for Windows 8.1 and Server 2012 R2

KB4514342 — Security Only Update for .NET Framework 4.5.2 for Windows Server 2012

KB4514349 — Security Only Update for .NET Framework 3.5 for Windows Server 2012

KB4514350 — Security Only Update for .NET Framework 3.5 for Windows 8.1 and Server 2012 R2

KB4514360 — Security and Quality Rollup for .NET Framework 4.8 for Windows Server 2012

KB4514361 — Security and Quality Rollup for .NET Framework 4.8 for Windows 8.1, RT 8.1, and Server 2012 R2

KB4514363 — Security and Quality Rollup for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows Server 2012

KB4514364 — Security and Quality Rollup for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 8.1, RT 8.1, and Server 2012 R2

KB4514367 — Security and Quality Rollup for .NET Framework 4.5.2 for Windows 8.1, RT 8.1, and Server 2012 R2

KB4514368 — Security and Quality Rollup for .NET Framework 4.5.2 for Windows Server 2012

KB4514370 — Security and Quality Rollup for .NET Framework 3.5 for Windows Server 2012

KB4514371 — Security and Quality Rollup for .NET Framework 3.5 for Windows 8.1 and Server 2012 R2

KB4514598 — Security Only Update for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows Server 2012

KB4514599 — Security Only Update for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 8.1 and Server 2012 R2

KB4514602 — Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 7 SP1 and Server 2008 R2 SP1

KB4514603 — Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows Server 2012

KB4514604 — Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 8.1, RT 8.1, and Server 2012 R2

KB4514605 — Security and Quality Rollup for .NET Framework 2.0, 3.0, 4.5.2, 4.6 for Windows Server 2008 SP2

KB4514354 — 2019-09 Cumulative Update for .NET Framework 4.8 for Windows Server 2016 and Windows 10 Version 1607

KB4514355 — 2019-09 Cumulative Update for .NET Framework 4.8 for Windows 10 Version 1703

KB4514356 — 2019-09 Cumulative Update for .NET Framework 4.8 for Windows 10 Version 1709

KB4514357 — 2019-09 Cumulative Update for .NET Framework 4.8 for Windows 10 Version 1803 and Windows Server 2016

KB4514358 — 2019-09 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1809

KB4514359 — 2019-09 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1903

KB4514366 — 2019-09 Cumulative Update for .NET Framework 3.5 and 4.7.2 for Windows 10 Version 1809

KB4514601 — 2019-09 Cumulative Update for .NET Framework 3.5, 4.7.2 and 4.8 for Windows 10 Version 1809

Known Issues

Windows 7 SP1 and Windows Server 2008 R2 (monthly rollup only)

  • VBScript may not be disabled in Internet Explorer even though it should be

Windows 8.1 and Windows Server 2008 R2

  • Certain operations may fail on Cluster Shared Volumes

Windows 10 version 1803

  • Operations may fail on Cluster Shared Volumes.
  • Black screen during first logon after update installation issue

Windows 10 version 1809

  • Same as Windows 10 version 1803 plus
  • Error on some devices with certain Asian language packs installed: 0x800f0982 – PSFX_E_MATCHING_COMPONENT_NOT_FOUND.
  • Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data, often 50 or 100 entries

Security advisories and updates

ADV990001 | Latest Servicing Stack Updates

ADV190022 | September 2019 Adobe Flash Security Update

Non-security related updates

Microsoft Office Updates

You find Office update information here.

How to download and install the September 2019 security updates

windows updates september 2019 microsoft

Most home systems receive updates automatically especially when they run Windows 10. Updates are not pushed in real-time to devices running Windows. Some administrators prefer to install security updates the moment they are released, others to wait to make sure that the updates don’t introduce any issues on the system.

Note: it is recommended that you back up the system partition before you install updates. Use programs like Paragon Backup & Recovery Free or Macrium Reflect for that.

Admins may check for updates manually to retrieve the released updates right away. Here is how that is done:

  • Open the Start Menu of the Windows operating system, type Windows Update and select the result.
  • Select check for updates in the application that opens. Updates may be installed automatically when they are found or offered by Windows; this depends on the operating system and version that is used, and update settings.

Updates may also be downloaded from the Microsoft Update Catalog website.

Direct update downloads

Windows 7 SP1 and Windows Server 2008 R2 SP

  • KB4516065 — 2019-09 Security Monthly Quality Rollup for Windows 7
  • KB4516033 — 2019-09 Security Only Quality Update for Windows 7

Windows 8.1 and Windows Server 2012 R2

  • KB4516067 — 2019-09 Security Monthly Quality Rollup for Windows 8.1
  • KB4516064 — 2019-09 Security Only Quality Update for Windows 8.1

Windows 10 (version 1803)

  • KB4516058 — 2019-09 Cumulative Update for Windows 10 Version 1803

Windows 10 (version 1809)

  • KB4512578 — 2019-09 Cumulative Update for Windows 10 Version 1809

Windows 10 (version 1903)

  • KB4515384 — 2019-09 Cumulative Update for Windows 10 Version 1903

Additional resources

Summary
Microsoft Windows Security Updates September 2019 overview
Article Name
Microsoft Windows Security Updates September 2019 overview
Description
It is September 10, 2019 and Microsoft has just released security and non-security updates for its Microsoft Windows operating system and other company products.
Author
Martin Brinkmann
Publisher
Ghacks Technology News
Logo
Ghacks Technology News
Advertisement

Related:

  • No Related Posts

How is URL list for application “Microsoft Update” updated

I need a solution

Hi;

My understanding is that if you wanted to exempt all URL to do with Windows Updates, you can do that by using the application “Microsoft Update”, which will know of all the URLs involved, This way you dont’ have to do it based on a changing list of URLs.

My question is: If this list of URLs is changed by Microsoft, how does the application “Microsoft Update” stay up to date with the latest URL list and how does the Proxy SG get updated with it.

Kindly

Wasfi

0

Related:

  • No Related Posts

Fix: Outlook does not support connections to Exchange ActiveSync

While trying to connect your Outlook account with Exchange by using ActiveSync protocol the users may get the Outlook does not support connections to exchange by using ActiveSync error. This error is commonly caused if the Outlook does not support connection to a server that is running Exchange server. A similar discussion can also be read on the Microsoft Community forum.

On the same Windows 8 Pro machine, on the same user account – Windows Mail app is connected successfully to my corporate e-mail account (‘Outlook‘ account type, use SSL connection, domain and user name specified).

In Outlook 2013 the same account can’t be connected (selecting ‘ActiveSync’ account type, specifying server name and user name, however there are no options to specify SSL and domain) – getting error message ‘Log onto Exchange ActiveSync mail server (EAS): The server cannot be found.’

Follow the steps listed in the article below to fix Outlook server issue with ActiveSync and Exchange.

Is the Exchange Activesync supported by Outlook?

1. Connect to Exchange using Standard Exchange Connection

  1. Launch the Outlook desktop app.
  2. Click on File and then click on Add Account button.

    outlook does not support connections to exchange by using activesyncoutlook does not support connections to exchange by using activesync
  3. Enter your email address and click Connect.outlook does not support connections to exchange by using activesyncoutlook does not support connections to exchange by using activesync
  4. Now you will be asked to enter your password again. Enter the password, and click OK.
  5. Click Finish to connect to exchange using standard exchange connection.
  6. Trying to set up your email account manually can create issues like the one mentioned earlier. Try to set up the email account normally and check if the error is resolved.

Deal with spam mails for good with these Exchange anti-spam software for Exchange email server.


2. Configure Outlook 2013 / 2016 Manually

  1. If you want to configure Outlook for Exchange by using ActiveSync do the following.
  2. Launch the Outlook desktop client.
  3. Choose “New Email Account“.
  4. Select “Manual setup or additional server types“.

    outlook does not support connections to exchange by using activesyncoutlook does not support connections to exchange by using activesync
  5. Select “Exchange ActiveSync“.
  6. Now you need to fill in the server setting. The username can be in Domainusername format.
  7. Now press and hold the Enter key on the Keyboard until all the boxes go away.
  8. Once the connection goes through. Launch the Outlook client and check if the error is resolved.

For Outlook 2016 / Office 365

  1. Launch the Outlook client in your Windows system.
  2. Click on File and select Add Account.
  3. Now enter the email address for the account and click the Advanced Options.
  4. Select “Let me set up my account manually” option.

    outlook does not support connections to exchange by using activesyncoutlook does not support connections to exchange by using activesync
  5. Click the Connect button.
  6. Select “Exchange” option.

    outlook does not support connections to exchange by using activesyncoutlook does not support connections to exchange by using activesync
  7. Enter the password for your ID and check if the connection is established without any error.

The EAS protocol provides access to data in exchange mailboxes thus keeping all of your connected devices in sync. Since EAS connection does not provide all the features of an Exchange account, Outlook does not support this method resulting in the error.

RELATED STORIES YOU MAY LIKE:

Related:

  • No Related Posts

Avoid embarrassing mistakes: How to recall an email in Outlook

Outlook Windows 10

How to recall an email in Outlook

Recalling an email in Outlook can save you from many awkward or embarrassing situations. Here’s how you can do that.

  1. Head to the Sent Items part of the Outlook app and double click the message that you want to recall.
  2. Navigate to the Message tab in the open window with the message.
  3. Head to the fourth group of options in the top menu bar under Move, and choose Recall this Message.
  4. Choose to delete the unread copy of the message on the server, or replace it with a new message.
  5. Press OK

Applies to All Windows 10 Versions

One of the most embarrassing things in life is replying to an email, and realizing you’ve replied to all, or sent out something to the recipient that wasn’t meant to see. Luckily, there is a way around this common problem. With the Outlook app as part of Office 365, you can easily recall an email — granted that you’re using a Microsoft Exchange account and the feature has been enabled by your IT department. In this guide, we’ll show you how you avoid mistakes and recall emails in Outlook.

Steps to recall an email in Outlook

The first step in recalling an email in Outlook is to head to the Sent Items part of the Outlook App. After that, you can double click the message that you want to recall. Then, you need to navigate to the Message tab in the open window with the message. You can then head to the fourth group of options in the top menu bar under Move, and choose Recall this Message.

After following the steps above, a new window with the recall a message option should have appeared. From there, you’ll have two options, both of which will require you to press on OK afterward. You can either delete the unread copy of the message on the server, or you can replace it with a new message. The recipient might have already viewed the message, so deleting the unread copy might not always work. You can, however, select the option to receive a report on if the recall was successful.

Speed is of the essence here, and you should always recall right as you realize your mistake. If all else fails, that’s where the second option comes in, allowing you to write an apology message so that the original (error) email does not get opened.

Other ways to avoid having to recall messages

Recalling messages might not always work, but there are some ways you can avoid getting into the situation. First off, you should always slow down and double-check where your emails are heading. You also can even these troubles by setting up an Outlook rule to delay emails. This ensures that your messages sent through Outlook will be delayed by a certain number of minutes, giving you a short period of time to recall messages if something were to go wrong.

Share This

Further reading: Email, Microsoft, Outlook

Related:

  • No Related Posts

'404 Not Found' when trying to browse a newly published Managed Path in SharePoint when accessed using Storage Zones Controller SharePoint Connector

After publishing a new Managed Path in SharePoint, you may find that attempts to access this resource by using Storage Zones Controller SharePoint Connector fail. Upon closer inspection, the Storage Zone Controller log files may contain error messages similar to the following:

ERROR GetParent:: Exception thrown Message(The remote server returned an error: (404) Not Found.) StackTrace( at System.Net.HttpWebRequest.GetResponse()

at Microsoft.SharePoint.Client.SPWebRequestExecutor.Execute()

at Microsoft.SharePoint.Client.ClientContext.GetFormDigestInfoPrivate()

at Microsoft.SharePoint.Client.ClientContext.EnsureFormDigest()

at Microsoft.SharePoint.Client.ClientContext.ExecuteQuery()

at SharePointConnector*Util.SharePointUtility.GetParent(ClientObject spItem))

Related:

  • No Related Posts

Truffle Announces Upcoming Dev Support for Corda, Hyperledger Fabric, Tezos

Blockchain development company Truffle has unveiled plans to expand its fully managed developer suite to include support for the blockchain protocols Corda, Hyperledger Fabric and Tezos.

Truffle founder and CEO Tim Coulter announced the company’s plans at TruffleCon 2019 — Truffle’s annual dev conference — on Microsoft’s campus in Redmond, Washington. Coulter commented on how he thinks these tools will pave the way for collaboration via interoperability, saying:

“We are empowering developers to build enterprise-grade solutions on any network of their choosing, creating a path for future cross-network collaboration.”

According to a press release shared with Cointelegraph, the Truffle Suite is a fully managed blockchain for dev workflow, from backend work on smart contracts to frontend creation of applications.

Truffle’s developer tools reportedly date back to 2015, when they were developed from within ConsenSys’ venture production studio. As further noted, Truffle later received a $3 million investment in 2019 and partnered with Goldman Sachs and JP Morgan, as well as Microsoft Azure.

At press time, Truffle’s developer suite supports the blockchain protocols of Ethereum and Quorum.

Interoperability outside of code development

Having interoperable industry systems is a goal in fairly disparate contexts. As previously reported by Cointelegraph, the transportation group Blockchain in Transport Alliance (BiTA) is attempting to drive supply chain interoperability through blockchain technology. BiTA president Patrick Duffy has commented on the group’s goals, noting that blockchain “has the potential to smooth the transactions that occur between shippers and carriers, but it requires the active participation of transportation leaders.”

Related:

  • No Related Posts