as thin clients and wait 5 minutes after the last client booted to
allow the clients to report their existence to the central server. When
this is done, log on to the central server and run
-<tt>sitesummary2ldapdhcp</tt> in the <tt>konsole</tt> to use the
+<tt>sitesummary2ldapdhcp -a</tt> in the <tt>konsole</tt> to use the
collected information to generate system objects in LDAP. The output
will look similar to this:</p>
<p><blockquote><pre>
-% sitesummary2ldapdhcp
+% sitesummary2ldapdhcp -a
info: Updating machine tjener.intern [10.0.2.2] id ether-00:01:02:03:04:05.
info: Create GOsa machine for auto-mac-00-01-02-03-04-06 [10.0.16.20] id ether-00:01:02:03:04:06.
<p>We plan to release beta3 with the updated version of this feature
enabled this weekend. You might want to give it a try.</p>
+
+<p>Update 2012-01-28: When calling sitesummary2ldapdhcp to add new
+hosts, one need to add the option -a. I forgot to mention this in my
+original text, and have added it to the text now.</p>
</div>
<div class="tags">Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary</a>.</div>
as thin clients and wait 5 minutes after the last client booted to
allow the clients to report their existence to the central server. When
this is done, log on to the central server and run
-<tt>sitesummary2ldapdhcp</tt> in the <tt>konsole</tt> to use the
+<tt>sitesummary2ldapdhcp -a</tt> in the <tt>konsole</tt> to use the
collected information to generate system objects in LDAP. The output
will look similar to this:</p>
<p><blockquote><pre>
-% sitesummary2ldapdhcp
+% sitesummary2ldapdhcp -a
info: Updating machine tjener.intern [10.0.2.2] id ether-00:01:02:03:04:05.
info: Create GOsa machine for auto-mac-00-01-02-03-04-06 [10.0.16.20] id ether-00:01:02:03:04:06.
<p>We plan to release beta3 with the updated version of this feature
enabled this weekend. You might want to give it a try.</p>
+
+<p>Update 2012-01-28: When calling sitesummary2ldapdhcp to add new
+hosts, one need to add the option -a. I forgot to mention this in my
+original text, and have added it to the text now.</p>
</description>
</item>
as thin clients and wait 5 minutes after the last client booted to
allow the clients to report their existence to the central server. When
this is done, log on to the central server and run
-<tt>sitesummary2ldapdhcp</tt> in the <tt>konsole</tt> to use the
+<tt>sitesummary2ldapdhcp -a</tt> in the <tt>konsole</tt> to use the
collected information to generate system objects in LDAP. The output
will look similar to this:</p>
<p><blockquote><pre>
-% sitesummary2ldapdhcp
+% sitesummary2ldapdhcp -a
info: Updating machine tjener.intern [10.0.2.2] id ether-00:01:02:03:04:05.
info: Create GOsa machine for auto-mac-00-01-02-03-04-06 [10.0.16.20] id ether-00:01:02:03:04:06.
<p>We plan to release beta3 with the updated version of this feature
enabled this weekend. You might want to give it a try.</p>
+<p>Update 2012-01-28: When calling sitesummary2ldapdhcp to add new
+hosts, one need to add the option -a. I forgot to mention this in my
+original text, and have added it to the text now.</p>
+
</div>
<div class="tags">
as thin clients and wait 5 minutes after the last client booted to
allow the clients to report their existence to the central server. When
this is done, log on to the central server and run
-<tt>sitesummary2ldapdhcp</tt> in the <tt>konsole</tt> to use the
+<tt>sitesummary2ldapdhcp -a</tt> in the <tt>konsole</tt> to use the
collected information to generate system objects in LDAP. The output
will look similar to this:</p>
<p><blockquote><pre>
-% sitesummary2ldapdhcp
+% sitesummary2ldapdhcp -a
info: Updating machine tjener.intern [10.0.2.2] id ether-00:01:02:03:04:05.
info: Create GOsa machine for auto-mac-00-01-02-03-04-06 [10.0.16.20] id ether-00:01:02:03:04:06.
<p>We plan to release beta3 with the updated version of this feature
enabled this weekend. You might want to give it a try.</p>
+
+<p>Update 2012-01-28: When calling sitesummary2ldapdhcp to add new
+hosts, one need to add the option -a. I forgot to mention this in my
+original text, and have added it to the text now.</p>
</div>
<div class="tags">
as thin clients and wait 5 minutes after the last client booted to
allow the clients to report their existence to the central server. When
this is done, log on to the central server and run
-<tt>sitesummary2ldapdhcp</tt> in the <tt>konsole</tt> to use the
+<tt>sitesummary2ldapdhcp -a</tt> in the <tt>konsole</tt> to use the
collected information to generate system objects in LDAP. The output
will look similar to this:</p>
<p><blockquote><pre>
-% sitesummary2ldapdhcp
+% sitesummary2ldapdhcp -a
info: Updating machine tjener.intern [10.0.2.2] id ether-00:01:02:03:04:05.
info: Create GOsa machine for auto-mac-00-01-02-03-04-06 [10.0.16.20] id ether-00:01:02:03:04:06.
<p>We plan to release beta3 with the updated version of this feature
enabled this weekend. You might want to give it a try.</p>
+
+<p>Update 2012-01-28: When calling sitesummary2ldapdhcp to add new
+hosts, one need to add the option -a. I forgot to mention this in my
+original text, and have added it to the text now.</p>
</description>
</item>
as thin clients and wait 5 minutes after the last client booted to
allow the clients to report their existence to the central server. When
this is done, log on to the central server and run
-<tt>sitesummary2ldapdhcp</tt> in the <tt>konsole</tt> to use the
+<tt>sitesummary2ldapdhcp -a</tt> in the <tt>konsole</tt> to use the
collected information to generate system objects in LDAP. The output
will look similar to this:</p>
<p><blockquote><pre>
-% sitesummary2ldapdhcp
+% sitesummary2ldapdhcp -a
info: Updating machine tjener.intern [10.0.2.2] id ether-00:01:02:03:04:05.
info: Create GOsa machine for auto-mac-00-01-02-03-04-06 [10.0.16.20] id ether-00:01:02:03:04:06.
<p>We plan to release beta3 with the updated version of this feature
enabled this weekend. You might want to give it a try.</p>
+
+<p>Update 2012-01-28: When calling sitesummary2ldapdhcp to add new
+hosts, one need to add the option -a. I forgot to mention this in my
+original text, and have added it to the text now.</p>
</description>
</item>
as thin clients and wait 5 minutes after the last client booted to
allow the clients to report their existence to the central server. When
this is done, log on to the central server and run
-<tt>sitesummary2ldapdhcp</tt> in the <tt>konsole</tt> to use the
+<tt>sitesummary2ldapdhcp -a</tt> in the <tt>konsole</tt> to use the
collected information to generate system objects in LDAP. The output
will look similar to this:</p>
<p><blockquote><pre>
-% sitesummary2ldapdhcp
+% sitesummary2ldapdhcp -a
info: Updating machine tjener.intern [10.0.2.2] id ether-00:01:02:03:04:05.
info: Create GOsa machine for auto-mac-00-01-02-03-04-06 [10.0.16.20] id ether-00:01:02:03:04:06.
<p>We plan to release beta3 with the updated version of this feature
enabled this weekend. You might want to give it a try.</p>
+<p>Update 2012-01-28: When calling sitesummary2ldapdhcp to add new
+hosts, one need to add the option -a. I forgot to mention this in my
+original text, and have added it to the text now.</p>
+
</div>
<div class="tags">
as thin clients and wait 5 minutes after the last client booted to
allow the clients to report their existence to the central server. When
this is done, log on to the central server and run
-<tt>sitesummary2ldapdhcp</tt> in the <tt>konsole</tt> to use the
+<tt>sitesummary2ldapdhcp -a</tt> in the <tt>konsole</tt> to use the
collected information to generate system objects in LDAP. The output
will look similar to this:</p>
<p><blockquote><pre>
-% sitesummary2ldapdhcp
+% sitesummary2ldapdhcp -a
info: Updating machine tjener.intern [10.0.2.2] id ether-00:01:02:03:04:05.
info: Create GOsa machine for auto-mac-00-01-02-03-04-06 [10.0.16.20] id ether-00:01:02:03:04:06.
<p>We plan to release beta3 with the updated version of this feature
enabled this weekend. You might want to give it a try.</p>
+
+<p>Update 2012-01-28: When calling sitesummary2ldapdhcp to add new
+hosts, one need to add the option -a. I forgot to mention this in my
+original text, and have added it to the text now.</p>
</description>
</item>
as thin clients and wait 5 minutes after the last client booted to
allow the clients to report their existence to the central server. When
this is done, log on to the central server and run
-<tt>sitesummary2ldapdhcp</tt> in the <tt>konsole</tt> to use the
+<tt>sitesummary2ldapdhcp -a</tt> in the <tt>konsole</tt> to use the
collected information to generate system objects in LDAP. The output
will look similar to this:</p>
<p><blockquote><pre>
-% sitesummary2ldapdhcp
+% sitesummary2ldapdhcp -a
info: Updating machine tjener.intern [10.0.2.2] id ether-00:01:02:03:04:05.
info: Create GOsa machine for auto-mac-00-01-02-03-04-06 [10.0.16.20] id ether-00:01:02:03:04:06.
<p>We plan to release beta3 with the updated version of this feature
enabled this weekend. You might want to give it a try.</p>
+<p>Update 2012-01-28: When calling sitesummary2ldapdhcp to add new
+hosts, one need to add the option -a. I forgot to mention this in my
+original text, and have added it to the text now.</p>
+
</div>
<div class="tags">
as thin clients and wait 5 minutes after the last client booted to
allow the clients to report their existence to the central server. When
this is done, log on to the central server and run
-<tt>sitesummary2ldapdhcp</tt> in the <tt>konsole</tt> to use the
+<tt>sitesummary2ldapdhcp -a</tt> in the <tt>konsole</tt> to use the
collected information to generate system objects in LDAP. The output
will look similar to this:</p>
<p><blockquote><pre>
-% sitesummary2ldapdhcp
+% sitesummary2ldapdhcp -a
info: Updating machine tjener.intern [10.0.2.2] id ether-00:01:02:03:04:05.
info: Create GOsa machine for auto-mac-00-01-02-03-04-06 [10.0.16.20] id ether-00:01:02:03:04:06.
<p>We plan to release beta3 with the updated version of this feature
enabled this weekend. You might want to give it a try.</p>
+<p>Update 2012-01-28: When calling sitesummary2ldapdhcp to add new
+hosts, one need to add the option -a. I forgot to mention this in my
+original text, and have added it to the text now.</p>
+
</div>
<div class="tags">
as thin clients and wait 5 minutes after the last client booted to
allow the clients to report their existence to the central server. When
this is done, log on to the central server and run
-<tt>sitesummary2ldapdhcp</tt> in the <tt>konsole</tt> to use the
+<tt>sitesummary2ldapdhcp -a</tt> in the <tt>konsole</tt> to use the
collected information to generate system objects in LDAP. The output
will look similar to this:</p>
<p><blockquote><pre>
-% sitesummary2ldapdhcp
+% sitesummary2ldapdhcp -a
info: Updating machine tjener.intern [10.0.2.2] id ether-00:01:02:03:04:05.
info: Create GOsa machine for auto-mac-00-01-02-03-04-06 [10.0.16.20] id ether-00:01:02:03:04:06.
<p>We plan to release beta3 with the updated version of this feature
enabled this weekend. You might want to give it a try.</p>
+
+<p>Update 2012-01-28: When calling sitesummary2ldapdhcp to add new
+hosts, one need to add the option -a. I forgot to mention this in my
+original text, and have added it to the text now.</p>
</description>
</item>