When to use packages
With all this information of application management, you might wonder what the point in using packages is. Many customers of Configuration Manager still use packages as their primary deployment method.
I have heard a lot of reasons why people still use packages after their migration to Configuration Manager. One thing that is common after discussing this with customers is that reasons for sticking with packages are generally not valid.
The most common reason is that executable or batch files cannot be created as applications. This is simply not the case. Configuration Manager has a deployment type called script installer. The easiest way to think of the script installer is for anything else not listed in the drop-down box.
Uses for the script installer deployment type could be some of the following, which might be used to deploy applications:
Executable
InstallShield installers
Batch files
PowerShell
VBScript
JScript
Custom bootstrap
Usage scenarios for packages
Packages do still...
