Create a vApp from a Catalogue Item

Follow these steps to create a new vApp.

 

1. vApps can be created from the catalogue items in two ways. Either: 

 

From Content Libraries, select vApp Templates > source > Create vApp.

 

 

OR, from the ORG vCD. Under Compute select vApps > New > add vApp From Catalog.

 

 

2. Select the Template to import and click Next.

 

 

3. Name your vApp and set both Runtime Lease and Storage Lease to Never Expires. Click Next.

 

 

4. In the Configure Resources screen, select the vDC and Storage Tier from the Storage Policy dropdown list. Click Next. 

 

 

5.  The Compute Policies will display. It is recommended that these settings are modified after deployment.

 

 

6. In the Customize Hardware screen, review the settings and click Finish.  It is recommended that these settings are modified after deployment. 

 

 

7. In the Configure Networking screen, select the network you want to connect to, and click Next.

 

 

8. In the Ready to Complete screen, review the settings and click Finish

 

 

9. A network must be connected to a vApp in order for the VMs within the vApp to use it. Select vApps > Actions > Add Network.

 

 

10. The Add Network window appears. Select Org VDC Network > the required network > Add.

 

 

11. To configure the resources on the newly deployed VM, select the Virtual Machines tab. Locate the new VM and click Details.

 

 

12. The VM details display. These are divided into 3 sections - General, Hardware and Guest OS Customisation.

 

In the General section, you can configure the VM settings including:

  • VM name
  • OS version
  • Boot delay
  • Storage policy.

 

 

13. In the Hardware section you can configure items such as:

  • Hard Disks (add new, or increase existing).
  • Compute > CPU, Memory.
  • NIC's > edit existing, delete or add new.

 

 

14. In the Guest OS Customisation section (shown below) you can configure:

  • Guest customisation
  • SID
  • Passwords
  • Domain
  • Script file 

 

Important: 
In order for Guest OS Customisation to work, the template used to deploy the VM must have VM Tools installed. 
- If an imported machine in vCloud does not have Enable Guest Customisation enabled, applying this setting can cause issues on the next startup.
- If it is unavoidable, disable Change SID before enabling Enable guest customisation.
- Once guest customisation is completed after the first boot, and the VM configuration is completed, disable Enable guest customisation. 

 

 

15. To start the vApp, navigate to the vApps tab. Locate the vApp and click Actions > Power On. 

 

Note: The first startup will take time as the VM completes your selected customisation and hardware changes. 

 

 

16. To open the VM console, click VM Console. Or access it from the vApp view as VM Consoles.  

 

Note: 

- VM console access is only used when network connectivity is not available. For example, during the initial configuration or when troubleshooting (in certain circumstances). 
For normal use, a standard RDP session is recommended. 

- VMs created in vCloud Standard can also be viewed in the Compute Overview Page of CloudCreator. See Compute


-
It may take 20 minutes or more before a new VM is available for Scheduled Actions in CloudCreator. 

 

 


 

 
 
 
 
 
 
 
 
 

The page cannot be found

The page you are looking for might have been removed, had its name changed, or is temporarily unavailable. Please make sure you spelled the page name correctly or use the search box.