That’s correct. I expect, but don’t know for sure, that 1610 (1610 because the 
math 1606 – 1602 = 4, 1606 + 4 = 1610) will be a baseline build. Baseline 
builds are those released on media and intended for direct new site 
installation. This makes sense also because its release should thus coincide 
with the release of System Center 2016 (which I expect 1610 will be part of in 
some form or fashion at least in name, marketing terms, and/or licensing) at 
Ignite.

J

From: [email protected] [mailto:[email protected]] On 
Behalf Of Adam Juelich
Sent: Tuesday, July 26, 2016 10:56 AM
To: [email protected]
Subject: Re: [External] [mssms] ConfigMgr 1606 current branch available now

My understanding is that they will only provide an updated ISO once a year.  
Currently you have to move to 1511 and then upgrade.

On Tue, Jul 26, 2016 at 10:08 AM, Brian Illner 
<[email protected]<mailto:[email protected]>> wrote:
We’re going to be upgrading our SCCM environment before too long.

Does anyone know if MS plans to make a new downloadable ISO for this build?

Or will we still have to upgrade to 1511 and then apply the updated builds?

BRIAN ILLNER | Canal Insurance Company
864.250.9227<tel:864.250.9227>
864.679.2537<tel:864.679.2537> Fax
Visit canalinsurance.com<http://canalinsurance.com> for news and information.
WARNING:  As the information in this transmittal (including attachments, if 
any) may contain confidential, proprietary, or business trade secret 
information, it should only be reviewed by those who are the intended 
recipients.  Unless you are an intended recipient, any review, use, disclosure, 
distribution or copying of this transmittal (or any attachments) is strictly 
prohibited.   If you have received this transmittal in error, please notify me 
immediately by reply email and destroy all copies of the transmittal.  While 
Canal believes this transmittal to be free of virus or other defect, it is the 
responsibility of the recipient to ensure that it is virus free and no 
responsibility is accepted by Canal (or its subsidiaries and affiliates) for 
any loss or damage arising therefrom.
From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] 
On Behalf Of Linkey, Mike
Sent: Tuesday, July 26, 2016 8:18 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [External] [mssms] ConfigMgr 1606 current branch available now

I let it sit for a few hours then tried it all again and then it worked.  Must 
have been having a moment…Thanks for the input.

Mike L.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Jason Sandys
Sent: Monday, July 25, 2016 1:52 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [External] [mssms] ConfigMgr 1606 current branch available now

Are you sure it’s not installed already?

Re-running the script btw won’t change anything – all that the script does is 
flip a value in the site control file.

J

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Linkey, Mike
Sent: Monday, July 25, 2016 11:31 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [External] [mssms] ConfigMgr 1606 current branch available now

Yep several times in fact.  It was there Friday, but gone today.  I see this in 
the hman.log file

Configuration Manager Update (PackageGuid=705820EF-6982-4417-8E54-307454C9A17A) 
is not applicable and should be filtered.

Don’t get why it says it is not applicable especially since I have ran that 
script at least 6 times again today.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Jason Sandys
Sent: Monday, July 25, 2016 9:48 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [External] [mssms] ConfigMgr 1606 current branch available now

No. Did you run the PowerShell script to opt in to the fast ring?

J

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Linkey, Mike
Sent: Monday, July 25, 2016 8:04 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [External] [mssms] ConfigMgr 1606 current branch available now

I saw this was available on Friday before I left.  Today, it is no longer an 
option for Updating.  Did it get pulled?

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Brian Illner
Sent: Friday, July 22, 2016 11:40 AM
To: [email protected]<mailto:[email protected]>
Subject: [External] [mssms] ConfigMgr 1606 current branch available now


[https://abs.twimg.com/sticky/default_profile_images/default_profile_6_normal.png]

david james (@djammmer<https://twitter.com/djammmer?refsrc=email&s=11>)

7/22/16, 12:01 
PM<https://twitter.com/djammmer/status/756519487457734656?refsrc=email&s=11>
#ConfigMgr<https://twitter.com/search?q=%23ConfigMgr&src=hash> 1606 current 
branch available now, for everyone. Opt into fast ring to get it immediately. 
blogs.technet.microsoft.com/enterprisemobi…<https://t.co/7UMaFuZVva>



CONFIDENTIALITY NOTICE: The e-mail transmission (and/or the documents 
accompanying such) may contain confidential information. Such information is 
intended only for the use of the individual or entity named above. If you are 
not the named or intended recipient, you are hereby notified that any 
disclosure, copying, distribution, or the taking of any action in reliance on 
the contents of such information is strictly prohibited. If you have received 
this email in error, please notify the sender and then delete the email. Thank 
you for your cooperation.


CONFIDENTIALITY NOTICE: The e-mail transmission (and/or the documents 
accompanying such) may contain confidential information. Such information is 
intended only for the use of the individual or entity named above. If you are 
not the named or intended recipient, you are hereby notified that any 
disclosure, copying, distribution, or the taking of any action in reliance on 
the contents of such information is strictly prohibited. If you have received 
this email in error, please notify the sender and then delete the email. Thank 
you for your cooperation.


CONFIDENTIALITY NOTICE: The e-mail transmission (and/or the documents 
accompanying such) may contain confidential information. Such information is 
intended only for the use of the individual or entity named above. If you are 
not the named or intended recipient, you are hereby notified that any 
disclosure, copying, distribution, or the taking of any action in reliance on 
the contents of such information is strictly prohibited. If you have received 
this email in error, please notify the sender and then delete the email. Thank 
you for your cooperation.





Reply via email to