# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2017-2024, Veyon Solutions
# This file is distributed under the same license as the Veyon package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
# 
# Translators:
# Neal Joos, 2024
# R. van den Hoek, 2024
# Tobias Junghans, 2024
# 425526ed1f8bf401a74c2eb95fa32529_b267230 <4a462d278d8cf83757a3d1dd08695cb5_776931>, 2024
# Alex Rijckaert, 2024
# 
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Veyon 4.9.1\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-12-11 11:21+0100\n"
"PO-Revision-Date: 2024-09-13 09:03+0000\n"
"Last-Translator: Alex Rijckaert, 2024\n"
"Language-Team: Dutch (https://app.transifex.com/veyon-solutions/teams/65452/nl/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: nl\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

msgid "Deployment"
msgstr "Implementatie"

msgid "Initial steps"
msgstr "Eerste stappen"

msgid "Install Veyon on the reference/teacher computer"
msgstr "nstalleer Veyon op de referentie-/leraarcomputer"

msgid "Install Veyon Add-ons on the reference/teacher computer"
msgstr "Installeer Veyon Add-ons op de referentie-/leraarcomputer"

msgid "Import the purchased license file(s)"
msgstr "Importeer aangeschafte licentiebestand(en)"

msgid "Make changes to the configuration as desired"
msgstr "Breng naar wens wijzigingen aan in de configuratie"

msgid "Export the configuration"
msgstr "De configuratie exporteren"

msgid "Automated/silent installation"
msgstr "Geautomatiseerde/stille installatie"

msgid ""
"Like Veyon itself the add-ons can also be installed in *silent mode* by "
"passing the ``/S`` parameter and optionally ``/D=...``. Please refer to "
"chapter :ref:`AutoInstall` in the administrator manual for details."
msgstr ""
"Net als Veyon zelf kunnen de add-ons ook in *stille modus* geïnstalleerd "
"worden door de ``/S`` parameter en optioneel ``/D=...`` door te geven. "
"Raadpleeg hiervoor het hoofdstuk :ref:`AutoInstallatie` in de administrator "
"handleiding."

msgid "Deploying licenses"
msgstr "Licenties implementeren"

msgid ""
"Since all licenses are part of a Veyon configuration they can be deployed "
"easily using the well-known mechanisms for :ref:`importing the configuration"
" during installation <InstallationConfigurationImport>`. A configuration "
"containing the licenses can already be imported/applied when the add-ons are"
" not yet installed. This will make the add-ons work instantly whenever they "
"get installed later."
msgstr ""
"Omdat alle licenties deel uitmaken van een Veyon configuratie kunnen ze "
"eenvoudig worden ingezet met behulp van de bekende mechanismen voor "
":ref:`configuratie importeren tijdens installatie "
"<InstallationConfigurationImport>`. Een configuratie die de licenties bevat "
"kan al geïmporteerd/toegepast worden als de add-ons nog niet geïnstalleerd "
"zijn. Dit zorgt ervoor dat de add-ons direct werken wanneer ze later worden "
"geïnstalleerd."

msgid "Entra ID Connector"
msgstr "ID Connector invoeren"

msgid "General"
msgstr "Algemeen"

msgid ""
"The Veyon Entra ID Connector add-on extends Veyon Master to read devices and"
" their location from an Entra ID instance. Once set up, computers and "
"locations no longer have to be maintained in the builtin network object "
"directory. A previously configured LDAP/ActiveDirectory integration can be "
"replaced with the Entra ID connector after migrating an On Premise "
"ActiveDirectory to Entra ID in the Azure cloud."
msgstr ""
"De Veyon Entra ID Connector add-on breidt Veyon Master uit om apparaten en hun locatie uit een Entra ID instantie te lezen. Eenmaal ingesteld, hoeven computers en locaties niet langer te worden onderhouden in de ingebouwde netwerk object directory. Een eerder geconfigureerde LDAP/ActiveDirectory integratie kan worden vervangen door de Entra ID connector na migratie van een On Premise ActiveDirectory naar Entra ID in de Azure cloud.\n"
"\n"
"Vertaald met www.DeepL.com/Translator (gratis versie)"

msgid "Initial setup"
msgstr "Eerste installatie"

msgid ""
"First of all the Veyon Add-ons package needs to be installed. Make sure to "
"download and install the version corresponding to your Veyon installation, "
"i.e. Veyon 4.9.1 requires Veyon Add-ons 4.9.1 while for Veyon 4.8.3 you need"
" to install version 4.8.3 of the add-ons. Please refer to "
":ref:`DeployingAddons` for further information."
msgstr ""

msgid ""
"After the installation has completed, you'll see some new configuration "
"pages in the Veyon Configurator program. One of them is called "
":guilabel:`Entra ID Connector` and allows to set up the add-on:"
msgstr ""
"Nadat de installatie is voltooid, ziet u enkele nieuwe configuratiepagina's "
"in het Veyon Configurator programma. Een daarvan heet :guilabel:`Entra ID "
"Connector` en maakt het mogelijk om de add-on in te stellen:"

msgid "Entra ID Connector configuration page"
msgstr "Configuratiepagina Entra ID Connector"

msgid "App registration"
msgstr "App registratie"

