---
title: "Hyper-V: Installing a Nasuni Edge Appliance or NMC"
slug: "hyper-v-installing-a-nasuni-edge-appliance-or-nmc"
updated: 2026-06-09T15:24:24Z
published: 2026-06-09T15:24:24Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nasuni.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Hyper-V: Installing a Nasuni Edge Appliance or NMC

## Overview of Installing Nasuni on Microsoft Hyper-V

This chapter explains how to download the software and perform the initial installation of a Nasuni Edge Appliance or Nasuni Management Console (NMC) on a virtual platform.

For additional information on the initial configuration of a Nasuni Edge Appliance, see [Nasuni Edge Appliance Initial Configuration Guide](https://docs.nasuni.com/docs/initial-configuration-guide). For additional information on the initial configuration of the NMC, see [Nasuni Management Console Guide](https://docs.nasuni.com/docs/nasuni-management-console).

> [!CAUTION]
> *Warning:***IF YOU EVER NEED TO TRANSITION FROM ONE HYPERVISOR PLATFORM TO A DIFFERENT HYPERVISOR PLATFORM, DO NOT USE ANY OF THE MIGRATION TOOLS OF EITHER HYPERVISOR PLATFORM. INSTEAD, PERFORM A RECOVERY PROCEDURE, USING THE NEW HYPERVISOR PLATFORM AS THE DESTINATION. FOR DETAILS, SEE**[**NEA RECOVERY**](/v1/docs/nasuni-edge-appliance-recovery-guide-recovery)**OR**[**NMC RECOVERY GUIDE**](/v1/docs/nmc-recovery-guide-recovery)**.**

> [!CAUTION]
> *Warning:***DO NOT ATTEMPT TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP. ATTEMPTING TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP PUTS THE EDGE APPLIANCE IN AN UNKNOWN STATE IN RELATION TO THE NASUNI ORCHESTRATION CENTER (NOC), AND REQUIRES A DISASTER RECOVERY PROCESS TO BE RECOVERED. THIS MIGHT RESULT IN DATA LOSS.**

> [!WARNING]
> *Important: Installing third-party software on Nasuni appliances is not allowed.*

> [!TIP]
> *Tip: In the Nasuni model, customers provide their own cloud accounts for the storage of their data. Customers should leverage their cloud provider's role-based access and identity access management features as part of their overall security strategy. Such features can be used to limit or prohibit administrative access to the cloud account, based on customer policies.*

## Downloading Nasuni Edge Appliance or NMC Software

A Nasuni Edge Appliance or Nasuni Management Console (NMC) can run as a virtual appliance on your network and is distributed as a downloadable image. You need to register on the Nasuni Web site for a user account and password to access the download page.

To download Nasuni Edge Appliance or NMC software from the Nasuni Web site:

1. Log in to your Nasuni account Web site ( [https://portal.nasuni.com/](https://portal.nasuni.com/)) and click **Install Software**.

The **Installs**page appears. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-1DSY6BPL.png)
2. Select the appropriate format for your virtual environment from these choices:
  - **AMAZON EC2**: Follow the instructions to continue installation using appliance AMIs.
  - **AZURE FORMAT**: A .`vhd` file, appropriate for Microsoft Azure environments.
  - **GOOGLE CLOUD FORMAT**: A `disk.raw` file contained in a .`tar`.`gz` file, appropriate for Google Cloud environments.
  - **HYPER-V FORMAT**: Hyper-V format is appropriate for Microsoft Hyper-V environments:

versions 2019 and later.
  - **NUTANIX FORMAT**: A .`qcow2` file appropriate for Nutanix AHV environments.
  - **SCALE FORMAT**: A file appropriate for Scale HyperCore environments.
  - **OVF FORMAT**: OVF format is appropriate for VMware ESXi 7.0 and above environments.
3. From the drop-down list, select an available release for the Edge Appliance or NMC. The list of available releases can change.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-9m8p8dgb.png)

Sample release drop-down list.

> [!NOTE]
> *Note: If you are running a recovery procedure, select the same version family as your existing Edge Appliance to ensure software compatibility. For example, if the existing Edge*
> 
> *Appliance is running version 9.5.1, you could select version 9.5.4 (which is in the same 9.5.x version family), but not version 9.7.1 (which is in a different version family). If you need to use a different version than those offered, contact Nasuni Customer Support.*

> [!TIP]
> *Tip: For update paths, see*[Compatibility and Support.](/v1/docs/compatibility-support)

> [!NOTE]
> *Note: You can perform the Recovery process to the same version of the software that you were running, or to a newer version than you were running, but not to an older version.*

> [!NOTE]
> *Note: If you already have the software installation file, you do not have to download it again. However, the software installation file must not be older than the version you are recovering.*
4. Save the Nasuni Edge Appliance or NMC software .`zip` file to a location on your local drive.

The amount of time to download the Nasuni Edge Appliance software file depends on your Internet connection.

The amount of time to download the NMC software file depends on your Internet connection.
5. Unzip the Nasuni Edge Appliance or NMC software file.

## Installing a Nasuni Edge Appliance into Microsoft Hyper-V

You can run a Nasuni Edge Appliance in Microsoft Hyper-V. This section explains how to import a Nasuni Edge Appliance into Microsoft Hyper-V, which is included with Windows Server.

> [!CAUTION]
> *Warning:***NASUNI CIFS SHARES DO NOT SUPPORT STORING MICROSOFT HYPER-V SYSTEM FILES USING SMB 3 CONNECTIONS.**

> [!NOTE]
> *Note: You should install Microsoft Hyper-V before performing this procedure.*

> [!NOTE]
> *Note: Ensure that you have downloaded the appropriate version for your Microsoft Hyper-V environment, as in*[*step 2.*](/v1/docs/chapter-2-installing-a-nasuni-edge-appliance-or-nmc#G61000664000)

> [!WARNING]
> *Important: Edge Appliances and the NMC must be configured with operational DNS servers and a time server (internal or external) within your environment.*

> [!WARNING]
> *Important: Installing third-party software on Nasuni appliances is not allowed.*

> [!WARNING]
> ***Important****: Nasuni VMs require UEFI boot and no longer support legacy BIOS.*

> [!WARNING]
> *Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:*
> 
> *“Nasuni recommends running the Management Console on ESX 7.0 or later.”*

### Considerations for Microsoft Hyper-V

Hyper-V-based appliance installations are achieved by importing a copy of the virtual machine image. (See “[Downloading Nasuni Edge Appliance or NMC Software”.](/v1/docs/chapter-2-installing-a-nasuni-edge-appliance-or-nmc#downloading-nasuni-edge-appliance-or-nmc-software)) Because the settings and disks of the image remain in place after a successful deployment, many of these settings must be adjusted to suit the environment when deploying the virtual machine.

The settings that must be confirmed and adjusted include:

- Disabling virtual machine checkpoints.
- Setting a location for the Smart Paging File.
- Setting an appropriate amount of RAM allocated to the virtual machine.
  - Default: 8 GiB.
- Setting an appropriate number of virtual processors.
  - Default: 2 virtual processors.
- Reconfiguring the virtual machine’s NUMA architecture.
  - Default: 1 NUMA node.
- Adjusting the size of the Cache and Copy-On-Write disks.
  - Cache default: 250 GB.
  - COW default: 64 GB.
- Connecting the virtual network adapter to an appropriate virtual switch.
  - Default: Not connected.
- Upgrading the configuration version of the virtual appliance.
  - Default: 5.0.

### Deployment

Before deploying a Nasuni Edge Appliance virtual machine, ensure that any virtual switches to be used by the appliance are properly configured. For best performance, the network adapters assigned to the virtual switches should not be shared with the management operating system, and should have singleroot I/O virtualization (SR-IOV) enabled, where possible.

Ensure that you have downloaded and extracted the appropriate version of the Nasuni Edge Appliance software for your Hyper-V environment. See “[Downloading Nasuni Edge Appliance or NMC Software”.](/v1/docs/chapter-2-installing-a-nasuni-edge-appliance-or-nmc#downloading-nasuni-edge-appliance-or-nmc-software)

To install a Nasuni Edge Appliance into Microsoft Hyper-V Server:

1. Launch Hyper-V Manager.

The **Hyper-V Manager** opens. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-P4906C4I.png)
2. Click **Action**, then select **Import Virtual Machine** from the drop-down menu. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-VC9WSOQ7.png)

The **Import Virtual Machine** page appears. If the **Before You Begin** page appears, click **Next**.

The **Locate Folder** page appears. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-XTR2LVER.png)
3. Click **Browse** and navigate to the location of the unzipped Nasuni Edge Appliance software.

Select the `Filer` directory and click **Select Folder**.

The selected directory appears in the **Folder** text box. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-68MNSXW9.png)
4. Click **Next**.

The **Select Virtual Machine** page appears. “`Nasuni Filer`” should be highlighted. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-8XEZDCIO.png)
5. Click **Next**.

