> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> What the VMware vSphere integration brings to your Neo Agent setup

VMware vSphere runs your clients' virtual machines on ESXi hosts that a vCenter Server manages. Connect your vCenter to Neo once, at the MSP level, with its address and a vCenter user for Neo.

## What Neo can do with vSphere

<CardGroup cols={2}>
  <Card title="Create virtual machines" icon="server">
    Deploy a VM from one of your templates, with your guest customization specification, or clone an existing VM, in the folder, resource pool and datastore the ticket needs. Neo can also create an empty VM with the CPU, memory, disk and network you ask for.
  </Card>

  <Card title="Manage virtual machines" icon="sliders">
    Power a VM on, off or restart it, change its CPU, memory, disks and networks, take, revert and remove snapshots, move it to another host or datastore, rename it, turn it into a template, and delete it.
  </Card>

  <Card title="The VM behind a ticket" icon="magnifying-glass">
    Find a VM by name, IP address, DNS name or the UUID your RMM shows, and read its power state, host, guest OS, disk space, snapshots and open alarms.
  </Card>

  <Card title="Hosts, storage and alarms" icon="hard-drive">
    Read host health and maintenance mode, datastore free space and what fills it, triggered alarms, recent events and tasks, and performance counters.
  </Card>

  <Card title="Inside the guest" icon="terminal">
    With VMware Tools running, run a program inside a VM, such as restarting a service, with a guest OS account a technician gives for the ticket.
  </Card>
</CardGroup>

With the access you choose, Neo can also manage hosts and clusters, datastores, networks, alarms, permissions and vCenter settings. Some changes always ask a technician first, under every access profile, such as deleting a VM or a datastore file, or changing permissions: [the full list](/integrations/vsphere/connecting-to-neo#changes-that-always-ask-a-technician).

## Your clients in vSphere

vSphere has no client object of its own: you keep a client's VMs in a datacenter, a VM folder or a resource pool that you name. Neo finds a client's VMs by those names, so it works with the layout you already use. There is no Organization Mapping tab for vSphere.

## What Neo never does

* Read or hand out a vCenter session, a remote console ticket or a host service ticket.
* Move a file's bytes into or out of a guest OS.
* Back up, restore or reset a host's whole configuration.
* Delete a folder, a datacenter, a resource pool or a vApp, which would delete or move every VM inside it. Neo deletes VMs one at a time, with a technician's approval.

Neo also removes the fields vSphere keeps credentials in (passwords, keys, tickets, session ids, the transfer links of an OVF import or export, guest environment variables named like credentials, SNMP communities, credential settings such as `guestinfo.userdata`, and the user name and password in a URL) from every answer before an agent sees it. A guest customization password that vCenter stores encrypted with its own key stays as it is, so Neo can deploy from your customization specifications.

## Next steps

<Card title="Connect vSphere" icon="plug" href="/integrations/vsphere/connecting-to-neo">
  Make a vCenter user for Neo and save it in Neo with your vCenter address.
</Card>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.