msgid ""
"In order to fill the required fields, the connector has to be registered in "
"your Entra ID instance first. For doing so open a web browser and nagivate "
"to the Entra ID management area in the Azure Portal. Here you can register "
"the Veyon Entra ID Connector as an application:"
msgstr ""
"Om de vereiste velden in te vullen, moet de connector eerst worden "
"geregistreerd in je Entra ID instance. Open hiervoor een webbrowser en "
"nagivate naar de Entra ID management area in de Azure Portal. Hier kunt u de"
" Veyon Entra ID Connector als applicatie registreren:"

msgid "App registration of the Veyon Entra ID Connector – Step 1"
msgstr "App registratie van de Veyon Entra ID Connector - Stap 1"

msgid ""
"Clicking :guilabel:`New registration` opens a new dialog where you have to "
"enter a suitable name, e.g. *Veyon Entra ID Connector* and click on "
":guilabel:`Register`:"
msgstr ""
"Door te klikken op :guilabel:`Nieuwe registratie` wordt een nieuw "
"dialoogvenster geopend waarin u een geschikte naam moet invoeren, bijv. "
"*Veyon Entra ID Connector* en klik op :guilabel:`Registreren`:"

msgid "App registration of the Veyon Entra ID Connector – Step 2"
msgstr "App registratie van de Veyon Entra ID Connector - Stap 2"

msgid ""
"After the app has been registered, you can already see the required IDs in "
"the :guilabel:`Overview` page. Copy the *Application (client) ID* and "
"*Directory (tenant) ID* to the corresponding fields in the Veyon "
"Configurator:"
msgstr ""

msgid "App registration of the Veyon Entra ID Connector – Step 3"
msgstr "App-registratie van de Veyon Entra ID Connector - Stap 3"

msgid "Client secrets"
msgstr "Klantgeheimen"

msgid ""
"Next, the client secret or certificate must be configured with which the "
"Entra ID Connector can authenticate itself to the Azure cloud. Open the "
":guilabel:`Certificates & secrets` page and click on :guilabel:`New client "
"secret`. Give the secret a name and specify when it will expire. Do not "
"choose a too short period as you have to create a new secret and reconfigure"
" Veyon everytime a client secret has expired:"
msgstr ""
"Vervolgens moet het client geheim of certificaat worden geconfigureerd "
"waarmee de Entra ID Connector zich kan aanmelden bij de Azure cloud. Open de"
" :guilabel:`Certificates & secrets` pagina en klik op :guilabel:`New client "
"secret`. Geef het geheim een naam en geef aan wanneer het verloopt. Kies "
"geen te korte periode, aangezien u een nieuw geheim moet aanmaken en Veyon "
"opnieuw moet configureren telkens wanneer een client geheim is verlopen:"

msgid "Create client secret for the Veyon Entra ID Connector – Step 1"
msgstr "Clientgeheim aanmaken voor de Veyon Entra ID Connector - Stap 1"

msgid ""
"After the client secret has been created, you have to copy its value to the "
":guilabel:`Client secret` field in the Veyon Configurator."
msgstr ""
"Nadat de client geheim is aangemaakt, moet u de waarde ervan kopiëren naar "
"het veld :guilabel:`Client secret` in de Veyon Configurator."

msgid "Create client secret for the Veyon Entra ID Connector – Step 2"
msgstr "Clientgeheim voor de Veyon Entra ID Connector aanmaken - Stap 2"

msgid ""
"The client secret value has to be copied immediately since it is only shown "
"once directly after creating the client secret. If you forgot to copy it, "
"you have to delete the secret and create a new one."
msgstr ""
"De waarde van de cliëntgeheimen moet direct worden gekopieerd, omdat ze maar"
" één keer worden getoond direct na het aanmaken van de cliëntgeheimen. Als "
"je het vergeten bent te kopiëren, moet je het geheim verwijderen en een "
"nieuwe aanmaken."

msgid ""
"You can now verify that the tenant ID, application ID and client secret are "
"correct by clicking on the :guilabel:`Test access` button."
msgstr ""
"U kunt nu controleren of de tenant-ID, de applicatie-ID en het clientgeheim "
"correct zijn door op de knop :guilabel:`Test toegang` te klikken."

msgid ""
"A good alternative to client secrets are client certificates. This allows "
"storing the secret at a specific location where you can set access "
"permissions as desired. Otherwise the client secret is stored (encrypted) as"
" part of the Veyon Configuration."
msgstr ""
"Een goed alternatief voor client geheimen zijn client certificaten. Dit "
"maakt het mogelijk om het geheim op een specifieke locatie op te slaan waar "
"u de toegangsrechten naar wens kunt instellen. Anders wordt het client "
"geheim (versleuteld) opgeslagen als onderdeel van de Veyon Configuratie."

msgid "API permissions"
msgstr "API-rechten"

msgid ""
"The last important task is to set up the permissions for the registered app "
"so that the Entra ID Connector can read the required information from Entra "
"ID. Navigate to the :guilabel:`API permissions` page, click on the "
":guilabel:`Add a permission` button and select :guilabel:`Microsoft Graph`:"
msgstr ""
"De laatste belangrijke taak is het instellen van de machtigingen voor de "
"geregistreerde app zodat de Entra ID Connector de vereiste informatie van "
"Entra ID kan lezen. Navigeer naar de :guilabel:`API-machtigingen` pagina, "
"klik op de :guilabel:`Een toestemming toevoegen` knop en selecteer "
":guilabel:`Microsoft Graph`:"