The **Choose Import Type** page appears. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-NQHOE33H.png)
6. Select “**Copy the virtual machine (create a new unique ID)**”, then click **Next**.

The “**Choose Folders for Virtual Machine Files**” page appears. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-9486K25N.png)
7. Either accept the default locations, or select the “**Store the virtual machine in a different location**” checkbox to select new file locations. Click **Next**.

> [!TIP]
> *Tip: If you install a Nasuni Edge Appliance to a location that is not the Windows default location, you might receive the “TestVM failed to start” error message. If so, remove and re-add the virtual hard drive using these steps:*
> 
> - *Run Hyper-V Manager.*
> - *Right-click the settings of the virtual machine.*
> - *Find the Virtual Hard Drive, and click “Remove”.*
> - *Re-add the same Virtual Hard Drive.*
> - *Restart the virtual machine. It should boot successfully.*

The “**Locate Virtual Hard Disks**” page appears. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-PQOKSOOV.png)
8. Click **Browse**, then navigate to the location where the virtual hard disks for the virtual machine are to be stored. Click **Next**. The “**Choose Folders to Store Virtual Hard Disks**” page appears. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-IDDE6MGL.png)
9. Either accept the default location, or click **Browse** to select a new location. Click **Next**. The “**Connect Storage**” page appears. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-E2ZVX1ED.png)
10. Select “**Use virtual hard disk**”, then click **Browse** and navigate to the configured virtual hard disk. Click **Next**. The “**Configure Memory**” page appears. Nasuni does not support Dynamic Memory. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-NLQ63G7K.png)
11. Specify the memory settings you want to use on the computer. Nasuni does not support Dynamic Memory. Click **Next**. The “**Completing Import Wizard**”****page appears. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-2ZJQG0Y7.png)
12. Review the selected settings. If any settings are incorrect, click **Previous** and change the settings. If all settings are correct, click **Finish**. The Nasuni Edge Appliance virtual machine is imported. This can take several minutes.

