# 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:
# Peeter Ramst <peeter.ramst@aste.edu.ee>, 2024
# Peeter Ramst <peeter@aste.edu.ee>, 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: Peeter Ramst <peeter@aste.edu.ee>, 2024\n"
"Language-Team: Estonian (https://app.transifex.com/veyon-solutions/teams/65452/et/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: et\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

msgid "Deployment"
msgstr "Kasutuselevõtt"

msgid "Initial steps"
msgstr "Esialgsed sammud"

msgid "Install Veyon on the reference/teacher computer"
msgstr "Installige Veyon tugi-/õpetaja arvutisse"

msgid "Install Veyon Add-ons on the reference/teacher computer"
msgstr "Installige Veyoni lisandmoodulid viite-/õpetaja arvutisse"

msgid "Import the purchased license file(s)"
msgstr "Importige ostetud litsentsifail(id)"

msgid "Make changes to the configuration as desired"
msgstr "Tehke konfiguratsioonis soovitud muudatused"

msgid "Export the configuration"
msgstr "Ekspordi konfiguratsioon"

msgid "Automated/silent installation"
msgstr "Automaatne / vaikne paigaldus"

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 ""
"Nagu Veyon ise, saab lisandmooduleid installida ka *vaikses režiimis*, "
"edastades parameetri ``/S`` ja valikuliselt ``/D=...``. Üksikasju vaadake "
"administraatori juhendi peatükist :ref:`Automaatne installimine`."

msgid "Deploying licenses"
msgstr "Litsentside kasutuselevõtt"

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 ""
"Kuna kõik litsentsid on osa Veyoni konfiguratsioonist, saab neid hõlpsasti "
"juurutada, kasutades installimise ajal konfiguratsiooni importimiseks "
":ref:`tuntud mehhanisme <InstallationConfigurationImport>`. Litsentse "
"sisaldavat konfiguratsiooni saab juba importida/rakendada, kui "
"lisandmoodulid pole veel installitud. See paneb lisandmoodulid koheselt "
"tööle, kui need hiljem installitakse."

msgid "Entra ID Connector"
msgstr "Entra ID pistik"

msgid "General"
msgstr "Üldine"

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 ""
"Veyon Entra ID Connectori lisandmoodul laiendab Veyon Masterit, et lugeda "
"seadmeid ja nende asukohta Entra ID eksemplarist. Pärast seadistamist ei pea"
" arvuteid ja asukohti enam sisseehitatud võrguobjektide kataloogis "
"säilitama. Varem konfigureeritud LDAP/ActiveDirectory integratsiooni saab "
"asendada Entra ID konnektoriga pärast On Premise ActiveDirectory "
"migreerimist Entra ID-le Azure'i pilves."

msgid "Initial setup"
msgstr "Algseadistus"

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 ""
"Kui installimine on lõppenud, näete Veyon Configurator programmis mõnda uut "
"konfiguratsioonilehte. Üks neist kannab nime :guilabel: :guilabel:`Entra ID "
"Connector` ja võimaldab seadistada lisandmooduli:"

msgid "Entra ID Connector configuration page"
msgstr "Entra ID Connectori konfiguratsioonileht"

msgid "App registration"
msgstr "Rakenduse registreerimine"

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 ""
"Nõutavate väljade täitmiseks tuleb konnektor esmalt registreerida teie Entra"
" ID eksemplaris. Selleks avage veebibrauser ja minge Azure'i portaalis Entra"
" ID haldusalale. Siin saate Veyon Entra ID Connectori rakendusena "
"registreerida:"

msgid "App registration of the Veyon Entra ID Connector – Step 1"
msgstr "Veyon Entra ID konnektori rakenduse registreerimine – 1. samm"

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 ""
"Klõpsates :guilabel:`Uus registreerimine` avaneb uus dialoog, kuhu tuleb "
"sisestada sobiv nimi, nt. *Veyon Entra ID Connector* ja klõpsake nuppu "
":guilabel:`Registreeri`:"

