Unless your limited by politics, I would go to a parallel scenario with one 
beef virtual server and get to CM12 ASAP.

From: [email protected] [mailto:[email protected]] On 
Behalf Of Enley, Carl
Sent: Wednesday, April 08, 2015 11:43 AM
To: [email protected]
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.



Reply via email to