As most people know we took down GotDotNet and have relocated most of our external tools and code to http://code.msdn.com or http://codeplex.com. I have relocated OABInteg to the following location: http://code.msdn.com/oabinteg. I have updated the web documentation on how to use the tool as well we can be found here: http://blogs.msdn.com/dgoldman/archive/2005/08/28/oabinteg-and-how-to-use-it-to-troubleshoot-oab-generation-issues.aspx.
New Changes to OABInteg
As per request from the military I have added a new logging switch: /v:3 (ErrorsOnlyLogging). By using this switch the following things will happen when you run the proxytest test.
*Total number of temp legacyExchangeDN's found: 5**Total number of objects that are missing some main attributes: 126**Total number of objects that mail and proxy attribute don't match: 12**Total number of objects that do not have a domain value: 0**Total number of objects that do not have a valid Unicode domain value: 0**Total number of objects that do not have a valid SMTP Domain because first character is not greater than '/': 0**Total number of objects that do not start with /o= or /O=: 1**Total user objects that are missing the Primary Proxy address attribute: 0***Total user objects with proxy addresses equal to or over 64 characters: 0***Total objects with the '@' character in the legacyExchangeDN: 6****Total objects with bad Active Directory Backlinks: 0Total objects that have a legacyExchangeDN of ADCDisableMail: 1Total objects that have a legacyExchangeDN of ADCDisableMailByADC: 0
NOTE: The ErrorsOnlyLogging switch can only be used with the proxytest only!
For more information on how to use the proxytest feature in OABInteg please see the following blog: http://blogs.msdn.com/dgoldman/archive/2007/03/08/how-to-use-oabinteg-s-oabfldcheck-and-proxytest-to-find-oab-issues.aspx
Dave