> [!WARNING]
> ***Important****: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:*
> 
> *“Nasuni recommends running the Management Console on ESX 7.0 or later.”*

After the import completes, the Nasuni Edge Appliance virtual machine appears in the **Virtual Machines** list as “`Nasuni Filer`”. ![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/image-NZ6DMV8Z.png)

The Nasuni Edge Appliance virtual machine is initially Off.

You can now continue with “[Configuring a Nasuni Edge Appliance”.](/v1/docs/chapter-2-installing-a-nasuni-edge-appliance-or-nmc#configuring-a-nasuni-edge-appliance)

### Configuring a Nasuni Edge Appliance

To configure the installation, follow these steps:

1. Launch Hyper-V Manager.

The **Hyper-V Manager** opens.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-cfzdwjij.png)

Hyper-V Manager.
2. To upgrade the configuration version, follow these steps:
  1. In the **Virtual Machines** list, locate the Nasuni Filer virtual machine, and right-click it.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-0ofvym4t.png)

Virtual Machines menu.
  2. From the drop-down menu, select **Upgrade Configuration Version**.

The **Upgrade Configuration Version** confirmation dialog box appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-i39i5j75.png)

Upgrade Configuration Version dialog box.
  3. Click **Upgrade**.

The configuration version is upgraded.
3. After the configuration version has upgraded, disable checkpoints by following these steps:

> [!WARNING]
> *Important: Nasuni strongly recommends disabling Hyper-V checkpoints (also called Hyper-V snapshots), because attempting to restore from a Hyper-V checkpoint can ruin the installation.*

