Re: [mssms] SCCM current branch and AMT

Nash, Thank you. I have been using the unprovision tool with burp suite and it works well. Jessie On Wed, May 10, 2017 at 3:35 PM, Nash Pherson wrote: > Hi Jessie, > > > > You can try the Intel AMT Unprovision Utility: > > https://downloadcenter.intel.com/download/21018 >

RE: [mssms] SCCM Current Branch

sad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] Im Auftrag von Miller, Todd Gesendet: Samstag, 9. Juli 2016 07:17 An: <mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>> <mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>> Betreff: Re:

Re: [mssms] SCCM Current Branch

16 17:14 To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: Re: [mssms] SCCM Current Branch The version numbers are based on dates, so you can quickly see what order they are in. 1602 = February 2016 1511 = November 2015 If the version comes with "TP" that means it is

RE: [mssms] SCCM Current Branch

myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] On Behalf Of Hun boy Sent: Friday, 8 July, 2016 06:52 To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: Re: [mssms] SCCM Current Branch So

Re: [mssms] SCCM Current Branch

No > > 1602 > > 5.00.8355.1000 > > 3/11/2016 > > No > > Yes > > > > > > *From:* listsad...@lists.myitforum.com [mailto: > listsad...@lists.myitforum.com] *On Behalf Of *Hun boy > *Sent:* Friday, 8 July, 2016 06:52 > > > *To:* mssms@lists.myitforum.c

RE: [mssms] SCCM Current Branch

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Hun boy Sent: Friday, 8 July, 2016 06:52 To: mssms@lists.myitforum.com Subject: Re: [mssms] SCCM Current Branch Sorry, if i hijack this thread. If MS keep changing the numbers like 1606, 1511

Re: [mssms] SCCM Current Branch

listsad...@lists.myitforum.com> on behalf of Lindenfeld, Ivan <ivan.lindenf...@fnf.com> Sent: Thursday, July 7, 2016 7:53 PM To: mssms@lists.myitforum.com Subject: RE: [mssms] SCCM Current Branch I interpret the public data as: CM 1606 = Windows 10 Anniversary Edition release CM later this ye

RE: [mssms] SCCM Current Branch

lways in lock-step. My 2.1 cents :-) Shane From: ja...@sandys.us<mailto:ja...@sandys.us> To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] SCCM Current Branch Date: Tue, 5 Jul 2016 13:11:06 + Adam is correct.

RE: [mssms] SCCM Current Branch

My 2.1 cents :-) Shane From: ja...@sandys.us To: mssms@lists.myitforum.com Subject: RE: [mssms] SCCM Current Branch Date: Tue, 5 Jul 2016 13:11:06 + Adam is correct. It’s important to denote the TP releases as such because there will also be a full production 1606 rele

RE: [mssms] SCCM Current Branch

.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Brian Illner Sent: Wednesday, 6 July, 2016 09:07 To: mssms@lists.myitforum.com Subject: RE: [mssms] SCCM Current Branch The MS recommendation was within the Config Mgr program in Microsoft Connect. I cannot find the specific feedback/bug

RE: [mssms] SCCM Current Branch

or any loss or damage arising therefrom. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike Sent: Tuesday, July 5, 2016 11:30 AM To: mssms@lists.myitforum.com Subject: RE: [mssms] SCCM Current Branch +1 From: listsad...@lists.myitforum.com<

RE: [mssms] SCCM Current Branch

Sent: Tuesday, July 5, 2016 11:30 AM To: mssms@lists.myitforum.com Subject: RE: [mssms] SCCM Current Branch +1 From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Tuesday, July 5, 2016 9

RE: [mssms] SCCM Current Branch

+1 From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Tuesday, July 5, 2016 9:39 AM To: mssms@lists.myitforum.com Subject: RE: [mssms] SCCM Current Branch It’s never truly been broken. There are just a lot of caveats due to how

RE: [mssms] SCCM Current Branch

viable paths and it’s up to you to choose which is best for your organization. J From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Brian Illner Sent: Tuesday, July 5, 2016 8:26 AM To: mssms@lists.myitforum.com Subject: RE: [mssms] SCCM Current Branch

RE: [mssms] SCCM Current Branch

. J From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Juelich, Adam Sent: Tuesday, July 5, 2016 7:54 AM To: mssms@lists.myitforum.com Subject: Re: [mssms] SCCM Current Branch CB is 1602, and the TP release is 1606 I believe

RE: [mssms] SCCM Current Branch

sponsibility is accepted by Canal (or its subsidiaries and affiliates) for any loss or damage arising therefrom. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Juelich, Adam Sent: Tuesday, July 5, 2016 8:54 AM To: mssms@lists.myitforum.com Subject: Re: [mssms]

Re: [mssms] SCCM Current Branch

CB is 1602, and the TP release is 1606 I believe. *---* *Adam Juelich* Pulaski Community School District Client Management Specialist 920-822-6075 On Tue, Jul 5, 2016 at 7:12 AM, David Jones