Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Dokumen ini membandingkan fitur kebijakan OS dari VM Manager dengan
fitur kebijakan tamu lama.
Tabel perbandingan
Fitur kebijakan OS dan kebijakan tamu (lama) merupakan bagian dari
rangkaian VM Manager, dan dapat diaktifkan dengan menyiapkan VM Manager.
Untuk informasi selengkapnya, lihat Menyiapkan VM Manager.
Namun, ada beberapa perbedaan di antara kedua opsi tersebut. Perbedaan ini
dirangkum dalam tabel berikut.
Kebijakan tamu (lama)
Kebijakan OS
Versi agen OS Config
Any
Versi bertanggal 20210427 atau lebih baru 1
Jenis resource2
Global
Zonal
Penerapan kebijakan dan kepatuhan didukung
Hanya penerapan
Peluncuran yang didukung 3
Laporan kepatuhan tersedia
Satu kebijakan dapat ditentukan untuk beberapa sistem operasi
Filter pengecualian tersedia saat memilih VM target
4Urutan langkah software hanya berjalan saat kebijakan tamu pertama kali dibuat.
Untuk menjalankan kembali urutan langkah software, Anda perlu menghapus dan membuat ulang kebijakan tamu.
Karena alasan ini, kebijakan OS menggunakan file yang dapat dieksekusi yang dapat
diperiksa dan diterapkan secara terus-menerus.
[[["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-08-19 UTC."],[[["\u003cp\u003eThis document contrasts VM Manager's OS policy feature with the legacy guest policy feature.\u003c/p\u003e\n"],["\u003cp\u003eBoth features are part of the VM Manager suite, but the OS policy requires a specific agent version (\u003ccode\u003e20210427\u003c/code\u003e or later), while the legacy guest policy works with any version.\u003c/p\u003e\n"],["\u003cp\u003eOS policy is zonal, whereas legacy guest policy is global.\u003c/p\u003e\n"],["\u003cp\u003eThe legacy guest policy only supports enforcement, while OS Policy is also able to provide policy compliance and rollout features.\u003c/p\u003e\n"],["\u003cp\u003eOS policies allow for more diverse use cases compared to legacy guest policies as they offer exclusion filters when selecting target VMs, as well as the ability to define a single policy for multiple operating systems.\u003c/p\u003e\n"]]],[],null,["# Compare OS policy versions\n\nThis document compares the OS policy feature of VM Manager with the legacy\nguest policy feature.\n\nComparison table\n----------------\n\nBoth the OS policy and guest policy (legacy) features are part of the\nVM Manager suite, and can be enabled by setting up VM Manager.\nFor more information, see [Set up VM Manager](/compute/vm-manager/docs/setup).\n\nHowever, there are a few differences between the two options. These differences\nare summarized in the following table.\n\n\n^1^To view agent version, see\n[View OS Config agent version](/compute/vm-manager/docs/upgrade-vm-manager#view-version).\n\n^2^For information about resource types, see\n[Global, regional, and zonal resources](/compute/docs/regions-zones/global-regional-zonal-resources).\n\n^3^For information about rollouts, see\n[Understanding rollouts](/compute/vm-manager/docs/os-policies/create-os-policy-assignment#rollouts).\n\n^4^A software recipe only runs when a guest policy is first created.\nTo rerun a software recipe, you would need to delete and recreate the guest policy.\nFor this reason, OS policy uses an executable that can be\ncontinuously checked and enforced.\n\n\u003cbr /\u003e\n\nWhat's next?\n------------\n\n- Learn more about [OS policies](/compute/vm-manager/docs/os-policies)."]]
