Why not use ADM Templates?

ADM Templates used to be the only way to manage applications. But ADM Templates have several drawbacks.

ADM Templates usually "tattoo" the registry

Applications need to be coded to use proper "policies" keys. Most applications aren't, and therefore don't ship with their own ADM files. You might be able to create you own ADM file, but the registry keys those manipulate end up "tattooing" the registry. When registry entries get "tattooed" they stick with the user wherever he or she roams. This produces the exact opposite affect of using Group Policy-based management in the first place. This makes overall management very difficult. PolicyPak applications ensure that your application's settings are always flexible and never tattooed.

ADM Templates cannot dictate all registry settings

ADM Templates do not have full control over all the registry settings. If you wanted to implement a REG_BINARY value, you simply cannot perform that function with an ADM template. PolicyPak applications ensure that your application's settings are always managed.

ADM Templates take work to code and troubleshoot

While the ADM syntax isn't "rocket science" it still take a long time to figure out which registry manipulations are available for any given application. All PolicyPak applications have all of the available settings, so you don't have to waste time troubleshooting.

ADM Templates do not share the same interface as the application

When configuring applications, you want all Group Policy administrators to be able to do it as easily as possible. Nothing is easier than a mirror of the actual application's interface instead of an ADM "interpretation" of the interface. PolicyPak applications always look like the application you're managing.