eightwone.com
Open in
urlscan Pro
192.0.78.25
Public Scan
URL:
https://eightwone.com/2019/02/12/exchange-updates-february-2019/
Submission: On August 19 via manual from JP
Submission: On August 19 via manual from JP
Form analysis 4 forms found in the DOM
GET https://eightwone.com/
<form method="get" id="searchform" action="https://eightwone.com/">
<label for="s" class="assistive-text">Search</label>
<input type="text" class="field" name="s" id="s" placeholder="Search">
<input type="submit" class="submit" name="submit" id="searchsubmit" value="Search">
</form>POST https://eightwone.com/wp-comments-post.php
<form action="https://eightwone.com/wp-comments-post.php" method="post" id="commentform" class="comment-form"><input type="hidden" id="highlander_comment_nonce" name="highlander_comment_nonce" value="e89d8c8267"><input type="hidden"
name="_wp_http_referer" value="/2019/02/12/exchange-updates-february-2019/">
<input type="hidden" name="hc_post_as" id="hc_post_as" value="guest">
<div class="comment-form-field comment-textarea">
<div id="comment-form-comment"><textarea aria-hidden="true" tabindex="-1"
style="position: absolute; inset: -999px auto auto 0px; border: 0px; padding: 0px; box-sizing: content-box; overflow-wrap: break-word; overflow: hidden; transition: none 0s ease 0s; height: 0px !important; min-height: 0px !important; font-family: Arial, Helvetica, Tahoma, Verdana, sans-serif; font-size: 14px; font-weight: 300; font-style: normal; letter-spacing: 0px; text-transform: none; text-decoration: none solid rgba(0, 0, 0, 0.7); word-spacing: 0px; text-indent: 0px; line-height: 22.75px; width: 614px;"
class="autosizejs "></textarea><textarea id="comment" name="comment" title="Enter your comment here..." placeholder="Enter your comment here..." style="height: 42px; overflow: hidden; overflow-wrap: break-word; resize: none;"></textarea>
</div>
</div>
<div id="comment-form-identity" style="display: none;">
<div id="comment-form-nascar">
<p>Fill in your details below or click an icon to log in:</p>
<ul>
<li class="selected" style="display:none;">
<a href="#comment-form-guest" id="postas-guest" class="nascar-signin-link" title="Login via Guest">
</a>
</li>
<li>
<a href="#comment-form-load-service:WordPress.com" id="postas-wordpress" class="nascar-signin-link" title="Login via WordPress.com">
<svg xmlns="http://www.w3.org/2000/svg" role="presentation" viewBox="0 0 24 24"><rect x="0" fill="none" width="24" height="24"></rect><g><path fill="#0087be" d="M12.158 12.786l-2.698 7.84c.806.236 1.657.365 2.54.365 1.047 0 2.05-.18 2.986-.51-.024-.037-.046-.078-.065-.123l-2.762-7.57zM3.008 12c0 3.56 2.07 6.634 5.068 8.092L3.788 8.342c-.5 1.117-.78 2.354-.78 3.658zm15.06-.454c0-1.112-.398-1.88-.74-2.48-.456-.74-.883-1.368-.883-2.11 0-.825.627-1.595 1.51-1.595.04 0 .078.006.116.008-1.598-1.464-3.73-2.36-6.07-2.36-3.14 0-5.904 1.613-7.512 4.053.21.008.41.012.58.012.94 0 2.395-.114 2.395-.114.484-.028.54.684.057.74 0 0-.487.058-1.03.086l3.275 9.74 1.968-5.902-1.4-3.838c-.485-.028-.944-.085-.944-.085-.486-.03-.43-.77.056-.742 0 0 1.484.114 2.368.114.94 0 2.397-.114 2.397-.114.486-.028.543.684.058.74 0 0-.488.058-1.03.086l3.25 9.665.897-2.997c.456-1.17.684-2.137.684-2.907zm1.82-3.86c.04.286.06.593.06.924 0 .912-.17 1.938-.683 3.22l-2.746 7.94c2.672-1.558 4.47-4.454 4.47-7.77 0-1.564-.4-3.033-1.1-4.314zM12 22C6.486 22 2 17.514 2 12S6.486 2 12 2s10 4.486 10 10-4.486 10-10 10z"></path></g></svg> </a>
</li>
<li>
<a href="#comment-form-load-service:Twitter" id="postas-twitter" class="nascar-signin-link" title="Login via Twitter">
<svg xmlns="http://www.w3.org/2000/svg" role="presentation" viewBox="0 0 24 24"><rect x="0" fill="none" width="24" height="24"></rect><g><path fill="#1DA1F2" d="M22.23 5.924c-.736.326-1.527.547-2.357.646.847-.508 1.498-1.312 1.804-2.27-.793.47-1.67.812-2.606.996C18.325 4.498 17.258 4 16.078 4c-2.266 0-4.103 1.837-4.103 4.103 0 .322.036.635.106.935-3.41-.17-6.433-1.804-8.457-4.287-.353.607-.556 1.312-.556 2.064 0 1.424.724 2.68 1.825 3.415-.673-.022-1.305-.207-1.86-.514v.052c0 1.988 1.415 3.647 3.293 4.023-.344.095-.707.145-1.08.145-.265 0-.522-.026-.773-.074.522 1.63 2.038 2.817 3.833 2.85-1.404 1.1-3.174 1.757-5.096 1.757-.332 0-.66-.02-.98-.057 1.816 1.164 3.973 1.843 6.29 1.843 7.547 0 11.675-6.252 11.675-11.675 0-.178-.004-.355-.012-.53.802-.578 1.497-1.3 2.047-2.124z"></path></g></svg> </a>
</li>
<li>
<a href="#comment-form-load-service:Facebook" id="postas-facebook" class="nascar-signin-link" title="Login via Facebook">
<svg xmlns="http://www.w3.org/2000/svg" role="presentation" viewBox="0 0 24 24"><rect x="0" fill="none" width="24" height="24"></rect><g><path fill="#3B5998" d="M20.007 3H3.993C3.445 3 3 3.445 3 3.993v16.013c0 .55.445.994.993.994h8.62v-6.97H10.27V11.31h2.346V9.31c0-2.325 1.42-3.59 3.494-3.59.993 0 1.847.073 2.096.106v2.43h-1.438c-1.128 0-1.346.537-1.346 1.324v1.734h2.69l-.35 2.717h-2.34V21h4.587c.548 0 .993-.445.993-.993V3.993c0-.548-.445-.993-.993-.993z"></path></g></svg> </a>
</li>
</ul>
</div>
<div id="comment-form-guest" class="comment-form-service selected">
<div class="comment-form-padder">
<div class="comment-form-avatar">
<a href="https://gravatar.com/site/signup/" target="_blank"> <img src="https://1.gravatar.com/avatar/ad516503a11cd5ca435acc9bb6523536?s=25" alt="Gravatar" width="25" class="no-grav grav-hashed grav-hijack" id="grav-ad516503a11cd5ca435acc9bb6523536-0">
</a>
</div>
<div class="comment-form-fields">
<div class="comment-form-field comment-form-email">
<label for="email">Email <span class="required">(required)</span> <span class="nopublish">(Address never made public)</span></label>
<div class="comment-form-input"><input id="email" name="email" type="email" value=""></div>
</div>
<div class="comment-form-field comment-form-author">
<label for="author">Name <span class="required">(required)</span></label>
<div class="comment-form-input"><input id="author" name="author" type="text" value=""></div>
</div>
<div class="comment-form-field comment-form-url">
<label for="url">Website</label>
<div class="comment-form-input"><input id="url" name="url" type="url" value=""></div>
</div>
</div>
</div>
</div>
<div id="comment-form-wordpress" class="comment-form-service">
<div class="comment-form-padder">
<div class="comment-form-avatar">
<img src="https://1.gravatar.com/avatar/ad516503a11cd5ca435acc9bb6523536?s=25" alt="WordPress.com Logo" width="25" class="no-grav grav-hashed grav-hijack" id="grav-ad516503a11cd5ca435acc9bb6523536-1">
</div>
<div class="comment-form-fields">
<input type="hidden" name="wp_avatar" id="wordpress-avatar" class="comment-meta-wordpress" value="">
<input type="hidden" name="wp_user_id" id="wordpress-user_id" class="comment-meta-wordpress" value="">
<input type="hidden" name="wp_access_token" id="wordpress-access_token" class="comment-meta-wordpress" value="">
<p class="comment-form-posting-as pa-wordpress">
<strong></strong> You are commenting using your WordPress.com account. <span class="comment-form-log-out"> ( <a href="javascript:HighlanderComments.doExternalLogout( 'wordpress' );">Log Out</a> /
<a href="#" onclick="javascript:HighlanderComments.switchAccount();return false;">Change</a> ) </span>
<span class="pa-icon"><svg xmlns="http://www.w3.org/2000/svg" role="presentation" viewBox="0 0 24 24">
<rect x="0" fill="none" width="24" height="24"></rect>
<g>
<path fill="#0087be"
d="M12.158 12.786l-2.698 7.84c.806.236 1.657.365 2.54.365 1.047 0 2.05-.18 2.986-.51-.024-.037-.046-.078-.065-.123l-2.762-7.57zM3.008 12c0 3.56 2.07 6.634 5.068 8.092L3.788 8.342c-.5 1.117-.78 2.354-.78 3.658zm15.06-.454c0-1.112-.398-1.88-.74-2.48-.456-.74-.883-1.368-.883-2.11 0-.825.627-1.595 1.51-1.595.04 0 .078.006.116.008-1.598-1.464-3.73-2.36-6.07-2.36-3.14 0-5.904 1.613-7.512 4.053.21.008.41.012.58.012.94 0 2.395-.114 2.395-.114.484-.028.54.684.057.74 0 0-.487.058-1.03.086l3.275 9.74 1.968-5.902-1.4-3.838c-.485-.028-.944-.085-.944-.085-.486-.03-.43-.77.056-.742 0 0 1.484.114 2.368.114.94 0 2.397-.114 2.397-.114.486-.028.543.684.058.74 0 0-.488.058-1.03.086l3.25 9.665.897-2.997c.456-1.17.684-2.137.684-2.907zm1.82-3.86c.04.286.06.593.06.924 0 .912-.17 1.938-.683 3.22l-2.746 7.94c2.672-1.558 4.47-4.454 4.47-7.77 0-1.564-.4-3.033-1.1-4.314zM12 22C6.486 22 2 17.514 2 12S6.486 2 12 2s10 4.486 10 10-4.486 10-10 10z">
</path>
</g>
</svg></span>
</p>
</div>
</div>
</div>
<div id="comment-form-googleplus" class="comment-form-service">
<div class="comment-form-padder">
<div class="comment-form-avatar">
<img src="https://1.gravatar.com/avatar/ad516503a11cd5ca435acc9bb6523536?s=25" alt="Google photo" width="25" class="no-grav grav-hashed grav-hijack" id="grav-ad516503a11cd5ca435acc9bb6523536-2">
</div>
<div class="comment-form-fields">
<input type="hidden" name="googleplus_avatar" id="googleplus-avatar" class="comment-meta-googleplus" value="">
<input type="hidden" name="googleplus_user_id" id="googleplus-user_id" class="comment-meta-googleplus" value="">
<input type="hidden" name="googleplus_access_token" id="googleplus-access_token" class="comment-meta-googleplus" value="">
<p class="comment-form-posting-as pa-googleplus">
<strong></strong> You are commenting using your Google account. <span class="comment-form-log-out"> ( <a href="javascript:HighlanderComments.doExternalLogout( 'googleplus' );">Log Out</a> /
<a href="#" onclick="javascript:HighlanderComments.switchAccount();return false;">Change</a> ) </span>
<span class="pa-icon"><svg xmlns="http://www.w3.org/2000/svg" role="presentation" x="0px" y="0px" viewBox="0 0 60 60">
<path fill="#519bf7" d="M56.3,30c0,-1.6 -0.2,-3.4 -0.6,-5h-3.1H42.2H30v10.6h14.8C44,39.3 42,42 39.1,43.9l8.8,6.8C53,46 56.3,39 56.3,30z"></path>
<path fill="#3db366" d="M30,57.5c6.7,0 13.1,-2.4 17.9,-6.8l-8.8,-6.8c-2.5,1.6 -5.6,2.4 -9.1,2.4c-7.2,0 -13.3,-4.7 -15.4,-11.2l-9.3,7.1C9.8,51.3 19.1,57.5 30,57.5z"></path>
<path fill="#fdc600" d="M5.3,42.2l9.3,-7.1c-0.5,-1.6 -0.8,-3.3 -0.8,-5.1s0.3,-3.5 0.8,-5.1l-9.3,-7.1C3.5,21.5 2.5,25.6 2.5,30S3.5,38.5 5.3,42.2z"></path>
<path fill="#f15b44" d="M40.1,17.4l8,-8C43.3,5.1 37,2.5 30,2.5C19.1,2.5 9.8,8.7 5.3,17.8l9.3,7.1c2.1,-6.5 8.2,-11.1 15.4,-11.1C33.9,13.7 37.4,15.1 40.1,17.4z"></path>
</svg></span>
</p>
</div>
</div>
</div>
<div id="comment-form-twitter" class="comment-form-service">
<div class="comment-form-padder">
<div class="comment-form-avatar">
<img src="https://1.gravatar.com/avatar/ad516503a11cd5ca435acc9bb6523536?s=25" alt="Twitter picture" width="25" class="no-grav grav-hashed grav-hijack" id="grav-ad516503a11cd5ca435acc9bb6523536-3">
</div>
<div class="comment-form-fields">
<input type="hidden" name="twitter_avatar" id="twitter-avatar" class="comment-meta-twitter" value="">
<input type="hidden" name="twitter_user_id" id="twitter-user_id" class="comment-meta-twitter" value="">
<input type="hidden" name="twitter_access_token" id="twitter-access_token" class="comment-meta-twitter" value="">
<p class="comment-form-posting-as pa-twitter">
<strong></strong> You are commenting using your Twitter account. <span class="comment-form-log-out"> ( <a href="javascript:HighlanderComments.doExternalLogout( 'twitter' );">Log Out</a> /
<a href="#" onclick="javascript:HighlanderComments.switchAccount();return false;">Change</a> ) </span>
<span class="pa-icon"><svg xmlns="http://www.w3.org/2000/svg" role="presentation" viewBox="0 0 24 24">
<rect x="0" fill="none" width="24" height="24"></rect>
<g>
<path fill="#1DA1F2"
d="M22.23 5.924c-.736.326-1.527.547-2.357.646.847-.508 1.498-1.312 1.804-2.27-.793.47-1.67.812-2.606.996C18.325 4.498 17.258 4 16.078 4c-2.266 0-4.103 1.837-4.103 4.103 0 .322.036.635.106.935-3.41-.17-6.433-1.804-8.457-4.287-.353.607-.556 1.312-.556 2.064 0 1.424.724 2.68 1.825 3.415-.673-.022-1.305-.207-1.86-.514v.052c0 1.988 1.415 3.647 3.293 4.023-.344.095-.707.145-1.08.145-.265 0-.522-.026-.773-.074.522 1.63 2.038 2.817 3.833 2.85-1.404 1.1-3.174 1.757-5.096 1.757-.332 0-.66-.02-.98-.057 1.816 1.164 3.973 1.843 6.29 1.843 7.547 0 11.675-6.252 11.675-11.675 0-.178-.004-.355-.012-.53.802-.578 1.497-1.3 2.047-2.124z">
</path>
</g>
</svg></span>
</p>
</div>
</div>
</div>
<div id="comment-form-facebook" class="comment-form-service">
<div class="comment-form-padder">
<div class="comment-form-avatar">
<img src="" alt="Facebook photo" width="25" class="no-grav">
</div>
<div class="comment-form-fields">
<input type="hidden" name="fb_avatar" id="facebook-avatar" class="comment-meta-facebook" value="">
<input type="hidden" name="fb_user_id" id="facebook-user_id" class="comment-meta-facebook" value="">
<input type="hidden" name="fb_access_token" id="facebook-access_token" class="comment-meta-facebook" value="">
<p class="comment-form-posting-as pa-facebook">
<strong></strong> You are commenting using your Facebook account. <span class="comment-form-log-out"> ( <a href="javascript:HighlanderComments.doExternalLogout( 'facebook' );">Log Out</a> /
<a href="#" onclick="javascript:HighlanderComments.switchAccount();return false;">Change</a> ) </span>
<span class="pa-icon"><svg xmlns="http://www.w3.org/2000/svg" role="presentation" viewBox="0 0 24 24">
<rect x="0" fill="none" width="24" height="24"></rect>
<g>
<path fill="#3B5998"
d="M20.007 3H3.993C3.445 3 3 3.445 3 3.993v16.013c0 .55.445.994.993.994h8.62v-6.97H10.27V11.31h2.346V9.31c0-2.325 1.42-3.59 3.494-3.59.993 0 1.847.073 2.096.106v2.43h-1.438c-1.128 0-1.346.537-1.346 1.324v1.734h2.69l-.35 2.717h-2.34V21h4.587c.548 0 .993-.445.993-.993V3.993c0-.548-.445-.993-.993-.993z">
</path>
</g>
</svg></span>
</p>
</div>
</div>
</div>
<div id="comment-form-load-service" class="comment-form-service">
<div class="comment-form-posting-as-cancel"><a href="javascript:HighlanderComments.cancelExternalWindow();">Cancel</a></div>
<p>Connecting to %s</p>
</div>
</div>
<script type="text/javascript">
var highlander_expando_javascript = function() {
function hide(sel) {
var el = document.querySelector(sel);
if (el) {
el.style.setProperty('display', 'none');
}
}
function show(sel) {
var el = document.querySelector(sel);
if (el) {
el.style.removeProperty('display');
}
}
var input = document.createElement('input');
var comment = document.querySelector('#comment');
if (input && comment && 'placeholder' in input) {
var label = document.querySelector('.comment-textarea label');
if (label) {
var text = label.textContent;
label.parentNode.removeChild(label);
comment.setAttribute('placeholder', text);
}
}
// Expando Mode: start small, then auto-resize on first click + text length
hide('#comment-form-identity');
hide('#comment-form-subscribe');
hide('#commentform .form-submit');
if (comment) {
comment.style.height = '10px';
var handler = function() {
comment.style.height = HighlanderComments.initialHeight + 'px';
show('#comment-form-identity');
show('#comment-form-subscribe');
show('#commentform .form-submit');
HighlanderComments.resizeCallback();
comment.removeEventListener('focus', handler);
};
comment.addEventListener('focus', handler);
}
}
if (document.readyState !== 'loading') {
highlander_expando_javascript();
} else {
if (typeof window.jQuery === 'function') {
// Use jQuery's `ready` if available.
// This solves some scheduling issues between this script and the main highlander script.
jQuery(document).ready(highlander_expando_javascript);
} else {
// If not available, add a vanilla event listener.
document.addEventListener('DOMContentLoaded', highlander_expando_javascript);
}
}
</script>
<div id="comment-form-subscribe" style="display: none;">
<p class="comment-subscription-form"><input type="checkbox" name="subscribe" id="subscribe" value="subscribe" style="width: auto;"> <label class="subscribe-label" id="subscribe-label" for="subscribe" style="display: inline;">Notify me of new
comments via email.</label></p>
<p class="post-subscription-form"><input type="checkbox" name="subscribe_blog" id="subscribe_blog" value="subscribe" style="width: auto;"> <label class="subscribe-label" id="subscribe-blog-label" for="subscribe_blog"
style="display: inline;">Notify me of new posts via email.</label></p>
</div>
<p class="form-submit wp-block-button" style="display: none;"><input name="submit" type="submit" id="comment-submit" class="submit wp-block-button__link" value="Post Comment"> <input type="hidden" name="comment_post_ID" value="11115"
id="comment_post_ID">
<input type="hidden" name="comment_parent" id="comment_parent" value="0">
</p>
<p style="display: none;"><input type="hidden" id="akismet_comment_nonce" name="akismet_comment_nonce" value="997d45f1b8"></p>
<input type="hidden" name="genseq" value="1629383680">
<textarea name="ak_hp_textarea" cols="45" rows="8" maxlength="100" style="display: none !important;"></textarea><input type="hidden" id="ak_js" name="ak_js" value="1629383681347">
</form>POST /2019/02/12/exchange-updates-february-2019/
<form action="/2019/02/12/exchange-updates-february-2019/" method="post">
<label for="target_email">Send to Email Address</label>
<input type="email" name="target_email" id="target_email" value="">
<label for="source_name">Your Name</label>
<input type="text" name="source_name" id="source_name" value="">
<label for="source_email">Your Email Address</label>
<input type="email" name="source_email" id="source_email" value="">
<input type="text" id="jetpack-source_f_name" name="source_f_name" class="input" value="" size="25" autocomplete="off" title="This field is for validation and should not be changed">
<div class="g-recaptcha" data-sitekey="6LcmyE0UAAAAALID28yVNg7pFCodGaArJzHitez_" data-theme="light" data-type="image" data-tabindex="0" data-lazy="true" data-url="https://www.google.com/recaptcha/api.js?hl=en"></div>
<img style="float: right; display: none" class="loading" src="https://s0.wp.com/wp-content/mu-plugins/post-flair/sharing/images/loading.gif" alt="loading" width="16" height="16">
<input type="submit" value="Send Email" class="sharing_send">
<a rel="nofollow" href="#cancel" class="sharing_cancel" role="button">Cancel</a>
<div class="errors errors-1" style="display: none;"> Post was not sent - check your email addresses! </div>
<div class="errors errors-2" style="display: none;"> Email check failed, please try again </div>
<div class="errors errors-3" style="display: none;"> Sorry, your blog cannot share posts by email. </div>
</form><form>
<li class="actnbr-login-nudge">
<div>Already have a WordPress.com account?
<a href="https://wordpress.com/log-in?redirect_to=https%3A%2F%2Fr-login.wordpress.com%2Fremote-login.php%3Faction%3Dlink%26back%3Dhttps%253A%252F%252Feightwone.com%252F2019%252F02%252F12%252Fexchange-updates-february-2019%252F">Log in now.</a>
</div>
</li>
</form>Text Content
Skip to primary content
EIGHTWONE (821)
NEWS, TIPS AND INFO ON EXCHANGE, TEAMS, AZURE AD, MICROSOFT 365 AND POWERSHELL
Search
MAIN MENU
*
* Tools
* Toolkit
* My Scripts
* Other Scripts
* Online Tools
* References
* Exchange Builds
* Exchange Schema Versions
* AD Schema Versions
* AD Functional Levels
* Exchange Solution Reviewed Program
* Learning
* Books
* Courses
* Public
* About
* Fun
* Custom Backgrounds
* Contact
POST NAVIGATION
← Previous Next →
EXCHANGE UPDATES – FEBRUARY 2019
Posted on February 12, 2019 by Michel de Rooij
Update: Added note that Exchange 2010 SP3 RU26 adds support for Windows Server
2012 R2.
Today, the Exchange Team released the overdue quarterly Cumulative Updates for
Exchange Server 2013, Exchange 2016 and Exchange 2019, as well as a Rollup for
Exchange Server 2010.
The KB articles that describe the fixes in each release and product downloads
are available as follows:
Version Build KB Download UMLP Schema Exchange 2019 CU1 15.2.330.5 KB4471391
VLSC N Exchange 2016 CU12 15.1.1713.5 KB4471392 Download UMLP N Exchange 2013
CU22 15.0.1473.3 KB4345836 Download UMLP N Exchange 2010 SP3 RU26 14.3.442.0
KB4487052 Download N
This update contain the following important changes and notes:
* Due to issue CVE-2018-8581, the EWS architecture was changed, in particular
push notifications. Details on the change are described in KB4490060; while
the change has been tested against EWS clients such as Outlook for Mac and
Skype for Business, organizations may need to test any applications
leveraging EWS to estimate potential impact of installing these Cumulative
Updates or Rollup. In addition, organizations are advised to password reset
Exchange computer accounts.
* These Exchange builds introduces a change in the shared permissions model
(this does not apply to Split Permissions Model). Result is that Exchange no
longer requires fargoing permissions in Active Directory (e.g. WriteDACL on
root of domain). To makes these changes become effective:
* For Exchange 2013-2019 Cumulative Updates, run setup using /PrepareAD. In
multi-forest environments, this needs to be done in every domain of the
forest.
* For Exchange 2010, go through the instructions mentioned in KB4490059.
* Organizations considering moving to the Split Permissions because of
CVE-2018-8581 should know Microsoft fully supports both models. Switching can
have serious consequences and therefor should be fully evaluated.
* This build of Exchange 2019 introduces cmdlets to block usage of legacy
authentication protocols for users through policies, e.g. Basic
Authentication.
* Prior to deploying Exchange 2016 CU12 or Exchange 2013 CU22 on Edge Transport
servers, install Visual C++ 2012 Runtime.
* These Cumulative Updates will remove the DisableLoopbackCheck key when
present; removing this key was a mitigation for CVE-2018-8581.
* Exchange 2010 SP3 RU26 adds support for Windows Server 2012 R2, to
accommodate for the Hybrid Agent.
Exchange 2019 CU1 fixes:
* 4487596 Emails are blocked in moderator mailbox Outbox folder when you send
large volumes of emails in Exchange Server 2019
* 4487591 The recipient scope setting doesn’t work for sibling domains when
including OUs in the scope in Exchange Server 2019
* 4487602 Outlook for Mac users can still expand a distribution group when
hideDLMembership is set to true in Exchange Server 2019
* 4488076 Outlook on the Web can’t be loaded when users use an invalid Windows
language in operating system in Exchange Server 2019
* 4488079 Exchange Server 2016 allows adding Exchange Server 2019 mailbox
server into a same DAG and vice versa
* 4488263 X-MS-Exchange-Organization-BCC header isn’t encoded correctly in
Exchange Server 2019
* 4488080 New-MigrationBatch doesn’t honor RBAC management scope in Exchange
Server 2019
* 4488262 Delivery Reports exception when tracking a meeting request that’s
sent with a room resource in Exchange Server 2019
* 4488268 Disable the irrelevant Query logs that’re created in Exchange Server
2019
* 4488267 Test-OAuthConnectivity always fails when Exchange Server uses proxy
to connect to Internet in Exchange Server 2019
* 4488266 Client application doesn’t honor EwsAllowList in Exchange Server 2019
* 4488265 “There are problems with the signature” error occurs for digital
signature message if attachment filtering is enabled in Exchange Server 2019
* 4488398 “The Microsoft Exchange Replication service may not be running on
server” error when you add a mailbox database copy in Exchange Server 2019
* 4488264 Mailbox that has a bad move request can’t be cleaned up from
destination mailbox database in Exchange Server 2019
* 4488261 Event ID 1002 when the store worker process crashes in Exchange
Server 2019
* 4488260 New-MailboxExportRequest and New-MailboxImportRequest don’t honor
RBAC management scope in Exchange Server 2019
* 4488259 MailTip shows wrong number of users for a distribution group if the
users are in different domains in Exchange Server 2019
* 4488258 OAuth authentication is removed when saving MAPI virtual directory
settings in EAC in Exchange Server 2019
* 4490060 Exchange Web Services Push Notifications can be used to gain
unauthorized access
* 4490059 Reducing permissions required to run Exchange Server using Shared
Permissions Model
Exchange 2016 CU12 fixes:
* 4487596 Emails are blocked in moderator mailbox Outbox folder when you send
large volumes of emails in Exchange Server 2016
* 4456241 You receive a meeting request that has a “not supported calendar
message.ics” attachment in Exchange Server 2016
* 4456239 New-MailboxRepairRequest doesn’t honor RBAC RecipientWriteScope
restrictions in Exchange Server 2016
* 4487591 The recipient scope setting doesn’t work for sibling domains when
including OUs in the scope in Exchange Server 2016
* 4468363 MRM does not work for mailboxes that have an online archive mailbox
in Exchange Server
* 4487603 “The action cannot be completed” error when you select many
recipients in the Address Book of Outlook in Exchange Server 2016
* 4487602 Outlook for Mac users can still expand a distribution group when
hideDLMembership is set to true in Exchange Server 2016
* 4488076 Outlook on the Web can’t be loaded when users use an invalid Windows
language in operating system in Exchange Server 2016
* 4488079 Exchange Server 2016 allows adding Exchange Server 2019 mailbox
server into a same DAG and vice versa
* 4488077 Can’t configure voice mail options when user is in different domain
in Exchange Server 2016
* 4488263 X-MS-Exchange-Organization-BCC header isn’t encoded correctly in
Exchange Server 2016
* 4488080 New-MigrationBatch doesn’t honor RBAC management scope in Exchange
Server 2016
* 4488262 Delivery Reports exception when tracking a meeting request that’s
sent with a room resource in Exchange Server 2016
* 4488268 Disable the irrelevant Query logs that’re created in Exchange Server
2016
* 4488267 Test-OAuthConnectivity always fails when Exchange Server uses proxy
to connect to Internet in Exchange Server 2016
* 4488266 Client application doesn’t honor EwsAllowList in Exchange Server 2016
* 4488265 “There are problems with the signature” error occurs for digital
signature message if attachment filtering is enabled in Exchange Server 2016
* 4488264 Mailbox that has a bad move request can’t be cleaned up from
destination mailbox database in Exchange Server 2016
* 4488261 Event ID 1002 when the store worker process crashes in Exchange
Server 2016
* 4488260 New-MailboxExportRequest and New-MailboxImportRequest don’t honor
RBAC management scope in Exchange Server 2016
* 4488259 MailTip shows wrong number of users for a distribution group if the
users are in different domains in Exchange Server 2016
* 4488258 OAuth authentication is removed when saving MAPI virtual directory
settings in EAC in Exchange Server 2016
* 4490060 Exchange Web Services Push Notifications can be used to gain
unauthorized access
* 4490059 Reducing permissions required to run Exchange Server using Shared
Permissions Model
Exchange 2013 CU22 fixes:
* 4487603 “The action cannot be completed” error when you select many
recipients in the Address Book of Outlook in Exchange Server 2013
* 4490060 Exchange Web Services Push Notifications can be used to gain
unauthorized access
* 4490059 Reducing permissions required to run Exchange Server using Shared
Permissions Model
Exchange 2010 SP3 RU26 fixes:
* 4490060 Exchange Web Services Push Notifications can be used to gain
unauthorized access
Notes:
* These Cumulative Updates do not contain schema changes compared to their
previous Cumulative Update. However, due to changes in the permissions
architecture, you need to run setup /PrepareAD to implement these changes as
well as apply any RBAC changes, before deploying or updating Exchange
servers.
* When upgrading from an n-2 or earlier version of Exchange, or an early
version of the .NET Framework, consult Upgrade Paths for CU’s & .NET.
* Don’t forget to put the Exchange server in maintenance mode prior to
updating. Regardless, setup will put the server in server-wide offline mode
post-analysis, before making actual changes.
* When using Exchange hybrid deployments or Exchange Online Archiving (EOA),
you are required to delay installing at most one version (n-1).
* If you want to speed up the update process for systems without internet
access, you can follow the procedure described here to disable publisher’s
certificate revocation checking.
* Cumulative Updates can be installed directly; no need to install RTM prior to
installing Cumulative Updates.
* Once installed, you can’t uninstall a Cumulative Update nor any of the
installed Exchange server roles.
* The order of installation shouldn’t matter with the “every server is an
island” concept, yet recommended is to upgrade internet-facing,
non-internet-facing servers first, followed by Edge Transports.
Caution:
As for any update, I recommend to thoroughly test updates in a test environment
prior to implementing them in production. When you lack such facilities, hold
out a few days and monitor the comments on the original publication or forums
for any issues.
RATE THIS:
i
2 Votes
SHARE THIS:
* Click to share on Twitter (Opens in new window)
* Click to share on Facebook (Opens in new window)
* Click to share on Reddit (Opens in new window)
* Click to email this to a friend (Opens in new window)
* Click to print (Opens in new window)
*
LIKE THIS:
Like Loading...
This entry was posted in Exchange 2010, Exchange 2013, Exchange 2016, Exchange
2019, Misc and tagged CU1, CU12, CU22, Hotfix, Rollup by Michel de Rooij.
Bookmark the permalink.
ABOUT MICHEL DE ROOIJ
I'm a Microsoft Office Apps and Services MVP, with focus on Exchange Server,
Office 365 and with a PowerShell affection. I'm is a consultant, publisher of
EighTwOne, published author, and speaker. You can find me on Twitter, LinkedIn,
Facebook.
View all posts by Michel de Rooij →
10 THOUGHTS ON “EXCHANGE UPDATES – FEBRUARY 2019”
1. blaketex on February 12, 2019 at 10:36 PM said:
Michel-
What happened to Microsoft’s plan not to release CUs for Exchange 2013 after
CU 21?
Blake Woodard
LikeLike
Reply ↓
2. Keith on February 12, 2019 at 10:48 PM said:
The order in which you upgrade servers with Cumulative Updates is
irrelevant? So you can update non-internet-facing servers first and not
experience any down-proxy request issues? I have always updated
internet-facing servers first as there have always been issues in the past
with OWA access, Etc. when upgrading non-internet-facing servers first.
LikeLike
Reply ↓
* Michel de Rooij on February 13, 2019 at 10:20 AM said:
I still would recommend the practice to upgrade internet-facing,
non-internet-facing then Edge Transports.
LikeLike
Reply ↓
* Yuriy Samorodov on February 19, 2019 at 11:40 PM said:
This is a general recommendation to start with Hub and Mailbox servers and
proceed with CAS and Edge afterwards.
LikeLike
Reply ↓
3. Pingback: CVE-2018-8581: Exchange Vulnerability | EighTwOne (821)
4. Yuriy Samorodov on February 19, 2019 at 11:38 PM said:
It looks like there is a typo.
Exchange 2013 CU22 requires Visual C++ 2013 Redistributable, not VC++ 2012
LikeLike
Reply ↓
* Michel de Rooij on February 20, 2019 at 9:57 AM said:
MB servers require VC+2013, ET servers VC++2012
LikeLike
Reply ↓
5. Yuriy Samorodov on February 19, 2019 at 11:49 PM said:
Just tested CVE-2019-0686 against Exchange 2013 CU22 using method discussed
below and was able to escalate regular user mailbox permissions up to Domain
Admin level, dumped AD and made that user member of Domain Admin group
within that user context
Reference:
https://dirkjanm.io/abusing-exchange-one-api-call-away-from-domain-admin/
LikeLike
Reply ↓
6. Bob on June 14, 2019 at 8:22 AM said:
Where is CU2 for Exchange 2019?
LikeLike
Reply ↓
7. Pingback: Exchange-Mail – JD's Notepad
LEAVE A REPLY CANCEL REPLY
Fill in your details below or click an icon to log in:
*
*
*
*
Email (required) (Address never made public)
Name (required)
Website
You are commenting using your WordPress.com account. ( Log Out / Change )
You are commenting using your Google account. ( Log Out / Change )
You are commenting using your Twitter account. ( Log Out / Change )
You are commenting using your Facebook account. ( Log Out / Change )
Cancel
Connecting to %s
Notify me of new comments via email.
Notify me of new posts via email.
This site uses Akismet to reduce spam. Learn how your comment data is processed.
COPYRIGHT
Unauthorized use or duplication of this material without permission from
EighTwOne is strictly prohibited. Excerpts and links may be used, provided full
and clear credit is given to EighTwOne with appropriate direction to original
content.
DISCLAIMER
EighTwOne takes steps to make sure content of this site is correct. However,
usage is at your own risk. EighTwOne does not accept responsibility or liability
for errors or omissions in the content. Content is “as is”, without guarantees
on completeness or accuracy of results obtained from using this information.
Opinions expressed are my own.
ABOUT MICHEL DE ROOIJ
Michel is an Office Apps & Services MVP with a PowerShell affection, and
publisher of EighTwOne. You can find him on Twitter, LinkedIn, Facebook. Please
use the Contact form for questions, or inquiries on consulting, support or other
engagements.
Blog at WordPress.com.
%d bloggers like this:
Send to Email Address Your Name Your Email Address
Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.
* FollowFollowing
* EighTwOne (821)
Already have a WordPress.com account? Log in now.
* * EighTwOne (821)
* Customize
* FollowFollowing
* Sign up
* Log in
* Copy shortlink
* Report this content
* Manage subscriptions
* Collapse this bar