The features File Portal and Web Manager of VMware Horizon Mirage both need Microsoft .NET Framework to work properly. While the File Potal still uses .NET Framework 3.5 SP1 the new Web Manager needs .NET Framework 4.0.
Sometimes if you want to access one of these consoles right after the installation you either get a HTTP 403 error (Web Manager) or HTTP 500 error (File Portal).
Both of these errors most often occure when the relevant .NET Framework version isn’t registered properly with IIS (Internet Information Service).
To solve this issue just run one of the following commands:
For the installation of the Mirage server components some specific Windows features are needed.
For the Mirage server, the the management server and the management console Microsoft .NET Framework 3.5 SP1 is needed. The installation of this feature can be accomplished via the Server Manager or via PowerShell.
To install .NET Framwork via PowerShell just start PowerShell as an administrator and then run the following two commands:
To install the Mirage File Portal (WebAccess) also requires .NET Framework 3.5 SP1 but additionally it requires the Microsoft Internet Information Service (IIS) with some additional components like the IIS 6 Management Compatibilit feature.
To install these features through the Server Manager can be a bit cumbersome and using the following PowerShell commands to install IIS and all the features required by the Mirage File Portal is much easier.
If you haven’t installed .NET Framework before installing IIS just add the NET-Framework-Core at the end of the Add-WindowsFeature command for the IIS feature installation (and don’t forget to add a comma after Web-Lgcy-Mgmt-Console).