techcommunity.microsoft.com Open in urlscan Pro
2a02:26f0:7100:1a9::207e  Public Scan

URL: https://techcommunity.microsoft.com/t5/exchange-team-blog/released-march-2021-exchange-server-security-updates/ba-p/2175901
Submission: On May 02 via api from US — Scanned from DE

Form analysis 2 forms found in the DOM

Name: form_4005740289e5c0POST https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.searchformv32.form.form

<form enctype="multipart/form-data" class="lia-form lia-form-inline SearchForm" action="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.searchformv32.form.form" method="post" id="form_4005740289e5c0" name="form_4005740289e5c0">
  <div class="t-invisible"><input value="blog-id/Exchange/article-id/29561" name="t:ac" type="hidden"><input value="search/contributions/page" name="t:cp" type="hidden"><input
      value="MA5UzNUXH-RXq3RWEjEfEpGGpxok9v3INItA4n_3iW2Ve7jXQw9-gj4-dbTbz-yjrv5fp98HfaTuCHBw8ecsXlM3IMLSn4XdguRf0tXgN5wikuR5PFuavZMb9bp2ihzDGXLNbeZS8uvIFIz0HECvzbwG8BXP46G-6-hsWt9IMzySk5abXtXxFwPt4nhSD_V_fm3Z-WvcowsUJi0TjXrdxbZ825-CnudXYIS9qT1Nb2OXmX0Q-cthkG_JkAKgnO4FO9I8NHMKOVVu4tvSBwIS7BL8UKMFBQaKd896a-q9n9gHYTpOZxQIJ7V_q5Vp6ZmtJ88wIJjth1xKjaxivULk1TGQl4akg2AJAeDVzpvuWMcoa0tgsom-IEzV1NDz03dn7Tchj1SiFvrcPI7BXILF3HG3TkuwNhWEod42LKYpNGlphFmA8k8BWYJNGPh9a8rRcy5cmflh3H4aBEc34umlyY24GKfNX28XBVbme8u7tcj8Hvp97RklHwDwiIpRwXLIEhUmOsVYecwNkEO3l82rGUv--QNW4lxW_L5azOuaJn68v7zylSkDJkI1q2ZVuG0hkqMkQ3Tw3wUjYY32yIvZPErNyxKtHYV45sWftzsKD1TqBBaS93WBIvkF0C0DY2O6C6_awJ58ixXK2VmOcr-bjqIFajeaJVDS_NrwQYx2GMReADlFVADWTAop4gmt29NQ8h5brNEMsiJ-SdIac3bWVhR2gR7DslMagCIIrXPJUmQYBwt21JehdkftTzMQFuJxdkmQChvsgc4EV8wf-Vkbtkgr6n0pdHzAHolcfq3hOu-DVDNkioYIYuWYXiPq1n7i8697ee7I5j-XJMamgJ_0-CdY2d4H4iv1d6v6bSA-f8RvrTC8kBxSBHmqhKPG_yGG1-ch6mkAdU09If5j-s3dqYHCQh_Xvm53kjbj-D5QOCCGLm0smsVvUMMl4mI8vEvgSZf1KI4dv7scIQdmooGFsDoldEweh-MsPg9GoSQa5SR9A9i08ZnJZ3703DeTqRT1PPTna7U1izDgArITql0xYNZJQLEJBZCCkBVhJAVCjYHAF4qvmzO1q0Ncljx-PCnnaP_4SYsHoXe845VKxwiO2ZxmcU0uXD9kiOD9maFZVNHfQEyptsYpJba93341GcABUCpdrn_NQvbd4Fhl0D-0iHgAaeFufaPk9ewr2F5xJwZP9ZQWMOcPQRL4kKD7_Z_R41kqVEK-xpZeUrsp46oQtRzBs7MJHKellKNGT3rfN7iPYW6bOz1WEAbb7uPtQjakPsoaEwXUhSPFJVBosEe0IA.."
      name="lia-form-context" type="hidden"><input value="BlogArticlePage:blog-id/Exchange/article-id/29561:searchformv32.form:" name="liaFormContentKey" type="hidden"><input
      value="yDZKQFNI0U/sd9X4pbUemqvQQZw=:H4sIAAAAAAAAALWSzUrDQBSFr4Wuigiib6DbiajdqAhFUISqweBaZibTNJpk4sxNEzc+ik8gvkQX7nwHH8CtKxfmzxJbwaTUVZhzw/nOmblP79COD+FAC6r40OAyQOWyCF0ZaMOkjtgrJgOp/NHONtER810sP9nfIkGtoCuVQ2hI+VAQpKHQqO67hEslPJcRRrUgPZaKlOOxKzx7wxIYhZtX487b+stnC5b60MnZ0junvkBY7d/QETU8GjiGlUYKnP0kRFguwEcFeAHBe02Dm0pyobWV+Wid0sbP9u7g4/G1BZCE8QWc1U3kpzapWoqZ+S+SvoMHgPQ+ypGVj/IoC2dlqHZ8CWZdV7xljUqszZa43voPYNHkFE7qGkdaqKrl1Pm7wEqmV59gcYjGkQOJP25h6jyJnOlzRv4DUURusIWhknbEsWo5K002vhzNufG1WHmDLwdzh8gDBQAA"
      name="t:formdata" type="hidden"></div>
  <div class="lia-inline-ajax-feedback">
    <div class="AjaxFeedback" id="feedback_4005740289e5c0"></div>
  </div>
  <input value="p5CsK7kD6_kpr7W5MSve-37FQHXAG7bLYHMZw3bqcqI." name="lia-action-token" type="hidden">
  <input value="form_4005740289e5c0" id="form_UIDform_4005740289e5c0" name="form_UID" type="hidden">
  <input value="" id="form_instance_keyform_4005740289e5c0" name="form_instance_key" type="hidden">
  <span class="lia-search-input-wrapper">
    <span class="lia-search-input-field">
      <span class="lia-button-wrapper lia-button-wrapper-secondary lia-button-wrapper-searchForm-action"><input value="searchForm" name="submitContextX" type="hidden"><input class="lia-button lia-button-secondary lia-button-searchForm-action"
          value="Search" id="submitContext_4005740289e5c0" name="submitContext" type="submit"></span>
      <input placeholder="Search the community" aria-label="Search" title="Search" class="lia-form-type-text lia-autocomplete-input search-input lia-search-input-message" value="" id="messageSearchField_4005740289e5c0_0" name="messageSearchField"
        type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Enter a search word</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="0W4FBD7oDyzwO1EbYovnf2V7fmfSJX0BHlrl8pMvSfk." rel="nofollow" id="disableAutoComplete_40057402b08e7d" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/29561&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div>
      <input placeholder="Search the community" aria-label="Search" title="Search" class="lia-form-type-text lia-autocomplete-input search-input lia-search-input-tkb-article lia-js-hidden" value="" id="messageSearchField_4005740289e5c0_1"
        name="messageSearchField_0" type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Enter a search word</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="IpJw-3QPFwLDb1A0KYuCGPwS4Kdi1-wEIvHvaDg6uWY." rel="nofollow" id="disableAutoComplete_400574030f81c3" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/29561&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div>
      <input placeholder="Search all content" ng-non-bindable="" title="Enter a user name or rank" class="lia-form-type-text UserSearchField lia-search-input-user search-input lia-js-hidden lia-autocomplete-input"
        aria-label="Enter a user name or rank" value="" id="userSearchField_4005740289e5c0" name="userSearchField" type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Enter a user name or rank</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="f9vKIcpLcccle7y75ql4FnzGHiiX2rKeQ7aZ1a2aQZA." rel="nofollow" id="disableAutoComplete_400574033999d2" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/29561&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div>
      <input title="Enter a search word" class="lia-form-type-text NoteSearchField lia-search-input-note search-input lia-js-hidden lia-autocomplete-input" aria-label="Enter a search word" value="" id="noteSearchField_4005740289e5c0_0"
        name="noteSearchField" type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Enter a search word</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="PqYWkjeGn0yPCN7y1MCqg9_7iq8z7VOE7_Rb2FKIBjg." rel="nofollow" id="disableAutoComplete_40057403631029" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/29561&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div>
      <input title="Enter a search word" class="lia-form-type-text ProductSearchField lia-search-input-product search-input lia-js-hidden lia-autocomplete-input" aria-label="Enter a search word" value="" id="productSearchField_4005740289e5c0"
        name="productSearchField" type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Enter a search word</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="trRIpp_fEy_zHkk_DuPmsHyGDLkYI1iBdwTXLjjTYmw." rel="nofollow" id="disableAutoComplete_4005740382eb73" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/29561&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div>
      <input class="lia-as-search-action-id" name="as-search-action-id" type="hidden">
    </span>
  </span>
  <span class="lia-cancel-search" tabindex="0">cancel</span>
