Having written SYDI from scratch, I know it inside and out. Unfortunately I don’t think I’ve managed to communicate how SYDI works in an efficient way. The readme file included in SYDI is far from perfect. While people in this line of business can usually figure out how it works, others will just ignore reading the manual anyway. In this how-to I will go through the basics of how SYDI-Server works and then describe how I use SYDI-Server.<\/p>\n
Getting the Software<\/strong><\/p>\n You probably have the software already, but just in case. Download it from the SYDI website<\/a>, or if you love this site and don’t want to leave it no matter what: you can download it from here<\/a>. This guide is written for SYDI-Server 2.0, if there is a newer version when you read this, don’t worry; it should be useful anyway. Just be sure to check the changelog.txt file for new features.<\/p>\n Unzip the file to your target directory.<\/p>\n Running SYDI in default mode<\/strong><\/p>\n To see what the software does, open a command prompt and navigate to your sydi directory. This step requires you to have Microsoft Word installed on your computer. Type the command:<\/p>\n cscript.exe sydi-server.vbs [enter]<\/p>\n A message box appears and asks you which host you want to target, the default is localhost. You can select another host if you have administrative access on that machine. Though for now, just press enter.<\/p>\n In the command prompt window you will now see that SYDI starts to gather information about your machine. Soon a Word document is created and SYDI writes the information gathered into the document.<\/p>\n Take a look at the document. Not all this information will be relevant to you and you can remove the parts you don’t want by reading further. Close Word, or save the file it if you want to.<\/p>\n The Options<\/strong><\/p>\n To view the available options use the help command (-h):<\/p>\n cscript.exe sydi-server.vbs -h [enter]<\/p>\n Options in five categories will be listed; Gathering, Output, Word, XML and Other. In reality there are only two, Gathering and Output.<\/p>\n Gathering the Information<\/strong><\/p>\n Breaking down the gathering option we have five different arguments -w for WMI options, -r for Registry options and -u and -p for username and password if you want to connect to a different user. Finally we have the -t option where you specify which host you want to target against.<\/p>\n Looking closer at the -w argument from the help menu (-h) you could see that SYDI defaults to using -wabefghipPqrsSu, meaning everything gathered from the WMI providers will be included.<\/p>\n You cannot remove everything from the report, but let’s create a document without all the extra information. Run:<\/p>\n cscript.exe sydi-server.vbs -w [enter]<\/p>\n As you can see the report created is much shorter than the previous one. We have removed the optional WMI providers, but we still have the basic ones and the information coming from the Registry.<\/p>\n To choose which options you want, just check the help menu and see what they mean. If we want to add Bios Information, Printers and Services we would run:<\/p>\n cscript.exe sydi-server.vbs -wbps [enter]<\/p>\n This way you can pick and choose the options you want. The Registry switch works the same way. For an even smaller report you can run:<\/p>\n cscript.exe sydi-server.vbs -w -r [enter]<\/p>\n Now you can add the registry options that you want. Please note though that a lot of the “Computer Roles” are gathered from the Windows Components, so if you want these roles you must have the Windows Components in your report (-rc).<\/p>\n Using the -t option removes the message box asking you which host you want to target. A few examples of using the -t switch:<\/p>\n cscript.exe sydi-server.vbs -tServer1 The user and password options should work as you would expect them to, if they don’t: report the bug to me \ud83d\ude42<\/p>\n Word Options<\/strong><\/p>\n As you’ve seen, sydi-server defaults to writing output to Word. The reason for this is so that you can get a quick overview of what the script can collect without having to do any tricks. Having said that, I only use the Word option to get a quick view of a machine, later I throw away the document. I always use the XML format which I later convert to a Word document, more on that later. Even though you won’t use the Word options much we’ll just take a quick look at them to see what you can do, it won’t be a total waste as a few of the options are used by another script called ss-xml2word.vbs.<\/p>\n -b is for the border of the tables created in the document. As you might have noticed there isn’t any borders by default (when you print the document). You can use all borders you have installed in Word. To test it, type:<\/p>\n cscript.exe sydi-server.vbs -b”Table Contemporary” [enter]<\/p>\n -f is if you want different font sizes, the default font size for the text is 12. To change it, use:<\/p>\n cscript.exe sydi-server.vbs -f8<\/p>\n -d tells SYDI not to display Word until the entire report is written. Using the -d option makes the process go faster. Also if you want to save the file (-o option, more on that later), you might not want to see Word at all. For example if you are running a scheduled task you don’t want a GUI to be loaded.<\/p>\n -n will remove all the text inside the brackets, such as “Logical location: [provide info: Server VLAN 2]”. This way you won’t have a bad conscience about not completing the documentation. \ud83d\ude42 But as I have already stated, the whole idea of sydi-server writing directly to word is obsolete. If you start changing the document after it is created and want to run SYDI again your changes will be lost, or you will have to cut and paste them to the new document. There is a way around this though (hint: continue reading!).<\/p>\n -T This is if you want to specify a corporate Word Template file (.dot), which enables you to choose which fonts you want to have as well as their size. This way you can get your “look and feel” in the document.<\/p>\n Read Part 2<\/a> [tags]network documentation, server documentation, sydi, how to, tutorial[\/tags]<\/p>\n","protected":false},"excerpt":{"rendered":" Having written SYDI from scratch, I know it inside and out. Unfortunately I don’t think I’ve managed to communicate how SYDI works in an efficient way. The readme file included in SYDI is far from perfect. While people in this line of business can usually figure out how it works, others will just ignore reading […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":""},"categories":[4],"tags":[],"_links":{"self":[{"href":"http:\/\/ogenstad.net\/wp-json\/wp\/v2\/posts\/66"}],"collection":[{"href":"http:\/\/ogenstad.net\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/ogenstad.net\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/ogenstad.net\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/ogenstad.net\/wp-json\/wp\/v2\/comments?post=66"}],"version-history":[{"count":0,"href":"http:\/\/ogenstad.net\/wp-json\/wp\/v2\/posts\/66\/revisions"}],"wp:attachment":[{"href":"http:\/\/ogenstad.net\/wp-json\/wp\/v2\/media?parent=66"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/ogenstad.net\/wp-json\/wp\/v2\/categories?post=66"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/ogenstad.net\/wp-json\/wp\/v2\/tags?post=66"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\ncscript.exe sydi-server.vbs -tDC1
\ncscript.exe sydi-server.vbs -tWebServer
\ncscript.exe sydi-server.vbs -t192.168.0.10<\/p>\n
\n Read Part 3<\/a><\/p>\n