Release Notes

Policy Template Editor 2.0.3 (build 1014)

• When copying and pasting policies, the settings on the windows2000 tab where not copied. This has been fixed.

Policy Template Editor 2.0.2 (build 1013)

• When copying and pasting "Checkbox" policy parts, the "Valueon" value was not always correctly copied. This has been fixed.

Policy Template Editor 2.0.1 (build 1012)

• In policies for Windows2000, there is an optional "EXPLAIN" field. This field was not always correctly encapsulated in quotes when saved to the .adm file. This has been fixed.

Policy Template Editor 2.0.0 (build 1011)

• Support For version 3 of the template file format, for Windows 2000.
• Support for version dependent setting inside the same template. This are the "#if version" statements in the template files. Many default templates for windows2000 have completely different settings if read by different versions of the Policy Editor. This is now also supported by the Policy Template editor.
• Added support for reading and writing UNICODE files. Many of the standard W2000 template files are in UNICODE. These where not editable with the previous version.
• For dropdown lists and combo box policy parts the NOSORT keyword is now supported.
• Expandable text is no also supported for the combobox policy part
• Remarks: Due to the fact that Windows 2000 templates are often in UNICODE, we had to modify the program so that this is supported. As a consequence the current version of the Editor can only be installed on NT4 or Windows2000. It cannot be installed anymore on Windows95/98. Note however that ASCII files are still explicitly supported, so it is still possible to create templates for windows95/98 with the new version.

Policy Template Editor 1.3.2 (build 1008)

• When copying an policy where "default value" was selected, the pasted policy was set to "explicit value". This has been fixed.
• When the orignal template file string section contained strings not encapsulated in quotes the string section somtimes whas not correctly read from the file. this has been fixed.

Policy Template Editor 1.3.1 (build 1007)

• When a policy object was copied, the valuename was not copied. This has been fixed.

Policy Template Editor 1.3 (build 1006)

• When the "Use Key" option is selected in e.g. a catagory or policy, it is checked that the key is not an empty string.
• The checked als default/unchecked as default setting of a checkbox policy part is now correctly updated after a change.
• When reading a sub-catagory the "Use Key/Use Default" option is now correctly shown.
• The "KeepOnTop" property of the "properties" window in now on by default.

Policy Template Editor 1.2 (build 1003)

• Files were sometimes not correctly read when some keywords were lowercase.
• When creating a new policy, the icon was a book and not a sheet.
• When exiting the program, if changes have been made to the adm file, the user was not prompted to save his work, now the PTE does prompt the user.
• When closing the string tables box, the left view dit show the string names instead of the display names. This has been solved.
• When copying a catagory or policy section from one file to an other the displayname information was not copied, now it is. NOTE: if there are contradictions the source display name prevails.

Policy Template Editor 1.1 (build 1001)

• The PTE now supports version 2 of the Template File format, instead of version 1. This is a rather minor change in the template file format, which consists of the extra option "Expandable text" in the EDITTEXT policy part.
• The PTE no longer requires the Template keywords of input files to be in capitals.
• The PTE now supports the "#if VERSION ........#endif" switch in input template files. This support indicates that the PTE can read template files of other versions than 2. Note that the PTE converts this on input to version 2. Sections which are not compatible with version 2 are skipped, and will not be retained when saved.
• The PTE can read files which contain #ifdef Keyword .......#endif switches in input files. Since currently the Policy Editor does not support any keywords, the PTE does neither, and all #ifdef Keyword statements evaluate to false on input.