</form>

Name: formPOST https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.searchformv32.form.form

<form enctype="multipart/form-data" class="lia-form lia-form-inline SearchForm" action="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.searchformv32.form.form" method="post" id="form" name="form">
  <div class="t-invisible"><input value="blog-id/Exchange/article-id/29561" name="t:ac" type="hidden"><input value="search/contributions/page" name="t:cp" type="hidden"><input
      value="M-yg6w5JTVJPdpUfEa8bsdCRAJmw_AWfjaySjQauqJh86dedph0Nox7f7GKK-1iQNEbG9EfFWUEUYbma3i0oTpzTk7d3rKZnNuE3-5nEXbBD2beE9TaTXfrf0w-BeIjeVPgBooPqvLE-j2eIHs8IIvC-b49pe3EwdCcwsZqhNG-0l4eiH6yuZ9QwCaICjGtEnYuDD4DghVgPktfzp89dS5OJqve4hzVzY0jweaOmcpQhJlkFVHNDBnGScjSUJ8IbuI1lcnLEnjKMpgME6MxI0JTq7EzKApEJXxK4oRpFRstB3MaNL5LrPfF5P4rGBxvD-FzD2BuvffYQERwLizwDhLPLAWPb0n9IeFj0G9MtqpVVI-PYIfodY4-a2qizVPtQRJ94FCxz3RBWg-FGawaTwlkt1Q7KvsR-fm1HYKyIZvj_ZRTDl84q-8Mbu1BQ4wUbr6JFUgIkYrsYzz2lkP7YZqI0NoOyejo9SN0VbaGdr4x1Zcpu0XkjBoxh_wY_2_mgAmrPgQqKF4ng3658d1YcG2gjkJycOT95HVQp9qXnYCQYtqbHYJKLVtFUHQarmn49p_1AbFhAxgOxDSGCEBt60IVmcmlJhJGmxJ8ruK_NoQtEUxSj_BmwcQzR8SdYsVtc7y4BWJql1gAbffiuV8nE_MVut_oBcWt6Ous3iSoaVdYEhthORn3LddrpUheqF3MKG4nYrMYj6GVKJvMJNY_PXdEllZCDXSON3Jls15Y-kurDg8TEY5_uLiZCALYfND_W7EwVH4RrsSsc3DoIxR68fXAaSPl7Yq7I9O5GGAtyatj05t6mT_i1StRoZX5-5wSN8ykomCF8RYeNqoIx64BTca5Xeq7DCHjhGzkzTqbIF19lZ_biykoSc27sBs8P_rYk2FOZ3kqeoQL1eanrNYeYelSCQOmzf9CWyGcl46A_hXGcMrAYWD7f-hsd8wR1tCxH95dHcFe-wxW-itVZCYUDul7x17fJ7-Y-n15VHPwt_OT9iMiZiTdZbJ2LWYdSu9PJ2n5RytuJvO1wmiU82Q9YNaTIWwFlsPSudYcoV_ZcEGa6jqc2pCGbaaZxFnR7wPpFdfGWtHLZ4YlNK0T6Fb6-_MBqEyzLIGlbsUFHixnW8Fw2KJRc349mGK0gCebX0kqIy3FdJ2Z-NrV_epNfcjchj7tBoVhOqP9WmdzdXcVuYOk."
      name="lia-form-context" type="hidden"><input value="BlogArticlePage:blog-id/Exchange/article-id/29561:searchformv32.form:" name="liaFormContentKey" type="hidden"><input
      value="yDZKQFNI0U/sd9X4pbUemqvQQZw=:H4sIAAAAAAAAALWSzUrDQBSFr4Wuigiib6DbiajdqAhFUISqweBaZibTNJpk4sxNEzc+ik8gvkQX7nwHH8CtKxfmzxJbwaTUVZhzw/nOmblP79COD+FAC6r40OAyQOWyCF0ZaMOkjtgrJgOp/NHONtER810sP9nfIkGtoCuVQ2hI+VAQpKHQqO67hEslPJcRRrUgPZaKlOOxKzx7wxIYhZtX487b+stnC5b60MnZ0junvkBY7d/QETU8GjiGlUYKnP0kRFguwEcFeAHBe02Dm0pyobWV+Wid0sbP9u7g4/G1BZCE8QWc1U3kpzapWoqZ+S+SvoMHgPQ+ypGVj/IoC2dlqHZ8CWZdV7xljUqszZa43voPYNHkFE7qGkdaqKrl1Pm7wEqmV59gcYjGkQOJP25h6jyJnOlzRv4DUURusIWhknbEsWo5K002vhzNufG1WHmDLwdzh8gDBQAA"
      name="t:formdata" type="hidden"></div>
  <div class="lia-inline-ajax-feedback">
    <div class="AjaxFeedback" id="feedback"></div>
  </div>
  <input value="UXvGK3whn-OGj-VaQ0_3xXyGTIQSyRxQg7jSOYMF-2Q." name="lia-action-token" type="hidden">
  <input value="form" id="form_UIDform" name="form_UID" type="hidden">
  <input value="" id="form_instance_keyform" name="form_instance_key" type="hidden">
  <span class="lia-search-input-wrapper">
    <span class="lia-search-input-field">
      <span class="lia-button-wrapper lia-button-wrapper-secondary lia-button-wrapper-searchForm-action"><input value="searchForm" name="submitContextX" type="hidden"><input class="lia-button lia-button-secondary lia-button-searchForm-action"
          value="Search" id="submitContext" name="submitContext" type="submit"></span>
      <input placeholder="Search the community" aria-label="Search" title="Search" class="lia-form-type-text lia-autocomplete-input search-input lia-search-input-message" value="" id="messageSearchField_0" name="messageSearchField" type="text"
        aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Enter a search word</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="6vri1Hj9BhwuAb3lL5_5knKtQlkDMyn6SzBA8tF-yGI." rel="nofollow" id="disableAutoComplete_40057403ee1fe9" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/29561&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div>
      <input placeholder="Search the community" aria-label="Search" title="Search" class="lia-form-type-text lia-autocomplete-input search-input lia-search-input-tkb-article lia-js-hidden" value="" id="messageSearchField_1"
        name="messageSearchField_0" type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Enter a search word</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="1FYxdnj-O-Z8AtMng_NsGPP7v9e1QTX0BX5d9OLivyg." rel="nofollow" id="disableAutoComplete_4005740410d2f4" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/29561&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div>
      <input placeholder="Search all content" ng-non-bindable="" title="Enter a user name or rank" class="lia-form-type-text UserSearchField lia-search-input-user search-input lia-js-hidden lia-autocomplete-input"
        aria-label="Enter a user name or rank" value="" id="userSearchField" name="userSearchField" type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Enter a user name or rank</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="yph9uF2OVi7OBYSjuAW1Y2F0LhD2A_baF1oicyM1Zv4." rel="nofollow" id="disableAutoComplete_40057404305d61" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/29561&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div>
      <input title="Enter a search word" class="lia-form-type-text NoteSearchField lia-search-input-note search-input lia-js-hidden lia-autocomplete-input" aria-label="Enter a search word" value="" id="noteSearchField_0" name="noteSearchField"
        type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Enter a search word</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="oeAWJnOnihCAYhaoZceDqL7HRaJOf1RnvuobXwd2D20." rel="nofollow" id="disableAutoComplete_4005740455829c" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/29561&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div>
      <input title="Enter a search word" class="lia-form-type-text ProductSearchField lia-search-input-product search-input lia-js-hidden lia-autocomplete-input" aria-label="Enter a search word" value="" id="productSearchField"
        name="productSearchField" type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Enter a search word</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="weeaKor6AMdlvi9nns9nfya3I6_FgNeC_6Wrgbp3kmo." rel="nofollow" id="disableAutoComplete_40057404794845" href="https://techcommunity.microsoft.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/Exchange/article-id/29561&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div>
      <input class="lia-as-search-action-id" name="as-search-action-id" type="hidden">
    </span>
  </span>
  <span class="lia-cancel-search">cancel</span>