msgid "App registration of the Veyon Entra ID Connector – Step 2"
msgstr "Veyon Entra ID konnektori rakenduse registreerimine – 2. samm"

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 "Veyon Entra ID konnektori rakenduse registreerimine – 3. samm"

msgid "Client secrets"
msgstr "Kliendi salad"

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 ""
"Järgmisena tuleb konfigureerida kliendi saladus või sertifikaat, millega "
"Entra ID Connector saab end Azure'i pilves autentida. Avage leht "
":guilabel:`Sertifikaadid ja saladused` ja klõpsake :guilabel:`Uus kliendi "
"saladus`. Andke saladusele nimi ja täpsustage, millal see aegub. Ärge valige"
" liiga lühikest perioodi, kuna peate looma uue saladuse ja Veyoni uuesti "
"konfigureerima iga kord, kui kliendi saladus on aegunud:"

msgid "Create client secret for the Veyon Entra ID Connector – Step 1"
msgstr "Veyon Entra ID konnektori kliendisaladuse loomine – 1. samm"

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 ""
"Pärast kliendi saladuse loomist peate kopeerima selle väärtuse Veyoni "
"konfiguraatoris väljale :guilabel:`Kliendi saladus`."

msgid "Create client secret for the Veyon Entra ID Connector – Step 2"
msgstr "Veyon Entra ID konnektori kliendisaladuse loomine – 2. samm"

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 ""
"Kliendi saladuse väärtus tuleb kohe kopeerida, kuna seda näidatakse ainult "
"üks kord vahetult pärast kliendisaladuse loomist. Kui unustasite selle "
"kopeerida, peate saladuse kustutama ja looma uue."

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 ""
"Nüüd saate kontrollida, kas rentniku ID, rakenduse ID ja kliendi saladus on "
"õiged, klõpsates nuppu :guilabel:`Testi juurdepääsu`."

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 ""
"Hea alternatiiv kliendisaladustele on kliendisertifikaadid. See võimaldab "
"salvestada saladust kindlasse kohta, kus saate vastavalt soovile "
"juurdepääsuõigusi määrata. Muidu kliendi saladus salvestatakse "
"(krüpteeritakse) Veyoni konfiguratsiooni osana."

msgid "API permissions"
msgstr "API-õigused"

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 ""
"Viimaseks oluliseks ülesandeks on registreeritud rakenduse õiguste "
"seadistamine, et Entra ID konnektor saaks lugeda Entra ID-st vajalikku "
"teavet. Liikuge lehele :guilabel:`API õigused` klõpsake nuppu "
":guilabel:`Lisa luba` ja valige :guilabel:`Microsoft Graph`:"

msgid "Set up permissions for the Veyon Entra ID Connector – Step 1"
msgstr "Seadistage Veyon Entra ID konnektori load – 1. samm"

msgid ""
"Now the actual permissions have to be selected. Select "
":guilabel:`Application permissions`, search for the *Device.Read.All* "
"permission and check it:"
msgstr ""
"Nüüd tuleb valida tegelikud load. Valige :guilabel:`Rakenduse õigused`, "
"otsige *Seade.Loe.Kõik* luba ja kontrollige seda:"

msgid "Set up permissions for the Veyon Entra ID Connector – Step 2"
msgstr "Seadistage Veyon Entra ID konnektori load – 2. samm"

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 ""
"Korrake seda sammu õiguste *Grupp.Loe.Kõik*, *Grupiliige.Loe.Kõik* ja "
"*Kasutaja.Loe.Kõik* jaoks. Pärast kõigi nõutavate õiguste kontrollimist "
"klõpsake :guilabel:`Lisa õigused`."

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 ""
"Viimane samm on nende lubade jaoks administraatori nõusoleku andmine. Seda "
"saab hõlpsasti teha, klõpsates :guilabel:`Anna administraatori nõusolek "
"<YOUR-ORGANIZATION>`:"

