Mengaktifkan pengumpulan atribut perangkat yang dapat dikonfigurasi
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Dokumen ini menunjukkan cara administrator dapat mengaktifkan Verifikasi Endpoint untuk mengumpulkan
atribut perangkat terperinci yang disebut atribut perangkat yang dapat dikonfigurasi, seperti
atribut metadata file, folder, dan biner; entri registry; dan
properti dalam plist.
Administrator dapat menggunakan atribut perangkat yang dapat dikonfigurasi ini untuk membuat tingkat
akses.
Di menu navigasi, klik Perangkat > Perangkat seluler & endpoint > Setelan > Universal.
Luaskan tab Konfigurasi Verifikasi Endpoint.
Dari panel Unit Organisasi, pilih unit organisasi Anda.
Bergantung pada jenis atribut perangkat yang dapat dikonfigurasi yang ingin dikumpulkan Verifikasi Endpoint, konfigurasikan setelan:
Untuk mengumpulkan atribut metadata file, folder, atau biner, lakukan hal berikut:
Di bagian Konfigurasi file atau folder, klik Tambahkan konfigurasi.
Di dialog Tambahkan konfigurasi, masukkan detail berikut:
Nama untuk konfigurasi.
Sistem operasi perangkat.
Jalur ke file, folder, atau biner.
Jika Anda memasukkan jalur untuk biner, pilih
Dapat dieksekusi.
Klik Tambahkan konfigurasi.
Untuk mengumpulkan atribut konfigurasi registry atau plist, lakukan hal berikut:
Di bagian Registry or plist configurations, klik Add configuration.
Di dialog Tambahkan konfigurasi, masukkan detail berikut:
Nama untuk konfigurasi.
Sistem operasi perangkat.
Jalur ke file registry atau plist.
Kunci (opsional untuk Windows):
Windows: subkunci registry, misalnya: IsClipboardSignalProducingFeatureAvailable.
Jika Anda tidak memasukkan nilai, nilai default akan digunakan.
macOS: kunci dalam file plist, yang dapat berupa angka, string, atau nilai boolean.
Anda juga dapat memberikan kunci bertingkat menggunakan . sebagai pemisah.
Misalnya, jika ada kamus B di dalam kamus A dan kamus B berisi string atau angka dengan kunci key1, kunci akhir akan menjadi A.B.key1.
Array didukung dengan cara berikut: A.B.key[0] atau A.B.key[1].C. Hanya indeks hard code yang didukung.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eEndpoint Verification can be configured to collect detailed device attributes, including metadata of files, folders, binaries, registry entries, and plist properties.\u003c/p\u003e\n"],["\u003cp\u003eAdministrators can leverage these collected device attributes to establish and manage access levels based on specific device configurations.\u003c/p\u003e\n"],["\u003cp\u003eConfiguration involves logging into the Google Admin console and navigating to the Endpoint Verification settings to add specific file, folder, binary, registry, or plist configurations.\u003c/p\u003e\n"],["\u003cp\u003eWhen configuring file, folder, or binary attribute collection, administrators must specify the path and, if applicable, indicate whether the item is executable, and respect the file size limit of 1GB.\u003c/p\u003e\n"],["\u003cp\u003eWhen configuring registry or plist attribute collection, administrators need to specify the path, and for Windows they may optionally input a subkey, while for macOS, nested keys in plists are supported using dot notation.\u003c/p\u003e\n"]]],[],null,["# Enable collection of configurable device attributes\n\nThis document shows how administrators can enable Endpoint Verification to collect\ngranular device attributes called *configurable device attributes*, such as\nmetadata attributes of files, folders, and binaries; registry entries; and\nproperties in a plist.\nAdministrators can use these configurable device attributes to create access\nlevels.\n\nBefore you begin\n----------------\n\n- [Deploy Endpoint Verification](/endpoint-verification/docs/deploying-with-admin-console).\n\n- [Install the Endpoint Verification helper app (version 2.11 or later)](/endpoint-verification/docs/deploying-with-admin-console#install-native-helper).\n\nConfigure the Endpoint Verification settings\n--------------------------------------------\n\nTo enable Endpoint Verification to collect the [device configuration attributes](/endpoint-verification/docs/device-information#configuration-attributes), do\nthe following:\n\n1.\n\n Log in to the **Google Admin console** by using your Google Workspace\n administrator account.\n\n [Log in to Google Admin console](https://admin.google.com/ac/devices/list)\n\n \u003cbr /\u003e\n\n2. In the navigation menu, click **Devices \\\u003e Mobile \\& endpoints \\\u003e Settings \\\u003e Universal**.\n\n3. Expand the **Endpoint Verification configuration** tab.\n\n4. From the **Organizational Units** pane, select your organization unit.\n\n | **Note:** If the organization unit that you selected is a child of a top-level organizational unit, then the settings that you configure will override the settings that were inherited from the top-level organizational unit.\n5. Depending on the type of configurable device attributes you want Endpoint Verification\n to collect, configure the settings:\n\n - **To collect metadata attributes of a file, folder, or binary, do the following:**\n\n 1. In the **File or folder configuration** section, click **Add configuration**.\n 2. In the **Add configuration** dialog, enter the following details:\n\n - Name for the configuration.\n - Operating system of the devices.\n - Path to the file, folder, or binary.\n\n | **Note:** The size of a file or a binary must be less than or equal to 1 GB.\n 3. If you entered the path for a binary, then select\n **Is executable**.\n\n 4. Click **Add configuration**.\n\n - **To collect registry or plist configuration attributes, do the following:**\n\n 1. In the **Registry or plist configurations** section, click **Add configuration**.\n 2. In the **Add configuration** dialog, enter the following details:\n\n - Name for the configuration.\n - Operating system of the devices.\n - Path to the registry or plist file.\n\n | **Note:** The size of a plist file must be less than or equal to 512 MB.\n - Key (optional for Windows):\n\n - Windows: a subkey of the registry, for example: `IsClipboardSignalProducingFeatureAvailable`.\n If you don't enter a value, then the default value is taken.\n\n - macOS: keys in the plist file, which can be a number, string, or a boolean value.\n You can also provide nested keys by using `.` as the delimiter.\n\n For example, if there is a dictionary B inside dictionary A and dictionary B contains a string or number with key `key1`, the final key would be `A.B.key1`.\n Arrays are supported in the following manner: `A.B.key[0]` or `A.B.key[1].C`. Only hard-coded indexes are supported.\n 3. Click **Add configuration**.\n\nWhat's next\n-----------\n\n- [Learn more about the configurable device attributes](/endpoint-verification/docs/device-information#configuration-attributes).\n- [Create device-based access levels](/endpoint-verification/docs/creating-device-access-level)."]]