</form>

Text Content

We use optional cookies to improve your experience on our websites, such as
through social media connections, and to display personalized advertising based
on your online activity. If you reject optional cookies, only cookies necessary
to provide you the services will be used. You may change your selection by
clicking “Manage Cookies” at the bottom of the page. Privacy Statement
Third-Party Cookies

Accept Reject Manage cookies


Skip to main content

Microsoft

Tech Community

Home

Community Hubs

Community Hubs
 * Community Hubs Home
 * Products
 * Special Topics
 * Video Hub

Close


PRODUCTS (68)


SPECIAL TOPICS (41)


VIDEO HUB (855)


MOST ACTIVE HUBS

Microsoft Teams
Microsoft Excel
Windows
Security, Compliance and Identity
Office 365
SharePoint
Windows Server
Azure
Exchange
Microsoft 365
Microsoft Edge Insider
.NET
Sharing best practices for building any app with .NET.
Microsoft FastTrack
Best practices and the latest news on Microsoft FastTrack
Microsoft Viva
The employee experience platform to help people thrive at work


MOST ACTIVE HUBS

ITOps Talk
Core Infrastructure and Security
Microsoft Learn
Education Sector
Microsoft 365 PnP
AI and Machine Learning
Microsoft Mechanics
Healthcare and Life Sciences
Small and Medium Business
Public Sector
Internet of Things (IoT)
Azure Partner Community
Expand your Azure partner-to-partner network
Microsoft Tech Talks
Bringing IT Pros together through In-Person & Virtual events
MVP Award Program
Find out more about the Microsoft MVP Award Program.


VIDEO HUB

Azure
Exchange
Microsoft 365
Microsoft 365 Business
Microsoft 365 Enterprise
Microsoft Edge
Microsoft Outlook
Microsoft Teams
Security
SharePoint
Windows
Browse All Community Hubs

Blogs

Blogs

Events

