Piszki Lab | EN

My case study in the clouds…

2014/07/11
by Piotr Pisz
7 Comments

Integrating VMware Hyperic 5.8.2 and vCenter 5.5 (via Infrastructure Navigator 5.8)

VMware Hyperic is the perfect complement to a whole range of applications for vSphere environment monitoring. However, compared to VMware Operations Manager, LogInsight and Infrastructure Navigator, VMware Hyperic is more than just another probe servant to collect data (which does not change the fact that highly accurate probe). With it, you can load up to tcServer or Apache Tomcat application and run it. You can automatically restart a application service  that stopped working, you can start emergency plans containing a range of activities carried out step by step in case of emergency. In this article I will describe one of the underrated function of which is to integrate the vSphere Web Client with VMware Hyperic. With this integration, it is possible to install the Hyperic agents from the Web Client and monitoring their status!

hy0

 

Continue Reading →

2014/07/07
by Piotr Pisz
0 comments

VMware vCenter Hyperic 5.8 Appliance: Replacing server SSL certificate.

Hyperic Appliance, apart from the obvious benefit, which is to install everything with one hand, it also has one disadvantage. Everything is pre-configured. In the Lab we use your own CA and all services that operate here on ports 443 are exposed to the signed certificate kept by this CA (including Hyperic). The change procedure is very simple, log in as root with the password specified during appliance installation. Go to the directory /opt/hyperic /server-current/conf and issue the following command:

hyp1

Continue Reading →

2014/06/25
by Piotr Pisz
0 comments

Upgrade Horizon Workspace 1.8.1 to Horizon Workspace Portal 2.0

VMware Horizon with View 6.0 has just been presented, under this strange name has been hidden new VMware Horizon Portal 2.0. According to the information contained in the release notes, the only supported migration path is to raise the version 1.8.2 to version 2.0. The first problem is that there is no version 1.8.2 officially (at 2014.06.24). The second problem is that with version 2.0 “Horizon Files” (data-va) is abandoned. In a production environment we need to wait with upgrade to the clarification of all doubts. However, according to the official documentation, supported migration path is … from 1.8 to 2.0! Therefore, in the LAB can we safely practice the upgrade. The whole procedure should start by stopping the entire vApp and make the snapshots for all vm (including external database if we use it). In the next step, if we use Horizon Files, we have according to this KB, export files from the data-va and find for them another safe marina. We can also ignore data-va, while upgrading process, data-va is disconnected from the portal and will be able to safely remove it.

up6

Continue Reading →

2014/06/24
by Piotr Pisz
0 comments

Horizon Workspace: Troubleshooting

When setting up the Horizon Workspace, sometimes you will come across a variety of messages, most often they arise from the fact that we forgot to do some step from the documentation. Unfortunately, once we do this, it is very difficult to link the message to the missed activity (ie not enabled option). In this post I will describe the most common problems, and as I had to deal with the next, I will be quite add them to this list.

ERROR_NETNAME_DELETED

During the reconfiguration of one machine connector-va, while renaming the network share where ThinApp applications reside, surprised me with an error as shown below.

herr1

Continue Reading →

2014/06/17
by Piotr Pisz
0 comments

Horizon Workspace: ThinApp applications on computer that is not a member of AD

An absolute novelty that appeared in the Horizon Workspace 1.8 is the ability to use ThinApp application on computers that are not members of an Active Directory domain. This means, that you can connect from the Internet, from any computer to our Workspace website and run ThinApp. With little restriction, in this version, you can run only “full” applications, there is no the possibility of streaming applications over the Internet. It is also necessary to install an client of VMware Horizon Workspace (ThinApp applications need to act HorizonPlugin.dll). After a quick install we can collide with the following error (Failed to copy file: The network path was not found):

work0

Continue Reading →

2014/06/05
by Piotr Pisz
0 comments

Horizon Workspace: F5 BIG-IP and multiple instances of the connector-va.

In this post I will explain further configuration of Horizon Workspace 1.8.1 and F5 BIG-IP. We passed the stage of balancing traffic to duplicate gateway-va machines, now we will replicate the connector-va machine. In addition to balancing traffic, We configure everything so that it was possible “Windows” authentication type and set option “Enable redirect” to access from the Internet. As a result, the computer that is located away from AD domain, may still use Kerberos authentication when accessing ThinApp applications (available directly from the portal Workspace).

conn1

Based on the diagram it is easy to guess that the virtual address connector-va must be fully accessible from the Internet and local area network (configured NAT). He must have also configured with the correct FQDN (correct local and Internet PTR record in DNS) and import the valid SSL certificate (in the Horizon Workspace, the best solution is a wildcard certificate). Certificate of connector-va machine is generated each time using a script wizardssl.hzn, in F5, we will use the same SSL profile that we created for workspace.pulab.pl address.

Continue Reading →