Import from Hyper-V / Node Related

• When you add a node by IP address/node name or import virtual machines from Hyper-V, error message appears asking for administrator privilege.
• Symptom
• When you add a node by IP address or node name on Windows operating systems (Windows Vista or later versions) that supports User Account Control (UAC), the following error message appears:
• Administrator privilege is required.
• If you import virtual machines from a Hyper-V Server that supports UAC and use a new Windows local user account available in the administrators group, the following error message appears:
• Check if the account has administrator permission for this Hyper-V Server.
• Solution
• This default Windows behavior is due to a UAC remote restriction. As a workaround, use a built-in administrator or a domain administrator or you can disable Remote UAC.
• You need to disable Remote UAC manually to add the node using the same account.
• Follow these steps:
1. Click Start, type regedit in the Search programs and files field, and press Enter.

   The Windows Registry Editor opens.

   Note: You may need to provide administrative credentials to open Windows Registry Editor.

2. Locate and click the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

3. From the Edit menu, click New, and then click DWORD (32-bit) Value.
4. Specify LocalAccountTokenFilterPolicy as the name for the new entry and then press Enter.
5. Right-click LocalAccountTokenFilterPolicy and then click Modify.
6. Specify 1 in the Value data field and then click OK.
7. Exit the Registry Editor.
8. For more information, refer article.

• Unable to remove hypervisor for a node.
• Symptom
• At present, removing the hypervisor function for a node is not supported.
• Solution
• As a workaround, delete the node and add again.

• No warning or pop-up message appears when you add a node to the Console that is managed by another Console.
• Symptom
• With the all-in-one UI in Arcserve UDP , you do not have multiple Arcserve UDP Consoles. As a result, you can move the Agent from one server to another only when the old Server is retired.
• Solution
• Moving the node from one Console that is already managed by another Console is a very rare scenario.
• Heartbeat of the VM is not detected in the given specified time.
• Symptom
• When the source node is Windows 2008 or below, the Assured Recovery fails due to Hyper-V 2016 issue and the following error message appears:
• cannot detect the heartbeat
• Solution
• You can change Hypervisor to other upgraded versions or use VMware.