Events
 * Events Home
 * Microsoft Ignite
 * Microsoft Build
 * Community Events

Microsoft Learn

Microsoft Learn
 * Home
 * Community
 * Blog
 * Azure
 * Dynamics 365
 * Microsoft 365
 * Security, Compliance & Identity
 * Power Platform
 * Github
 * Teams
 * .NET


Lounge

Lounge
 * 831K Members
 * 5,138 Online
 * 2.2M Discussions

Search
Enter a search word

Turn off suggestions
Enter a search word

Turn off suggestions
Enter a user name or rank

Turn off suggestions
Enter a search word

Turn off suggestions
Enter a search word

Turn off suggestions
cancel
Turn on suggestions
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Sign In

Sign In




Enter a search word

Turn off suggestions
Enter a search word

Turn off suggestions
Enter a user name or rank

Turn off suggestions
Enter a search word

Turn off suggestions
Enter a search word

Turn off suggestions
cancel
Turn on suggestions
Showing results for 
Show  only  | Search instead for 
Did you mean: 



 * Home
 * Exchange
 * Exchange Team Blog
 * Released: March 2021 Exchange Server Security Updates

 * Back to Blog
 * Newer Article
 * Older Article





RELEASED: MARCH 2021 EXCHANGE SERVER SECURITY UPDATES

 * Subscribe to RSS Feed
 * 
 * Mark as New
 * Mark as Read
 * 
 * Bookmark
 * Subscribe
 * 
 * Email to a Friend
 * 
 * Printer Friendly Page
 * Report Inappropriate Content


By
The Exchange Team
Published Mar 02 2021 01:08 PM 843K Views
Skip to footer content
The_Exchange_Team
Microsoft
‎Mar 02 2021 01:08 PM


RELEASED: MARCH 2021 EXCHANGE SERVER SECURITY UPDATES

‎Mar 02 2021 01:08 PM

Note: this post is getting frequent updates; please keep checking back. Last
update: 3/19/2021

Microsoft has released a set of out of band security updates for vulnerabilities
for the following versions of Exchange Server:

 * Exchange Server 2013
 * Exchange Server 2016
 * Exchange Server 2019

Security updates are available for the following specific versions of Exchange:

IMPORTANT: If manually installing security updates, you must install .msp from
elevated command prompt (see Known Issues in update KB articles)

 * Exchange Server 2010 (update requires SP 3 or any SP 3 RU – this is a Defense
   in Depth update)
 * Exchange Server 2013 (update requires CU 23)
 * Exchange Server 2016 (update requires CU 19 or CU 18)
 * Exchange Server 2019 (update requires CU 8 or CU 7)
 * NEW! Security Updates for older Cumulative Updates of Exchange Server (the
   list is now finalized)

Because we are aware of active exploits of related vulnerabilities in the wild
(limited targeted attacks), our recommendation is to install these updates
immediately to protect against these attacks.

The vulnerabilities affect Microsoft Exchange Server. Exchange Online is not
affected.

For more information, please see the Microsoft Security Response Center (MSRC)
blog.

For technical details of these exploits and how to help with detection, please
see HAFNIUM Targeting Exchange Servers. There is a scripted version of this
check available on GitHub here.

 

Mitigations, investigation and remediation:


ARE THERE ANY MITIGATIONS I CAN IMPLEMENT RIGHT NOW?

MSRC team has released a One-Click Microsoft Exchange On-Premises Mitigation
Tool (EOMT). The MSTIC blog post called Microsoft Exchange Server
Vulnerabilities Mitigations – March 2021 can help understand individual
mitigation actions. A stand-alone ExchangeMitigations.ps1 script is also
available.


HOW CAN I TELL IF MY SERVERS HAVE ALREADY BEEN COMPROMISED?

Information on Indicators of Compromise (IOCs) – such as what to search for, and
how to find evidence of successful exploitation (if it happened), can be found
in HAFNIUM Targeting Exchange Servers. There is a scripted version of this
available on GitHub here.


MORE INFORMATION ABOUT INVESTIGATIONS

To aid defenders in investigating these attacks where Microsoft security
products and tooling may not be deployed, we are releasing a feed of observed
indicators of compromise (IOCs). The feed of malware hashes and known malicious
file paths observed in related attacks is available in both JSON and CSV formats
at the below GitHub links. This information is being shared as TLP:WHITE. CSV
format and JSON format are available. 


WHAT ABOUT REMEDIATION?

MSTIC team has (on March 6th) updated their blog post Microsoft Exchange Server
Vulnerabilities Mitigations – March 2021 to include information about Microsoft
Support Emergency Response Tool (MSERT) having been updated to scan Microsoft
Exchange Server. Please download a new copy of MSERT often, as updates are made
in the tool regularly! Please also see MSRC Guidance for responders:
Investigating and remediating on-premises Exchange Server vulnerabilities.

 

Installing and troubleshooting updates:


DOES INSTALLING THE MARCH SECURITY UPDATES REQUIRE MY SERVERS TO BE UP TO DATE?

Today we shipped Security Update (SU) fixes. These fixes can be installed only
on servers that are running the specific versions listed previously, which are
considered up to date. If your servers are running older Exchange Server
cumulative or rollup update, we recommend to install a currently supported RU/CU
before you install the security updates. If you are unable to get updated
quickly, please see March 2021 Exchange Server Security Updates for older
Cumulative Updates of Exchange Server.


HOW CAN I GET AN INVENTORY OF THE UPDATE-LEVEL STATUS OF MY ON-PREMISES EXCHANGE
SERVERS?

You can use the Exchange Server Health Checker script, which can be downloaded
from GitHub (use the latest release). Running this script will tell you if you
are behind on your on-premises Exchange Server updates (note that the script
does not support Exchange Server 2010).


WHICH OF MY SERVERS SHOULD I UPDATE FIRST?

Exploitation of the security vulnerabilities addressed in these fixes requires
HTTPS access over the Internet. Therefore, our recommendation is to install the
security updates first on Exchange servers exposed/published to the Internet
(e.g., servers publishing Outlook on the web/OWA and ECP) and then update the
rest of your environment.


WILL THE INSTALLATION OF THE SECURITY UPDATES TAKE AS LONG AS INSTALLING AN
RU/CU?

Installation of Security Updates does not take as long as installing a CU or RU,
but you will need to plan for some downtime.


