{"id":8067,"date":"2026-10-18T11:39:11","date_gmt":"2026-10-18T08:39:11","guid":{"rendered":"https:\/\/support.withsecure.com\/?post_type=support_article&p=8067"},"modified":"2026-10-18T11:39:11","modified_gmt":"2026-10-18T08:39:11","slug":"unable-to-manage-or-import-a-new-linux-security-64-host-to-policy-manager-server-due-to-the-same-unique-id-uid-when-installing-it-in-the-virtual-environment-or-linux-containers","status":"publish","type":"support_article","link":"https:\/\/support.withsecure.com\/en\/support-articles\/unable-to-manage-or-import-a-new-linux-security-64-host-to-policy-manager-server-due-to-the-same-unique-id-uid-when-installing-it-in-the-virtual-environment-or-linux-containers\/","title":{"rendered":"Unable to manage or import a new Linux Security 64 host to Policy Manager Server due to the same unique ID (UID) when installing it in the virtual environment or Linux containers"},"content":{"rendered":"

Issue:<\/h3>\n

Unable to manage or import a new Linux Security 64 host to Policy Manager Server due to the same unique ID (UID) when installing it in the virtual environment or Linux containers<\/p>\n

Resolution:<\/h3>\n
WithSecurity Linux Security 64 derives the UID from the unique information provided by the hardware.
\u00a0<\/div>\n
Most virtualization platforms emulate the unique hardware information as well so every clone should be unique.<\/p>\n

This UID cannot be cleared or changed.<\/p>\n

Normally, the unique hardware ID can be seen with the following command:
# cat \/sys\/class\/dmi\/id\/product_uuid<\/i><\/div>\n

\u00a0<\/div>\n
Currently, there is no mechanism in Linux Security 64 to clear the UID as it comes from the operating system.<\/span><\/span>
\u00a0<\/div>\n
Having the same host identity for two different Linux Security 64 hosts affects the policy distribution and etc as it will force Policy Manager to generate policies every time the host connects, which also causes additional overhead on the server resources.<\/p>\n

Apart from that, you will not be able to identify the actual host if one host gets infected in that situation.<\/p>\n

Both hosts will initiate connections to the Policy Manager Server, the server will still be able to answer to them and the policy counter will be increased accordingly.<\/p>\n

For some cases, editing the virtualization configuration file could be considered for such environment.<\/p>\n

In case of VMware, you could refer to the following documentation on how exactly it is done.
\u00a0
https:\/\/kb.vmware.com\/s\/article\/1541<\/a><\/p>\n

In case of Hyper V virtual environment, there are some documentations below on how UUID could be changed in order to solve the duplication issue.<\/p>\n

https:\/\/docs.microsoft.com\/en-us\/answers\/questions\/450978\/is-it-possible-to-change-the-uuid-of-a-hyper-v-hos.html<\/a><\/p>\n

In case of container, you could consider to carry out the following steps that could possibly workaround the issue.<\/p>\n

1. Generate a new UUID within the container
2. Save it as file with \u201cuuidgen > filename\u201d
3. Mount the file to \u201c\/sys\/class\/dmi\/id\/product_uuid"
\u00a0 \u00a0 # mount –bind filename \/sys\/class\/dmi\/id\/product_uuid
4. Perform the reboot
5. Check the newly generated local "product_uuid"
6. Migrate this container to an host running another container with Linux Security 64\u00a0<\/em>
\u00a0
Note:<\/strong>
At the moment, installation of Linux Security 64 in the container is not officially tested and not supported.<\/span><\/span>\u00a0<\/span><\/span><\/div>\n","protected":false},"excerpt":{"rendered":"

Unable to manage or import a new Linux Security 64 host to Policy Manager Server due to the same unique ID (UID) when installing it in the virtual environment or Linux containers<\/p>\n","protected":false},"template":"","support_article_product":[106],"class_list":["post-8067","support_article","type-support_article","status-publish","hentry"],"acf":{"source_foreign_id":"000006178","source_version":1,"source_system":"salesforce","source_date_updated":"2026-10-18 08:39:11","import_hash":"52ce7dd948d68b672b46a39954280611b2fdfefa","vanilla_article_id":"","vanilla_url":"","vanilla_kb_id":"","vanilla_category_id":"","machine_translated":false,"reactions_helpful_yes":"","reactions_helpful_no":""},"_links":{"self":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/support_article\/8067","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/support_article"}],"about":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/types\/support_article"}],"wp:attachment":[{"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/media?parent=8067"}],"wp:term":[{"taxonomy":"support_article_product","embeddable":true,"href":"https:\/\/support.withsecure.com\/en\/wp-json\/wp\/v2\/support_article_product?post=8067"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}