So the SYDI project is coming of age and will be moving to its own domain. I haven’t launched the site yet but it should be out soon.
My plan is to use Drupal 5 when it is released, which I hope is very soon.
If there is anything you would like to see on the new website please let me know.
The new link to SYDI will be http://SYDIproject.com. Initially the content of the site will match the current one but I have plans to publish more information so hopefully you’ll find the new site more useful.
A few days ago the download counters for SYDI went passed 50 000! Although it’s great to see that so many are using the scripts what I like best about the project is when I receive feedback from you. If you have anything to say about SYDI good or bad just tell me.
[tags]sydi, network documentation, move, drupal[/tags]
Thanks for all of your hard work. It is greatly appreciated and highly useful.
Patrick,
First off, let me say, I am very pleased with what you have enabled us to accomplish using SYDI as a jumping off point for getting our documentation standardized between our customers.
I have written a few batch programs that have enabled a simplified use of the product that calls the servers you want to document from a text file and also includes a way to enter the username, domain name, password etc in the startup script and that is passed to the VB scripts as necessary.
Not that what I did using your code is impressive, I am no programmer just an AD / Exchange admin who hacks at batch and vb occasionally to accomplish some specific task which bring me to my next point.
It has been a long time since we’ve seen an update to SYDI. I have tried in vein to duplicate what you were able to accomplish with Exchange 2003, but alas, my skills are not up to par and I am having a bit of trouble trying to get information out of Exchange 2007. It seems that early in the code you call to AD to find the location of the Information store. Well, in EX2K7, an information store in not mandatory so the script end with a failure that the object does nto exist. I overcame this by using a move.last rather than the move.next and in this case, the EX 2K7 server was the last in the list but I am sure you see the problem on a larger scale.
Likewise, EX 2K7 does NOT use WMI calls. Alas, the information one is able to gleen from the registry or through WMI for Exchagne is limited for Exchange 2K7 configurations. (All data is stored in AD now). Add to that teh complication of documenting a 2K3/2K7 hybrid enviornment. Yea, it is starting to get ugly.
I have looked on the interenet for a prodcut to buy but I am just not finding anything that does as good a job for post-installation documentation as SYDI does.
Any chance we could work together to release an Exchange 2007 documentation script? Think of it, The world will be needing an updated SYDI to work with 2008 server, SQL 2008, EX2007 and with Visual Studio 2008 released, native XML generation is imbeded in .net 3.5 so… It could be fun!!
Warmest Regards,
DJ Dennis