Hi everyone
The previous two articles were about ESXi 5 and vCenter Server 5 installations. This time I am going to talk about the installation of vSphere Client which is the main management console of VMware virtualization environment. First, I will explain the step by step installation of it (which is too easy) and then I will talk about the basic processes that you have to complete after installation.
Hello friends
This article is a continuation of ESXi 5 installation article and I will show you how you can install vCenter Server for your virtualization environment. The vCenter Server is the core component for VMware virtualization and is used to manage the hosts, virtual machines, resources etc. So let me first show you what you have to be careful of before installation and then I will show you the installation steps.
Hi everyone
It has been a long time since my last article. I have been very very busy therefore couldn’t find time to write. But now I am back again :) . I hope you are all well. This article is the first part of a Vmware vSphere environment deployment article series. Throughout this series, I will try to explain what has to be done to build a vSphere virtualization environment, what are the components etc. I am very sure that you are aware of the components for a vSphere environment but the fundamental parts are ESXi hypervisor and vCenter Server. Todays topic is ESXi.
This problem occurs if you have enabled the auto-creation of user accounts in System Configuration of Maia 1.0.3. At least we met this error message in version 1.0.3.r1575_1. It is triggered in the validation call when checking the “theme_id” while maiad is trying to create the relevant user account that received its first message. Actually the reason is just a small typo but it causes a huge trouble as the email messages are getting deferred. Worse still, reckoning the time spent in seeking a solution, it may become more depressing.
Here’s the original error message;
By the new release of PostfixAdmin 2.3.5, a character encoding problem appeared under “Name” column of PostfixAdmin. Naturally, this situation concerns the people who are using non-ASCII characters inside their full names. At first appearance it might be supposed to be related to UTF-8 settings of PHP or MySQL server, but no, it isn’t. Anyway, with a little investgation, you’d also notice that those full name data are correctly stored within MySQL postfix:mailbox table. So please don’t track it down somewhere else, here’s the confirmed workaround;
