Updates UCS chapter

manuals/en/main/operating-system-univention-corporate-server.tex

@@ -78,7 +78,7 @@ \subsubsection{UCR variables}
 UCR variables can be set via the Univention Configuration Registry Web interface 
 
 \begin{center}
-  \includegraphics[width=0.8\textwidth]{\idir univention-configuration-registry-settings}
+  \includegraphics[width=1.0\textwidth]{\idir univention-configuration-registry-settings}
 \end{center}
 
 or using the \command{ucr} command line tool:
@@ -95,8 +95,6 @@ \subsubsection{UCR variables}
 [ ok ] Reloading Bareos Director: bareos-dir.
 \end{commands}
 
-
-
 \subsubsection{Setup}
 
 After installation of the Bareos app, Bareos is ready for operation. A default configuration is created automatically.
@@ -204,17 +202,27 @@ \subsubsection{Backup Storage}
 
 
 \subsubsection{Client and backup job management}
-\paragraph{Add a client to the backup setup}$\;$
+
+\paragraph{Add a client to backup on your Domaincontroller master}$\;$
 
 The univention Bareos application comes with an automatism for the client and job configuration. If you want to add a client to the Bareos director configuration, you need to set the checkbox to true, as you can see in the screenshot below.
 
 \begin{center}
-  \includegraphics[width=0.60\textwidth]{\idir bareos-univention}
+  \includegraphics[width=0.8\textwidth]{\idir univention-client-job-activation}
 \end{center}
 
-After having enabled the Bareos backup for a client, it will be configured automatically and loaded into the configuration. Therefore Bareos comes with a special cronjob called \command{univention-bareos}, which performs a restart every day at 20:30 o'clock (Remember: backups will be started at 21:00 o'clock!).
+After having enabled the Bareos backup for a client on your Domaincontroller master, where usually your director- and storage-daemon are running, it will be configured automatically and loaded into the bareos-director configuration. Therefore Bareos comes with a special cronjob called \command{univention-bareos}, which performs a restart every day at 20:30 o'clock (Remember: backups will be started at 21:00 o'clock!). That said, if you add a client to backup, a Client Resource and a Job Resource in e.g. \file{/etc/bareos/autogenerated/clients/testw1.example.com.include} will be generated and included via \file{/etc/bareos/autogenerated/clients.include} to make your new client known to the Director.
+
+\paragraph{Install and initial configuration of a client}$\;$
+
+Even if the corresponding client configuration for the file daemon is generated automatically on your Domaincontroller master as mentioned above, it needs to be copied manually to the client e.g. via scp. The generated client configuration is located under \file{/etc/bareos/autogenerated/fd-configs/testw1.example.com.conf}.
 
-So if you add a client to the backup at \file{client.conf}, the connection and job data are created, also the corresponding \file{bareos-fd.conf} will be generated to place them on the client you want to backup (you also need to install the bareos-fd client on the client which is to be backed up).
+After you have \ilink{installed bareos-fd on the client}{SecondClient}, copy the generated client configuration over to the client and save it to \file{/etc/bareos/bareos-fd.conf}. Finally, restart the bareos-fd with the copied configuration.
+
+\begin{commands}{copy client configuration from the server to the testw1.example.com client}
+root@ucs:~# <input>CLIENTNAME=testw1.example.com</input>
+root@ucs:~# <input>scp /etc/bareos/autogenerated/fd-configs/${CLIENTNAME}.conf root@${CLIENTNAME}:/etc/bareos/bareos-fd.conf</input>
+\end{commands}
 
 \paragraph{Client and job configuration}$\;$