Comments on: How to Document Servers with SYDI – Part 2 of 3 http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/ Security Stories and Help with Network Documentation Thu, 22 Jul 2010 01:25:49 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Marvin http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/comment-page-1/#comment-51991 Marvin Thu, 22 Jul 2010 01:25:49 +0000 http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/#comment-51991 Thank you so much for this tool. Love this program and it just helped me to document all the servers I manage. If I can only have one suggestion or if any users has already done it. When you convert all your raw files to an excel and does the summary of all computers, is it possible to include storage information so in a glance you know status of your storage. Thank you so much for this tool. Love this program and it just helped me to document all the servers I manage. If I can only have one suggestion or if any users has already done it. When you convert all your raw files to an excel and does the summary of all computers, is it possible to include storage information so in a glance you know status of your storage.

]]> By: Carts http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/comment-page-1/#comment-50977 Carts Sun, 21 Feb 2010 21:13:40 +0000 http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/#comment-50977 Fantastic, time saving, standards building, piece of vbscript. I appreciate the work that has gone into this immensely. Cheers Fantastic, time saving, standards building, piece of vbscript. I appreciate the work that has gone into this immensely.

Cheers

]]> By: alan mitchell http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/comment-page-1/#comment-50434 alan mitchell Mon, 11 Jan 2010 16:00:18 +0000 http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/#comment-50434 'file:///C:/Scripts/sydi/log files/serverhtml.xsl' System error: -2146697211. To fix this issue in Sydi. Use the two files inside the xml folder named: serverhtml.xsl sydi-html-styles.xsl Paste them into the Log files folder and now you should be able to open teh .xml files in a browser. Alan Mitchell cooldisks ‘file:///C:/Scripts/sydi/log files/serverhtml.xsl’
System error: -2146697211.

To fix this issue in Sydi. Use the two files inside the xml folder named:
serverhtml.xsl
sydi-html-styles.xsl

Paste them into the Log files folder and now you should be able to open teh .xml files in a browser.

Alan Mitchell
cooldisks

]]> By: bob young http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/comment-page-1/#comment-49425 bob young Tue, 13 Oct 2009 18:36:54 +0000 http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/#comment-49425 I am trying to use Sydi to gather information about my servers and then export it to a text file. I am able to export to XML or Word and convert to HTML but I would like to export to txt. Does anyone have any advise? I am trying to use Sydi to gather information about my servers and then export it to a text file. I am able to export to XML or Word and convert to HTML but I would like to export to txt. Does anyone have any advise?

]]> By: Tony http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/comment-page-1/#comment-49390 Tony Thu, 08 Oct 2009 06:03:42 +0000 http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/#comment-49390 On further investigation, it's the space in the OU it had a problem with, which I thought I would have avoided with the inverted commas. I've got it to work by repositioning the inverted commas like this: <i>cscript sydi-wrapper.vbs -aOU="Citrix Servers",OU=Sydney,DC=blah,DC=local</i> So my syntax was incorrect after all. Thanks! On further investigation, it’s the space in the OU it had a problem with, which I thought I would have avoided with the inverted commas. I’ve got it to work by repositioning the inverted commas like this:
cscript sydi-wrapper.vbs -aOU=”Citrix Servers”,OU=Sydney,DC=blah,DC=local
So my syntax was incorrect after all.

Thanks!

]]> By: Patrick http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/comment-page-1/#comment-49381 Patrick Tue, 06 Oct 2009 16:44:10 +0000 http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/#comment-49381 <strong>Tony</strong> - I don't have any problem running SYDI-Wrapper against sub OUs. Could you make sure you have the latest version and try again? Tony – I don’t have any problem running SYDI-Wrapper against sub OUs. Could you make sure you have the latest version and try again?

]]> By: Tony http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/comment-page-1/#comment-49355 Tony Fri, 02 Oct 2009 01:49:52 +0000 http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/#comment-49355 Thanks for a great tool, Patrick, it's made my life a lot easier! One slight problem I have is that the sydi-wrapper script doesn't seem to handle nested AD OUs. If I run the script as so: cscript sydi-wrapper.vbs -a"OU=Citrix Servers,OU=Sydney,DC=Stark Industries,DC=com" it just shows me the help options, as though my syntax is incorrect. If I run the script as cscript sydi-wrapper.vbs -a"OU=Sydney,DC=Stark Industries,DC=com" it works fine, but that's not where my servers are and so I get no output. :) I've got around the issue by using a text file, but I thought I'd flag it to you in the hopes it's something you can maybe fix in a later build. ;) Thanks for a great tool, Patrick, it’s made my life a lot easier!

One slight problem I have is that the sydi-wrapper script doesn’t seem to handle nested AD OUs. If I run the script as so:
cscript sydi-wrapper.vbs -a”OU=Citrix Servers,OU=Sydney,DC=Stark Industries,DC=com”
it just shows me the help options, as though my syntax is incorrect. If I run the script as
cscript sydi-wrapper.vbs -a”OU=Sydney,DC=Stark Industries,DC=com”
it works fine, but that’s not where my servers are and so I get no output. :)

I’ve got around the issue by using a text file, but I thought I’d flag it to you in the hopes it’s something you can maybe fix in a later build. ;)

]]> By: Randy http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/comment-page-1/#comment-49215 Randy Wed, 16 Sep 2009 14:45:21 +0000 http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/#comment-49215 I found out why the Programs weren't showing up, the WMI Windows Installer Provider wasn't Installed. So that is fixed, still looking for Sugestions to also capture Scheduled Tasks. Thanks! I found out why the Programs weren’t showing up, the WMI Windows Installer Provider wasn’t Installed. So that is fixed, still looking for Sugestions to also capture Scheduled Tasks.

Thanks!

]]> By: Yasir http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/comment-page-1/#comment-47961 Yasir Thu, 04 Jun 2009 08:48:20 +0000 http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/#comment-47961 Hi Patrick, I would like to know if there is any way to build a MySQL/MS Access/MS SQL database directly from the sydi-wrapper.vbs reports. Thanks Yasir Hi Patrick,
I would like to know if there is any way to build a MySQL/MS Access/MS SQL database directly from the sydi-wrapper.vbs reports.

Thanks
Yasir

]]> By: Patrick Ogenstad http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/comment-page-1/#comment-47006 Patrick Ogenstad Tue, 05 May 2009 18:00:55 +0000 http://ogenstad.net/2006/10/18/how-to-document-servers-with-sydi-part-2-of-3/#comment-47006 Jack - I agree, a diff option would be good. I might also take a look at that when I have time. Rafael - You might also have to edit the log directory. If you're unable to connect try using -uDOMAIN\user. Another option is to use runas.exe. Jack – I agree, a diff option would be good. I might also take a look at that when I have time.

Rafael – You might also have to edit the log directory. If you’re unable to connect try using -uDOMAIN\user. Another option is to use runas.exe.

]]>