msgid "Set up permissions for the Veyon Entra ID Connector – Step 1"
msgstr "Machtigingen instellen voor de Veyon Entra ID Connector - Stap 1"

msgid ""
"Now the actual permissions have to be selected. Select "
":guilabel:`Application permissions`, search for the *Device.Read.All* "
"permission and check it:"
msgstr ""
"Nu moeten de eigenlijke machtigingen worden geselecteerd. Selecteer "
":guilabel:`Toepassingsrechten`, zoek naar de toestemming *Device.Read.All* "
"en vink deze aan:"

msgid "Set up permissions for the Veyon Entra ID Connector – Step 2"
msgstr "Machtigingen instellen voor de Veyon Entra ID Connector - Stap 2"

msgid ""
"Repeat this step for the permissions *Group.Read.All*, "
"*GroupMember.Read.All* and *User.Read.All*. After checking all required "
"permissions, click on :guilabel:`Add permissions`."
msgstr ""
"Herhaal deze stap voor de machtigingen *Group.Read.All*, "
"*GroupMember.Read.All* en *User.Read.All*. Nadat u alle vereiste "
"machtigingen hebt gecontroleerd, klikt u op :guilabel:`Machtigingen "
"toevoegen`."

msgid ""
"The last step is to grant admin consent for these permissions. This can "
"easily be done by clicking on :guilabel:`Grant admin consent for <YOUR-"
"ORGANIZATION>`:"
msgstr ""
"The last step is to grant admin consent for these permissions. This can "
"easily be done by clicking on :guilabel:`Grant admin consent for <YOUR-"
"ORGANIZATION>`:"

msgid "Set up permissions for the Veyon Entra ID Connector – Step 3"
msgstr "Machtigingen instellen voor de Veyon Entra ID Connector - Stap 3"

msgid "Filters"
msgstr "Filters"

msgid ""
"Filters make it possible to read out only certain objects (devices, users "
"and groups) and make them available for Veyon. This depends largely on how "
"the objects are structured in your Entra ID instance and which of them are "
"required for Veyon. If, for example, security groups are used as locations "
"(rooms), the :guilabel:`Device groups filter` can be adjusted accordingly so"
" that only groups starting with ``Room`` are used as locations. In that case"
" a suitable filter would be ``startsWith(displayName, 'Room')``."
msgstr ""

msgid ""
"See `Operators and functions supported in filter expressions "
"<https://learn.microsoft.com/en-US/graph/filter-query-"
"parameter?tabs=http#operators-and-functions-supported-in-filter-"
"expressions>`_ for further information."
msgstr ""
"Zie `Bedieningselementen en functies ondersteund in filterexpressies "
"<https://learn.microsoft.com/en-US/graph/filter-query-"
"parameter?tabs=http#operators-and-functions-supported-in-filter-"
"expressions>`_ voor meer informatie."

msgid "Devices"
msgstr ""

msgid ""
"In this section you can configure how certain device properties are "
"retrieved. While the display name is always used as computer name, both "
"hostname and the MAC address can be determined in different ways."
msgstr ""

msgid "Hostname source"
msgstr ""

msgid ""
"If all device names match the hostnames and can be resolved to IP addresses "
"using an internal DNS server (BIND, AD DS etc.) you can keep the default "
"option :guilabel:`Device name`. You should not rely on legacy name "
"resolution protocols such as NetBIOS. You can easily verify this by running "
"``nslookup <HOSTNAME>``. If the device names can't be resolved by a DNS "
"server in your network, it's recommended to either resolve them via "
"`multicast DNS <https://en.wikipedia.org/wiki/Multicast_DNS>`_ or store the "
"actual hostname or host address in a custom :guilabel:`Hostname attribute`."
msgstr ""

msgid "MAC address source"
msgstr ""

msgid ""
"Veyon uses MAC addresses for powering on computers via `Wake-on-LAN "
"<https://en.wikipedia.org/wiki/Wake-on-LAN>`_. If you want to take advantage"
" of this feature you can populate each device's MAC addresses in a certain "
"(extension) attribute and enter the name of this attribute in the "
":guilabel:`MAC address attribute` field. If your devices are managed via "
"Microsoft Intune you can also change the setting to use the Ethernet or Wi-"
"Fi MAC addresses stored in Intune. Depending on the selected option, only "
"the Ethernet or Wi-Fi MAC addresses are read or one of them while the first "
"one is prioritized (i.e. the 2nd address only used if the 1st address is "
"empty)."
msgstr ""

msgid "Locations"
msgstr "Locaties"

msgid ""
"In Veyon all computers are grouped into locations (rooms). To properly group"
" the devices read from Entra ID, a suitable mapping mode needs to be chosen:"
msgstr ""

msgid "Use device groups"
msgstr "Apparaatgroepen gebruiken"

msgid ""
"Select this mode if your devices belong to (security) groups which "
"correspond to locations. This is the most preferred way since in Entra ID "
"it's quite easy to create groups for each room and add the devices to the "
"corresponding groups. Most likely you will have to configure a suitable "
":guilabel:`Device groups filter` in the :guilabel:`Filters` section such "
"that only these groups (e.g. starting with name ``Room``) are displayed as "
"locations. Optionally you can configure the name of the group attribute "
"which to use as location name. Per default the group's display name is used."
msgstr ""

