The question came up on the forum if it is possible to have a universal configuration for all packages. A universal configuration would be one configuration that has configuration entries for objects in all or many of the packages on a given machine or environment. The catch is that some configuration entries would apply to objects in specific packages that don't exist in other packages. So, when applying the configuration, you would get a warning for each attempted configuration of non-existant package object.
This is OK to do. It's possible and the warnings are only warnings, meaning they don't fail the package no matter how many you get. It's also possible to suppress the warnings generated by configuration with the "SuppressConfigurationWarnings" property on the package.
However, why do this when there is a better way. In an article I wrote for the November SQL Server Magazine, I talk about a better approach that is both adaptable and more powerful. I call it two stage configuration or making your packages location independent. If you use this method, you can eliminate a large percentage of the configurations for a given machine and you don't need to suppress configuration warnings.
http://www.windowsitpro.com/Article/ArticleID/47688/47688.html
Hope this helps,
Thanks,
Universe.Earth.Software.Microsoft.SQLServer.IS.KirkHaselden