[prev in list] [next in list] [prev in thread] [next in thread] 

List:       patchmanagement
Subject:    [patchmanagement] =?UTF-8?Q?Coming_next_week=3A_=E2=80=9CDemystifying_Dual_Scan=E2=80=9D?=
From:       Emin <emin.atac () gmail ! com>
Date:       2017-04-27 8:04:05
Message-ID: CAGN5iahYM_KAAPK+pQyN9tZLJDTykR38-6xx+oSemEVdFmGeBg () mail ! gmail ! com
[Download RAW message or body]

hi, fyi,

Source:
https://blogs.technet.microsoft.com/wsus/2017/04/26/coming-next-week-demystifying-dual-scan/


Steve Henry [MSFT]April 26, 2017
------------------------------

Hello everyone: it's been a while since our last broadcast. We're nearly
finished compiling all the details needed to publish a post that ideally
clears up the confusion around Dual Scan, offers hope for the future, and
gives you a workaround that you can use in the meantime. This is a
complicated issue with several corner cases to address, and we're striving
to cover all the bases in the first attempt. If you're managing clients
currently running 1607 (which came with the Anniversary Update), or you
plan to migrate soon, then you will want to know this information.

Please stay tuned for a post to this [and the Configuration Manager] blog
next week for the details on how to best understand and work with Dual Scan.

---
PatchManagement.org is hosted by Shavlik

The content on the email list is intended for assisting administrators.  If you would \
like to use any of this content in a blog or media publication, please contact the \
owners of the list for approval.

To unsubscribe send a blank email to leave-patchmanagement@patchmanagement.org
If you are unable to unsubscribe via this email address, please email
owner-patchmanagement@patchmanagement.org


[Attachment #3 (text/html)]

<div dir="ltr">hi, fyi,<br><br>Source: <a \
href="https://blogs.technet.microsoft.com/wsus/2017/04/26/coming-next-week-demystifyin \
g-dual-scan/">https://blogs.technet.microsoft.com/wsus/2017/04/26/coming-next-week-demystifying-dual-scan/</a><br><br><span \
class="gmail-byline"><span class="gmail-author gmail-vcard"><a class="gmail-url \
gmail-fn gmail-n gmail-profile-usercard-hover">Steve Henry \
[MSFT]</a></span></span><span class="gmail-posted-on gmail-posted-on-margin"><span \
class="gmail-screen-reader-text"></span><time class="entry-date gmail-published \
gmail-updated" datetime="2017-04-26T18:16:54+00:00">April 26, 2017</time></span><span \
class="gmail-comments-link"><span class="gmail-glyphicon \
gmail-glyphicon-comment"></span></span>				<span class="gmail-social-icons-wrap">  
	</span>
	
		
		<hr>
	

	<div class="entry-content gmail-single">
		<p>Hello everyone: it's been a while since our last broadcast.  We're 
nearly finished compiling all the details needed to publish a post that 
ideally clears up the confusion around Dual Scan, offers hope for the 
future, and gives you a workaround that you can use in the meantime.  
This is a complicated issue with several corner cases to address, and 
we're striving to cover all the bases in the first attempt.  If you're 
managing clients currently running 1607 (which came with the Anniversary
 Update), or you plan to migrate soon, then you will want to know this 
information.</p>
<p>Please stay tuned for a post to this [and the Configuration Manager] 
blog next week for the details on how to best understand and work with 
Dual Scan.</p>
	</div></div>



[prev in list] [next in list] [prev in thread] [next in thread]