msgid "Use location attribute of device"
msgstr "Gebruik locatiekenmerk van apparaat"

msgid ""
"As an alternative to location-based groups, the location of each computer "
"can also be stored in an (extension) attribute. In this case, the name of "
"this attribute must be specified."
msgstr ""

msgid "Extract from hostname via regular expression"
msgstr "Extractie uit hostnaam via standaard expressie"

msgid ""
"If the hostnames contain the room or location name, you can let Entra ID "
"Connector extract the location name. This is done by applying a regular "
"expression on the hostnames. The first capture group of the regular "
"expression is then used as location / computer name."
msgstr ""

msgid ""
"For example, if the hostnames have the format ``r<ROOM-NUMBER>-c<COMPUTER-"
"NUMBER>`` (e.g. ``r101-c01.example.org``), you can use the following regular"
" expression to extract the location name:"
msgstr ""

msgid "``([^-]*)-.*``"
msgstr "``([^-]*)-.*``"

msgid ""
"The first capture (in braces) captures everything until the first minus "
"sign, so the location displayed in Veyon Master will be ``r101``."
msgstr ""
"De eerste opname (tussen accolades) vangt alles op tot het eerste minteken, "
"zodat de locatie die in Veyon Master wordt weergegeven ``r101`` is."

msgid ""
"Please refer to the `Wikipedia article on regular expressions "
"<https://en.wikipedia.org/wiki/Regular_expression>`_ for more information on"
" the concept, syntax and available pattern options."
msgstr ""
"Raadpleeg het `Wikipedia-artikel over reguliere expressies "
"<https://en.wikipedia.org/wiki/Regular_expression>`_ voor meer informatie "
"over het concept, de syntaxis en beschikbare patroonopties."

msgid "Completion"
msgstr "Voltooiing"

msgid ""
"Finally, the network object directory backend needs to be changed to *Entra "
"ID Connector* so that Veyon Master actually uses the Entra ID Connector add-"
"on."
msgstr ""
"Ten slotte moet de backend van de netwerkobjectdirectory worden gewijzigd in"
" *Entra ID Connector*, zodat Veyon Master de add-on Entra ID Connector "
"daadwerkelijk gebruikt."

msgid "Change network object directory backend to Entra ID Connector"
msgstr "Netwerkobjectdirectory wijzigen in Entra ID Connector"

msgid ""
"Now you can start Veyon Master and should see the locations and computers "
"from your Entra ID directory."
msgstr ""
"Nu kunt u Veyon Master starten en zou u de locaties en computers uit uw "
"Entra ID directory moeten zien."

msgid ""
"Due to limitations in the Windows SSP authentication API, it's **not** "
"possible to use Veyon's *logon authentication* with cloud-only Entra ID "
"accounts. Please use *key file authentication* instead or make sure the "
"accounts including password hashes are synced to an On Premise Active "
"Directory."
msgstr ""

msgid "Veyon Add-ons Integration Manual"
msgstr "Veyon handleiding voor integratie van add-ons"

msgid ":ref:`genindex`"
msgstr ":ref:`genindex`"

msgid "Internet Access Control"
msgstr "Toegangscontrole internet"

msgid ""
"The Veyon Internet Access Control add-on allows blocking the access to the "
"Internet for the whole class or individual computers in situations such as "
"exams. The Internet access is blocked client-side by using mechanisms "
"provided by the different backends."
msgstr ""
"De Veyon Internet Access Control add-on maakt het mogelijk om de toegang tot"
" het internet te blokkeren voor de hele klas of individuele computers in "
"situaties zoals examens. De internettoegang wordt client-side geblokkeerd "
"met behulp van mechanismen die door de verschillende backends worden "
"geleverd."

msgid ""
"After the installation has completed, you'll see some new configuration "
"pages in the Veyon Configurator program. One of them is called "
":guilabel:`Internet access control` and allows to set up the add-on:"
msgstr ""
"Nadat de installatie is voltooid, ziet u enkele nieuwe configuratiepagina's "
"in het Veyon Configurator programma. Een daarvan heet :guilabel:`Internet "
"access control` en maakt het mogelijk om de add-on in te stellen:"

msgid "Internet Access Control configuration page"
msgstr ""

msgid ""
"In most cases you can leave the default settings and continue with deploying"
" the add-on to the student computers."
msgstr ""

msgid ""
"If you make changes to the configuration, remember to always deploy the "
"updated configuration to the student computers! Only the client-side "
"settings affect the way the Internet access is blocked on the clients."
msgstr ""

msgid ""
"Now you can start Veyon Master and can click the :guilabel:`Internet access`"
" button to open the menu with the :guilabel:`Block Internet access` and "
":guilabel:`Unblock Internet access` items. After activating the "
":guilabel:`Block Internet access` item, the users on the selected "
"computer(s) no longer should be able to open a website on the Internet. If "
"they still are, please check the settings and possibly try another blocking "
"mode or backend."
msgstr ""
"Nu kunt u Veyon Master starten en op de knop :guilabel:`Internet access` "
"klikken om het menu met de items :guilabel:`Block Internet access` en "
":guilabel:`Unblock Internet access` te openen. Na het activeren van het item"
" :guilabel:`Blokkeer internettoegang` zouden de gebruikers op de "
"geselecteerde computer(s) niet langer een website op het internet moeten "
"kunnen openen. Als dit nog steeds het geval is, controleer dan de "
"instellingen en probeer eventueel een andere blokkeermodus of backend."

