Windows Client
This guide focuses on managing Windows clients in opsi environments, covering several key aspects:
-
Automatic OS Installation
-
Adding and integrating Windows computers into opsi (installation of the Client Agent)
-
Deploying standard software on the opsi server
-
Deploying standard software on Windows clients
-
Creating opsi packages and packaging your own software
-
Notes on Windows clients
-
Special commands for Windows
-
Directories you may use
-
To manage Windows clients, it’s essential to have an opsi Server already installed and operational. |
Conventions and Notations
In this manual, we adhere to specific conventions for spelling and emphasis:
-
File and directory names are presented in
proportional font
. -
Longer commands and listings are contained in separate boxes. These can be conveniently transferred using copy & paste:
this is a command
-
opsi-script
code is displayed like this:
Message "Installing "+ $ProductId$ +" ..."
-
Elements in
<angle brackets>
indicate placeholders that you need to replace with their actual values. For instance, the file share containing opsi packages is referred to as<opsi-depot-share>
. On an actual server, this is typically found at/var/lib/opsi/depot
. Hence, the software package<opsi-depot-share>/ooffice
would be located at/var/lib/opsi/depot/ooffice
. -
Menu entries and button labels are formatted in italics.
-
Keyboard keys and combinations are enclosed in square brackets, for example, [C], [Ctrl]+[C], etc.