FAQ for setup and application of the WAN extension
Do I need a license?
Yes, the extension is still part of the cofinancing scheme and therefore subject to a fee. You can test the extensions free of charge for a limited amount of time. In order to do so please contact sales@uib.de.
How do I activate the WAN extension on a client?
The activation of the WAN extension can be performed per client via the checkbox on the management console. The client will receive the specific configuration change the next time it connects to the opsi server. It then becomes active the next time the client is restarted.
Must the opsi client agent be deployed once again for the activation?
No, that is not necessary since the client can get the configuration automatically at the next connection to the opsi server. That can be at the next boot process or after an "on_demand" event.
How can I activate clients that are already in Home Office?
If the clients can be reached by the opsi server in home office, the change of the configuration can be performed by triggering an "on_demand" event. (This only works if the data transfer is set to cifs)
In the event that the clients in the home office cannot be reached by the opsi server, they can be updated via this opsi-admin call. (This should also work for clients that have been switched to webdav)
On the command line of the server this can be done using:
opsi-admin -a https://<ClientIp>:4441/opsiclientd -u <user> -p <pass> method fireEvent "on_demand"
or
opsi-admin -a https://<ClientIp>:4441/opsiclientd -u "<FQDN>" -p "<OpsiHostKey>" method fireEvent "on_demand"Replace the corresponding entries:
-
<ClientIp> = IP address of the clients
-
<user> = local administrator on the client or a member of the local administrator group
-
<pass> = password of the administrator
-
<FQDN> = FQDN of the client
-
<OpsiHostKey> = opsi hostkey of the client
How big is the cache on the client?
The cache on the client is set to 20 GB by default. The programs and updates to be installed are stored here. During an update, only the changed data is copied to the cache directory via a sync process. The size of the cache should be chosen generously so that large packages can also be saved.
How can I change the size of the cache on the client?
With this command, this parameter will be created in the management console. The value can then be individually adjusted for each client:
opsi-admin -d method config_createUnicode "opsiclientd.cache_service.product_cache_max_size" "Maximum product cache size in bytes" "40000000000" "40000000000" "True" "False"How can I increase the time the client waits for a response before rebooting for an installation?
With this command, this parameter will be created in the management console. The value can then be individually adjusted for each client:
opsi-admin -d method config_createUnicode "opsiclientd.event_sync_completed{cache_ready_user_logged_in}.shutdown_warning_time" "How long should to wait for an answer before a reboot. The default is 3600 seconds." "3600" "3600" "True" "False"If you want to increase the time by 8 hours enter 28000 seconds here.
"on_demand" installations in WAN mode?
The installations are triggered as if the client would not be a WAN client.
-
The config server is requested directly.
-
The installation starts without caching directly from the mounted depot share.
Does the kiosk mode work in WAN mode?
The kiosk mode works only if the opsi config server is available. Also in WAN-mode the kiosk connects directly to the opsi server. If the request to install a package is not only saved but also executed directly, the installation is performed the standard way and not in WAN mode, which means the packages are not cached. You can use the kiosk on a WAN client, but the actual WAN mode components are not used.
Can the Install by shutdown mode be combined with the WAN mode?
No, Install by shutdown mode is not compatible with WAN extension.
Subscription MSHotfix and WAN mode
Basically you can deploy the Mshotfix packages from your subscription on your WAN clients. However, it should be noted that these standard packages are very large in size(e.g. Windows 10 64 bits is around 6GB).
For this reason "modular" Mshotfix packages are provided for Windows 10 that only contain the patches for a certain ReleaseID, e.g. mshotfix-win10-1809-x64-glb. The size of these "modular" packages is currently about 1 GB). Therefore we strongly suggest to use these "modular" packages in WAN mode.