msgid "Set up permissions for the Veyon Entra ID Connector – Step 3"
msgstr "Seadistage Veyon Entra ID konnektori load – 3. samm"

msgid "Filters"
msgstr "Filtrid"

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 ""
"Vaadake jaotist `Filtriavaldistes toetatud operaatorid ja funktsioonid "
"<https://learn.microsoft.com/en-US/graph/filter-query-"
"parameter?tabs=http#operators-and-functions-supported-in-filter-expressions>"
" `_ lisateabe saamiseks."

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 "Asukohad"

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 "Kasutage seadmerühmi"

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 "Kasutage seadme asukoha atribuuti"

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 "Väljavõte hostinimest regulaaravaldise kaudu"

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 ""
"Esimene jäädvustamine (sulgudes) jäädvustab kõike kuni esimese "
"miinusmärgini, nii et Veyon Masteris kuvatakse asukoht ``r101``."

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 ""
"Mõiste, süntaksi ja saadaolevate mustrivalikute kohta lisateabe saamiseks "
"vaadake `Vikipeedia artiklit regulaaravaldiste kohta "
"<https://en.wikipedia.org/wiki/Regular_expression>`_."

msgid "Completion"
msgstr "Lõpetamine"

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 ""
"Lõpuks tuleb võrguobjekti kataloogi taustaprogrammiks muuta *Entra ID "
"Connector*, et Veyon Master tegelikult kasutaks Entra ID Connectori "
"lisandmoodulit."

msgid "Change network object directory backend to Entra ID Connector"
msgstr "Muutke võrguobjekti kataloogi taustaprogrammiks Entra ID Connector"

msgid ""
"Now you can start Veyon Master and should see the locations and computers "
"from your Entra ID directory."
msgstr ""
"Nüüd saate käivitada Veyon Masteri ja peaksite nägema asukohti ja arvuteid "
"oma Entra ID kataloogist."

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 "Veyoni lisandmoodulite integreerimise juhend"

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

msgid "Internet Access Control"
msgstr "Interneti juurdepääsu juhtimine"

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 ""
"Veyon Internet Access Controli lisandmoodul võimaldab blokeerida kogu klassi"
" või üksikute arvutite juurdepääsu Internetile sellistes olukordades nagu "
"eksamid. Interneti-juurdepääs blokeeritakse kliendipoolselt erinevate "
"taustaprogrammide pakutavate mehhanismide abil."

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 ""
"Kui installimine on lõppenud, näete Veyon Configurator programmis mõnda uut "
"konfiguratsioonilehte. Üks neist kannab nime :guilabel: `Interneti "
"juurdepääsu kontroll` ja võimaldab seadistada lisandmooduli:"

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 ""
"Nüüd saate käivitada Veyon Masteri ja klõpsata nuppu :guilabel:`Interneti-"
"juurdepääs`, et avada menüü koos :guilabel:`Interneti-juurdepääsu "
"blokeerimise` ja :guilabel:`Interneti-juurdepääsu blokeeringu "
"tühistamisega`. Pärast üksuse :guilabel:`Blokeeri Interneti-juurdepääs` "
"aktiveerimist ei tohiks valitud arvuti(te) kasutajad enam Internetis "
"veebisaiti avada. Kui need on endiselt olemas, kontrollige seadeid ja "
"proovige võib-olla mõnda muud blokeerimisrežiimi või taustaprogrammi."

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 "Interneti blokeerimine süsteemi tulemüüri kaudu"

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 "Blokeerige TCP-portide kogu väljaminev liiklus"

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 "Blokeerige kogu väljaminev liiklus välistele alamvõrkudele"

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 "Blokeeri liiklus (näit puhverserver või DNS) serveritesse"

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 "Luba eelkonfigureeritud tulemüüri reegel"

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 "Internetiühenduse blokeerimine marsruutimistabeli muutmisega"

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 "Litsenseerimine"

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 ""
"Kõik Veyoni kaubanduslikud lisad nõuavad kehtivat litsentsi. Litsents kehtib"
" konkreetse lisandmooduli ja teatud installi ID jaoks. Unikaalne installi ID"
" luuakse Veyoni esmakordsel installimisel ja see on osa programmi "
"konfiguratsioonist. Installi ID-d ei tohiks kunagi muuta nt. muutes "
"konfiguratsiooni JSON-faili, kuna see ei tööta enam teie litsentsitud "
"lisandmoodulitel."