> [!CAUTION]
> *Warning:***DO NOT ATTEMPT TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP.**
> 
> **ATTEMPTING TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP PUTS THE EDGE APPLIANCE IN AN UNKNOWN STATE IN RELATION TO THE NASUNI ORCHESTRATION CENTER (NOC), AND REQUIRES A DISASTER RECOVERY PROCESS TO BE RECOVERED. THIS MIGHT RESULT IN DATA LOSS.**
  1. In the **Virtual Machines** list, locate the Nasuni Filer virtual machine, and right-click it.
  2. From the drop-down menu, select **Settings**.

The **Settings** page appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-hdq9ffm6.png)

Settings page.
  3. In the left-hand pane, under the **Management** section, click **Checkpoints**.

The **Checkpoints** screen appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-4a2deqcp.png)

Checkpoints screen.
  4. Ensure that the “**Enable checkpoints**” checkbox is not selected.
  5. Click **Apply**, then click **OK**.
4. It is necessary to specify certain Integration Services in order to enable the hypervkvpd service to start on appliances.

> [!NOTE]
> *Note: If you skip this step, a Health Monitor message might appear stating that services are unhealthy.*

To specify Integration Services, follow these steps:
  1. In the **Virtual Machines** list, locate the Nasuni Filer virtual machine, and right-click it.
  2. From the drop-down menu, select **Settings**.

The **Settings**page appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-evm8b6oc.png)

Settings page.
  3. In the left-hand pane, under the **Management** section, click **Integration Services**.

The **Integration Services** screen appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-ulcgwou5.png)

Integration Services screen.
  4. Ensure that the “**Data Exchange**” and “**Guest Services**” checkboxes are selected.
  5. Click **Apply**, then click **OK**.
5. If you deployed a Nasuni Edge Appliance virtual machine with the default file location settings, to specify the location of the Smart Paging File, follow these steps:
  1. Right-click the Nasuni Filer virtual machine and click **Settings** from the drop-down menu.
  2. In the left-hand pane, under the Management section, click **Smart Paging File Location**.

The **Smart Paging File Location** screen appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-yg1v78e1.png)

“Smart Paging File Location” screen.
  3. Click **Browse** and navigate to a suitable location for the Smart Paging File.

This should be on a separate disk from the host’s operating system (usually C:).
  4. Click **Apply**, then click **OK**.
6. To connect the virtual network adapter to a virtual switch, follow these steps:
  1. Right-click the Nasuni Filer virtual machine and click **Settings** from the drop-down menu.
  2. In the left-hand pane, under the **Hardware** section, click **Network Adapter**.

The **Network Adapter** screen appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-aqbhzi42.png)

Network Adapter screen.
  3. From the **Virtual Switch** drop-down menu, select a suitable virtual switch.
  4. Click **Apply**, then click **OK**.
7. To specify the RAM memory to allocate to a Nasuni Edge Appliance, follow these steps:
  1. Right-click the Nasuni Filer virtual machine and click **Settings**.
  2. In the left-hand pane, under the **Hardware** section, click **Memory**.

The **Memory** screen appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-uwqv63el.png)

Memory screen.
  3. In the RAM text box, enter the amount of **RAM** (in megabytes) to allocate to a Nasuni Edge Appliance.
  4. Move the **Memory weight** slider to **High**.
  5. Click **Apply**, then click **OK**.
8. To specify the number of virtual processors to allocate to a Nasuni Edge Appliance, follow these steps:
  1. Right-click the Nasuni Filer virtual machine and click **Settings**.
  2. In the left-hand pane, under the **Hardware** section, click **Processor**.

The **Processor** screen appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-sc84nju9.png)

Processor screen.
  3. In the **Processor** area, select the **Number of virtual processors** to allocate to a Nasuni Edge Appliance.
  4. Click **Apply**, then click **OK**.
9. To configure NUMA topology, follow these steps:
  1. Right-click the Nasuni Filer virtual machine and click **Settings**.
  2. In the left-hand pane, under the Hardware section, click the + next to **Processor**, then click **NUMA**.

The **NUMA Configuration** screen appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-c9bu7gzb.png)

NUMA Configuration screen.
  3. At the bottom of the **NUMA Configuration** screen, click **Use Hardware Topology** to ensure proper virtual NUMA layout.
  4. Click **Apply**, then click **OK**.
