And if it's a money thing to replace the BDP's, with P2P go with a free option like BranchCache... *cough* *cough*.... :)
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Andreas Hammarskjöld Sent: den 8 april 2015 20:57 To: mssms@lists.myitforum.com Subject: [mssms] RE: SCCM 2007 Migrate to new Hardware - I would do a trial run of it, but you can see supported confs here: https://technet.microsoft.com/en-us/library/ee344146.aspx So basically, do a backup on a rainy day and: (greatly simplified) · Create a new virtual box, 5000 is fine for a virtual for your central. ConfigMgr is always top down upgrade. But in this case you are putting a backup back. · Install on a new 2008 R2 server. · Install SQL 2012. · Raid, just go with fast enough in that virtual. · Start ConfigMgr and select the site repair mode, follow the guide. · Some hotfixes required for sql 2012 to work as intended with 2007. But going to 2008 R2 sucks (2012 is not supported) & SQL 2012 is also old. So if you are putting in the time, go to 2012 R2 and SQL 2014. //A From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael Mott Sent: den 8 april 2015 17:54 To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: SCCM 2007 Migrate to new Hardware - Unless your limited by politics, I would go to a parallel scenario with one beef virtual server and get to CM12 ASAP. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Enley, Carl Sent: Wednesday, April 08, 2015 11:43 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] SCCM 2007 Migrate to new Hardware - I have been approached with a project to migrate our existing SCCM 2007 R2 environment to new Server hardware. We are currently running on Server 2003 and need to get to 2008R2 before EOL in June\July. I suppose a in place upgrade is not supported? I have suggested time and time again that we should put our efforts into SCCM 2012 but Mgt has not made a decision and time is running out. We have 2 primary sites with about 5000 clients and I am looking for a brief outline of the steps required to perform this upgrade with no loss of data \ production services - patching, software distribution, reporting etc... Some of my questions surround the following: · In what order should the upgrade take place ? Primary Parent site first? · Can I go from X86 server OS to X64 server OS. · Physical to Virtual supported · Sql Server versions, do they need to be the same (2005) · Drive configuration (Raid levels etc..) · Are there any gotchas that I should be looking at? If anyone has performed this task before and you are willing to share some tips or outline the steps that you have taken I would greatly appreciate it. Thanks ________________________________ 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.
