SCCM Site Backup and Restore to new server - or start over

[mdrabble]

I'm busy updating my 2012r2 servers to server 2019 and I've come to do my sccm server.

 

Have tried an in place upgrade and it the OS upgrade worked fine - SCCM however didn't like it so much to the point it wouldn't load!, so I have rolled backed the VM and now I'm looking to do a backup and restore of the sccm site.

 

On the new sccm server, does the server/drives have to be the same or have I got room to change things - such as have additional drives to store the sql db and additional drives for packages and contents?

 

Originally had OS, sql and sql db on drive c: and all sccm contents/packages/wsus etc on drive d:

 

Looking to have a separate drive for sql db and then separate drives for content and application sources etc.

 

Or..... since I will be reinstalling most of the desktops over the summer, do I start SCCM from scratch and import packages I'm actually using to save having to import old bits of software I'm not using anymore.

 

Thoughts, comments and suggestions welcome

 

Cheers

[Steve21]

Are you on the latest CB update before the upgrade? No reason it shouldn't work with an inplace, any error etc showing?

 

You can have different drives for things like packages (Always prefer this route, I normally have seperate Server + OS + Packages etc drive setup), but you'd need to manually (or via some scripts you can download) move all the existing packages config to those locations, unless you delete them all and restart them

 

In terms of reinstalling it etc, do you have much setup? Config wise on SCCM that you'll want to keep? Thinking of policies/av rules/scripts/requirement baselines etc

 

Steve

[mdrabble]

Are you on the latest CB update before the upgrade? No reason it shouldn't work with an inplace, any error etc showing?

 

You can have different drives for things like packages (Always prefer this route, I normally have seperate Server + OS + Packages etc drive setup), but you'd need to manually (or via some scripts you can download) move all the existing packages config to those locations, unless you delete them all and restart them

 

In terms of reinstalling it etc, do you have much setup? Config wise on SCCM that you'll want to keep? Thinking of policies/av rules/scripts/requirement baselines etc

 

Steve

 

Yep - am on CB after the in-place upgrade sccm services would not load.

 

Installation is over 5 years old now, and if I'm honest, I've not removed old apps/packages so on that side of things it would force me into tidying that part up.

 

In terms of anything that I need to keep - scripts etc... think I've 1 or 2 scripts/policies etc (nothing that cannot be recreated from scratch)- setup is very basic (no thrills) to deploy images/update and software.

 

Cheers

Mark

[mdrabble]

Decided to reinstall from scratch - yes, it probably not necessary but will give me a chance to actually produce documentation for it this time around as I didn't document it last time!

 

Will use separate discs for DB, Content, etc

 

Have exported some collections, policies and applications/packages that I want to keep/re-import.

 

I've run out of things to do as the helpdesk is clear and I'm sat doing nothing - so at least it will keep me busy for a couple of days.

[psydii]

Not immediately helpful to you, but to others: Microsoft were collecting feedback about in-place upgrades earlier this year: