2014/08/19
by Piotr Pisz
0 comments
During the backup of virtual machines using Avamar 6.1 began to show errors as post title. Quite by accident, but with the growing trend. On the Internet you can find a lot of information on this topic , but in my case, the solution turned out to be a little different. On the machine which concerned the error, was never made a snapshot and in the folder does not exist delta file (and other eg. 0000.vmdk).
2014/08/11
by Piotr Pisz
0 comments
As already mentioned here, VIN 5.8.2 contains the vCenter Hyperic agents files in version 5.8.0. I have already tried to upload there version 5.8.2, but unfortunately without sucess. And now we have appropriate KB, clear and transparent like the morning mist. Fortunately, thanks to the previous attempts more or less understood what they meant and decided to complete the process (though lately I’ve been very close to success). Let’s start with the preparation of new agents. VIN hosts files for Linux systems and Windows in 32 and 64 bit versions. The relevant files can be downloaded directly from the vmware.com or “pull” from the directory in which you installed the full version of vCenter Hyperic (with agents), this applies to both versions, delivered as an appliance and on the Windows version (hyperic/server-current/hq-engine/hq-server/webapps/ROOT/WEB-INF/hq-agent-bundles). Prepare a package containing the relevant agent files is not easy, KB is not entirely truth, we need to perform some additional steps. Fortunately, we can use several parallel versions of the agent.
2014/08/05
by Piotr Pisz
0 comments
In vSphere are used by VMware two application servers, one is Apache Tomcat (mostly in version 6) and its counterpart from the Spring Source, Pivotal tcServer (mostly in version 7). All the important features such as vCenter operate on tcServer, less important solutions are slowly migrated from Tomcat to tcServer. By default, both servers support remote monitoring, but do not have it enabled. Monitoring the application server written in Java, is done using the JMX Remote Access console. Locally installed vCenter Hyperic agent on the vCenter Server 5.5 detects correctly SpringSource tc Runtime 7.0, but will not be able to connect to it.
2014/07/21
by Piotr Pisz
0 comments
One of the security options that are available in vSphere, is the ability to configure the “High Availability” at the level of a single machine and… a single application! vSphere App HA is nothing more, than another services integrator, delivered in the form of plug-in for vSphere Web Client. It is also the only known for me option in the VMware portfolio, which allows connect a single monitored application with specific actions. This specific action is to force reboot the entire virtual machine in response to the failure of the single application from inside the machine! This is the new quality, many Administrators do not know or do not know for sure how to use it. In this post, on a running example, I’ll show how to use the functionality that provides vSphere App HA (Appliance version 1.1).
2014/07/17
by Piotr Pisz
0 comments
Currently, all delivered by VMware Appliance is based on SUSE Linux Enterprise. In most cases, defined by VMware users have expiring passwords. This also applies to passwords administered during the deploying of the appliance (eg initial root and postgres password for vPostgres). Apart from security policies used in our production environments, in the Lab each time changing the user’s password to log in via SSH can be very tiring. This process can be very quickly improved.
Log in as the root user to the Appliance. Password expiration parameters for newly created users (PASS_MAX_DAYS, PASS_MIN_DAYS, PASS_WARN_AGE) are located in the /etc/login.defs. For existing users, the change can only occur with the chage command.
In addition, we can in the file /etc/pam.d/common-password-vmware.local set the parameter remember=0 (number of stored passwords). Parameters can be set in any configuration (eg after setting remember=0 every 60 days can be administered the same password at change), the change does not result in the need to restart the service or the entire appliance.
And that’s it, a simple change and what functional 
Was this information is helpful? Tell me, please leave a comment!
2014/07/15
by Piotr Pisz
0 comments
Recently we are extensively test a Horizon View 6 in a combination with the migration of workstations to Windows 8. Start and configure the first machine took an awfully long time. In the end I ran the console and was surprised to read the following message: Windows could not parse or process the unattend answer file for pass [specialize]. The settings specified in the answer file can not be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup]. Restart of the machine did not help.
Quick search for a solution on the Internet led me to the conclusion, that used Windows key is invalid. After checking, I was found that in a hurry typed KMS key instead of MAK (LAB do not have KMS server). Fixed profile, destroy vm, and another machine is personalized properly.