What if you have a CAS? /duckingforcover -JHam
From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Wednesday, October 5, 2016 2:02 PM To: [email protected] Subject: [mssms] RE: Question on migration Too much work. Why would you stand up a whole new site, migrate nearly everything - not everything can actually be migrated - redeploy all of the clients, redeploy content or fight with shared DPs, etc., etc. A backup and restore can be done easily within a day, tests your DR procedures in the process, and doesn't require you to reconfigure anything. J From: [email protected] [mailto:[email protected]] On Behalf Of Spengler, Jeff Sent: Wednesday, October 5, 2016 1:18 PM To: '[email protected]' <[email protected]> Subject: [mssms] RE: Question on migration Just curious..why never recommend a migration? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Wednesday, October 05, 2016 11:46 AM To: [email protected]<mailto:[email protected]> Subject: [EXTERNAL] [mssms] RE: Question on migration First a quick note, if you're on Server 2012, then you don't have WSUS 3. I would never recommend a migration unless you have some external constraint. Upgrading SQL in-place is almost trivial and works quite well. Upgrading ConfigMgr in-place works well as well. If you want to build new, site backup and restore to the new server is the best path and involves the least disruption. You can perform all of your in-place upgrades on the existing server and then backup and restore to the new server with like version of everything installed but no remnants of anything old. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kent, Mark Sent: Wednesday, October 5, 2016 11:45 AM To: '[email protected]' <[email protected]<mailto:[email protected]>> Subject: [mssms] Question on migration We are currently on SCCM 2012 R2 SP1. It runs on a Server 2012 (nonR2) server with SQL 2012 on box. We also run WSUS 3 and MDT (latest) on the same box. We also have three Server 2012 R2 servers running DP's (including PXE) and MP's. We need to make the move to SCCM CB, for obvious reasons, and I'm wondering what the consensus would be on a migration strategy. Do we attempt to update the server to R2, and then update SCCM, and the various pieces (SQL, MDT, etc.) after that. Or is it advisable to build a new 2012 R2 server (2016?) and try and migrate over to it? I'm looking to minimize downtime (who doesn't). I'm a little concerned about running numerous upgrades, sometimes it's like rolling dice, but if that's the best route I'll do that. I'd love to build new if possible, I just don't know how complex that would make the migration and if that would take longer. I should mentioned our Db had some minor corruption a few times, requiring repair with data loss. From what we gathered, it was due to the fact we were gathering too much process data which was filling up the Db quite a bit. Once we removed the amount of info that was being gathered from processes, the Db size went down and the corruption ended. Just looking for some pointers from anyone who has done this already, thanks! Mark Kent Manager, Client Systems Engineering Technology Support Services Resources for Information, Technology and Education (RITE) http://rite.buffalostate.edu<http://rite.buffalostate.edu/> --------------------------------------------------------------------- [Image removed by sender. Idaho Power Legal Disclaimer] This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. --------------------------------------------------------------------- ________________________________ CONFIDENTIALITY NOTICE: This email message and any attachments hereto are intended only for use by the addressee(s) named herein and may contain information which is legally privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, or an authorized representative of the intended recipient, of this email message, you are hereby notified that any review, dissemination, distribution, copying, or use (including any reliance thereon) of this email message, and/or any attachment hereto, is strictly prohibited. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is free from virus or other defect and no responsibility is accepted by the sending company, its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you have received this email message in error, please immediately notify the sender by return email and permanently delete from your system, the original and any copies of this email and any attachments hereto and any printout hereof. Unauthorized interception of this email is a violation of federal criminal law.
