Yes, that's why I wanted to make sure it's known that although the majority here have not had a problem, they do happen. This is not to make you overly freaked out, just make sure to test and backup because even with all of the tests we performed before the upgrade, it still failed.
As I understand the situation for us, at the root of the problem was with the secure communication over the service broker queue, the CAS would upgrade no problem, then it would send a message to the primaries for them to initiate their upgrade, but before the broker could process and send the queued message, the entire Broker Queue gets destroyed and completely rebuilt.... Along with its contents. Thus the message never made it to the primary site to do its steps of the upgrade. So as I understand it, a validation/recheck was added specifically for this issue to verify that the message was sent and received by the primary and if not, it gets resent now. Rick J. Jones Wireless from AT&T Domestic Desktop Application Management (206) 419-1104 From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Mawdsley R. Sent: Monday, December 18, 2017 5:27 AM To: mssms@lists.myitforum.com Subject: RE: [mssms] Upgrading Config Mgr It never fails until right when you least expect it to. Rich From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Enley, Carl Sent: 18 December 2017 13:00 To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Upgrading Config Mgr Wow - we went CM2012 to CBB 16.xx (don't remember) then to 1702 > 1706 > 1710 - never a single hiccup. Knock on wood..... From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of JONES, RICK J Sent: Friday, December 15, 2017 9:38 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: Re: [mssms] Upgrading Config Mgr I am hopeful that 1710 will be the one for us to be mostly painless, right now we are in no touchy time of the year as I'm sure many are, high sales time... First of the year though.... 1710 here we come! Rick J. Jones Wireless from AT&T Domestic Desktop Application Management (206) 419-1104<tel:(206)%20419-1104> -------- Original message -------- From: "Heaton, Joseph@Wildlife" <joseph.hea...@wildlife.ca.gov<mailto:joseph.hea...@wildlife.ca.gov>> Date: 12/15/17 6:02 PM (GMT-08:00) To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Upgrading Config Mgr Well, then I thank you for paving the way to our ease of upgrades :) From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of JONES, RICK J Sent: Friday, December 15, 2017 2:12 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Upgrading Config Mgr It's been a running joke with our PFE, I emphatically require him to be available as it will FAIL. Oh.. no, it will be better this time.... Ring, Ring... it failed... The last time we upgraded to 1706 the PFE setup some of the product engineers to be present, so I went to MS building, sat in a conference room with my screen projected on the wall as I kicked off the process that I knew would fail... The Product engineers were called into the room several times as it puked many steps through the process... and hmmm FAIL... uh... most of that upgrade was done by the Product Engineers... I believe in 1710 there are several enhancements as a result of their hands on experience with the pain that they were forced to experience in that conference room. Rick J. Jones Wireless from AT&T Domestic Desktop Application Management (206) 419-1104 From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Sherry Kissinger Sent: Friday, December 15, 2017 12:54 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: Re: [mssms] Upgrading Config Mgr Wow. We've had glitches or bumps in the road--but nothing ever earth shattering. and I think only for paranoia (turned out we didn't need them anyway) we had our PFEs available when we upgraded from cm12 to current branch. Otherwise... nothing where the system was "down" or "unusable" during or after an upgrade. We do of course have to do pre-announced change windows, when the system will be down for upgrading, with a detailed checklist and step-by-step checks to confirm all is well post-upgrade. and yes, that Change does have to be approved by the-powers-that-be. We just did 1706 to 1710 2 weeks ago (the infrastructure, not all clients immediately) we were done in 9 hours. It would have only taken 7.5 hrs... but again--some external thing we didn't know to block was locking something the upgrade wanted to have exclusive rights to. had to find and kill it. (we now have a step in our checklist to explicitly look for and kill if found during upgrades) That included the CAS, Primary Sites, all the other role servers (MP/DP/SUPs etc), and a preventative reboot before... and a "we might as well" reboot after on all the infrastructure servers, just in case one was needed. We'd rather reboot on a Saturday than figure out a reboot is needed mid-day Monday. Also included updating to the latest ADK, and the console instances hosted on Citrix. On Fri, Dec 15, 2017 at 2:24 PM, JONES, RICK J <rj7...@att.com<mailto:rj7...@att.com>> wrote: Just for those that think there is no big deal to this... EVERY SINGLE UPDATE we have done has failed in some way even back to SCCM 2007. EVERY SINGLE ONE. EVERY SINGLE time we have had to bring Microsoft in to fix the problem. EVERY SINGLE TIME. Rick J. Jones Wireless from AT&T Domestic Desktop Application Management (206) 419-1104<tel:(206)%20419-1104> From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] On Behalf Of Marable, Mike Sent: Friday, December 15, 2017 4:12 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Upgrading Config Mgr Same here. We would never be able to just click "go" without a vetted plan in place and change management involved. With 35K clients we are by no means a large organization, but if something were to go sideways in the upgrade and we skipped the planning and control, there wouldn't be enough time to update resumes once they came for us. On top of that there are other factors to figure in before you click "go". For example, in our case we are going to have to do a side-by-side site migration because our SQL cluster is no longer supported (hardware is out of warranty). Best practices from the Microsoft PFE was to do a site migration as opposed to attempting to just moving the database to a new cluster. So we're going to spend a great deal of time migrating content, collections, sequences, etc. to the new site servers, test and validate it all, then start migrating clients. Then we can click "go" and upgrade the new site to 18xx. Mike From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Mawdsley R. Sent: Friday, December 15, 2017 3:55 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Upgrading Config Mgr It's the same here.. and, I'd hope everywhere have some form of change control. Although it obviously depends on how big the shop is. I think everyone who has been through a failed upgrade at some point in time, is always slightly more weary of the potential for downtime. Personally, I'll upgrade my Dev environment a week or so after its out in Fast Ring.. then Prod a few weeks after its general release. But I'll submit a change, and communicate its upcoming upgrade to all relevant teams long before and in the build up to it being done. Rich Mawdsley From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Heaton, Joseph@Wildlife Sent: 14 December 2017 16:35 To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] Upgrading Config Mgr My organization requires a more formal plan for any updates. And it goes through a weekly approval board, so I still have to line everything up nicely. I got the go-ahead to upgrade ADK today, but the server updates haven't gone to the approval board yet. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Stuart Watret Sent: Wednesday, December 13, 2017 12:19 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: Re: [mssms] Upgrading Config Mgr You must be using lots of new features if you need a plan :) :) Run the pre-requ check that would tell you if 1702 to 1706 will work (it will) With quarterly updates I wouldn't spend to long planning ! Backup and press go....... Stuart On 12 Dec 2017, at 18:07, Heaton, Joseph@Wildlife <joseph.hea...@wildlife.ca.gov<mailto:joseph.hea...@wildlife.ca.gov>> wrote: I am currently running 1702. I've written up my plans and method for upgrading to 1706, but over the weekend 1710 showed up in my availables. I have seen some really cool stuff coming with 1710, but is it still too soon for production? Can I upgrade from 1702 directly to 1710? Joe Heaton Information Technology Operations Branch Data and Technology Division CA Department of Fish and Wildlife 1700 9th Street, 3rd Floor Sacramento, CA 95811 Desk: 916-323-1284<tel:(916)%20323-1284> ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues -- Thank you, Sherry Kissinger My Parameters: Standardize. Simplify. Automate Blog: http://mnscug.org/blogs/sherry-kissinger<https://urldefense.proofpoint.com/v2/url?u=http-3A__mnscug.org_blogs_sherry-2Dkissinger&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=8W05-ToKtZdWVatHir2IiQ&m=dzytjgWen4upRvAi5jmGvc9VoLsC-9TZSSOMqoNAnuY&s=tdcDnOO59GQiYPlt0GdnkwSPAYl1bmboQIbrc9kvoN0&e=>
