Deploy NetSpeek Edge in VMware Fusion as OVF
Before you begin ensure you have VMware Fusion installed.
1. Create a Custom Virtual Machine
- Open VMware Fusion.
- Click the + > New… option
- In the installation method screen, select “Import an existing virtual machine”. You’ll be met with a finder window
- You’ll be met with this view. Click “Choose File” and select the ovf file we provide you with. Click “Continue”.
- You’ll be met with a Finder window. Choose a location to store your VM. Click “Save”
- You’ll then be met with a loading page and the installation will complete. Then you’ll be met with this view. Click “Customize Settings”.
2. Adjust VM Network Settings
Note: The below network configuration interfaces are examples from MacOS Catalina, to bridge a WiFi network connection held by the host machine. The precise steps to bridge a network connection in your environment will differ based on the OS and network connectivity method of your host (e.g., a Windows host running VMware Fusion connected by Ethernet will have a different procedure than the example below).
- After setup, click Settings on your powered-off VM
- Select Network Adapter
- Under Bridged Networking, select Wi-Fi to allow the VM to be accessible from your local network.
3. Power on the VM
- Start the VM – VMware Fusion will automatically launch the console window.
- The console does not require login credentials and will show a command line interface similar to the image below.
4. Confirm the Edge Client is Running
- Click inside the console interface to ensure keyboard input is being sent to the Edge Client VM and run the command:
ip a - Note the IP address under an interface like
enp0s3.
5. Test Web Access
- On your host or another device on the same network, open a browser:
http://<vm-ip>:8080
Note that if your browser defaults to HTTPS (which is certificate-secured connections to websites), you will need to manually specify an HTTP url, including the port 8080, precisely as described in the example above. The NetSpeek Edge does not support HTTPS connections to the web UI in order to avoid connection problems introduced by self-signed certificates when using HTTPS.
- You should see the Edge Client Service Management UI.