10. To adjust the size of the cache and copy-on-write (COW) disks, follow these steps:
  1. Right-click the Nasuni Filer virtual machine and click **Settings**.
  2. In the left-hand pane, under the **Hardware** section, click the + next to the top **SCSIController**, then click **Hard Drive Cache.vhdx**.

The click **Hard Drive** screen appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-yef3bfk1.png)

Hard Drive screen.
  3. On the **Hard Drive** screen, in the Virtual hard disk area, click **Edit**.

The **Locate Virtual Hard Disk** page appears.
  4. Click **Next**.

The **Choose Action** page appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-sy1ctd5u.png)

Choose Action page.
  5. Select **Expand**, then click **Next**.

The **Expand Virtual Hard Disk** page appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-pdj7rgvz.png)

Choose Action page.
  6. Enter a **New size** (in gigabytes) for a Nasuni Edge Appliance cache disk, then click **Next**. The **Summary** page appears.

> [!WARNING]
> *Important: If multiple cache disks are provided before the first boot, Nasuni automatically provisions them as a striped set for best performance. Multiple cache disks must all be the same size, or the size of the smallest cache disk determines how much of each disk can be used. To add an additional cache disk after the first boot, contact Nasuni Support.*
  7. Review the settings, then click **Finish**.
  8. In the left-hand pane, under the **Hardware** section, click the + next to the next **SCSI Controller**, then click **Hard Drive Cow.vhdx**. The **Hard Drive** screen appears.
  9. On the **Hard Drive** screen, in the **Virtual hard disk** area, click **Edit**.

The **Locate Virtual Hard Disk** page appears.
  10. Click **Next**.

The **Choose Action** page appears.
  11. Select **Expand**, then click **Next**.

The **Expand Virtual Hard Disk** page appears.
  12. Calculate the size of the copy-on-write (COW) disk. The size of the COW disk should be 25 percent of the size of the Cache disk, up to 250 GB. COW disks that are smaller than 25 percent of the size of the cache disk and that are less than 250 GB result in a warning message. Enter the **New size** (in gigabytes) for a Nasuni Edge Appliance copy-on-write (COW) disk, then click **Next**. The **Summary** page appears.
  13. Review the settings, then click **Finish**.
  14. Click **Apply**, then click **OK**.
11. Nasuni recommends fixed disks for the cache disk and the COW disk. To convert the cache disk and COW disk specified in [step 10](/v1/docs/chapter-2-installing-a-nasuni-edge-appliance-or-nmc#G61000654894) to fixed disks, see ” [To convert a virtual hard disk”](https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ee941151(v=ws.10)#to-convert-a-virtual-hard-disk).

This completes the configuration procedure.

### Booting a Nasuni Edge Appliance

> [!WARNING]
> *Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:*
> 
> *“Nasuni recommends running the Management Console on ESX 7.0 or later.”*

1. Launch Hyper-V Manager.

The **Hyper-V Manager** opens.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-uh7wj0e7.png)

Hyper-V Manager.
2. In the **Virtual Machines** list, locate the Nasuni Filer virtual machine, and right-click it.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-jstfqj2s.png)

Virtual Machines menu.
3. From the drop-down menu, select **Start**.

The Nasuni Edge Appliance virtual machine starts.

> [!WARNING]
> *Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:*
> 
> *“Nasuni recommends running the Management Console on ESX 7.0 or later.”*
4. After a Nasuni Edge Appliance virtual machine starts, right-click the Nasuni Filer virtual machine again, and select **Connect** from the drop-down menu. The Nasuni Edge Appliance screen appears with a plain bar on the bottom that indicates the progress of the installation.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-tzx9iyq7.jpg)

Nasuni Edge Appliance installation progress screen.
5. After the initial installation completes, the Nasuni Edge Appliance console screen appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-1adu3cbu.png)

Nasuni Edge Appliance console screen.

> [!TIP]
> *Tip: The first boot of a Nasuni Edge Appliance might take slightly longer than subsequent boots.*
6. If DHCP is available on the network, make note of the “Assigned IP Address” that appears on the console screen. You use this IP address to access the Nasuni Edge Appliance user interface.

