![]() shutdown, -s shutdown computer after installation reboot, -r reboot computer after installation use-ip-address Use IP address to connect to client. use-hostname Use hostname to connect to client. use-fqdn, -c Use FQDN to connect to client. Username for authentication (default: Administrator). verbose, -v increase verbosity (can be used multiple times) version, -V show program's version number and exit h, -help show this help message and exit Host The hosts to deploy the opsi-client-agent to. ![]() Simple File Sharing (Folder Options) should be The c$ and admin$ must beĪccessible on every client. ĭeploy opsi client agent to the specified clients. Opsi_server:/var/lib/opsi/depot/opsi-linux-client-agent#. Opsi_server:/home/user# cd /var/lib/opsi/depot/opsi-client-agent It is also possible to use a user which only has rights to call the method host_createOpsiClient. The user required here needs to be a member of the group 'opsiadmin'. If the connection fails, a login window will appear, with the Service-URL (opsi-config-server), and user and password. This is tried first with the user and password provided in config.ini. ![]() The script connects to the server via the opsi webservice in order to create the client on the serverside and to retrieve the pckey. This may cause an UAC Message at this point. The script copies the needed files to a temporary local directory and starts from there the opsi-script (opsi-script.exe) elevated in order to do the installation. On the drive from the previous step, start the script opsi-client-agent\service_setup.cmdĭo not start the script elevated (via right mouse click: 'as Administrator') because an elevated script has no access to the network share. Mount the share \\\opsi_depot on a drive letter. Logon to the Windows client with administrative privileges. # and license management backend and opsipxeconfd backend: # file as main backend, mysql as hw/sw invent # Recommended standard configuration (dhcpd not at the opsi server) # the first matching regular expression will be decisive. # For every method executed on backend dispatcher # Backend names have to match a backend configuration # This file configures which methods are dispatched to which backends. To download updates from (opsi-package-updater) WakeOnLan (WOL): UDP 7 / UDP 9 / UDP 12287 Server to client, connection from client to itself via localhost.Ĭonnection from client to itself via localhost.Ī random port from the given range is selected.ĬIFS/SMB: UDP 137 / UDP 138 (netbios) / TCP 139 / TCP 445ĭepends on the version of the client operating system. ![]() Known Issues with the 64 Bit SupportĬlient to server, depot to server (bidirectional, connections via localhost). Integration with Automated Answers for the setup Program Customization after a silent/unattended Installation Suggestions on How to Solve Problems with opsi-script Scripts Testing and improving an opsi-script script The opsi PackageBuilder program to modify a script. The opsi-setup-detector program for creating a Windows script Installation of opsi-setup-detector, opsi PackageBuilder and opsi-logviewer Example: Windows-Template 'opsi-template' Methods of Non-Interactive Installation for Windows A Brief Tutorial: How to write a opsi-script Script Integration of New Software Packages into the opsi Server Processing of the Different Levels of Driver Integration Structure of the Driver Directory and Driver Files Drivers automatically assigned to the clients using the inventory fields Drivers that suitable for your hardware but not specially assigned Simplified Driver Integration during the unattended Windows Installation Structure of the Unattended Installation Products ![]() OS-Installation: Complete the Base Package for Windows Installation of a new Windows PC with opsi (OS Installation) Hardware Inventory with the netboot product hwinvent Inventory with the localboot products hwaudit and swaudit. Deploying opsi standard products: opsi-configed Using service_setup.cmd on Windows NT6 (outdated) Creating a new opsi client using the opsi-client-bootcd Creating a new opsi client via the command line Creating a new opsi client via the graphical management interface Start of the management interface opsi-configed Installation of the management interface opsi-configed Automatic import of the minimal opsi products Create users and configure the groups opsiadmin and opsifileadmins Set Samba Configuration and Change Passwords Update and Configuration of the opsi-server Installation on CentOS or RedHat Enterprise Linux (RHEL) Installation on openSUSE or Suse Linux Enterprise Server (SLES) Installation on a Univention Corporate Server (UCS) Prerequisites for an installation on a server Starting up the uib preconfigured Virtual Machine Notes on determining hardware requirements ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |