I remember struggling to get my head around Apache Webserver file permissions. It's a common issue, and I've seen forum posts this weekend with users struggling to get it right. That s what's prompted this post.
To allow the Apache web server process (httpd) to access and serve files from virtual host directories, httpd requires at least read access. However, with content management systems, httpd might also require write access to virtual host directories.
I've always wanted to find a cost effective way to implement 2-factor authentication. Commercial solutions are expensive, and if you are a small business, you might not want to spend a small fortune on implementing an enterprise solution with hardware tokens. I stumbled across Google Authenticator a while back and started to wonder how it can be used to implement a free 2-factor authentication solution in my lab. I also found a few posts that suggested teaming it up with Freeradius and that's really where this post started.
After updating my View environment to version 5.2, I noticed that my PowerCLI scripts that I run on the View Connection Server keep failing. After looking into the issue I found that each script execution fails when trying to load the snap-in for View PowerCLI into PowerShell with the following error:
"Add-PSSnapin : Cannot load Windows PowerShell snap-in VMware.View.Broker because of the following error: The Windows PowerShell snap-in module C:\Program Files\VMware\VMware View\Server\bin\PowershellServicesCmdlets.dll does not required Windows PowerShell snap-in strong name PowershellServiceCmdLets, Version=220.127.116.1115, Culture=neutral, PublicJeyToken=null"
To resolve the issue, the new PowershellServiceCmdlets.dll file installed during the View Connection Server update, needs to be registered with Windows PowerShell .
To register the file, open a new Windows PowerShell prompt and run the following script:
“C:\Program Files\VMware\VMware View\Server\Extras\PowerShell\add-snapin.ps1”
Ever wanted to build a home lab to study new technologies such as vCloud? I bet you have! However, all of us know that it could cost quite a bit to get it up and running. In addition to the initial capital expenditure in getting your home lab up and running, it also costs a small fortune in energy costs to keep it going. Well, now there's another way to getting a lab up and running, just a lot faster and much more cost effective.
If you’ve ever had to answer the following question “Is application X supported on the VMware Platform?”, then you will probably be familiar with the website that VMware has set up over at http://vmware-alliances.force.com/supportedapps/. It’s a website that is dedicated to Business Applications on the VMware Platform and currently, at the time of writing this post, shows that there are 3707 applications that are officially supported to run on the “VMware Platform”.
As most people in the VMware Virtualisation Community will know, we have been working on a new book entitled “VMware vSphere Performance”. The book was first announced in June 2011, and although being listed as available to pre-order on sites such as Amazon, the book is still yet to be published almost two years later.
Since the project began back in 2011, we have suffered several setbacks, with issues ranging form changes at the project management level, to issues with finding relevant performance related issues in order to produce content. I'm not going to go into much detail as to what exactly the issues were, however, since December 2011 the project has stalled and started up again on several occasions, and for the past year, there has been very little movement in terms of content being generated and therefore reviewed for the book. We have missed several targets in terms of publication dates. The book was originally planned to be released for VMware vSphere 5 and would cover VMware vSphere 4 and 5. We missed the publication for vSphere 5, and then vSphere 5.1 at which point Sybex (an imprint of Wiley) decided to push the publication date back even further and wait for the next release of VMware vSphere, whenever that may be, which would make sense, as at the time the shelf life of a book that is focused on vSphere 5 would not have been long enough to make it worth publishing.
Ever since the publication date got pushed back again, there have been even less interaction between the authors and the editorial teams, and I must admit that there were times that I had though that the book was dead. However, yesterday, the 24th of January, after a conversation with our technical editor, I decided to get in touch with all the authors, and the acquisition editor at Sybex, in order to determine the current state of the project. I have now received responses from most of the parties involved and to make a long story short, this is what is now going to happen.
We are yet to work out the finer details, but as of today, myself and co-author Jonathan Fitch will be taking control of the project in a much more involved way. Previously we were simply writing and submitting content and the rewriting the same content after editorial reviews. We are yet to determine who the “lead” author will be, but together we will review what has been done and what still needs doing, and together we will drive this thing forward. There is now a lot of work to be done, but we will be pushing hard for the next three to four months.
I would like to thank everyone who's been waiting for the book to hit the stands for their patience. I would also like to thank co-author Jonathan for his good work on the book thus far as well as technical editor Matt Liebowitz for his patience, understanding and words of encouragement.