msgid "Backends"
msgstr ""

msgid ""
"There are currently two backends providing different mechanisms to block the"
" Internet access. Both backends are described in the following subsections."
msgstr ""

msgid "Block internet access via system firewall"
msgstr "Blokkeer internettoegang via systeemfirewall"

msgid ""
"This is the standard backend that should preferably be used, as it offers "
"the most flexibility and works most reliably. When this backend is used, the"
" Veyon Service makes changes to the system firewall to block Internet "
"access. There are platform-specific differences here:"
msgstr ""

msgid "Windows"
msgstr "Windows"

msgid ""
"Veyon controls the integrated Windows firewall and makes temporary changes "
"to its configuration. This means that the Windows firewall must be "
"activated. In addition, changes to the configuration of the Windows firewall"
" must not be prevented by group policies."
msgstr ""

msgid "Linux"
msgstr "Linux"

msgid ""
"Veyon works on the basis of *nftables* and calls the related command line "
"tool ``nft``. This is used to temporarily add additional rules to block "
"Internet access."
msgstr ""

msgid ""
"For both operating systems, the backend configuration is identical. In "
"general different modes are available. The mode selection depends on the "
"network environment and the desired blocking behavior."
msgstr ""

msgid "Block all outbound traffic for TCP ports"
msgstr "Blokkeer al het uitgaande verkeer voor TCP-poorten"

msgid ""
"This is the default mode and should work in most environments. In this mode "
"the Veyon Service adds special rules to the firewall which block any traffic"
" to the configured ports. Use this mode if blocking the TCP ports 80/443 and"
" one or multiple custom ports (separated by space) is sufficient. To block "
"all traffic use the second mode."
msgstr ""

msgid "Block all outbound traffic to non-local subnets"
msgstr "Blokkeer al het uitgaande verkeer naar niet-lokale subnetten"

msgid ""
"In this mode, all network traffic directed to networks outside the local "
"subnets is blocked. On Windows, the Veyon service temporarily changes the "
"configuration of all firewall profiles (domain, private, public) to “ "
"Outbound connections that do not match a rule are blocked”. If "
":guilabel:`Exceptions` are configured, appropriate rules are added to allow "
"access to these networks, hosts or ports. This can be used, for example, to "
"preserve access to the intranet and other internally hosted platforms. "
"External websites can also be defined as exceptions here under certain "
"circumstances, but the addresses of all servers/CDNs from which the website "
"loads resources must then also be specified."
msgstr ""

msgid "Block traffic to (e.g. proxy or DNS) servers"
msgstr "Blokkeer verkeer naar (bijvoorbeeld proxy- of DNS-) servers"

msgid ""
"If the student computers access the Internet via a proxy server, you can "
"select this option. A firewall rule is then added that simply blocks all "
"traffic to the proxy address. Alternatively, access to certain DNS servers "
"can also be blocked, although in most cases this leads to problems when "
"accessing internal resources such as network drives etc."
msgstr ""

msgid "Enable preconfigured firewall rule"
msgstr "Voorgeconfigureerde firewallregel inschakelen"

msgid ""
"If the three modes above are not suitable for your network you can also "
"configure an own custom rule in the Windows Firewall. This rule should be "
"disabled by default. The Veyon Service will enable this rule while the "
"Internet access is to be blocked. On Linux the Veyon Service calls ``nft`` "
"to load the nftables rules from the file "
"``/etc/veyon/iac/firewall/rules.d/<RULENAME>``. You can define any nftables "
"rules in this file."
msgstr ""

msgid "Block internet access by modifying routing table"
msgstr "Internettoegang blokkeren door routering-tabel te wijzigen"

msgid ""
"If the firewall backend cannot be used (e.g. if a 3rdparty firewall software"
" is used instead of the Windows Firewall), you can use this backend as a "
"fallback. It works in a very simple way by temporarily removing the default "
"route from the routing table and/or adding a user-defined (possibly "
"deliberately invalid) route to block Internet access. In any case, the "
"settings should be made carefully so that access to the internal network "
"continues to function properly. Especially in larger segmented networks, "
"both options should be combined by removing the default route on the one "
"hand and adding a route to the internal network on the other."
msgstr ""

msgid "Licensing"
msgstr "Licenties"

msgid ""
"All commercial addons for Veyon require a valid license. A license is valid "
"for a specific addon and a certain installation ID. The unique installation "
"ID is created upon the first installation of Veyon and is part of the "
"program configuration. You should never change the installation ID e.g. by "
"editing the configuration JSON file since this will make your licensed "
"addons not work any longer."
msgstr ""
"Alle commerciële addons voor Veyon vereisen een geldige licentie. Een "
"licentie is geldig voor een bepaalde addon en een bepaalde installatie-ID. "
"De unieke installatie-ID wordt bij de eerste installatie van Veyon "
"aangemaakt en maakt deel uit van de programmaconfiguratie. U mag de "
"installatie-ID nooit wijzigen, bijvoorbeeld door het JSON-"
"configuratiebestand te bewerken, omdat uw gelicentieerde addons dan niet "
"meer werken."

