To edit a vCenter compute resource:

  1. Go to your Control Panel > Settings menu.
  2. Click the Compute Resources icon.
  3. Click the Actions button next to the vCenter compute resource that you want to edit, and then click Edit.
  4. On the screen that follows, change details as required:
    • Label - enter a compute resource label
    • Compute Resource Type - select the vCenter compute resource type
    • Operating System Type - select the operating system type of the virtual servers that can live on this compute resource:
      • Windows only - when this option is selected, only VSs with the operating system Windows will be living on this compute resource. This compute resource will not be available for selection when creating a Linux or FreeBSD VS, nor when migrating a VS. 
      • Any OS - when this option is selected, any VS with any operating system will live on compute resource. By default, each compute resource will be created with the Any OS option. The existing compute resources also will have the Any OS set.
      • Non-Windows - when this option is selected, only VSs with the operating system Linux or FreeBSD will be possible to create on this compute resource. This compute resource will be skipped for Windows-based VSs in VS creation wizard, or when migrating a VS. Also when failover happens, Windows-based VSs won’t migrate to this compute resource.
    • CPU Units - adjust the slider to set the desired amount of CPU units for this compute resource
    • Enabled - whether the compute resource is enabled or not (compute resources that are not enabled cannot be used to host VSs)
    • Collect Stats - move the slider to the right to collect statistics for this compute resource
    • Compute Zone - the compute zone to which the compute resource is assigned
    • API URL - set the vCenter API URL - e.g.
    • Login - specify the vCenter login
    • Password - specify the vCenter password
  5. Click Save.
  6. Go to vCenter compute resource's label > Tools

  7. Click Resync vCenter to import all networks and datastore that are not currently synchronized in OnApp from vCenter.

    • The vCenter networks are imported into one network zone and you can move them to different zones.
    • In one network zone, you can have networks that are assigned to vCenter and networks that are assigned to Xen/KVM compute resources.