From what I can tell so far yep. From: [email protected] [mailto:[email protected]] On Behalf Of Raymond, Dan J (N-CSC) Sent: Thursday, July 18, 2013 8:50 AM To: [email protected] Subject: RE: [mssms] RE: MS13-052 (KB2840628)
Is it just the KB2840628 version of MS13-052 causing the issues? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Linkey, Mike Sent: Thursday, July 18, 2013 5:20 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: MS13-052 (KB2840628) This also hosed up a bunch of our in house developed apps. Took us 3 days to figure out what. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected]<mailto:[email protected]> Sent: Wednesday, July 17, 2013 8:50 PM To: SMS Subject: Re: [mssms] RE: MS13-052 (KB2840628) Looks very similar to what Brian posted a couple days ago http://myitforum.com/myitforumwp/2013/07/15/configmgr-issues-with-ms13-052-kb2840628/ Sent from Microsoft Surface Pro From: Jason Sandys Sent: Wednesday, July 17, 2013 9:08 PM To: [email protected]<mailto:[email protected]> CSS put up a blog earlier today discussing what they’ve seen: http://blogs.technet.com/b/configmgrteam/archive/2013/07/17/issues-reported-with-ms13-052-kb2840628-and-configmgr.aspx J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Dzikowski, Michael Sent: Monday, July 15, 2013 9:15 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: MS13-052 (KB2840628) What are the reported issues? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Saturday, July 13, 2013 3:42 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] MS13-052 (KB2840628) Received official confirmation that MS13-052 (KB2840628) causes issues with ConfigMgr 2012 (and maybe 2007). It is being actively investigated so you may want to hold off on installing it on your servers (workstations should be fine). There are known work-arounds for two of the issues caused (I think Marcum was/is going to blog with more details). J ________________________________ This message is intended only for the use of the intended recipient. If you are not an intended recipient, you are hereby notified that any use, dissemination, disclosure or copying of this communication is strictly prohibited. If you have received this communication in error please destroy all copies of this message and its attachments and notify the sender immediately.
