WARNINGS

D I S C L A I M E R

These tags should be considered POTENTIAL RISKS from a security standpoint. Guard all access to them. It is not advised that you place them on any machines where hackers* or other malicious people may have easy access to them. (Hopefully you realized that already, though.)

These CFX tags tag can modify the security settings for: 1) the SAM NT User/Group database 2) the NTFS File Permissions (ACLs) and 3) IIS Internet HTTP and FTP sites. This, it should be obvious, can potentially cause SEVERE problems if misused or deployed in an incorrect manner. If you are not a security expert you should consult with one before utilizing these server extensions on production servers.

B U G S

It happens. This is why feedback from a wide range of people is crucial in this case. IF SOMETHING DOESN'T WORK, TELL US.

Due to the extremely serious nature of this tag, test your code on your development servers throughly before migrating. Do not blindly assume a new version of any tag will work exactly as the one before. Unintentional side effects can occur due to code changes.

If you have questions about the implementation of a function of the tag or detect obvious bugs or limitations, see either the help or the feedback section for information on contacting us for ASAP corrections to the code base.

Remember: The first step in fixing a situation is alerting us to it.

C O N F I D E N C E T E S T S

Each tag has, along with it's unified documentation page, several of what are called "confidence tests". These are CFML pages which use all of the tag(s) functions in both basic and more aggressive ways. Their purpose is to inspire confidence in the end-user (you) and the programmer (that'd be me) that the tags are working as they are supposed to.

They also make for some useful examples.

The test pages are not meant to be used on production servers as those which are not marked READONLY will create test files, folders, users, groups and other such things when used. All others will. That is their purpose. This is normal. In general the tags will clean up after themselves, but in some cases they purposely won't. Be aware of this. Examine the cfm page source yourself first if you are unsure what the test is supposed to do.

Those tests marked as STRESS tests should only be tried with foreknowledge that they are meant to try to crash your computer or network. Some STRESS tests will do outrageous things like creating a thousand (1,000) NT user accounts and permission-secured folders to go with them. If you click that a couple times in a row you'll quickly become very unpopular on your LAN network.

Be patient with STRESS tests. Some of them make take several minutes to complete.

Btw, test names may include, but are not limited to: "sissycat", "susycat", "fluffercat", (lots more names ending in "cat"), "test" and "bogusbogusbogus", etc. Also popular with STRESS tests are things like "User1000", etc.

One last note. Sometimes the point is to test if the tag can handle error situations gracefully (that is, does it return a pleasant little error message for you or does the system crash and reboot.) Any test marked with (FAIL) is intended to do just this. So don't panick if error messages fill your screen (as long as it's not an "unexpected" error). That's supposed to happen.

Please refer to the help or basic introduction pages for further information.