msgid "Installing a license"
msgstr "Litsentsi installimine"

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 ""
"Pärast ühe või mitme litsentsifaili saamist saab need installida Veyon "
"Configuratori konfiguratsioonilehe :guilabel:`Licensing` kaudu. "
"Litsentsifaili valimiseks ja importimiseks klõpsake nuppu :guilabel:`+`. "
"Pärast edukat importi kuvatakse litsentsid ja lisateave tabelis. Imporditud "
"litsentside püsivaks salvestamiseks klõpsake nuppu :guilabel:`Rakenda`."

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 ""
"Litsentsitud lisandmoodulitele juurdepääsu saamiseks peate taaskäivitama "
"kõik Veyoniga seotud programmikomponendid. Tavaliselt piisab Veyon "
"Configuratori taaskäivitamisest, kuna esmalt peate niikuinii uued lisad "
"konfigureerima."

msgid "Transferring installed licenses to other computers"
msgstr "Installitud litsentside ülekandmine teistele arvutitele"

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 ""
"Kui soovite kasutada Veyon Masterit koos lisandmoodulitega teistes "
"arvutites, peate litsentsid neile üle kandma. Saate seda hõlpsalt teha, "
"eksportides konfiguratsiooni arvutisse, kuhu litsentsid importisite. "
"Eksporditud konfiguratsioon sisaldab seejärel nii installi ID-d kui ka "
"imporditud litsentse. Soovi korral saab seda importida kõikidesse "
"klientarvutitesse. Vaadake üksikasju administraatori käsiraamatu peatükist "
":ref:`ConfImportExport`."

msgid "Command line interface"
msgstr "Käsurea liides"

msgid ""
"There's a CLI module ``licensing`` which allows managing licenses at the "
"command line:"
msgstr ""
"Seal on CLI-moodul ``litsentsimine``, mis võimaldab hallata litsentse "
"käsureal:"

msgid ""
"This command imports the license in the given file into the local "
"configuration."
msgstr "See käsk impordib antud faili litsentsi kohalikku konfiguratsiooni."

msgid "This command shows details on all installed licenses."
msgstr "See käsk näitab kõigi installitud litsentside üksikasju."

msgid "This command removes the license with the specified ID."
msgstr "See käsk eemaldab määratud ID-ga litsentsi."

msgid "Network Discovery"
msgstr "Võrgu avastamine"

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 ""
"Veyon Network Discovery lisandmoodul laiendab Veyon Masterit, et skannida "
"konfigureeritud võrke arvutite jaoks, milles töötab üks või mitu Veyon "
"Serveri eksemplari. Kõik avastatud arvutid ja RDP seansid kuvatakse koheselt"
" paneelil Asukohad ja arvutid. Pärast seadistamist ei pea enam arvuteid ja "
"asukohti säilitama sisseehitatud võrguobjektide kataloogis ega "
"konfigureerima LDAP/ActiveDirectory integratsiooni. Viimaseks, kuid mitte "
"vähem tähtsaks, sobib lisand suurepäraselt DHCP-põhistele võrkudele, kus "
"arvutite IP-aadressid pidevalt muutuvad."

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 ""
"Kui installimine on lõppenud, näete Veyon Configurator programmis mõnda uut "
"konfiguratsioonilehte. Üks neist kannab nime :guilabel:`Network discovery` "
"ja võimaldab seadistada lisandmooduli:"

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 ""
"Saate alustada vaikesätetega, kui arvuti alamvõrk on piisavalt väike, st "
"IPv4 eesliide on ``/24`` või alamvõrgu mask on ``255.255.255.0``. Suuremate "
"alamvõrkude puhul on soovitatav muuta režiim :guilabel:`Scan network ranges`"
" ja lisada testimiseks võrguvahemikuga rühm (võtke IP-aadressid oma "
"keskkonda):"

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 ""
"Lõpuks tuleb võrguobjekti kataloogi taustaprogrammi muuta *Network "
"discovery*, et Veyon Master tegelikult kasutaks võrgutuvastuse "
"lisandmoodulit."

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 ""
"Nüüd saate käivitada Veyon Masteri ja peaksite nägema oma võrgus olevaid "
"arvuteid, kus töötab Veyon Server. Sõltuvalt alamvõrgu või võrguvahemiku "
"suuruses(st) võib esialgne skannimine võtta veidi aega (halvimal juhul kuni "
"1–2 minutit)."

