PENDING New Install of SCCM - Old version is broken

[jcummings68]

So I have an old version of SCCM 1806 that would not update past that version. I even engaged MS Support on the issue, but sadly they were of little help. In the end, I decided the best result was to kill the old instance and do a fresh install on a new VM.

Can I just kill the SCCM and SCCMSQL VMs, remove the System Management container contents, and when I spin up the new version, have it overwrite the old client from the previous install? Not sure if those clients will start barking because they cannot connect back to the old instance?

Seems like it should be as simple as that, but tell me, what might I be missing here?

Thanks in advance.

 

[Prajwal Desai]

You can set up a new instance of ConfigMgr with new site code keeping the old one as it is. In case you want to migrate the objects from old to new ConfigMgr setup, you can do it. Removing system management container is not required, you can clean up that folder if required.

 

[Prajwal Desai]

So I have an old version of SCCM 1806 that would not update past that version. I even engaged MS Support on the issue, but sadly they were of little help. In the end, I decided the best result was to kill the old instance and do a fresh install on a new VM.

Can I just kill the SCCM and SCCMSQL VMs, remove the System Management container contents, and when I spin up the new version, have it overwrite the old client from the previous install? Not sure if those clients will start barking because they cannot connect back to the old instance?

Seems like it should be as simple as that, but tell me, what might I be missing here?

Thanks in advance.

I am also surprised to know Microsoft support couldn't fix the issue with your old ConfigMgr setup. What exactly were the issues that you facing?.