Deploy Security Connector

Depending on the hypervisor that you want to use for Security Connector, you can deploy Security Connector on a Microsoft Hyper-V or VMware ESXi hypervisor.

Deploy Security Connector on Microsoft Hyper-V

The ZIP file you downloaded contains these files:

  • PowerShell Utility Script: create-akamai-sc-vm.ps1

  • Virtual Hard Disk Image File: akamai-sc-<imageID>.vhd

    where <imageID> is the ID of the hard disk image file.

You can deploy Security Connector with the PowerShell utility script or manually with a virtual hard disk image file.

Create the Security Connector virtual machine with the PowerShell utility script

Before you begin

  1. Download Security Connector.

  2. Confirm that the folder you extracted contains the create-akamai-sc-vm.ps1 file.

You can use the PowerShell utility script to create the Security Connector VM.

📘

The PowerShell utility script is not supported with Microsoft Hyper-V on Windows Server 2008. If you plan to deploy Hyper-V on Windows Server 2008, use the virtual hard disk image file and deploy it manually. For instructions, see Manually create the Security Connector virtual machine with the hard disk image file.

To create the Security Connector VM with the PowerShell utility script:

  1. Open a PowerShell window.

  2. Type this command to execute the script:

    <path_to_unzipped_folder>/create-akamai-sc-vm.ps1

    where <path_to_unzipped_folder> is the path to the folder with the PowerShell script.

  3. If you see "The script is not digitally signed. You cannot run this script on the current system" error message, complete these steps to set the execution policy to bypass.

    1. In the PowerShell window, enter this command:

      Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

    2. When prompted for confirmation, enter Y and press Enter.

  4. When prompted, enter the VM name, disk path, and virtual switch name. The VM is created.

  5. Open Hyper-V Manager.

  6. Select the VM and in the Actions menu, click Start. After starting the VM, in the Actions menu, click Connect to access the VM. It may take a few minutes for the machine to start. Ignore any errors that may appear while the VM boots.

Next steps

Create a security connector password.

Manually create the Security Connector virtual machine with the hard disk image file

Before you begin

  1. Download Security Connector.

  2. Confirm that the folder you extracted contains the akamai-sc-<imageID>.vhd file, where is the ID associated with the image.

You can manually deploy the Security Connector VM with the hard disk image file. These instructions apply to Microsoft Hyper-V on Windows Server 2016. These steps may vary on other versions of Windows or Windows Server.

📘

The virtual hard disk file image file that's used to create the virtual machine is the hard disk drive for the virtual machine. Therefore, the changes you make to the virtual machine are saved to the hard disk or the image file. If you need to create a new Security Connector virtual machine, make sure you download a new image file.

To manually create the Security Connector VM with the hard disk image file:

  1. Open Hyper-V Manager.

  2. Select the computer or local server where you're deploying the VM.

  3. In the Actions menu, select New > Virtual Machine.

  4. Review the Before You Begin content and click Next.

  5. In the Specify Name and Location window, enter a name for the VM and click Next.

  6. In the Assign Memory window, enter 2048 in the Startup Memory field and click Next.

  7. In the Configure Networking window, select the virtual switch that you want from the Connection menu, and click Next.

  8. In the Connect Virtual Hard Disk window, complete these steps:

    1. Select Use an existing virtual hard disk option and click Browse.

    2. Browse to the akamai-sc-<imageID>.vhd file, where is the ID associated with the virtual hard disk image file.

    3. Click Open.

    4. Click Next

  9. Review the summary with the details you selected for the VM. Click Finish.

  10. Modify the number of virtual processors:

    1. Select the VM that was created in step 9 and in the Actions menu, click Settings.

    2. In the Hardware menu, select Processor.

    3. In the Number of virtual processors field, enter 2 and click Apply.

  11. Update the network adapter settings:

    1. In the Hardware menu, click Add Hardware.

    2. Select Network Adapter and click Add.

    3. Select the network adapter you added.

    4. Select the virtual switch. Depending on your network topology, this may be the switch you added in step 7.

    5. Click Apply and then click OK.

  12. Select the VM and in the Actions menu, click Start. After starting the VM, in the Actions menu, click Connect to access the VM. It may take a few minutes for the machine to start. Ignore any errors that may appear while the VM boots.

Next steps

Create a security connector password.

Deploy Security Connector on VMware ESXi

Before you begin

  1. Download Security Connector.

  2. Make sure the OVA file is located on your local computer.

This procedure uses the vSphere client. For more information on deploying an OVA file, or if you choose to create a new VM from the OVA file, see the VMware production documentation.

To deploy the Security Connector OVA file in VMware:

  1. Log in to the vSphere client.

  2. Right-click the data center or resource pool that you want to use for the VM.

  3. Click Deploy OVF Template. A wizard appears.

  4. On the Select an OVF template window, select Local file and click Browse to find the Security Connector OVA file. After you find it, click Open and then Next.

  5. In the Virtual machine name field, enter a unique name for the VM.

  6. Select a location for the VM and click Next.

  7. Review the template details and click Next.

  8. Select the disk format for the VM, the storage policy, and the datastore for the VM. Click Next.

  9. Select a destination network for each source network. Click Next.

  10. Review the settings you selected. Click Finish.

Next steps

Create a security connector password.


Did this page help you?