Installing VMware Horizon Mirage 4.20

I have been working with Mirage the past few weeks as part of our Horizon Suite deployment. First thing to note is that Mirage is a very cool bit of software and its also very clever. I will get to some of those points in another blog post. I also want to talk about our use case as cool tech aside we have to have a use case and a business case to have this deployed… Don’t we!?

So, lets talk installing the product. I had a few little niggles hence why I thought a post would be handy to others who could run into the same issues as me. I am not going to a full step by step guide as the Admin Guide from VMware provides that, however I will post about the errors that I got. Maybe it is just me but the admin guide was a little lacking on a few points.

First things first if you have not already got it, make sure that you have the latest installer version 4.20. This means that you get the new licensing model which is pretty handy. See my post here for more on that.

I can’t say that the admin guide was wrong on this but if like me you misread the install order is very specific and running the Mirage Server setup before the management server will cause a fun little error (See below) where by it fails to register the server due to a mismatch. I quickly worked out that this just installs server files and running the management server must be available. D’oh!!

Mirage Setup 2 Failed to register server due to version mismatch error

So just to clarify here is a little screen shot I took of my installers with the order that you should install them in.

Mirage Setup 0 Install order

Before you start the install make sure that you have turned UAC off, I actually thought I had it off in my template but it would appear not as I got this nice message, turns out the installer was right. So off went UAC.

Mirage Setup 1 turn off UAC

The next thing that caught was all around the database setup. We have a SQL DBA and he doesn’t like giving us rights to create databases so we have to give him all the information. We are running 2008 R2 SQL database servers and it made sense that I use them instead of MSDE. If this was my lab or a POC I would consider MSDE for ease of setup.

My first error was actually connecting to the database server stated that the connection had failed based on install user rights.

Mirage Setup Error Failed to connect to DBWe have enterprise SQL so my instance name was left blank as I knew I was in the default instance. I created a ODBC connection to the server and DB that had been created, which tested out fine. It is also worth noting that I had asked the DBA to create me a DB called VMware_Horizon_Mirage and give my Mirage service account DB Creator rights.

To fix this error I had got the DBA to extend the DB Creator rights to the SQL Server Instance, which he did under duress. I promised he could revoke them after the install and pledged my soul to the SQL god for good measure!!

Some progress ensued but I was then confronted by this error saying that the MIrageDB does not exist. Now I have to say that the Admin Guide says that you can get your DBA to create the DB up front but I didn’t see it mention that it must be called a specific name. Mirage Setup Error MirageDB does not existSo after another trip to the DBA we renamed the database to MirageDB, thinking that would be it I went back to my install, just to get this nice message!

Mirage Setup Error User does not have DBOwner RightsOh man… I asked for the DB Creator rights which is what the Admin Guide said that I needed. So back to the DBA again and I get DB Owner rights to the Database. Thais got to be it I thought and yes I got further but the Mirgae setup had another ace up its sleeve.

Mirage Setup Error SQL Log File

It was a nice error as it says exactly what is wrong “Failed to modify Mirage_DB.log as it does not exist” so back to the DBA and I ask him if the DB rename should have renamed the log file. He made a funny noise and proceeded to rename the file for me.

Back to the installer and we have success!! Happy days.

I hope that this helps someone else avoid multiple trips to their DBA as most of these problems where simple to fix.

8 thoughts on “Installing VMware Horizon Mirage 4.20

  1. Myles Gray March 31, 2014 / 1:37 pm

    Reblogged this on Myles Gray and commented:
    Excellent post, had this problem today as well.

  2. kiasushou May 26, 2014 / 3:39 pm

    you save my day on finding this annoying error. Why on earth that only mirage has so rigid DB requirement….

  3. Ahmed Atia July 19, 2014 / 4:49 am

    Thank you!

    Your post was valuable for me. I would like to add that if there’s someone like me who has no experience with SQL servers, and wants to set up Mirage in a lab, then you should enable the remote TCP/IP connections in the “SQL Server Configuration Manager”; since it is disabled by default.

  4. Ahmed Atia July 19, 2014 / 5:02 am

    Just one more question if you were to help:
    I’m trying to set up Mirage 5.0, which is the latest version right now, after successfully solving the previous SQL server issues, I got a new one during the installation. A error message pops up saying: “VMWare Mirage Database already exists, but its version is not supported by this installation. Please upgradethe VMWare Mirage Database before retrying this installation.”

    According to the installation guide, the version I am using is supported (see below for the version numbers)

    Does anybody happen to encounter this issue before?

    SQL Version: 2008 Express R2 SP2
    OS of the SQL server: Windows Server 2012 R2

    Mirage Management Server Version: 5.0 (specifically: 500.50438)
    OS of the Mirage Management Server: Windows Server 2012 R2

    I should also mention that I had tried to install SQL Express 2012 SP1 on the Mirage Management Server itself, and it threw the same error message (version is not supported!!!), that’s why I set up a separate server for the SQL setup, and decided to use a not-up-to-date version of SQL Express (2008 R2 SP2).

    Your input is much appreciated. Thank you!

  5. Ahmed Atia July 19, 2014 / 6:08 am

    Nevermind the previous comment, I solved it out.
    I re-ran the Mirage Management installation wizard, ticked the Create New Storage Area, and when I clicked Next, a warning appeared saying the previous installation of Management Server is already installed (!!!) I hit continue and it allowed me to resume the wizard. I typed the administrator’s password and the domain administrators group name and clicked Next and the setup completed successfully.

    I really don’t know what was wrong the first two times! However, I’m glad it worked now. Now I’m going to install the rest of Mirage Components, hopefully they are less annoying.

    Thank you!

    • infrastructureguy July 19, 2014 / 9:33 pm

      Hi Ahmed, I am glad you got around all of your problems. I have just got back from some much needed holiday. Thanks for contributing your solutions to this post. There does not seem to be a lot of info out there on Mirage. But it’s a powerful product with a whole host of use cases. Which I really must post about at some point.

    • john June 18, 2015 / 11:02 pm

      Are you running 2 node mirage server here? how did you setup the 2nd node? I keep running into same error about database already exisits

      • infrastructureguy June 19, 2015 / 10:21 am


        I have only ever deployed Mirage with one node. So I have no experience with a two node deployment. Because it’s so hungry I tore down my lab so I can’t even have a go there.

        Have you tried a post in the VMware community forum. They are normally quick to respond. Have you tried to lab this setup. Do the logs give any clues?

        Sorry I can’t give you a answer to fix this one. Good luck.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s