Jump to content
EduGeek EdSec 2026 is on Tuesday in Derby! Join us for a day of EdTech security focused talks, networking, and an evening social ×

Recommended Posts

Posted

Righto,

 

I'm half way through a migration from an existing SCCM 2012 SP1 server to another. New server name etc. Got the new one up and running (server 2012, sql 2012 etc), SCCM installed and a migration ran which copied over boundaries, collections etc without problem. However, for the life of me can't seem to get my head around migrating over packages. Going on the technet articles (which are rather difficult to understand at the best of times, where articles like "Procedure for reassigning distribution points to another server" doesn't actually tell you the procedure or give any clues in English) I can see how to "upgrade" a DP however it doesn't copy/synchronise any of the packages/applications as I would, probably erroneously, expect.

 

I suspect I might need to start from scratch which I'm trying real hard to avoid, but any of the SCCM gurus here been able to tackle this?

Posted

I did a backup of my server. Settup the new one and restored the backup. Really easy to do.

 

Anyway for packages wouldn't it be as easy as putting them on the new DP?

Posted

Aye but you can't restore a backup to a machine with a different name. Site code remains the same but that's not much help unfortunately :( Shame, as you say that's a really easy process.

 

I can certainly just copy packages across but they won't show up in SCCM without some work and I don't know what that entails.

Posted
Because that would mean renaming the original server which is a primary file server and hosts far too much. As said, the original server must remain exactly as is, minus SCCM. Looks like I've got to start over.
Posted
Sorry i am with you i was assuming it was only for SCCM. I have never done what you are asking, but i did think they would just show up as both SCCM installs use the same DB.
Posted

I think I'm going to use it as a reason to start from scratch and clear out some stuff from the initial install which, regardless of the year of testing, still has a lot of "mistakes" and leftovers.

At least with a running system I can go through and cherry pick the bits I need :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...