MY ORGANIZATION NEEDS TO 'GET CURRENT' FIRST... WE NEED TO APPLY A CUMULATIVE
UPDATE. ANY TIPS FOR US?

Please see the Upgrade Exchange to the latest Cumulative Update article for best
practices when installing Exchange Cumulative Updates. To ensure the easiest
upgrade experience (and because in many organizations Exchange and Active
Directory roles are separate) you might wish to run /PrepareAD (in the Active
Directory site that Exchange is a member of) before running the actual CU Setup.
You can use this document as a guide to understand what you might have to do.


ERRORS DURING OR AFTER SECURITY UPDATE INSTALLATION! HELP!

It is extremely important to read the Known Issues section in the Security
Update KB article (here and here depending on the version). If installing the
update manually, you must run the update from the elevated command prompt. If
you are seeing unexpected behavior, check the article addressing troubleshooting
failed installations of Exchange security updates (we will keep updating this
article).

 

Additional Q&A:


ARE THERE ANY OTHER RESOURCES THAT YOU CAN RECOMMEND?

Microsoft Defender Security Research Team has published a related blog post
called Defending Exchange servers under attack which can help you understand
some general practices around detection of malicious activity on your Exchange
servers and help improve your security posture.


MY ORGANIZATION IS IN HYBRID WITH EXCHANGE ONLINE. DO I NEED TO DO ANYTHING?

While those security updates do not apply to Exchange Online / Office 365, you
need to apply those Security Updates to your on-premises Exchange Server, even
if it is used for management purposes only. You do not need to re-run HCW if you
are using it.


DO WE NEED TO INSTALL THOSE UPDATES ON MANAGEMENT TOOLS ONLY WORKSTATIONS OR
SERVERS?

Machines with Management Tools only are not impacted (there are no Exchange
services installed) and do not require installation of March SUs. Please note
that a 'management server' which many of our Hybrid customers have (which is an
Exchange server kept on premises to be able to run Exchange management tasks) is
different. For Hybrid, please see the Hybrid question above.


THE LAST EXCHANGE 2016 AND EXCHANGE 2019 CU’S WERE RELEASED IN DECEMBER OF 2020.
ARE NEW CU’S RELEASING IN MARCH 2021?

EDIT: Exchange Server 2016 CU 20 and Exchange Server 2019 CU 9 are now released
and those CUs contain the Security Updates mentioned here (along with other
fixes). Customers who have installed SUs for older E2016/2019 CUs can simply
update to new CUs and will stay protected.


ARE EXCHANGE SERVER 2003 AND EXCHANGE SERVER 2007 VULNERABLE TO MARCH 2021
EXCHANGE SERVER SECURITY VULNERABILITIES?

No. After performing code reviews, we can state that the code involved in the
attack chain to begin (CVE-2021-26855) was not in the product before Exchange
Server 2013. Exchange 2007 includes the UM service, but it doesn’t include the
code that made Exchange Server 2010 vulnerable. Exchange 2003 does not include
the UM service.

 

Major updates to this post:

 * 3/19/2021: Added a link to Guidance for responders: Investigating and
   remediating on-premises Exchange Server vulnerabilities
 * 3/17/2021: Removed the mention of CompareExchangeHashes.ps1 script
   (deprecated). Added a Q&A pair for Management Tools only machines.
 * 3/16/2021: Added a note about Exchange 2016 CU 20 and Exchange 2019 CU 9
 * 3/15/2021: Added a link to One-Click Microsoft Exchange On-Premises
   Mitigation Tool (EOMT)
 * 3/12/2021: Added a Q&A pair for Exchange 2003/2007
 * 3/11/2021: Added a note about final list of SU releases for out of support
   CUs
 * 3/10/2021: Added a note that the MSERT tool should be downloaded often as it
   gets updated regularly
 * 3/9/2021: Added a link to ExchangeMitigations.ps1 mitigation script
   and CompareExchangeHashes.ps1 file hashes check script.
 * 3/8/2021: Added a link about Updates for older Cumulative Updates of Exchange
   Server and information about a feed of observed indicators of compromise
   (IOCs).
 * 3/8/2021: Added a link to the guide that can help with steps that need to be
   taken to get current and update
 * 3/8/2021: Added a note about elevated CMD prompt installation of .msp files
 * 3/7/2021: Reorganized information to make it easier to navigate
 * 3/6/2021: Added information about MSERT tool to help with remediation
 * 3/6/2021: linked to an article about troubleshooting failed installations of
   Exchange security updates
 * 3/5/2021: linked to the new MSTIC blog post on Vulnerability Mitigations

The Exchange Team

 * Tags:
 * Announcements
   
 * Exchange 2010
   
 * Exchange 2013
   
 * Exchange 2016
   
 * Exchange 2019
   
 * On premises
   
 * Security
   


14 Likes
Like




293 Comments
ajc196
Contributor
‎Mar 02 2021 01:44 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 01:44 PM

Where are the updates...? I don't see any download links here or in any related
articles, there's nothing available with an update check on servers, and nothing
new in the Update Catalog for Exchange since February.

1 Like
Like




ajc196
Contributor
‎Mar 02 2021 01:50 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 01:50 PM

https://support.microsoft.com/en-us/topic/description-of-the-security-update-for-microsoft-exchange-...

 

(Sorry for double post since we can't edit/delete here, but wanted this out
there for others)

3 Likes
Like




Scott Schnoll
Microsoft
‎Mar 02 2021 01:58 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 01:58 PM

Thanks, @ajc196.  All download links are in the MSRC blog post
at https://msrc-blog.microsoft.com/2021/03/02/multiple-security-updates-released-for-exchange-server. 

2 Likes
Like




The_Exchange_Team
Microsoft
‎Mar 02 2021 01:59 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 01:59 PM

@ajc196 - downloads will be on the Microsoft Update soon. You can get them right
away if you go to individual CVEs mentioned in the MSRC blog
post: https://msrc-blog.microsoft.com/2021/03/02/multiple-security-updates-released-for-exchange-server/ 

0 Likes
Like




ajc196
Contributor
‎Mar 02 2021 02:00 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 02:00 PM

@Scott Schnoll Thanks! Those links were non-functioning a short while ago but
now work. Seems to have been the shuffle of taking things live ASAP.

