Beware of creating security templates for use in another OS

When you’re creating a security template with secedit.msc (e.g. for use in a software package), it is important to create this on the same operating system. For example: when you’re creating a security template on Windows XP, it can be imported on a Windows 7 machine without problems. But it won’t work! As I have experienced in packaging several applications and could not find the direct cause of some user related problems, it just turned out to be the security template which did not import the proper security rights. Just create the security template on the same OS and it will save you a lot of time.

Tags: security template,packaging,secedit