msgid "Installing a license"
msgstr "Een licentie installeren"

msgid ""
"After having received one or multiple license files they can be installed "
"through the :guilabel:`Licensing` configuration page in the Veyon "
"Configurator. Click on the :guilabel:`+` button to select the license file "
"and import it. After a successful import the licenses and additional "
"information show up in the table. Click on the :guilabel:`Apply` button to "
"save the imported licenses permanently."
msgstr ""
"Na ontvangst van een of meerdere licentiebestanden kunnen deze via de "
"configuratiepagina :guilabel:`Licenties` in de Veyon Configurator worden "
"geïnstalleerd. Klik op de :guilabel:`+` knop om het licentiebestand te "
"selecteren en te importeren. Na een succesvolle import verschijnen de "
"licenties en aanvullende informatie in de tabel. Klik op de knop "
":guilabel:`Toepassen` om de geïmporteerde licenties permanent op te slaan."

msgid ""
"In order to access the licensed addons you have to restart all Veyon-related"
" program components. Usually restarting the Veyon Configurator is sufficient"
" since you'll first have to configure the new addons anyway."
msgstr ""
"Om toegang te krijgen tot de gelicentieerde addons moet u alle Veyon "
"gerelateerde programmacomponenten opnieuw opstarten. Meestal is het "
"herstarten van de Veyon Configurator voldoende omdat u de nieuwe addons toch"
" eerst moet configureren."

msgid "Transferring installed licenses to other computers"
msgstr "Geïnstalleerde licenties overbrengen naar andere computers"

msgid ""
"If you want to use Veyon Master with the addons on other computers, you have"
" to transfer the licenses to them. You can easily do this by exporting the "
"configuration on the computer on which you imported the licenses. The "
"exported configuration then contains both the installation ID and the "
"imported licenses. It can be imported on all client computers as desired. "
"See chapter :ref:`ConfImportExport` in the administrator manual for details."
msgstr ""
"Als u Veyon Master met de addons op andere computers wilt gebruiken, moet u "
"de licenties naar hen overdragen. Dit kunt u eenvoudig doen door de "
"configuratie te exporteren op de computer waarop u de licenties hebt "
"geïmporteerd. De geëxporteerde configuratie bevat dan zowel de installatie-"
"ID als de geïmporteerde licenties. Deze kan naar wens op alle "
"clientcomputers worden geïmporteerd. Zie hoofdstuk :ref:`ConfImportExport` "
"in de beheerdershandleiding voor meer informatie."

msgid "Command line interface"
msgstr "Command line interface"

msgid ""
"There's a CLI module ``licensing`` which allows managing licenses at the "
"command line:"
msgstr ""
"Er is een CLI module ``licensing`` waarmee licenties beheerd kunnen worden "
"via de commandoregel:"

msgid ""
"This command imports the license in the given file into the local "
"configuration."
msgstr ""
"Dit commando importeert de licentie in het gegeven bestand in de lokale "
"configuratie."

msgid "This command shows details on all installed licenses."
msgstr "Dit commando toont details over alle geïnstalleerde licenties."

msgid "This command removes the license with the specified ID."
msgstr "Dit commando verwijdert de licentie met de opgegeven ID."

msgid "Network Discovery"
msgstr "Netwerk ontdekken"

msgid ""
"The Veyon Network Discovery add-on extends Veyon Master to scan configured "
"networks for computers running one or multiple Veyon Server instances. All "
"discovered computers and RDP sessions show up instantly in the Locations & "
"computers panel. Once set up, computers and locations no longer have to be "
"maintained in the builtin network object directory nor does the "
"LDAP/ActiveDirectory integration have to be configured. Last but not least, "
"the add-on is perfectly suited for DHCP-based networks where the IP "
"addresses of the computers are constantly changing."
msgstr ""
"De Veyon Network Discovery add-on breidt Veyon Master uit om geconfigureerde"
" netwerken te scannen op computers waarop één of meerdere Veyon Server "
"instanties draaien. Alle ontdekte computers en RDP-sessies verschijnen "
"direct in het paneel Locaties & computers. Eenmaal ingesteld, hoeven "
"computers en locaties niet langer te worden bijgehouden in de ingebouwde "
"netwerk object directory en hoeft de LDAP/ActiveDirectory integratie niet te"
" worden geconfigureerd. Last but not least is de add-on perfect geschikt "
"voor DHCP-gebaseerde netwerken waar de IP-adressen van de computers constant"
" veranderen."

msgid ""
"After the installation has completed, you'll see some new configuration "
"pages in the Veyon Configurator program. One of them is called "
":guilabel:`Network discovery` and allows to set up the add-on:"
msgstr ""
"Nadat de installatie is voltooid, ziet u enkele nieuwe configuratiepagina's "
"in het Veyon Configurator programma. Een daarvan heet :guilabel:`Network "
"discovery` en maakt het mogelijk om de add-on in te stellen:"

msgid "Network Discovery configuration page"
msgstr ""

