Planning Your Installation#

Whether you are looking for a way to install a single Omniverse foundation application for a user to test, or want to deploy an entire suite of Omniverse apps and content for your internal users to work and collaborate with, you should review and plan accordingly based on the requirements and options below to ensure your internal infrastructure is at the desired level of readiness.

System Requirements#

  • Ensure you have identified at least one computer with the ability to connect to the Internet to download the various installation files, applications and content archives from NVIDIA servers. All of these files are available for both Windows and Linux operating systems (except for the Enterprise Nucleus Server, which is only available for Linux via Docker) and it is up to you to determine which operating systems your users’ workstations need to be supported.

  • Confirm that you have hardware within your company firewall with ample disk space (100-500GB) where you can “stage” many of these downloaded files so they can be accessed as part of the installation or deployment process.

  • If you don’t have connected staging hardware that is accessible by users’ workstations (they are completely isolated from a network and Internet connections), you should have some form of portable media device (100-500GB) to manually move the downloaded files from one location to another.

  • Make sure to update the OS systems that will be utilized and installed upon (ie. Windows Update, etc.) so they are up to date

  • Verify that all orchestrations (if needed) have the correct versions in support of Omniverse deployed GPUs etc.

Configuration Options#

  • Ensure evaluation of Omniverse application and configuration needs for each internal customer group.

  • Create a topology of how Omniverse on internal customer systems (virtual or local) are connected to each other, Nucleus Server / Workstation, etc.

    • You can learn about Reference Architectures here.

    • You can learn about Virtualized Topologies here.

  • Omniverse currently does not support LDAP however, services like Microsoft InTune may be used to support hybrid and remote teams with disparate resources.

Omniverse Readiness#

  • Review and identify all internal customer requirements starting from application resource needs (Omniverse + other installed applications) working your way through to confirming your network, servers, and workstations meet these requirements for the collective requirements in deployment.

  • Pre-check that available Omniverse installation software are the correct versions required.

  • Ensure required Omniverse quantities of licensing are secured.

  • Download all necessary files from the Omniverse Enterprise Web Portal and transfer them to an easily accessible local networked system that will act as a staging area.

  • Ensure all necessary ports that need to be open for Omniverse applications to communicate with each other are configured properly.

Permissions#

  • Ensure that all extensions are downloaded/staged into IT managed public folders such as D:/omniverse/data. IT organizations tend to lock down non-user folders (anything sans %USER_ROOT%) will want to ensure that they have installed “all required” files in the read-only areas for workstation users.

As a first step, you must install the IT Managed Launcher to your users’ workstations.

On this page