Just a quick note on an issue you might see that can be a little bit confusing if you’re not aware of what’s going on. After migrating Software Update packages from System Center Configuration Manager 2007 to System Center 2012 Configuration Manager, it may appear that not all packages were migrated successfully. Usually the way this plays out is that after the migration, the admin looks at the updates package, sees fewer updates than he started with, and thinks something is wrong.
No cause for alarm though, as chances are all of the packages were actually migrated successfully. So why the discrepancy? Well there was an issue that I won’t get into here where ConfigMgr 2007 didn’t always display superseded updates correctly, so what’s happening is that the missing updates were removed because they were expired or superseded and no longer show up.
Hope this helps!
J.C. Hornbeck | System Center & Security Knowledge Engineer
App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/