The first Controller

The first Appliance in any Appgate SDP Collective must be a Controller. Until you have the Controller, there is no admin UI. Appliance configuration can be done in several ways depending on the appliance option used:

*Hosted instances*	The form you fill out for a hosted ZTP instance has all the required data fields, so the appliance is pre-configured and will appear as the first Controller. A second HA Controller will be automatically provisioned and joined to the Collective. This is the simplest way to get your Controller(s) up and running.
*Cloud instances*	Cloud instances use templates that can be customized by the vendor or generalized by Cloud provider: The template can include the required data fields, in which case the instance can be pre-configured so it appears as the first Controller. The template can also include a data field for the seed file, in which case it will then boot up into the function specified in the seed file. If the instance boots up unseeded, then it can be configured as if it were a physical machine.
Virtual machines **	VMs typically need an ISO image specified when creating an appliance. Certain VM types allow the seed file to be specified at the same time, in which case the VM will boot up into the function specified in the seed file. If the VM boots up unseeded, then it can be configured as if it were a physical machine.
Physical machines **	These will boot up unseeded. You can either run cz-setup to make a Controller, or upload a seed file to configure the function specified.

** These may require an Appliance installation to create a new Appgate SDP appliance.

The diagram below shows the options for creating new appliances of any type. After cz-setup is used for the first time to create the Controller, then additional appliances can be created using a seed file. There are hyperlinks in the diagram that take you to that point in the process.