Refer to your web server's documentation to ensure that standard CGI is enabled for the server, and that the CGI directory has the proper execute permissions.

On IIS, make sure that the IUSR_ account has Change rights in the temp directory. On other servers, ensure that the SYSTEM account, or user account under which the server runs, has Change rights in the temp directory.

Note: Enabling CGI on IIS for Windows Server 2003 and later requires additional configuration. See this article from our Knowledgebase for details.

If you are having trouble getting CGI programs to run, especially on IIS, then you might want to search our knowledgebase for help. Answers to the most-frequently asked questions are there.

Copy dompass.ini to the same directory as dompass.exe. Leave dompass.ini unchanged until you are sure Domain Password is working satisfactorily, then edit to suit your tastes. Note, you may need to add domain information per this KB article.

Add a link to dompass.exe on any page you want. For example, if your CGI directory is CGI-BIN, add this link: <a href="/cgi-bin/dompass.exe?">Change Password</a>

To use Domain Password on any web server, you must

• Adjust the Policies/Account settings in User Manager and turn off the "Users must log on in order to change password" checkbox.
• Adjust the Policies/User Rights settings in User Manager and add "Log on as a batch job" for "everyone" (or those users you want to be able to use Domain Password).
• Note: All regular Windows account restrictions apply. For example, if you have passwords restricted so they can only be changed every 10 days, then users will not be able to change passwords with DomPass more often then every 10 days. Ditto for allowing blank passwords, remembered passwords, and so forth. DomPass does not circumvent any Windows policies or security constraints.

          Username: 
  Current Password: 
      New Password: 
New Password Again: 

Note: Passwords are case-sensitive on this system. Password, PASSWORD, and password are three different passwords.

Version 1.1 (build 970302 or later) allows you to customize the entire format, as much or as little as you want.

Domain Password is self-configuring. It will discover the name of your primary domain controller and generate the proper HTML. You may override this by specifying a machine name on the PDC= line in dompass.ini. Specifying a PDC also makes the program more efficient, since the lookup can take a noticeable amount of time on some networks.

You may customize most aspects of Domain Password by editing the dompass.ini file. All of the text, and most of the HTML, can be changed by editing this file. To make Domain Password operate in Portuguese, for example, just replace the English text messages with the Portuguese equivalents.

Here is the default dompass.ini file. (It is included in the ZIP archive when you download.) All of the options are well-documented in the INI file itself, so there's not much point in repeating the instructions here.

By default, Domain Password looks for dompass.ini in the same directory where the you keep dompass.exe. This is also where Domain Password will write its log file, dompass.log. As of version 1.1.b.980925, you may change a registry setting to specify a different directory for dompass.ini and dompass.log. This feature was added to enhance security for servers that allow read access to all files in the CGI-BIN or SCRIPTS directory. If you are upgrading from a previous version, Domain Password will create the registry entry for you the first time you run Domain Password after the upgrade.

To change the directory where the config files are stored, use REGEDIT or REGEDT32 to modify Domain Password's ConfigDir setting:

    HKEY_LOCAL_MACHINE
        Software
            Greyware
                Domain Password
                    Parameters

Create the directory you specified above, and put the dompass.ini file in that directory. Use File Manager or Explorer to set the file permissions to Change for the users who should be able to access this file. Under IIS, this is usually the group Authenticated Users, and/or the user IUSR_machinename. Under other web servers, you will usually need to specify the account under which the web server runs, usually LocalSystem or System.

As long as the drive and directory you specify isn't shared, this will allow Domain Password to read the dompass.ini file and write the dompass.log file in this directory, but not allow access in any other way.