Skip to main content
Version: Next

Send Us Your Ivanti Neurons Export

When we are troubleshooting an issue with your Ivanti Neurons for ITSM archive, we will tell you exactly what we need and ask for only that - we don't want you to hand over your entire environment.

In most cases we ask for a structural or metadata export rather than a full database dump, so you do not need to run (or share) a full backup of your Neurons SQL Server database.

What we'll ask for​

We will specify the exact scope when we raise a request. This might be:

  • Metadata / structure — the Neurons schema (tables, columns, and relationships) so we can see how your instance is structured.
  • Specific records — a bounded set of records or lookup/configuration data relevant to the issue.
  • Attachments — only if the problem involves attachment data. If so, note that Neurons attachments may be stored inside the database, on disk, or in an Amazon S3 bucket depending on how your environment is configured, and they are not included in a standard database backup - they typically require a separate request to Ivanti.

For the underlying processes for obtaining your data (hosted vs self-managed backups, and requesting attachments), see Getting Your Ivanti Neurons Data.

Producing a metadata export with cz export​

The easiest way to give us exactly what we need is the metadata export built into the cortex-util.exe CLI. It exports the Neurons frs_def_* configuration tables with data, and every business table as structure only — no business records:

cortex-util.exe cz export --connection-string "server=neurons-host,1433;uid=user;password=pass;database=neurons" --file neurons-metadata.cze

This is the metadata-first behavior by design — you do not need any extra flag to get structure only for business tables.

Sending the file​

Once we've agreed what to send, if it is too large to attach to an email, we can work with a OneDrive or Google Drive link, or we recommend Our Box Drive. Contact us if you need to arrange a more secure transfer method.