Alternatively, if DHCP is not available, log into the console service screen by pressing **Enter** and signing in. The default login username is `service`, and the default password is `service`.

> [!NOTE]
> *Note: For security, use the*`changepassword`*command to change the password for the service console.*
  1. Enter the command: `editnetwork`.
  2. Enter the command: `setall static`.
  3. Enter the following network information for the Nasuni Edge Appliance:
    1. IP Address: Note this IP address. You use this IP address to access a Nasuni Edge Appliance user interface.
    2. Netmask
    3. MTU
    4. Hostname
    5. Default Gateway
    6. DNS Servers
    7. Search Domain
  4. After all values have been confirmed, enter the `save` command to commit the new network details.
7. The Nasuni Edge Appliance is now installed and ready to access using the IP address. See the [Nasuni Edge Appliance Initial Configuration Guide](https://docs.nasuni.com/docs/initial-configuration-guide) for instructions on completing the configuration of the Nasuni Edge Appliance.

> [!TIP]
> *Tip: If you install a Nasuni Edge Appliance to a location that is not the Windows default location, you might receive the “TestVM failed to start” error message. If so, remove and re-add the virtual hard drive using these steps:*
> 
> - Run Hyper-V Manager.
> - Right-click the settings of the virtual machine.
> - Find the Virtual Hard Drive, and click “Remove”.
> - Re-add the same Virtual Hard Drive.
> - Restart the virtual machine. It should boot successfully.

> [!TIP]
> *Tip: To access the NEA or NMC appliance using the serial console, instead of using the IP address obtained when installing the appliance, follow one of these procedures:*
> 
> - If the appliance is running on Amazon EC2, see instructions in [EC2 Serial Console for Linux instances.](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-serial-console.html)
> - If the appliance is running on Google Cloud, see instructions in [Troubleshooting using the serial console.](https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-using-serial-console)
> - If the appliance is running on Microsoft Azure, see instructions in [Azure Serial Console.](https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/serial-console-overview)

All supported hypervisors include a serial console that works with Nasuni. For other hypervisors, consult your vendor’s documentation for connection instructions.

## Installing the NMC into Microsoft Hyper-V

You can run the Nasuni Management Console (NMC) in Microsoft Hyper-V. This section explains how to import the Nasuni Management Console (NMC) into Microsoft Hyper-V.

> [!NOTE]
> *Note: You should install Microsoft Hyper-V before performing this procedure.*

> [!NOTE]
> *Note: Ensure that you have downloaded the appropriate version for your Microsoft Hyper-V environment, as in*[*step 2.*](/v1/docs/chapter-2-installing-a-nasuni-edge-appliance-or-nmc#G61000664000)

> [!WARNING]
> *Important: Installing third-party software on Nasuni appliances is not allowed.*

> [!WARNING]
> *Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:*
> 
> *“Nasuni recommends running the Management Console on ESX 7.0 or later.”*

### Deploying the NMC into Hyper-V

Ensure that you have downloaded and extracted the appropriate version of the NMC for your Hyper-V environment. See “[Downloading Nasuni Edge Appliance or NMC Software”.](/v1/docs/chapter-2-installing-a-nasuni-edge-appliance-or-nmc#downloading-nasuni-edge-appliance-or-nmc-software)

To install the NMC into Microsoft Hyper-V Server:

1. Launch Hyper-V Manager.

The **Hyper-V Manager** opens.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-r9es0fnb.png)

Hyper-V Manager.
2. Click **Action**, then select **Import Virtual Machine** from the drop-down menu.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-tltj1qgz.png)

Action menu.

The **Import Virtual Machine** page appears. If the **Before You Begin** page appears, click **Next**.

The **Locate Folder** page appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-qeat4ph9.png)

“Locate Folder” page.
3. Click **Browse** and navigate to the location of the unzipped NMC software. (See “[Downloading Nasuni Edge Appliance or NMC Software”](/v1/docs/chapter-2-installing-a-nasuni-edge-appliance-or-nmc#downloading-nasuni-edge-appliance-or-nmc-software).) Select the `NMC` directory and click Select Folder.

The selected directory appears in the Folder text box.
4. Click **Next**.

The **Select Virtual Machine** page appears. “`Nasuni Management Console`” should be highlighted.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-z6i1b4tb.png)

“Select Virtual Machine” page.
5. Click **Next**.

The **Choose Import Type** page appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-0ncmcgw8.png)