1 Like
Like




mattmn160
Senior Member
‎Mar 02 2021 02:55 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 02:55 PM

Direct
link https://support.microsoft.com/en-us/topic/description-of-the-security-update-for-microsoft-exchange-...

1 Like
Like




Elvecio_M
Established Member
‎Mar 02 2021 03:40 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 03:40 PM

Hi All

 

Questions:

1- Does anybody installed this patch?

2- Is it necessary to put the Exchange in Maintenance mode and  restart the
server after apply the patch?

 

Thanks.

2 Likes
Like




ajc196
Contributor
‎Mar 02 2021 03:50 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 03:50 PM

@Elvecio_M I've halfway through my servers, no issues thus far. Exchange
security updates temporarily stop and disable all Exchange services, so
definitely maintenance beforehand. All but one server I've updated wanted a
reboot, and I rebooted that one anyway.

0 Likes
Like




Nino Bilic
Microsoft
‎Mar 02 2021 03:51 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 03:51 PM

Thanks @ajc196 great to hear! That's how it should be. And yes, security updates
should prompt for reboot.

0 Likes
Like




Elvecio_M
Established Member
‎Mar 02 2021 04:04 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 04:04 PM

Hi @ajc196 

Thanks for the information. If you have any new updates about your installation
process, please share with us.

 

Thanks again.

0 Likes
Like




Tim_Aylett
Occasional Visitor
‎Mar 02 2021 04:12 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 04:12 PM

The Article mentions updates are available for "Exchange Server 2010 (RU 31 for
Service Pack 3 – this is a Defense in Depth update)" but I don't see a link to
this update in the other attached
articles https://msrc-blog.microsoft.com/2021/03/02/multiple-security-updates-released-for-exchange-server/%C... 

0 Likes
Like




EddieRowe
Occasional Contributor
‎Mar 02 2021 04:31 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 04:31 PM

What is meant by "defense in depth" for the 2010 patch since it is clear the
issues have not been fully patched since there are other patches for 2013, 2016
and 2019?  Am I save to assume only one part of the attack chain has been
mitigated?  We have been struggling to get hybrid mode working to move off 2010
to Exchange Online since last year.

0 Likes
Like




Nino Bilic
Microsoft
‎Mar 02 2021 04:31 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 04:31 PM

@Tim_Aylett The KB article for Exchange 2010 is here:

Description of the security update for Microsoft Exchange Server 2010 Service
Pack 3: March 2, 2021 ...

2 Likes
Like




Nino Bilic
Microsoft
‎Mar 02 2021 04:35 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 04:35 PM

@EddieRowe Exchange 2010 is not vulnerable to the same attack chain as Exchange
2013/2016/2019, but there is a vulnerability that we have addressed for Exchange
2010 and our recommendation is to install the update.

1 Like
Like




Jeff Guillet
MVP
‎Mar 02 2021 05:13 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 05:13 PM

I’m applying the updates to all my servers (2010/2013/2016/2019). The updates
install OK, but it doesn’t ask for a restart. Is one required?

0 Likes
Like




pquan
Visitor
‎Mar 02 2021 05:15 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 05:15 PM

Are these security updates available for Exchange 2016 CU 16?  Or are these
security updates to address vulnerabilities only in Exchange 2016 CU 18, 19;
respectively. 

2 Likes
Like




Jeff Guillet
MVP
‎Mar 02 2021 05:17 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 05:17 PM

Microsoft only supports the current and last CU. You will need to install one of
these CUs before you can install the update.

1 Like
Like




Michael Hincapie
Occasional Contributor
‎Mar 02 2021 05:17 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 05:17 PM

we are currently applying it and also no issues so far. 

1 Like
Like




Nino Bilic
Microsoft
‎Mar 02 2021 05:20 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 05:20 PM

@Jeff Guillet Our suggestion is to restart the server, yes. I have seen the
update tell to reboot but I guess depending on the scenario...

1 Like
Like




pquan
Visitor
‎Mar 02 2021 05:21 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 05:21 PM

Do these vulnerabilities exists in Exchange 2016 CU 16?

0 Likes
Like




Nino Bilic
Microsoft
‎Mar 02 2021 05:25 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 05:25 PM

@pquan Yes, but you need to roll forward to apply the updates.

2 Likes
Like




pquan
Visitor
‎Mar 02 2021 05:26 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 05:26 PM

Thank you, @Nino Bilic 

0 Likes
Like




EddieRowe
Occasional Contributor
‎Mar 02 2021 05:37 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 05:37 PM

We have some typos.  Description of the security update for Microsoft Exchange
Server 2010 Service Pack 3: March 2, 2021 ... has a link to download Update
Rollup 32 for Exchange Server 2010 SP3, but when you click on that link Download
Update Rollup 3 For Exchange 2010 SP3 (KB5000978) from Official Microsoft
Download Center says it is Rollup 3 instead of 32.

0 Likes
Like




Nino Bilic
Microsoft
‎Mar 02 2021 05:48 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 05:48 PM

@EddieRowe Yeah that should be fixed now. I just had to reload the page and it
says 32 now.

0 Likes
Like




Keith-Work-711
Senior Member
‎Mar 02 2021 06:41 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 06:41 PM

Installing on our first server to gauge the impact. Getting lots of "Files in
use" errors. We're killing processes and retrying multiple times now.

0 Likes
Like




LeeMEI
Occasional Visitor
‎Mar 02 2021 07:16 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 07:16 PM

So the Known Issue of applying it by double click breaking ECP/OWA... It's great
the article warns you of that... would be better if it told you HOW TO FIX IT
too!  Or where to find how to fix it.  So... anyone know how to fix it?!  

 

(Cancelled mid-way.  Rolled back.  Re-installed correctly, ECP is broken; OWA
works).

0 Likes
Like




Nino Bilic
Microsoft
‎Mar 02 2021 07:33 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 07:33 PM

@Keith-Work-711 and @LeeMEI - please make sure to check "KNOWN ISSUES" in the KB
article talking about updates. This is not an issue with this particular update,
rather - all security updates need to be run elevated if installed manually.

0 Likes
Like




LeeMEI
Occasional Visitor
‎Mar 02 2021 07:44 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 07:44 PM