msgid "Options"
msgstr "Valikud"

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 ""
"Pärast soovitud alamvõrkude või võrguvahemike konfigureerimist võite hakata "
"kohandama arvutite kontrollimise valikuid, et vähendada esialgset "
"kontrollimise kestust."

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 ""
"Enamikul juhtudel saate :guilabel:`paralleelsete skannimiste` arvu "
"suurendada 100–300-ni. Veyon Master avab paralleelselt määratud arvu TCP-"
"ühendusi, seega veenduge, et te ei ammendaks arvuti ressursse ega "
"operatsioonisüsteemi seatud protsessipõhiseid ressursipiiranguid."

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 ""
"Kui kõik arvutid on samas LAN-is (st pingi ajad on tavaliselt alla 1 ms), "
"saate :guilabel:`scan timeout`i ka vähendada 25–100 ms-ni. Iga selle ajalõpu"
" jooksul reageeriv arvuti kuvatakse Veyon Masteris."

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 ""
"Skannimise ajalõpuga 25 ms ja 250 paralleelse skaneerimisega suudab Veyon "
"skannida ``25*250=6250`` arvutit sekundis. Selle valemi abil saate hõlpsalt "
"arvutada oma keskkonna jaoks ideaalsed sätted, nii et Veyon Master ei nõua "
"skannimiseks liiga kaua aega, tuvastades samal ajal kõik arvutid "
"usaldusväärselt."

msgid "Sessions"
msgstr "Sessioonid"

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 "Arvutinimed"

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 ""
"Windowsis tuleks WINS-i pärandlahutus NetBIOS-i kaudu keelata, et vältida "
"probleeme, mille puhul NetBIOS-i hostinimi ei kattu täpselt DNS-i "
"hostinimega (eriti kuna NetBIOS-i hostinimed koosnevad alati ainult "
"suurtähtedest, tegelikud DNS-i hostinimed tavaliselt mitte). Kui NetBIOS on "
"lubatud, võib Network Discovery igal skannimisel/värskendusel saada "
"operatsioonisüsteemilt juhuslikult muutuvaid hostinimetüüpe (teatud IP-"
"aadressi jaoks). See põhjustab pidevaid taasühendamisi arvutitega, kuna "
"Veyoni arvates on iga kord avastatud erinev arvuti."

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 "Seansi hosti hostinimi"

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 "Keskkonnamuutuja"

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 "Registrivõti"

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 "Väljavõte arvutinimedest"

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

msgid "Groups of logged-in users"
msgstr "Sisselogitud kasutajate rühmad"

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 ""
"CLI-moodul ``networkdiscovery`` võimaldab arvutite otsimist käsurealt:"

msgid ""
"This command scans either the subnets of the local host or the specified "
"subnets for computers running the Veyon Server."
msgstr ""
"See käsk kontrollib kas kohaliku hosti alamvõrke või Veyoni serverit "
"kasutavate arvutite määratud alamvõrke."
