From: Petter Reinholdtsen
First, install a combined Main Server and Thin Client Server as the central server in the network. Next, PXE boot all the client machines as thin clients and wait 5 minutes after the last client booted to -allow the clients report their existence to the central server. When +allow the clients to report their existence to the central server. When this is done, log on to the central server and run sitesummary2ldapdhcp in the konsole to use the collected information to generate system objects in LDAP. The output diff --git a/blog/archive/2012/01/01.rss b/blog/archive/2012/01/01.rss index 49eaafcecb..282d441f71 100644 --- a/blog/archive/2012/01/01.rss +++ b/blog/archive/2012/01/01.rss @@ -226,7 +226,7 @@ summary on how to use it to set up a new school.</p> <p>First, install a combined Main Server and Thin Client Server as the central server in the network. Next, PXE boot all the client machines as thin clients and wait 5 minutes after the last client booted to -allow the clients report their existence to the central server. When +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 collected information to generate system objects in LDAP. The output diff --git a/blog/archive/2012/01/index.html b/blog/archive/2012/01/index.html index 05b0961b9f..b44c6aeca6 100644 --- a/blog/archive/2012/01/index.html +++ b/blog/archive/2012/01/index.html @@ -292,7 +292,7 @@ summary on how to use it to set up a new school.
First, install a combined Main Server and Thin Client Server as the central server in the network. Next, PXE boot all the client machines as thin clients and wait 5 minutes after the last client booted to -allow the clients report their existence to the central server. When +allow the clients to report their existence to the central server. When this is done, log on to the central server and run sitesummary2ldapdhcp in the konsole to use the collected information to generate system objects in LDAP. The output diff --git a/blog/index.html b/blog/index.html index 1bdf419cf2..5c6a5d590e 100644 --- a/blog/index.html +++ b/blog/index.html @@ -31,7 +31,7 @@ summary on how to use it to set up a new school.
First, install a combined Main Server and Thin Client Server as the central server in the network. Next, PXE boot all the client machines as thin clients and wait 5 minutes after the last client booted to -allow the clients report their existence to the central server. When +allow the clients to report their existence to the central server. When this is done, log on to the central server and run sitesummary2ldapdhcp in the konsole to use the collected information to generate system objects in LDAP. The output diff --git a/blog/index.rss b/blog/index.rss index b1ddc640b2..06baf54cab 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -20,7 +20,7 @@ summary on how to use it to set up a new school.</p> <p>First, install a combined Main Server and Thin Client Server as the central server in the network. Next, PXE boot all the client machines as thin clients and wait 5 minutes after the last client booted to -allow the clients report their existence to the central server. When +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 collected information to generate system objects in LDAP. The output diff --git a/blog/tags/debian edu/debian edu.rss b/blog/tags/debian edu/debian edu.rss index ecfe2e037b..2189673c06 100644 --- a/blog/tags/debian edu/debian edu.rss +++ b/blog/tags/debian edu/debian edu.rss @@ -5469,7 +5469,7 @@ summary on how to use it to set up a new school.</p> <p>First, install a combined Main Server and Thin Client Server as the central server in the network. Next, PXE boot all the client machines as thin clients and wait 5 minutes after the last client booted to -allow the clients report their existence to the central server. When +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 collected information to generate system objects in LDAP. The output diff --git a/blog/tags/debian edu/index.html b/blog/tags/debian edu/index.html index e299504204..1d9012108d 100644 --- a/blog/tags/debian edu/index.html +++ b/blog/tags/debian edu/index.html @@ -6302,7 +6302,7 @@ summary on how to use it to set up a new school.
First, install a combined Main Server and Thin Client Server as the central server in the network. Next, PXE boot all the client machines as thin clients and wait 5 minutes after the last client booted to -allow the clients report their existence to the central server. When +allow the clients to report their existence to the central server. When this is done, log on to the central server and run sitesummary2ldapdhcp in the konsole to use the collected information to generate system objects in LDAP. The output diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss index a4ff0ee12e..4bb4013d2f 100644 --- a/blog/tags/english/english.rss +++ b/blog/tags/english/english.rss @@ -6790,7 +6790,7 @@ summary on how to use it to set up a new school.</p> <p>First, install a combined Main Server and Thin Client Server as the central server in the network. Next, PXE boot all the client machines as thin clients and wait 5 minutes after the last client booted to -allow the clients report their existence to the central server. When +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 collected information to generate system objects in LDAP. The output diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html index b8558d15ef..2ff7bd2bf3 100644 --- a/blog/tags/english/index.html +++ b/blog/tags/english/index.html @@ -8019,7 +8019,7 @@ summary on how to use it to set up a new school.
First, install a combined Main Server and Thin Client Server as the central server in the network. Next, PXE boot all the client machines as thin clients and wait 5 minutes after the last client booted to -allow the clients report their existence to the central server. When +allow the clients to report their existence to the central server. When this is done, log on to the central server and run sitesummary2ldapdhcp in the konsole to use the collected information to generate system objects in LDAP. The output diff --git a/blog/tags/sitesummary/index.html b/blog/tags/sitesummary/index.html index 49b7e1112e..6997034674 100644 --- a/blog/tags/sitesummary/index.html +++ b/blog/tags/sitesummary/index.html @@ -199,7 +199,7 @@ summary on how to use it to set up a new school.
First, install a combined Main Server and Thin Client Server as the central server in the network. Next, PXE boot all the client machines as thin clients and wait 5 minutes after the last client booted to -allow the clients report their existence to the central server. When +allow the clients to report their existence to the central server. When this is done, log on to the central server and run sitesummary2ldapdhcp in the konsole to use the collected information to generate system objects in LDAP. The output diff --git a/blog/tags/sitesummary/sitesummary.rss b/blog/tags/sitesummary/sitesummary.rss index 0c7ef69353..59cde7f91a 100644 --- a/blog/tags/sitesummary/sitesummary.rss +++ b/blog/tags/sitesummary/sitesummary.rss @@ -146,7 +146,7 @@ summary on how to use it to set up a new school.</p> <p>First, install a combined Main Server and Thin Client Server as the central server in the network. Next, PXE boot all the client machines as thin clients and wait 5 minutes after the last client booted to -allow the clients report their existence to the central server. When +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 collected information to generate system objects in LDAP. The output diff --git a/blog/tags/standard/index.html b/blog/tags/standard/index.html index 6d4e26a034..8175ebc009 100644 --- a/blog/tags/standard/index.html +++ b/blog/tags/standard/index.html @@ -1909,7 +1909,7 @@ provided by external plugins like the Flash plugins.