Aspects to be aware of when migrating from Configmgr 2007 to 2012.
Configmgr 2012 has some new features regarding Software Update compared to 2007, one of them are updates that are superseded, Configmgr can automatically Expire these updates and also hide them from the Console. So when migrating Software Updates you need to have the same meta data in 2012 as you have in 2007, other wise migration will fail.
In 2012 RTM the Superseedence Rule was default set to Immediately expire.
But in SP1 it was changed to 3 months.
Now… hmmm thinking I would set it to at least 24months while doing migration so that it doesn’t supersede anything that is likely for me to have in my Software Update Groups that I want to migrate.
Before this setting the log says:
After setting this the log says:
And it shows up in CM Console
Now this all takes some time, because it needs a full sync, and some database processing.
When migration is complete I would set the Supersedens Rule back to default. This is btw a great feature.