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

List:       patchmanagement
Subject:    RE: [External] RE: [patchmanagement] .NET Framework July 30 2018 Update
From:       "Cain, Steven" <scain () severnbank ! com>
Date:       2018-07-31 15:20:31
Message-ID: 71FE9156D09A0F47B71ACA3B1AA68B21ADC474 () Argus-10 ! hpwsb ! local
[Download RAW message or body]

Looks that way. And if you have multiple versions on the same machine yo=
u have to deploy multiple patches, .NET 2.0, .NET 3.5, .NET 3.5.1, .NET 4.5=
.2, etc.

From: Rick McClure [mailto:rmcclure@rmc-enterprises.com]
Sent: Tuesday, July 31, 2018 9:36 AM
To: Patch Management Mailing List
Subject: [External] RE: [patchmanagement] .NET Framework July 30 2018 Updat=
e

So the way I read this is you have to apply the update that breaks things, =
THEN apply this update and hopefully it will fix things.....?  Right?

From: Cain, Steven [mailto:scain@severnbank.com]
Sent: Monday, July 30, 2018 11:21 PM
To: Patch Management Mailing List
Subject: [patchmanagement] .NET Framework July 30 2018 Update

https://blogs.msdn.microsoft.com/dotnet/2018/07/30/net-framework-july-2018-=
update/


---
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)]

<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:x="urn:schemas-microsoft-com:office:excel" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"> <head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">&nbsp;&nbsp; Looks that way. And if \
you have multiple versions on the same machine you have to deploy multiple patches, \
.NET 2.0, .NET 3.5, .NET 3.5.1, .NET 4.5.2, etc. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span \
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Rick \
McClure [mailto:rmcclure@rmc-enterprises.com] <br>
<b>Sent:</b> Tuesday, July 31, 2018 9:36 AM<br>
<b>To:</b> Patch Management Mailing List<br>
<b>Subject:</b> [External] RE: [patchmanagement] .NET Framework July 30 2018 \
Update<o:p></o:p></span></p> </div>
</div>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">So the way I read this is you have \
to apply the update that breaks things, THEN apply this update and hopefully it will \
fix things&#8230;..?&nbsp; Right? <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span \
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span \
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Cain, \
Steven [mailto:scain@severnbank.com] <br>
<b>Sent:</b> Monday, July 30, 2018 11:21 PM<br>
<b>To:</b> Patch Management Mailing List<br>
<b>Subject:</b> [patchmanagement] .NET Framework July 30 2018 \
Update<o:p></o:p></span></p> </div>
</div>
<p class="MsoNormal"><o:p>&nbsp;</o:p></p>
<p class="MsoNormal"><a \
href="https://blogs.msdn.microsoft.com/dotnet/2018/07/30/net-framework-july-2018-updat \
e/">https://blogs.msdn.microsoft.com/dotnet/2018/07/30/net-framework-july-2018-update/</a><o:p></o:p></p>
 <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>



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

Configure | About | News | Add a list | Sponsored by KoreLogic