“Choose Import Type” page.
6. Select “**Copy the virtual machine (create a new unique ID)**”, then click Next. The “Choose Folders for Virtual Machine Files” page appears.
7. Either accept the default locations, or select the “**Store the virtual machine in a different location**” checkbox and select new file locations. Click **Next**.

The “**Choose Folders to Store Virtual Hard Disks**” page appears.
8. Either accept the default location, or click **Browse** to select a new location. Click **Next**.

The **Completing Import Wizard** page appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-hki1rj75.jpg)

“Completing Import Wizard” page.
9. Review the selected settings. If any settings are incorrect, click **Previous** and change the settings. If all settings are correct, click **Finish**. The Nasuni Management Console virtual machine is imported. This can take several minutes.

> [!WARNING]
> *Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:*
> 
> *“Nasuni recommends running the Management Console on ESX 7.0 or later.”*

After the import completes, the Nasuni Management Console virtual machine appears in the **Virtual Machines** list as “`Nasuni Management Console`”.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-cp4immjq.png)

“Nasuni Management Console” entry in Virtual Machines list.

You can now continue with “[Configuring the Nasuni Management Console (NMC)”](/v1/docs/chapter-2-installing-a-nasuni-edge-appliance-or-nmc#configuring-the-nasuni-management-console-nmc).

### Configuring the Nasuni Management Console (NMC)

To configure the NMC installation, follow these steps:

1. Launch Hyper-V Manager.

The **Hyper-V Manager** opens.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-f1dhb2ie.png)

Hyper-V Manager.
2. To upgrade the configuration version, follow these steps:
  1. In the **Virtual Machines** list, locate the Nasuni Management Console virtual machine, and right-click it.
  2. From the drop-down menu, select **Upgrade Configuration Version**.

The **Upgrade Configuration Version** confirmation dialog box appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-feb58g2p.png)

Upgrade Configuration Version dialog box.
  3. Click **Upgrade**.

The configuration version is upgraded.
3. After the configuration version has upgraded, disable checkpoints by following these steps:

> [!WARNING]
> *Important: Nasuni strongly recommends disablingHyper-V checkpoints (also called Hyper-V snapshots), because attempting to restore from a Hyper-V checkpoint can ruin the installation.*

> [!CAUTION]
> *Warning:***DO NOT ATTEMPT TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP.**
> 
> **ATTEMPTING TO RESTORE FROM A VIRTUAL MACHINE SNAPSHOT OR BACKUP PUTS**
> 
> **THE VIRTUAL MACHINE IN AN UNKNOWN STATE IN RELATION TO THE NASUNI ORCHESTRATION CENTER (NOC), AND REQUIRES A RECOVERY PROCESS TO BE RECOVERED. THIS MIGHT RESULT IN DATA LOSS.**
  1. In the **Virtual Machines** list, locate the Nasuni Management Console virtual machine, and right-click it.
  2. From the drop-down menu, select **Settings**. The **Settings** page appears.
  3. In the left-hand pane, under the **Management** section, click **Checkpoints**. The **Checkpoints** screen appears.
  4. Ensure that the “**Enable checkpoints**” checkbox is not selected.
  5. Click **Apply**, then click **OK**.
4. It is necessary to specify certain Integration Services in order to enable the hypervkvpd service to start on appliances.

> [!NOTE]
> *Note: If you skip this step, a Health Monitor message might appear stating that services are unhealthy.*

To specify Integration Services, follow these steps:
  1. In the **Virtual Machines** list, locate the Nasuni Management Console virtual machine, and right-click it.
  2. From the drop-down menu, select **Settings**.

The **Settings** page appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-djgiqj8d.png)

Settings page.
  3. In the left-hand pane, under the **Management** section, click **Integration Services**.

The **Integration Services** screen appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-6spb20t0.png)

Integration Services screen.
  4. Ensure that the “**Data Exchange**” and “**Guest Services**” checkboxes are selected.
  5. Click **Apply**, then click **OK**.
