Warning: Constant ABSPATH already defined in /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php on line 24 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 {"id":135,"date":"2008-12-02T20:11:03","date_gmt":"2008-12-02T19:11:03","guid":{"rendered":"http:\/\/ogenstad.net\/?p=135"},"modified":"2008-12-02T20:11:03","modified_gmt":"2008-12-02T19:11:03","slug":"sydi-server-22-released","status":"publish","type":"post","link":"https:\/\/ogenstad.net\/2008\/12\/02\/sydi-server-22-released\/","title":{"rendered":"SYDI-Server 2.2 Released"},"content":{"rendered":"
Yesterday I released version 2.2 of my network documentation tool<\/a>, SYDI-Server. The new package contains some small fixes, but also a script which lets you audit local group memberships<\/a> in all your computers. That is local machine specific groups, not domain local groups. I’ve also launched a network documentation newsletter<\/a> for SYDI. This will be my main information channel for SYDI and my writings about network documentation. According to many of its users SYDI is a great tool. I would say it’s a great tool for doing mundane tasks i.e. collecting and presenting information. What I’m saying is that you don’t really need the sydi-server script, it’s just that if you use it you spend 2 minutes compared to several hours. However there’s much more to network documentation than the data collected from sydi-server.<\/p>\n If you like SYDI and want to improve your network documentation be sure to sign up, the newsletter is as free as SYDI.<\/p>\n Though before you sign up you might want to grab the latest sydi-server<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" Yesterday I released version 2.2 of my network documentation tool<\/a>, SYDI-Server. The new package contains some small fixes, but also a script which lets you audit local group memberships<\/a> in all your computers. That is local machine specific groups, not domain local groups.<\/p>\n So what you’ll be able to do is to track down all your users running as local administrators, or just find strange groups which shouldn’t appear in your organization.<\/p>\n
\n
\nSo what you’ll be able to do is to track down all your users running as local administrators, or just find strange groups which shouldn’t appear in your organization.<\/p>\n