msgid ""
"You can start with the default settings if the subnet of the computer is "
"small enough, i.e. the IPv4 prefix is ``/24`` or the subnet mask is "
"``255.255.255.0``. For larger subnets it's recommended to change the mode to"
" :guilabel:`Scan network ranges` and add a group with a network range for "
"testing (adopt the IP addresses to your environment):"
msgstr ""
"Je kunt beginnen met de standaardinstellingen als het subnet van de computer"
" klein genoeg is, d.w.z. het IPv4-prefix is ``/24`` of het subnetmasker is "
"``255.255.255.0``. Voor grotere subnetten is het aan te raden om de modus te"
" wijzigen in :guilabel:`Scan network ranges` en een groep toe te voegen met "
"een netwerkbereik om te testen (pas de IP-adressen aan aan je omgeving):"

msgid "Only scan subnet of larger network"
msgstr ""

msgid ""
"Finally, the network object directory backend needs to be changed to "
"*Network discovery* so that Veyon Master actually uses the Network Discovery"
" add-on."
msgstr ""
"Ten slotte moet de backend van de netwerkobjectdirectory worden gewijzigd in"
" *Netwerkontdekking*, zodat Veyon Master de add-on Netwerkontdekking "
"daadwerkelijk gebruikt."

msgid "Change network object directory backend to Network Discovery"
msgstr ""

msgid ""
"Now you can start Veyon Master and should see the computers in your network "
"running a Veyon Server. Depending on the size of the subnet or network "
"range(s), the initial scan process might take a while (up to 1-2 minutes in "
"the worst case)."
msgstr ""
"Nu kunt u Veyon Master starten en zou u de computers in uw netwerk met een "
"Veyon Server moeten zien. Afhankelijk van de grootte van het subnet of de "
"netwerkbereik(ken) kan het aanvankelijke scanproces even duren (in het "
"ergste geval tot 1-2 minuten)."

msgid "Options"
msgstr "Opties"

msgid ""
"After you have configured the desired subnets or network ranges, you can "
"start tweaking the options for scanning computers to decrease the initial "
"scan duration."
msgstr ""
"Nadat u de gewenste subnetten of netwerkbereiken hebt geconfigureerd, kunt u"
" beginnen met het tweaken van de opties voor het scannen van computers om de"
" initiële scanduur te verkorten."

msgid ""
"In most cases you can increase the number of :guilabel:`parallel scans` to "
"100–300. Veyon Master opens the specified number of TCP connections in "
"parallel so make sure to not exhaust the resources of the computer or per-"
"process resource limits set by the operating system."
msgstr ""
"In de meeste gevallen kunt u het aantal :guilabel:`parallel scans` tot "
"100-300 verhogen. Veyon Master opent het opgegeven aantal TCP-verbindingen "
"parallel, dus zorg ervoor dat u de bronnen van de computer of de door het "
"besturingssysteem ingestelde limieten voor bronnen per proces niet uitput."

msgid ""
"If all computers are on the same LAN (i.e. ping times of usually less than 1"
" ms) you can also decrease the :guilabel:`scan timeout` to 25–100 ms. Each "
"computer responding within that timeout is shown in Veyon Master."
msgstr ""
"Als alle computers zich op hetzelfde LAN bevinden (d.w.z. ping-tijden van "
"meestal minder dan 1 ms) kunt u ook de :guilabel:`scan timeout` tot 25-100 "
"ms verlagen. Elke computer die binnen deze time-out reageert, wordt in Veyon"
" Master weergegeven."

msgid ""
"With a scan timeout of 25 ms and 250 parallel scans Veyon is able to scan "
"``25*250=6250`` computers per second. Using this formula you can easily "
"calculate the ideal settings for your environment such that Veyon Master "
"does not require too long for scanning while still detecting all computers "
"reliably."
msgstr ""
"Met een scantime-out van 25 ms en 250 parallelle scans kan Veyon "
"``25*250=6250`` computers per seconde scannen. Met behulp van deze formule "
"kunt u eenvoudig de ideale instellingen voor uw omgeving berekenen, zodat "
"Veyon Master niet te lang nodig heeft om te scannen en toch alle computers "
"betrouwbaar detecteert."

msgid "Sessions"
msgstr "Sessies"

msgid ""
"One typical use case of the Network Discovery add-on are environments with "
"remote desktop servers running sessions which should be monitored using "
"Veyon. Since these sessions are dynamic, it's hard to use statically "
"configured hosts (even though optional port numbers can be specified). "
"Instead you can simply enable the option :guilabel:`Scan sessions on all "
"computers` and specify a limit – typically the maximum number of concurrent "
"sessions on the server. Optionally it's possible to exclude the first "
"session since often it's the local console session of the server at which "
"only administrators log in or the primary login screen is visible."
msgstr ""

msgid "Computer names"
msgstr "Computernamen"

msgid ""
"On Windows, legacy WINS resolution via NetBIOS should be disabled to prevent"
" issues where the NetBIOS hostname does not exactly match the DNS hostname "
"(especially since NetBIOS hostnames always consist of uppercase letters only"
" while the actual DNS hostnames usually do not). If NetBIOS is enabled, "
"Network Discovery may obtain randomly changing hostname types (for a certain"
" IP address) from the operating system on each scan/update. This causes "
"constant reconnects to the computers since from the view of Veyon, a "
"different computer has been discovered each time."
msgstr ""
"Op Windows moet WINS-resolutie via NetBIOS worden uitgeschakeld om problemen"
" te voorkomen waarbij de NetBIOS-hostnaam niet exact overeenkomt met de DNS-"
"hostnaam (vooral omdat NetBIOS-hostnamen altijd alleen uit hoofdletters "
"bestaan terwijl de werkelijke DNS-hostnamen dat meestal niet doen). Als "
"NetBIOS is ingeschakeld, kan Network Discovery bij elke scan/update "
"willekeurig veranderende hostnaamtypes (voor een bepaald IP-adres) "
"verkrijgen van het besturingssysteem. Dit veroorzaakt voortdurend opnieuw "
"verbinding maken met de computers omdat vanuit het gezichtspunt van Veyon "
"elke keer een andere computer is ontdekt."

