Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING Best way to migrate SCCM to new hardware

VoodooOneNine

Member
Messages
8
Reaction score
0
Points
1
Hello All,
Long time reader. First time post-er. I have been searching for quite some time and can not seem to find a definitive answer. So much info out there is also many years old.
This will be my first migration. I am looking to migrate our existing SCCM server from it's aging hardware to new hardware we just purchased.

What I would like to know is that in 2025, what is the best way to do this? Especially for a first timer. Any suggestions would be greatly appreciated.

We are on SCCM CB 2409 with the latest patches and SQL 2019 running on the same server.

Best,

VoodooOneNiner
 
Hello All,
Long time reader. First time post-er. I have been searching for quite some time and can not seem to find a definitive answer. So much info out there is also many years old.
This will be my first migration. I am looking to migrate our existing SCCM server from it's aging hardware to new hardware we just purchased.

What I would like to know is that in 2025, what is the best way to do this? Especially for a first timer. Any suggestions would be greatly appreciated.

We are on SCCM CB 2409 with the latest patches and SQL 2019 running on the same server.

Best,

VoodooOneNiner
Last time i did this a new server was built and given the role 'Site Server Passive Mode'. Then it was promoted to site server and the other demoted. There are plenty of guides with all the steps out there on the web. If i can find my own document i will share it
 
Last time i did this a new server was built and given the role 'Site Server Passive Mode'. Then it was promoted to site server and the other demoted. There are plenty of guides with all the steps out there on the web. If i can find my own document i will share it
Thanks for the reply Stanley.

I have seen this recommendation before. I think the issue I would have in setting up a secondary site would be that it would have a new site ID and a new IP once I promoted it to a primary. That would mean that all of out devices would have to find and relocate to the new server and not to mention the time it would take for all out devices to do that (we have a couple thousand). I would prefer that the transition is as invisible to the end user and possible.
 
Thanks for the reply Stanley.

I have seen this recommendation before. I think the issue I would have in setting up a secondary site would be that it would have a new site ID and a new IP once I promoted it to a primary. That would mean that all of out devices would have to find and relocate to the new server and not to mention the time it would take for all out devices to do that (we have a couple thousand). I would prefer that the transition is as invisible to the end user and possible.
That's incorrect, if your site name is cm_123 then your new server will be a passive site server on site cm_123. Once promoted I will be the site server of cm_123 and your current server will become passive site server of that site name
 
That's incorrect, if your site name is cm_123 then your new server will be a passive site server on site cm_123. Once promoted I will be the site server of cm_123 and your current server will become passive site server of that site name
Thanks for the info. I will give this a try. Not sure how to set the secondary as a "passive site server". Will look that up now. Thank you.
 
While researching the passive option, I read that you need to have a remote content database. That is something we do not have and wish not to implement. I would like to know what is the best way in 2025 to migrate out current SCCM server to new, physical hardware.
 
While researching the passive option, I read that you need to have a remote content database. That is something we do not have and wish not to implement. I would like to know what is the best way in 2025 to migrate out current SCCM server to new, physical hardware.
Can you show me where you read that please?
 
if you mean this

Move Content Library to File Share​

Next we need to move the content library to a network file share in which both the Active and Passive roles can access.

( Note: If the Manage Content Library option is “greyed out” it will be because you haven’t removed the distribution point role)

1.Go to Administration – Site Configuration – Sites

2.In the home tab Click Site – Manage Content Library

3. Enter the remote location you will move the content library to and click next.

Then yeah, i moved it to the new server not to a network share. A network share make more sense though as it helps for future migrations, apps and packages should also be on a remote share although they rarely are.
 
While researching the passive option, I read that you need to have a remote content database. That is something we do not have and wish not to implement. I would like to know what is the best way in 2025 to migrate out current SCCM server to new, physical hardware.
Can I ask why you don't want remote content? The passive site is the "safest" method to upgrade ConfigMgr. Just saying.
 
Can I ask why you don't want remote content? The passive site is the "safest" method to upgrade ConfigMgr. Just saying.
We have no where to move it to. Just want to move the existing SCCM server to new hardware. I am a little shocked that this is not a simpler task in this day and age.
 
We have no where to move it to. Just want to move the existing SCCM server to new hardware. I am a little shocked that this is not a simpler task in this day and age.
I'm not sure what you mean by that. ConfigMgr gives you the option to have "no down time" and no risk per se. You can do a backup and restore if you like but that will have downtime (and risk) and lots of it. So, pick the option that you want. Both options are covered within the docs.
 
I'm not sure what you mean by that. ConfigMgr gives you the option to have "no down time" and no risk per se. You can do a backup and restore if you like but that will have downtime (and risk) and lots of it. So, pick the option that you want. Both options are covered within the docs.
As I mentioned, This is my first time doing this. I am trying to fine the best method to do it. No downtime would be great. Any info on how to accomplish that would be much appreciated.
 
As I mentioned, This is my first time doing this. I am trying to fine the best method to do it. No downtime would be great. Any info on how to accomplish that would be much appreciated.
You have all the info you need. Now I imagine someone is expecting you to do this soon, so what are you going to do?
 

Forum statistics

Threads
7,131
Messages
27,848
Members
18,145
Latest member
Rothgar
Back
Top