Community
User Guides
Support
Community
Help Forums
English Forum
General
About our Community
General Discussion
News and Feedback
Products
F-Secure SAFE
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Other products
Beta programs
Feature Requests
Finnish Forum (Tukifoorumi)
Tuotteet Kotiin
F-Secure SAFE
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Muut tietoturvatuotteet
Support Articles
Language
English
Suomi
Deutsch
Français
日本語
Svenska
Dansk
Italiano
Nederlands
Norsk
Polski
中文 (繁體)
Products & Services
F-Secure TOTAL
F-Secure SAFE / Internet Security / Anti-Virus
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Other products
Common topics
User Guides
Support
Login
|
Register
Policy Manager identifies cloned virtual machines as identical machines and not registering as separate hosts - F-Secure Community
<main> <article class="userContent"> <p> </p>Policy Manager identifies cloned virtual machines as identical machines and not registering as separate hosts <h3>Symptoms </h3> <p>When deploying cloned virtual machines from a template, Policy Manager identifies them as identical machines even when each machine is configured to have unique accounts in Active Directory. The machines appear to have the same UID and setting the client installations deployment with the Randomise option does not solve the issue. </p> <h3>Diagnosis </h3> <p>The template may already have the UID specified. When you clone it, the new machines get the same UID. </p> <h3>Solution </h3> <ol><li> Install Client Security on a template with <strong>SMBIOS GUID</strong> selected. </li> <li> On the template, execute in Command Prompt: <code class="code codeInline" spellcheck="false">fsmautil resetuid randomguid</code>. <p><strong>Note:</strong> fsmautil utility can be found in <code class="code codeInline" spellcheck="false">F-Secure/common</code> folder. </p> </li> <li> Shutdown and save the template. </li> <li> Your template is ready and each cloned machine will get a new random GUID after first reboot. </li> </ol> </article> </main>