opsi (open pc server integration)

opsi is a solution for windows system management.

opsi is mainly developed by ​uib.

additional OPSI ressources

• opsi/dism
• opsi/howto
• opsi/winpe

General remarks about Windows silient/unattended configuration

/!\ more or less just some notes I've collected during work.

• windows/configuration
• windows/driver
• windows/fonts
• windows/group_policy
• windows/ie8
• windows/installation_image
• windows/languages
• windows/msoffice2010
• windows/shavlik
• windows/update
• windows/update/wuinstall
• windows/windows7
• windows/windows8

OPSI Products

These are the packages, that can be installed by OPSI.

Standard packages can be found at:

• ​http://download.uib.de/opsi4.0/products/netboot/
• ​http://download.uib.de/opsi4.0/products/localboot/
• ​http://download.uib.de/opsi4.0/products/contribute/
• ​https://forum.opsi.org/wiki/userspace:script_templates

Additional packages from ​http://www.dass-IT.de.

• copy the sources to your OPSI workbench
• if required, add the missing components
• create an OPSI package by
  • opsi-makeproductfile PACKAGENAME
• install package by
  • opsi-package-manager --install --properties ask PACKAGE.opsi

wsusoffline

Using "WSUS Offline Update", you can update any computer running Microsoft Windows and Office safely, quickly and without an Internet connection, see ​http://www.wsusoffline.net/

This tools will download all (most) available Windows and Microsoft Office Updates and collect them in the

Linux version is available here: ​http://software.opensuse.org/download/package?project=home:dassit:opsi:opsi4&package=wsusoffline

• download and extract wsusoffline
• start wsusoffline/sh/DownloadUpdates.sh
  • select required products and start the download
    • the updates will be stored in the subdirectory: client/
• copy the wsusoffline subdirectory client/ into the OPSI package at opsi_workbench/wsusoffline/CLIENT_DATA/client/

source:opsi/products/wsusoffline​

Known limitations

• wsusoffline 7.3
  • winxp, dotnet-Framework 3.5 Language Pack is known not to work. I suggest installating dotnet-Framework 3.5 as a separate package
• Why isn't the full wsusoffline application directly included in the OPSI package? Wouldn't it be easier to start the download directly in the OPSI directory instead of copying the client-directory to OPSI afterwards?
  • For the first run, this would be indeed easier. However, if you update the OPSI wsusoffline package to a newer version, all files already downloaded will be deleted (by opsi-package-manager), because they are not included in the package. Of course, you can backup them before, and apply them again after the update. However, then this approach would not be easier anymore. So in my opinion, it is cleaner, to handle the download indepent from the install part, and copy the full client-directory to OPSI after downloading the files.

xenserver-tools

Winodws tools when running on a Citrix XenServer:

source:opsi/products/xenserver-tools​