@Nino Bilic Thanks, but that's not really helpful.  As I said, it's great that
it's a known issue.  That it's known that the update doesn't properly prompt for
elevation and that it must be run from an elevated command prompt.  

 

What's done is done.  ECP is broken.  HOW DO WE FIX IT?  There's no mention of
restoring ECP / OWA if you failed to run it initially from an elevated command
prompt.  Why not? It would be helpful to folks who may not have read the blog
but were, instead, told to install this update and ASSUMED it would properly
elevate itself.

 

If we wait for the next CU and install that, will that fix it?  I'd rather not
wait, but I assume the next CU is due soon...

0 Likes
Like




Jeff Guillet
MVP
‎Mar 02 2021 07:49 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 07:49 PM

@LeeMEI If ECP is broken, you might try resetting the ECP virtual directory. 

0 Likes
Like




Keith-Work-711
Senior Member
‎Mar 02 2021 07:51 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 07:51 PM

FYI we are running them from an elevated command prompt. Other servers have not
had this issue of the "Files in use" and seem to have installed clean. Hopefully
just a single server issue.

0 Likes
Like




Susan Bradley
MVP
‎Mar 02 2021 07:51 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 07:51 PM

With my deepest respects, but Exchange has always needed patching like this,
this isn't new.  I've always had to apply Exchange updates like this.  This
isn't the first security update for Exchange, just the first zero day in the
news in a long time.

0 Likes
Like




Nino Bilic
Microsoft
‎Mar 02 2021 07:54 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 07:54 PM

@LeeMEI - Well, the article does give you some guidance around what to do if
services are not starting (I might be assuming that ECP is not running because
of this but I did not ask this before):

To fix this issue, use Services Manager to restore the startup type to
Automatic, and then start the affected Exchange services manually.

Or are you saying that all services are running and still ECP does not work? Did
the update actually successfully install (after elevated installation)?

1 Like
Like




Jeff Guillet
MVP
‎Mar 02 2021 07:55 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 07:55 PM

@Keith-Work-711 My best practice is to always restart the server before I apply
updates. That way all file locks are removed and you know the server is coming
up healthy (or not) before the updates are applied.

2 Likes
Like




LeeMEI
Occasional Visitor
‎Mar 02 2021 08:01 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 08:01 PM

@Susan Bradley while it's disappointing that updates for Exchange and
potentially other products have this quirk, that's not what I'm really bothered
by.  It's a known issue, so why isn't there a reference to how to resolve it if
the problem is experienced?  I'm not trying to suggest the post should include
in-depth resolutions to the potential issue(s), but rather, a brief note such
as @Jeff Guillet suggests, resetting the virtual directory (assuming that works)
or a link to another post concerning recovering from that issue should it have
occurred.

 

I'm not looking to troubleshoot this here, so if Jeff's solution doesn't work,
I'll be posting to other forums tomorrow.  Just frustrated that a known issue
exists and Microsoft, while acknowledging it's a known issue, posts absolutely
no information about recovering from it if it occurs.

0 Likes
Like




LeeMEI
Occasional Visitor
‎Mar 02 2021 08:16 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 08:16 PM

@Nino Bilic Sorry if I'm coming across a little harsh.  As I read the post, it
was not clear to me that the cause of the ECP or OWA not working would be
stopped services.  I took the note below the install workaround instructions to
be a possible side effect as I've seen that in the past, regardless of how the
update was applied.  As the post says the issue occurs because some services
aren't properly stopped, I thought that would likely mean some files wouldn't be
appropriately updated/settings applied and, as such, the services break.  I
would THINK a re-install of the patch (the second successful install I did of
it) would resolve the issues.  Unfortunately, that has not been the case.

 

