Microsoft System Center 2012 Configuration Manager continues to support packages and programs that were used in Configuration Manager 2007. A deployment that uses packages and programs might be more suitable than a deployment that uses an application when you deploy any of the following:

• Scripts that do not install an application on a computer, such as a script to defragment the computer disk drive.
  
  
• “One-off” scripts that do not need to be continually monitored.
  
  
• Scripts that run on a recurring schedule and cannot use global evaluation.
  
  

When you migrate a Configuration Manager 2007 site to a Configuration Manager hierarchy, you can migrate existing packages and deploy them in your Configuration Manager hierarchy. After migration is complete, your Configuration Manager 2007 packages appear in the Packages node in the Software Library workspace. You can modify and deploy these packages in the same way as you did by using Configuration Manager 2007 software distribution. The Import Package from Definition Wizard remains in Configuration Manager to import legacy packages. Advertisements are converted to deployments when they are migrated from Configuration Manager 2007 to a Configuration Manager hierarchy.

Packages can use some new features of Configuration Manager, including distribution point groups and the new monitoring functionality. Microsoft Application Virtualization applications can no longer be distributed by using packages and programs in Configuration Manager. To distribute virtual applications, you must create these as Configuration Manager applications.

In This Section

See Also

---

For additional information, see Information and Support for Configuration Manager.
To contact the documentation team, email SMSdocs@microsoft.com.