msgid ""
"Per default Network Discovery tries to perform DNS reverse lookups to "
"determine the hostnames corresponding to the discovered IP addresses. If "
"computers are not known to your DNS servers there are several other ways to "
"achieve human-readable computer names, especially in remote desktop "
"scenarios:"
msgstr ""

msgid "User login name / Full name of user"
msgstr ""

msgid ""
"Select one of these options to use the login or full name of the logged in "
"user as computer name."
msgstr ""

msgid "Session client name / Session client address"
msgstr ""

msgid ""
"Select one of these options to use the name or address of the client (i.e. "
"the workstation or thin client connected to the discovered remote desktop "
"session) as computer name."
msgstr ""

msgid "Hostname of session host"
msgstr "Hostnaam van sessie-host"

msgid ""
"Select this option to use the hostname of the remote desktop server (which "
"is hosting the discovered remote desktop session) as computer name."
msgstr ""

msgid "Environment variable"
msgstr "Omgevingsvariabele"

msgid ""
"Select this option to use the value of a certain environment variable in the"
" user session as computer name. The name of the environment variable has to "
"be specified."
msgstr ""

msgid "Registry key"
msgstr "Registersleutel"

msgid ""
"Select this option to use the value of a registry key as computer name. The "
"registry is read in the context of the logged in user so either a key in "
"``HKEY_CURRENT_USER`` or any other globally readable key can be read from."
msgstr ""

msgid ""
"For all data sources except for :guilabel:`IP address` and :guilabel:`DNS "
"name` Network Discovery establishes temporary connections to all discovered "
"computers to obtain the configured property. This slows down the scanning "
"process and sligtly increases CPU load on the hosts while being scanned."
msgstr ""

msgid ""
"Optionally computers whose names can't be resolved can be excluded from "
"being shown in Veyon Master."
msgstr ""

msgid ""
"Depending on the mode, discovered computers are shown in the *Discovered "
"computers* location or in locations named like the configured network ranges"
" groups. However it's possible to use other information to model locations "
"and map discovered computers to them. For this several alternative data "
"sources are available:"
msgstr ""

msgid "Extract from computer names"
msgstr "Afleiden uit computernamen"

msgid "See section :ref:`ExtractNamesViaRegEx` for details."
msgstr ""

msgid "Groups of logged-in users"
msgstr "Groepen ingelogde gebruikers"

msgid ""
"Select this option if users are organized in classes/courses and are members"
" of corresponding class/course groups. Then these class/course groups will "
"be used as locations. To only use these specific user groups (and filter out"
" unrelated user groups), you can configure a filter expression. Only groups "
"matching this filter expressions will be displayed as locations."
msgstr ""

msgid ""
"Select this option to use the value of a certain environment variable in the"
" user session as location name. The name of the environment variable has to "
"be specified."
msgstr ""

msgid ""
"Select this option to use the value of a registry key as location name. The "
"registry is read in the context of the logged in user so either a key in "
"``HKEY_CURRENT_USER`` or any other globally readable key can be read from."
msgstr ""

msgid "Extracting computer and location names via regular expressions"
msgstr ""

msgid ""
"Depending on the mode, discovered computers are shown in the *Discovered "
"computers* location or in locations named like the configured network ranges"
" groups. However if the hostnames also contain the room or location name, "
"you can let Network Discovery extract the location name and optionally also "
"the displayed computer name from the hostname. This is done by applying a "
"regular expression on the hostnames. The first capture group of the regular "
"expression is then used as location/computer name."
msgstr ""

msgid ""
"For example, if the hostnames have the format ``r<ROOM-NUMBER>-c<COMPUTER-"
"NUMBER>`` (e.g. ``r101-c01.example.org``), you can change the location data "
"source to :guilabel:`Extract from computer names` and use the following "
"regular expression to extract the location name:"
msgstr ""

msgid ""
"The same substring extraction is possible for computer names as well (except"
" for :guilabel:`Data source` is set to :guilabel:`IP address`). For the "
"example hostname scheme, a regular expression to extract the computer name "
"(i.e. strip location and domain name) would be:"
msgstr ""

msgid "``[^-]*-.([^.]*)*``"
msgstr "``[^-]*-.([^.]*)*``"

msgid ""
"The CLI module ``networkdiscovery`` allows scanning for computers at the "
"command line:"
msgstr ""
"Met de CLI-module ``networkdiscovery`` kunnen computers worden gescand via "
"de opdrachtregel:"

msgid ""
"This command scans either the subnets of the local host or the specified "
"subnets for computers running the Veyon Server."
msgstr ""
"Dit commando scant ofwel de subnetten van de lokale host of de opgegeven "
"subnetten op computers waarop de Veyon Server draait."
