Daniel, Keep the same hostname/IP but rename the new box AFTER shutting down the old box and BEFORE installing CM and doing the restore. If anything goes wrong, simply power down the new box and power back up the old box.
As for upgrading the clients, you may want to do that before you decommission the old box. I’m not sure how the client upgrade will take if the self-signed cert isn’t matching. I believe we ran into this situation before and ended up with orphaned clients. David--- From: [email protected] [mailto:[email protected]] On Behalf Of Corkill, Daniel Sent: Thursday, June 2, 2016 8:34 PM To: [email protected] Subject: RE: [mssms] Best upgrade path ? Hi all, Sorry to resurrect an old thread but I’m finalising our upgrade plan and have a few questions. I’m taking the option Jason has suggested because we too need to migrate from 2008 R2 to 2012 R2. The high level steps I’m looking at are: · Upgrade our current single primary site server (running Win 2008 R2 w/ CM 2012 SP1) to CM 1511 · Build a second box running Win 2012 R2 and install CM 1511 · Backup and restore the site server to the new box · Upgrade to CM 1602 on the new box · Upgrade the clients So besides that, what is everyone doing with regards to naming their new boxes? Are you keeping the same hostname/IP? In which case I’m guessing I’ll need to stand up the new box with a temp name and then rename it after restoring the site from backup and shutting down the old site server. Daniel. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Friday, 13 May 2016 11:20 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Best upgrade path ? There is a third and usually better option here: backup and restore. No migration needed, restore on update OS, tests your recovery procedures, clients and all site systems untouched, no “interim” periods, and lots more. J From: <[email protected]<mailto:[email protected]>> on behalf of "Marcum, John" <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Friday, May 13, 2016 at 8:03 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: RE: [mssms] Best upgrade path ? Personally I am in the middle of a side0by-side migration from 1602 to 1602 just because my old primary site is on 2008R2. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Freddy Grande Sent: Thursday, May 12, 2016 7:52 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] Best upgrade path ? We were on a similar boat; Initially single Primary Site Server on WS 2008 R2 with ConfigMgr 2012 R2 CU3 1. Upgraded in place to ConfigMgr 1511 a. Our plan was to upgrade that to 1602 but for some reason no matter what we did it never showed up on the console 2. Built new WS 2012 R2 with ConfigMgr 1511 > upgraded to 1602 3. Migrated pretty much everything from old server to new server (1511 to 1602 migration) 4. Had issues with DPs and we still seem to be having some weird cryptic issues a. Application Deployments with following errors: “CI Version Info timed out” or “CI documents download timed out” b. Site server deploys client to itself but it never reports to the actual site c. Errors showing in Site Status for Application Catalog web service point and Application Catalog website point but no relevant errors in logs If I could do it again I would bring up a new server without migrating anything and configuring it from scratch. We are small enough that we can actually do this but didn’t expect these many issues from a migration. You should note as well you can’t “install 1602” from scratch. You must install 1511 first and upgrade to it. Regards, Freddy -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Richard Bjerregaard Sent: Friday, 13 May 2016 6:49 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Best upgrade path ? Hi, So 1 vote for in-place upgrade of OS followed by in-place upgrade of SCCM Would anyone 1) Build a new server with W2K12R2, install SCCM R2 CU3, restore DB and Data from backup of old server, in-place upgrade SCCM to 1602. 2) Build a new server with W2K12R2, install SCCM 1602, manuel "rebuilt" configuration. Perhaps restore selected data from backup. 3) Build a new server with W2K12R2, install SCCM 1602, start from scratch with a new configuration, applications and TS. How will my clients reacts to all this? rg Richard 12. maj 2016, 20:24:07, you wrote: > I'm never a fan of in-place upgrading an OS, especially on a server. > Having said that I'd do an R revision in-place then upgrade CM in-place. > -----Original Message----- > From: [email protected]<mailto:[email protected]> > [mailto:[email protected]] On Behalf Of Richard > Bjerregaard > Sent: Wednesday, May 11, 2016 5:10 PM > To: [email protected]<mailto:[email protected]> > Subject: [mssms] Best upgrade path ? > Hi everyone > Looking for some guidance, high level steps. > Have > SCCM 2012 R2 CU3 running on Windows Server 2012 RTM > 4.500 clients, all windows 7, ~200 applications. > Just 1 server. Physical. > How can I get(upgrade) to SCCM 1602 on Windows Server 2012 R2 ? > I can properly wait until Server 2016 is released, if that makes a > difference. > Preparing for Windows 10. > rg > Richard > ________________________________ > Confidentiality Notice: This e-mail is from a law firm and may be > protected by the attorney-client or work product privileges. If you > have received this message in error, please notify the sender by > replying to this e-mail and then delete it from your computer. NOTICE: This email is confidential. If you are not the nominated recipient, please immediately delete this email, destroy all copies and inform the sender. Australian Maritime Systems Ltd. (AMS) prohibits the unauthorised copying or distribution of this email. This email does not necessarily express the views of AMS. AMS does not warrant nor guarantee that this email communication is free from errors, virus, interception or interference. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ********************************************************************* This email, including any attachment, is confidential to the intended recipient. It may also be privileged and may be subject to copyright. If you have received this email in error, please notify the sender immediately and delete all copies of the email. Any confidentiality or privilege is not waived. Neither the Council nor the sender warrant that this email does not contain any viruses or other unsolicited items. This email is an informal Council communication. The Council only accepts responsibility for information sent under official letterhead and duly signed by, or on behalf of, the Chief Executive Officer. Privacy Collection Notice Logan City Council may collect your personal information, e.g. name, residential address, phone number etc, in order to conduct its business and/or meet its statutory obligations. The information will only be accessed by employees and/or Councillors of Logan City Council for Council business related activities only. If your personal information will be passed onto a third party, Council will advise you of this disclosure, the purpose of the disclosure and reason why. Your information will not be given to any other person or agency unless you have given us permission or we are required by law. ________________________________ Legal Notice: This email is intended only for the person(s) to whom it is addressed. If you are not an intended recipient and have received this message in error, please notify the sender immediately by replying to this email or calling +44(0) 2083269015 (UK) or +1 866 592 4214 (USA). This email and any attachments may be privileged and/or confidential. The unauthorized use, disclosure, copying or printing of any information it contains is strictly prohibited. The opinions expressed in this email are those of the author and do not necessarily represent the views of 1E Ltd. Nothing in this email will operate to bind 1E to any order or other contract.
