ADSI VB Script Identify AD users with expired password

I would like to have a VB Script developed that will go through the entire list of users and computers in an AD OU and look for accounts with expired passwords. If the password is expired for more then a specific number of days it should pass that to the output. Please Check Deliverables. Note: Bonus available for additional functions! ## Deliverables I would like to have a VB Script developed that will go through the entire list of users and computers in an AD OU and look for accounts with expired passwords. If the password is expired for more then a specific number of days it should pass that to the output. The output should be configurable as a CSV File, echo or both. The output should indicate the account name, the OU, number of days expired, disabled status and if it is a machine account or a user account. You must be able to specify which OU to have the script look in, the script should check all OU's underneath the OU that it is specified. The script should also be able to run with just the domain specified and will start at the top level. The script should also contain a list of OUs to exclude. It should exclude all OUs underneath the specified OU. It should also accept a text file with these exclusions. I would like an option to exclude disabled accounts. I would like the option to specify accounts of user, machine, or both. The script should also contain a list of accounts to exclude. It should also accept a text file or a list of accounts specified in options with these exclusions. If possible I would like to have the ability to include wildcards in the user exclusion section so I can exclude accounts based on a prefix. Example “Service*?? would exclude all accounts starting with the word service or accounts like “Service-MOM,?? “Service-AD?? Please include an example of these exclusion text files. These text files can be stored in the directory the script runs from, another directory on the same machine, or a UNC path. The out files can be stored in the directory the script runs from, another directory on the same machine, or a UNC path. The Script should have logging. The level of logging should be specifiable in the script options The logging choices should be: 1. Log everything 2. Log only accounts disabled and moved. 3. Disable logging The script should contain full comments within the code. The script should also be developed so that it is modular and modules can be reused in other coding projects. The script should be developed using quality coding standards All options should be specified in the first few lines of the script. Options should also be able to be passed to the script through the command line. The script should deliver error messages that are intelligible if it has trouble. 1) Complete and fully-functional working Scripts(s) as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Windows 2003 Server. ADSI VB Script