--- title: Create an oVirt Discovery schedule in Discovery Admin Workspace description: Use the Discovery Admin Workspace dashboard to create an oVirt Discovery schedule. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/discovery/create-ovirt-schedule-DAW.html release: australia product: Discovery classification: discovery topic_type: task last_updated: "2026-07-27" reading_time_minutes: 3 keywords: [Discovery, Admin, Workspace] breadcrumb: [Discovery for cloud environment, Discovery, ITOM Visibility, IT Operations Management] --- # Create an oVirt Discovery schedule in Discovery Admin Workspace Use the Discovery Admin Workspace dashboard to create an oVirt Discovery schedule. ## Before you begin Verify the following: - You have at least one validated MID Server with a status of **Up**. The MID Server must reach the IP ranges that you intend to discover. You can install the MID Server by using [Use MID Server guided setup](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/use-mid-server-guidedsetup.md) or by manually downloading and running the installer. For details, see the MID Server installation instructions for [Linux](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/t_InstallAMIDServerOnLinux.md) and [Windows](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/mid-server-install-prereqs.md). - The MID Server used for Cloud Discovery is configured with the Cloud Management capability. - You have configured an oVirt user in the oVirt Administration Portal with the required roles and permissions. This configuration enables the MID Server to access the cloud resources you plan to discover. - You have created suitable credentials in the ServiceNow AI Platform to connect with the oVirt user that you want to use for discovery. For more information, see [Oracle Linux Virtualization Manager and Red Hat Virtualization discovery](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery-and-service-mapping-patterns/red-hat-virtualization-discovery.md). - You're using Discovery Admin Workspace v1.13.0 or later. Role required: discovery\_admin ## Procedure 1. Navigate to **Workspaces** > **Discovery Admin Workspace** > **Schedules**. 2. Select **New Discovery** from the header of any tab on the Schedules page. 3. Select **Cloud-based discovery** and select **Continue**. 4. Enter a unique and descriptive name for the Discovery schedule. 5. Select **oVirt** as the cloud provider. 6. Choose a MID Server. |Option|Description| |------|-----------| |**Use a cluster of MID servers**|Select an existing MID Server. Clusters provide failover protection and load balancing between MID Servers. See [Configure a MID Server cluster](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/t_ConfigureAMIDServerCluster.md) for more information.| |**Automatically select a MID server**|An available MID Server is automatically selected when the Discovery schedule runs. See [Automatic MID Server selection](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/agent-client-collector/acc-auto-mid-selection.md) for more information.| |**Search for a MID server**|Choose a MID Server to run the Discovery schedule. Only MID Servers that are validated, up, and have the Cloud Management capability are displayed.| 7. Select **Next**. 8. Select a cloud account.
| Option | Description |
|---|---|
| **Existing cloud account** | Select an existing cloud account on your instance. Once an account is selected, the **Account name** and **Manager URL** fields auto-populate. |
| **New cloud account** | Add a cloud account to your instance by entering an account name and Manager URL.**Note:** - The Manager URL is the URL you use to access the oVirt Administration Portal. - Example: `https://my-manager-instance.com:433` |