Centralizing Horizon View desktops using Mirage

This recipe will discuss the steps that are required to use Mirage in order to centralize desktops or endpoints, as they are named in the Mirage console.

Note

As with VMware Horizon View itself, ensure that any Mirage implementation includes redundant components that protect the configuration of the Mirage platform and the associated Horizon View desktop data in the event of an infrastructure outage or other failure.

Getting ready

Only the following two things are explicitly required to centralize endpoints using Mirage:

• The target endpoints must be listed in the Mirage console's Pending Devices window
• The Mirage server must have sufficient space, after deduplication, to host the data it imports from the devices being centralized

  Note

  Determining Mirage server space requirements is difficult due to the fact that each organization is likely to generate different amounts of unique data. When deploying your Mirage server, follow recommended guidelines...