Note: This article is specific to Non-Guest OS Customization (NGOC) Servers. For instructions on deploying a Cloud Server from a Guest OS Customization (GOC) Image, see: How to Deploy a Cloud Server from a Guest OS Customization Image. For more information on the differences between the two types of Images and corresponding deployments, see Introduction to Cloud Server Provisioning, OS Customization, and Best Practices.

Please note that Non-Guest OS Customization (NGOC) Images are available only in MCP 2.0 Data Center locations.

Note: Long-Term Retention Snapshot Images are created from Long-Term Retention Snapshots. They are always created as Without Guest OS Customization Images. For more information, see Introduction to Cloud Server Snapshot Long-Term Retention Images

Prerequisites:

  1. Only the Primary Administrator or a Sub-Administrator with the Server role can create a Cloud Server.
  2. The Source Image you are deploying from needs to be a Non-Guest OS Customization Image. Non-Guest OS Customization Images can be identified by the presence of a "plug" icon as shown in the diagram below:
  3. You must provide a unique VLAN on the same Network Domain for each NIC associated with the source Non-Guest OS Customization Image.
    1. You cannot connect two NICs to the same VLAN - each VLAN can only be connected to one NIC on a given Server.
    2. Each VLAN must be in a NORMAL state.
    3. For details on how to deploy a VLAN, see How to Deploy a MCP 1.0 Cloud Network or a MCP 2.0 Network DomainHow to Deploy a VLAN on a Network Domain in an MCP 2.0 Data Center 
  4. If the Source Image exists in a Data Center location with User-Manageable Clusters, then the specifications of the Cloud Server must be supported by the Target Cluster. For details, see How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location.
  5. The Data Center must be MCP 2.0. Non-Guest OS Customization Images are not supported in MCP 1.0 Data Center locations.
  6. In order to deploy a Server with disks that utilize the Provisioned IOPS Disk Speed, the Data Center must be enabled with that speed. See How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
  7. CPU count must be supported by the Servers Virtual Hardware version. We recommend keeping Virtual Hardware version up-to-date. See How to Update Virtual Hardware on a Cloud Server
    1. If changing the number of CPUs to anything other than 1, 2, or 4 CPUs, the Virtual Hardware must be Version 4 or greater
    2. Support for using 3/5/6/7/8 virtual CPU's requires Virtual Hardware version 7
    3. Support for using more than 8 vCPU  requires Virtual Hardware version 8
    4. Support for using more than 32 vCPU requires Virtual Hardware version 9
    5. Support for using more than 64 vCPU's requires Virtual Hardware version 11
    6. Support for using more than 128 vCPU's requires Virtual Hardware version 15
  8. RAM count must be supported by Server's Virtual Hardware version. We recommend keeping the Virtual Hardware version up-to-date. See How to Update Virtual Hardware on a Cloud Server
    1. Support for using more than 64 GB RAM requires Virtual Hardware version 7
    2. Support for using more than 255 GB RAM requires Virtual Hardware version 8
    3. Support for using more than 1011 GB RAM requires Virtual Hardware version 11
    4. Support for using more than 4080 GB RAM requires Virtual Hardware version 13
  9. Advanced Virtualization Settings validations:
    1. For more information on Advanced Virtualization Settings, See Introduction to Advanced Virtualization Settings
      1. If the Source Image has Nested Hardware Virtualization set to true, then the Target Cluster must be enabled to support Advanced Virtualization Settings. See How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
      2. If the Source Image has CPU Latency Sensitivity set to HIGH, then the Target Cluster must be enabled to support Advanced Virtualization Settings. See How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
      3. If Source Image has Numa Autosize numaAutosize set to true, then the Target Cluster must be enabled to support Advanced Virtualization Settings. See How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
      4. If Source Image has Enable Host Info to VM Tools set to true, then the Target Cluster must be enabled to support Advanced Virtualization Settings. See How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location

Content / Solution:

  1. From the Home page, click the Deploy Server button:


  2. The Select Image tab of the Deploy Server dialog will be displayed:


  3. Search for the NGOC OS Image that you want for your Cloud Server. You can choose from a variety of filters or search by Name using the respective search bars:

  4. Select a Non-Guest OS Customization Server Image from which to deploy your new Cloud Server. Once you have clicked on the desired Image, the system will indicate that it has been selected:

    Note: The description will indicate the total number of NICs on the Image. You must specify a unique VLAN in the Network Domain for each NIC as part of the deployment.

  5. Verify that you have selected the correct Server image. Click the Next button:


  6. The Server Details tab of the Deploy Server dialog will be displayed:

  7. Enter the appropriate Server details, then click Customize:

  8.  The Server Spec tab of the Deploy Server dialog will be displayed. Set the specific Server parameters:

  9. Click the Next button. The system will show you an overview of the Server deployment:

    Note: You can choose to Start the Server(s) upon deployment by checking the highlighted box.


  10. Once you have reviewed the Server, click the Deploy button. The system will display a message indicating that the deployment is in progress:


  11. The Server will be added to the Server pool and the system will indicate that the Server deployment is in progress:

    Note: Your Server will take time to deploy. The specific amount of time is variable depending on several factors. For more details, see Introduction to Cloud Server Provisioning, OS Customization, and Best Practices.
     
  12. Assuming the Server is successfully deployed, it will appear in the Servers tab of the Network / Network Domain dashboard. Note the IP address is now listed and you are free to access and/or manage the Server to make additional changes:

    Note: If you chose to start the Server upon deployment, it will be in a running state as indicated by the color of the Server icon. 

    Note: If for some reason the server deployment fails (though this is rare with Non-Guest OS Customization deployments), the pending Server will be displayed in the Admin UI with a brown/maroon bar with brief information about the error. The full error description will be displayed in a popup and will also be logged in the Administrator Logs. To review the Administrator Logs, see How to Create an Administrator Logs Report. To remove the failed deployment, follow the instructions at How to Remove a Failed Server Deployment
     

  13. As described in the warnings in Step #8, you will now need to configure the Guest OS to the desired settings including assigning both IPv4 and IPv6 addresses to each NIC, add/modify DNS entries, adjust Windows timezone configurations, and change the root/administrator password (if desired). In many cases, the NIC configurations and gateway will be invalid and the Server will be unavailable on the Network - this will require logging in via Console as described in How to Get Virtual Console Access to a Cloud Server.

Content by Label Macro. Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.


Related issues