Yes, OWA works, but ECP is broken.  All services appeared to start properly
(except POP/IMAP but we don't use them anyway).  Attempting to access ECP
provides login, then redirects to a bad URL (http://localhost/owa/ecp) which
returns an unhelpful error, Bad Request.  I expect it to redirect to

https://localhost/ecp/?ExchClientVer=15

 

I've since found it I go to https://localhost/ecp/?ExchClientVer=15 directly,
everything works.  Seems it's just the handoff from the login to the admin
center

 

Perhaps it's just bad timing and something else is wrong not related to the
patch.

1 Like
Like




Nino Bilic
Microsoft
‎Mar 02 2021 08:39 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 08:39 PM

@LeeMEI Not a problem whatsoever; it sucks when things go wrong. It's great that
you were able to figure that out! I have to admit that I do not know for sure
what is up with this but at least it is not a real fire for you right now.

0 Likes
Like




julian_hsu
Occasional Visitor
‎Mar 02 2021 09:23 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 09:23 PM

Hi all

 

for OWA

Please execute UpdateCas.ps1 in Exchange Install Patch

\Exchange Server\V15\Bin\UpdateCas.ps1

 

For ECP

the below link solve my problem

https://social.technet.microsoft.com/Forums/ie/en-US/44289975-878d-4f51-a73d-f38176ec714d/owa-sudden...

 

 

 

1 Like
Like




Imrul Emon
Senior Member
‎Mar 02 2021 09:34 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 09:34 PM

Patched our test Exchange 2013 CU 23 servers, no issues identified.

1 Like
Like




SRaines
Occasional Visitor
‎Mar 02 2021 10:32 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 10:32 PM

Windows 2016 DC, Exchange Svr 2016 CU17  and both servers are failing to install
the KB5000871 with "The upgrade patch cannot be installed by the Windows
Installer service because the program to be upgraded may be missing, or the
upgrade patch may update a different version of the program.  Verify that the
program to be upgraded exists on you computer and that you have the correct
upgrade patch.   I have done both.  I have downloaded it from the Catalog and
the Download Center and no difference.   Any ideas?

1 Like
Like




Imrul Emon
Senior Member
‎Mar 02 2021 10:39 PM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 02 2021 10:39 PM

Hi Sraine, 

You will need Exchange Server 2016 (CU 19, CU 18). It  looks you have Exchange
2016 CU17.

2 Likes
Like




ChrisAtMaf
Occasional Contributor
‎Mar 03 2021 01:59 AM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 03 2021 01:59 AM

The following article contains instructions for detecting whether CVE-2021-26855
exploitation has taken place

 

Import-Csv -Path (Get-ChildItem -Recurse -Path "$env:PROGRAMFILES\Microsoft\Exchange Server\V15\Logging\HttpProxy" -Filter '*.log').FullName | Where-Object {  $_.AuthenticatedUser -eq " -and $_.AnchorMailbox -like 'ServerInfo~*/*' } | select DateTime, AnchorMailbox

https://www.microsoft.com/security/blog/2021/03/02/hafnium-targeting-exchange-servers/

The command is broken (it will never execute and generates a PowerShell
continuation prompt (>>). This can be fixed by changing the double quote after
$_.AuthenticatedUser -eq " to two single quotes '' - please update the article
ASAP!

Import-Csv -Path (Get-ChildItem -Recurse -Path "$env:PROGRAMFILES\Microsoft\Exchange Server\V15\Logging\HttpProxy" -Filter '*.log').FullName | Where-Object {  $_.AuthenticatedUser -eq '' -and $_.AnchorMailbox -like 'ServerInfo~*/*' } | select DateTime, AnchorMailbox

 

1 Like
Like




Nino Bilic
Microsoft
‎Mar 03 2021 02:06 AM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 03 2021 02:06 AM

@ChrisAtMaf Thank you - reported to that blog team...

1 Like
Like




Nando90
Occasional Visitor
‎Mar 03 2021 02:46 AM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 03 2021 02:46 AM

Hi community,

 

A quick question: Is the Exchange 2016 CU17 affected by the release ?

0 Likes
Like




ChrisAtMaf
Occasional Contributor
‎Mar 03 2021 03:10 AM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 03 2021 03:10 AM

@Nino Bilic No worries. The command picked up what looked like two attempts to
exploit our server this morning, so it's important people run it!

0 Likes
Like




StuartH .
Occasional Contributor
‎Mar 03 2021 03:11 AM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 03 2021 03:11 AM

Exchange 2016, and was on CU17....I tried to install straight to CU19, and get
"The upgrade patch cannot be installed by the Windows Installer service because
the program to be upgraded may be missing, or the upgrade patch may update a
different version of the program.  Verify that the program to be upgraded exists
on you computer and that you have the correct upgrade patch"

Installed CU18 just fine...and I thought the rollups were cumulative anyhow,
hence why I tried to go straight the CU19.  So, I am not on CU18, and cannot get
to CU19....what is "missing" ?

0 Likes
Like




Mike Janeiro
Regular Visitor
‎Mar 03 2021 03:46 AM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 03 2021 03:46 AM

We have Exchange redirecting to ADFS for user authentication. Can this
vulnerability still be exploited in this configuration?

 

1 Like
Like




brett77
Occasional Visitor
‎Mar 03 2021 04:01 AM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 03 2021 04:01 AM

Has anyone had issue where autodiscover ews are throwing 500 errors? 

 

I fixed the ECP issue now I'm just struggling to get fat clients connected.

 

 

Thanks. 

0 Likes
Like




floWinkel
Senior Member
‎Mar 03 2021 04:02 AM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 03 2021 04:02 AM

If the Exchange environment and all https Services like OWA,ECP etc. behind a
Web-Application Module like Big-IP from F5. Is there the same risiko for
this vulnerabilities ?

1 Like
Like




KDCAP
Occasional Visitor
‎Mar 03 2021 04:49 AM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 03 2021 04:49 AM

Trying to update our Exch 2013 CU23 server, and am getting this error.:

 

> This upgrade patch cannot be installed by the Windows Installer service
> because the program to be upgrade may be missing, or the upgrade patch may
> update a different version of the program. Verify that the program to be
> upgraded eists on your computer and that your have the correct upgrade path.

I tried running the install troubleshooter, and FixMissingMSI app to see if
there were fixes or corrupt registry entries, no dice. Any ideas?

0 Likes
Like




Nino Bilic
Microsoft
‎Mar 03 2021 05:07 AM
 * Mark as Read
 * Mark as New
 * 
 * Bookmark
 * 
 * Permalink
 * Print
 * Email to a Friend
 * 
 * Report Inappropriate Content

‎Mar 03 2021 05:07 AM

@Nando90 Yes it is impacted, but you need to go to a later CU to be able to
install the update

0 Likes
Like




 * « Previous
 * * 1
   * 2
   * 3
   * …
   * 6
 * Next »

You must be a registered user to add a comment. If you've already registered,
sign in. Otherwise, register and sign in.

 * Comment

Co-Authors
The_Exchange_Team

Version history
Last update:
‎Mar 19 2021 01:44 PM
Updated by:
The_Exchange_Team


Labels
 * Announcements 374
 * Exchange 2010 305
 * Exchange 2013 199
 * Exchange 2016 111
 * Exchange 2019 42

 * « Previous « Previous
 * Next » Next »




SHARE

 * Share to LinkedIn
 * Share to Facebook
 * Share to Twitter
 * Share to Email




Browse

Skip to primary navigation

WHAT'S NEW

 * Surface Pro X
 * Surface Laptop 3
 * Surface Pro 7
 * Windows 10 Apps
 * Office apps

MICROSOFT STORE

 * Account profile
 * Download Center
 * Microsoft Store support
 * Returns
 * Order tracking
 * Store locations
 * Buy online, pick up in store
 * In-store events

EDUCATION

 * Microsoft in education
 * Office for students
 * Office for schools
 * Deals for students and parents
 * Microsoft Azure in education

ENTERPRISE

 * Azure
 * AppSource
 * Automotive
 * Government
 * Healthcare
 * Manufacturing
 * Financial Services
 * Retail

DEVELOPER

 * Microsoft Visual Studio
 * Window Dev Center
 * Developer Network
 * TechNet
 * Microsoft developer program
 * Channel 9
 * Office Dev Center
 * Microsoft Garage

COMPANY

 * Careers
 * About Microsoft
 * Company News
 * Privacy at Microsoft
 * Investors
 * Diversity and inclusion
 * Accessibility
 * Security

 * Sitemap
 * Contact Microsoft
 * Privacy
 * Manage cookies
 * Terms of use
 * Trademarks
 * Safety and eco
 * About our ads
 * © 2022 Microsoft

Auto-suggest helps you quickly narrow down your search results by suggesting
possible matches as you type.

Auto-suggest helps you quickly narrow down your search results by suggesting
possible matches as you type.