This disclaimer governs your use of our website; by using our website, you accept this disclaimer in full. If you disagree with any part of this disclaimer, you must not use our website.
(2) Intellectual property rights
Unless otherwise stated, we or our licensors own the intellectual property rights in the website and material on the website. Subject to the licence below, all these intellectual property rights are reserved.
(3) Licence to use website
You may view, download for caching purposes only, and print pages from the website for your own personal use, subject to the restrictions below.
You must not:
(a) republish material from this website (including republication on another website), unless a link pointing back to this website is published with the material;
(b) sell, rent or otherwise sub-license material from the website;
(c) show any material from the website in public, without publicly acknowledging the source of the information or material showed;
(e) edit or otherwise modify any material on the website.
(4) Limitations of warranties and liability
Whilst we endeavour to ensure that the information on this website is correct, we do not warrant its completeness or accuracy; nor do we commit to ensuring that the website remains available or that the material on the website is kept up-to-date. To the maximum extent permitted by applicable law we exclude all representations, warranties and conditions relating to this website and the use of this website (including, without limitation, any warranties implied by law of satisfactory quality, fitness for purpose and/or the use of reasonable care and skill). Nothing in this disclaimer (or elsewhere on our website) will exclude or limit our liability for fraud, for death or personal injury caused by our negligence, or for any other liability which cannot be excluded or limited under applicable law. Subject to this, our liability to you in relation to the use of our website or under or in connection with this disclaimer, whether in contract, tort (including negligence) or otherwise, will be limited as follows:
(a) to the extent that the website and the information and services on the website are provided free-of-charge, we will not be liable for any loss or damage of any nature;
(b) we will not be liable for any consequential, indirect or special loss or damage;
(c) we will not be liable for any loss of profit, income, revenue, anticipated savings, contracts, business, goodwill, reputation, data, or information.
(6) Entire agreement
This disclaimer constitutes the entire agreement between you and us in relation to your use of our website, and supersedes all previous agreements in respect of your use of this website.
(7) Law and jurisdiction This disclaimer will be governed by and construed in accordance with English law, and any disputes relating to this disclaimer will be subject to the non-exclusive jurisdiction of the courts of England and Wales.
(9) Our details
(1) What information do we collect?
We may collect, store and use the following kinds of personal data:
(a) information about your computer and about your visits to and use of this website (including your IP address, geographical location, browser type, referral source, length of visit and number of page views);
(b) information relating to any transactions carried out between you and us on or in relation to this website;
(c) information that you provide to us for the purpose of registering with us, including Names, email addresses and passwords. Passwords used to register on this website are encrypted and cannot be read by any administrator or other user;
(d) information that you provide to us for the purpose of subscribing to our website services, email notifications and/or newsletters and RSS Feeds;
(e) any other information that you choose to send to us;
A cookie consists of information sent by a web server to a web browser, and stored by the browser. The information is then sent back to the server each time the browser requests a page from the server. This enables the web server to identify and track the web browser.
We may use both “session” cookies and “persistent” cookies on the website. We will use the session cookies to: keep track of you whilst you navigate the website.
We will use the persistent cookies to enable our website to recognise you when you visit. Session cookies will be deleted from your computer when you close your browser. Persistent cookies will remain stored on your computer until deleted, or until they reach a specified expiry date.
Most browsers allow you to refuse to accept cookies. (For example, in Internet Explorer you can refuse all cookies by clicking “Tools”, “Internet Options”, “Privacy”, and selecting “Block all cookies” using the sliding selector.) This will, however, have a negative impact upon the usability of many websites.
(3) Using your personal data
(a) administer the website;
(b) improve your browsing experience by personalising the website;
(c) enable your use of the services available on the website;
(d) send you general (non-marketing) commercial communications;
(e) send you email notifications which you have specifically requested;
(f) provide third parties with statistical information about our users – but this information will not be used to identify any individual user;
(a) to the extent that we are required to do so by law;
(b) in connection with any legal proceedings or prospective legal proceedings;
(5) International data transfers
(6) Security of your personal data
We will take reasonable technical and organisational precautions to prevent the loss, misuse or alteration of your personal information. We will store all the personal information you provide on our secure password- and firewall- protected servers. Of course, data transmission over the internet is inherently insecure, and we cannot guarantee the security of data sent over the internet, outside of our immediate network. You are responsible for keeping your password and user details confidential. We will not ask you for your password.
(7) Policy amendments
(8) Your rights
You may instruct us to provide you with any personal information we hold about you. Provision of such information may be subject to the payment of a fee. You may instruct us not to process your personal data for marketing purposes by email at any time.
(9) Third party websites
The website contains links to other websites. We are not responsible for the privacy policies or practices of third party websites.
(10) Updating information
Please let us know if the personal information which we hold about you needs to be corrected or updated.
Since moving to Lincolnshire in August 2014 and whist still working on customer sites in London the majority of the time, I found myself doing a lot of train journeys to and from London. I also started to realise that due to the workload I’ve been facing this year, sometimes juggling up to 5 customer engagements at once, that I very rarely have a few minutes during the day to actually read up on product documentation or anything else that is not directly related to the task at hand.
As we all know, things are moving very rapidly in our industry, more so now than ever before and the hypervisor and features that were once regarded as “awesome” back in the VMware ESX 3 or even 4 days now pale into insignificance when compared to the cast number of features and capabilities that lies simply within the ESXi 5.5 hypervisor. Then, when considering the entire vCloud suite of products and how they interact with each other and the hypervisor, it doesn’t take much to work out that things are becoming more and more complex with every release.
There seems to be some confusion as to whether or not the Identity Appliance that ships as part of vRealize Automation (previously known as vCloud Automation Center, which will be referred to as vCAC 6 for the rest of this article) is required when deploying vCAC 6.1 in conjunction with vSphere 5.5 and later.
As of vSphere 5.1, Single Sign-On (SSO) is a pre-requisite to installing the components for and including vCenter Server. It’s no secret that VMware’s initial implementation of SSO in vSphere 5.1 was terrible. It was over complicated in terms of its implementation requirements, even requiring its own database, to be manually set up using SQL scripts. Thankfully, VMware addressed many if not all of the SSO issues in its release vSphere 5.5, with SSO now being a much more simple and robust component in your vSphere 5.5 environment.
I’ve been thinking about retiring my old home lab server hardware for some time now. I’ve had two little HP ProLiant ML110 G5 servers for 5+ years. They’ve been good little machines and didn’t cost too much to run, but I can now tell that time has taken its toll on them. They each have a dual core Intel Xeon processor and maxed out at 8GB of RAM. With the management components of products such as vSphere, vCAC, vCD, etc. nowadays requiring at least 8GB per appliance, these machines have basically been made obsolete by the requirements of most enterprise applications today.
I am happy to announce that our new book, VMware vSphere Performance (ISBN: 9781118008195) is now available on Amazon.com and Amazon.co.uk in eBook format on Kindle as well as Paperback. The Paperback version should be in stock at Amazon.com by 12 May 2014.
This title was first announced in 2011 and due to a number of issues and difficulties, the book was delayed several times. However, due to the hard work and dedication of my co-authors, Matt Liebowitz, Christopher Kusek and the editorial team at John Wiley & Sons, Inc. we were able to finally bring the title to print.
On the 20th of February 2014, I published some of my PowerCLI scripts to GitHub in an attempt to have some sort of version control system in place as well as to make the scripts available to the general public. However, my current role doesn't really require that much scripting, and it really is only the occasional script that I have to put together. Therefore, I've only learned a little of PowerShell, basically enough to get the job done. I come from a C/C++ programming background and feel much more comfortable when working on a file with a .c, .cpp or a .h file extension.
Too many times now have I had to browse in a billion locations on my file systems, trying to find that one script that I wrote two or three years ago. I really have a bad habit of misfiling little scripts. That has got to change. So, I have started a little project to collect all of the PowerCLI scripts that I write and use from time to time, in a Git repository. I really needed to find a way of keeping scripts version controlled in a distributed system, whilst at the same time keeping them in a cloud based storage location other than simply Dropbox, where others can collaborate and add to it if they would wish to do so.
The repository is still very small, as I've only started working on it yesterday, however, as I write more and more scripts, I will be adding them to the repository and pushing them up to GitHub. There's no need to be able to use Git in order to make use of the scripts. Just download whatever you need and run them. However, feel free to contribute more scripts if you like.
Here is the URL to the repository: https://github.com/rynardtspies/ScriptKit
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.