5. If you deployed the Nasuni Management Console virtual machine with the default file location settings, to specify the location of the Smart Paging File, follow these steps:
  1. Right-click the Nasuni Management Console virtual machine and click Settings from the drop-down menu.
  2. In the left-hand pane, under the **Management** section, click **Smart Paging File Location**. The **Smart Paging File Location** screen appears.
  3. Click **Browse** and navigate to a suitable location for the Smart Paging File.

This should be on a separate disk from the host’s operating system (usually C:).
  4. Click **Apply**, then click **OK**.
6. To connect the virtual network adapter to a virtual switch, follow these steps:
  1. Right-click the Nasuni Management Console virtual machine and click **Settings** from the drop-down menu.
  2. In the left-hand pane, under the **Hardware** section, click **Network Adapter**. The **Network Adapter** screen appears.
  3. From the **Virtual Switch** drop-down menu, select a suitable virtual switch.
  4. Click **Apply**, then click **OK**.

This completes the configuration procedure.

### Booting the Nasuni Management Console

> [!WARNING]
> *Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:*
> 
> *“Nasuni recommends running the Management Console on ESX 7.0 or later.”*

1. Launch Hyper-V Manager.

The **Hyper-V Manager** opens.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-2e97uzyj.png)

Hyper-V Manager.
2. In the **Virtual Machines** list, locate the Nasuni Management Console virtual machine, and rightclick it.
3. From the drop-down menu, select **Start**.

The Nasuni Management Console virtual machine starts.

> [!WARNING]
> *Important: When using virtual machine Edge Appliances or NMCs, Nasuni recommends running under a hypervisor that is still supported by its vendor. If a customer runs an Edge Appliance or NMC on an unsupported hypervisor version, a warning is logged at boot time. The warning is of the form:*
> 
> *“Nasuni recommends running the Management Console on ESX 7.0 or later.”*
4. After the Nasuni Management Console virtual machine starts, right-click the Nasuni Management Console virtual machine again, and select **Connect** from the drop-down menu. The Nasuni Management Console screen appears with a plain bar on the bottom that indicates the progress of the installation.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-p2zjtfs9.png)

Nasuni Management Console installation progress screen.
5. After the initial installation completes, the Nasuni Management Console console screen appears.

![](https://cdn.document360.io/2adf6ce2-c120-4520-b135-0fc4463ddde3/Images/Documentation/chapter-1-platform-considerations-image-cpkxdmhn.png)

Nasuni Management Console console screen.

> [!TIP]
> *Tip: The first boot of a Nasuni Management Console might take slightly longer than subsequent boots.*
6. If DHCP is available on the network, make note of the “Assigned IP Address” that appears on the console screen. You use this IP address to access the Nasuni Management Console user interface.

Alternatively, if DHCP is not available, log into the console service screen by pressing Enter and signing in. The default login username is `service`, and the default password is `service`.

> [!NOTE]
> *Note: For security, use the*`changepassword`*command to change the password for the service console.*
  1. Enter the command: `editnetwork`.
  2. Enter the command: `setall static`.
  3. Enter the following network information for the Nasuni Management Console:
    1. IP Address: Note this IP address. You use this IP address to access the Nasuni Management Console user interface.
    2. Netmask
    3. MTU
    4. Hostname
    5. Default Gateway
    6. DNS Servers
    7. Search Domain
  4. After all values have been confirmed, enter the `save` command to commit the new network details.
7. The Nasuni Management Console is now installed and ready to access using the IP address. See the [Nasuni Management Console Guide](https://docs.nasuni.com/docs/nasuni-management-console) for instructions on completing the configuration of the Nasuni Management Console.

> [!TIP]
> *Tip: To access the NEA or NMC appliance using the serial console, instead of using the IP address obtained when installing the appliance, follow one of these procedures:*
> 
> - If the appliance is running on Amazon EC2, see instructions in [EC2 Serial Console for Linux instances.](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-serial-console.html)
> - If the appliance is running on Google Cloud, see instructions in [Troubleshooting using the serial console.](https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-using-serial-console)
> - If the appliance is running on Microsoft Azure, see instructions in [Azure Serial Console.](https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/serial-console-overview)

All supported hypervisors include a serial console that works with Nasuni. For other hypervisors, consult your vendor’s documentation for connection instructions.