Ogenstad.net

Security Stories and Help with Network Documentation

Once upon a time this used to be my blog. For current updates head over to Networklore.

About / Stories / Contact

  • GitHub
  • LinkedIn
  • RSS
  • Twitter

Powered by Genesis

SYDI Articles and Network Documentation Guides

February 28, 2007 by patrick.ogenstad

As I said a while ago I moved SYDI, my network documentation project, to a new domain. Now I’m beginning to add information about SYDI and network documentation in general. The first article is under the best practices section and is titled How to use SYDI Server with Login Scripts.

If you have any requests, please let me know.

Regarding my stories I am going to write more of them and the next installment of The Broken NDA is coming, sorry for the delay!

[tags]sydi,network documentation[/tags]

Filed Under: SYDI

Comments

  1. Scooter says

    April 18, 2007 at 4:01 am

    I was wondering if there are any options to document using sydi by using IP ranges instead of domains or active directory.

  2. Athif says

    May 1, 2007 at 1:43 pm

    Hi,

    Many thanks for the great script.

    On my server, I have installed Microsoft WORD VIEWER and ran the SYDI-SERVER.vbs script and it throws the following error;

    Start subroutine: PopulateWordfile()
    429 — ActiveX component can’t create object (.)
    Could not open Microsoft Word, verify that it is correctly installed on the computer you are scanning from.

    Is this a limitation? As a policy, I can’t install MS Word on the web server – I can only install WORD VIEWER.

    Please advice. I will be glad if the script can work with word viewer or atleast if the script can save the result to a .doc file which I can copy to my workstation and open it.

    Thanks again.
    Athif – http://www.msmvps.com/athif

  3. Patrick Ogenstad says

    May 2, 2007 at 7:33 pm

    Scooter: No, however if you list all the ip addresses in a textfile you can run SYDI-Wrapper against that textfile and the result will be the same.

    Athif: If you are using the Word output you have to have Word installed on the computer you are running the script from. However you can also write output to an XML file and convert it to a Word document with ss-xml2word.vbs. Check the guide here; How to use SYDI-Server.

  4. Mats Larsson says

    May 11, 2007 at 10:18 am

    Hi !
    This is realy a great script.

    I like to convert my xml file to Swedish but I ran into problems

    C:\sydi\tools\ss-xml2word.vbs(1249, 3) Microsoft VBScript runtime error: Type mismatch: ‘oWord.Selection.TypeText’

    I have specifed the path to all files and tried different things

  5. Patrick Ogenstad says

    May 11, 2007 at 3:37 pm

    Mats: This might be a bug in SYDI but I would still guess it is related to paths (I have to include some more error handling in the next version).

    Could you describe how you run ss-xml2word, ie the parameters you use and where the files reside?

  6. Patrik says

    June 21, 2007 at 9:30 am

    Make a startupscript that echoes the computername/ipadress to a textfile in a shared folder.

    Then use wrapper to schedule a job that checks the if the file exists and then moves it, scans the computers in it and then delete the file.

    Have been using this for a year now and it works perfect. Only computers that recently have been restarted are scanned and the user don´t see any delays.

  7. Michael Capozzi says

    February 21, 2008 at 8:36 pm

    I get the following error when running sydi-wrapper.vbs.

    C:\sydi\tools>cscript sydi-wrapper.vbs -tc:\sydi\tools\computers.txt
    Microsoft (R) Windows Script Host Version 5.7
    Copyright (C) Microsoft Corporation. All rights reserved.

    C:\sydi\tools\sydi-wrapper.vbs(117, 2) Microsoft VBScript runtime error: ActiveX
    component can’t create object: ‘Scripting.FileSystemObject’

  8. korre says

    June 5, 2009 at 12:26 pm

    I generated local xml files on two servers,
    then afterwords I used my local Windows 7 w/ Office 2007 box to convert xml to doc:
    1) Server 2003 – conversion fr xml to doc worked file
    2) Small Business Server 2008 – conversion to doc failed:

    Reading SYDI-Server Source File: SBS-sydioutput.xml
    Reading Written Documentation:

    Creating new document
    Opening Empty document
    Setting styles
    Reading Language File: lang_english.xml
    Inserting Table Of Contents
    Writing Section: System Information
    Writing Section: Hardware Platform
    Writing Sub-Section: General Information
    Writing Section: Software Platform
    Writing Sub-Section: General Information
    Writing Section: Storage
    Writing Sub-Section: General Information
    Writing Section: Network Configuration
    Writing Sub-Section: IP Configuration
    Writing Section: Miscellaneous Configuration
    C:\Users\Jaan\Desktop\Sydi-project\Sydi-files\sydi-server-2.3\ss-xml2word.vbs(1281, 3) Microsoft VBScript runtime error: Type mismatch: ‘oWord.Selection.TypeText’

  9. Patrick says

    August 12, 2009 at 8:17 pm

    korre Make sure the xml file is a valid xml file. Can you open it with Internet Explorer?

  10. Dilson Fernandes says

    May 2, 2011 at 6:23 pm

    Hi,
    I´m a problemam witch sydi-server-2.3 script.
    Win 7 and XP, Office 2003 and 2007

    I´m return erro:
    C:\sydi-server-2.3\tools\ss-xml2word.vbs(1281, 3) Microsoft VBScript Erro de tempo de execução do Microsoft VBScript: Tipos incompatíveis: ‘oWord.Selection.TypeText’

    I need that script for iventory my workstations.
    Please, contact-me !!!

  11. Vali says

    December 20, 2011 at 3:35 pm

    Hello,
    I have a problem, since Microsoft Word is not installed on our servers and I’d like to run the sydiscript using a pocket USB version of MS Word. How can I use this? I don’t want to use the XML option. Is it possible to run the Word application from an USB stick to create the Sydi server documentation?
    For example the Wordfile is on U:\Wordpocket\Winword.exe.

    regards,

    Valiant

  12. Sten says

    February 13, 2013 at 11:13 pm

    I am getting an error when running sydi-server version 2.3 on a Windows Server 2003 R2 system. The script errors out (2663, 3) VBScript runtime error: object required: ‘objDbrWindowsComponents’. This is occuring in the populatexmlfile sub-routine. I notice a warning in the script before this that Win32_Product class is not installed; I am not sure if this is related, just adding as much information as possible. Because of change control restrictions and the way I am forced to access this system (local administrator), I cannot install anything, nor do I believe that I can run the script from another server that has Word installed.

    Great product. This is the first issue I have run into having “documented” around 80 Windows servers before.

  13. Peter says

    June 13, 2019 at 12:06 pm

    hi, when I run sydi it only outputs the sub contents under table of contents, is there any way of getting it to produce the main contents along with sub contents.
    my table of contents all start with 2.1 general information instead of stating at
    1. System summary
    2. Hardware Platform
    2.1 General information