Author: Luca Sturlese
Have your tried to ping your computer or server and it fails even though you know that it is online and connected to the network? One of the reasons why this fails could be because ping is disabled in the Windows Firewall. This article discusses how to resolve this and allow ping through the Windows Firewall.
Here is a quick fix to a problem that I had the other day, which I thought my be useful to a few people.
You logging into the vSphere 5.1 Web Client with the local vSphere Single Sign-On (SSO) user of admin@System-Domain and it fails with the error message of associated users password is expired.
Below is the solution to this error message…
I have decided to build a new test lab at home based on VMware architecture so that I can test and learn new technologies which I don’t always get a chance to play with at work. I have decided to go with a two physical host approach and use my existing Synology DS1813+ NAS for the storage. Because I want to simulate a physical network as much as possible, I am using a Cisco SG300-10 layer 3 switch to perform all of the management of all of the VLANs and the routing between them and my home network.
I am currently in the process of purchasing all of the hardware and building the lab. Below are all of the details of what my final test lab will look and the reasonings behind why I have made the decisions I have….
Since vSphere 4.1 you have the option of setting the number of cores per CPU in a virtual machine. This allows you to present logical processors to a VM into specific socket and core configurations. This feature is commonly know as corespersocket.
So the question arises…. is it better two assign multiple sockets or multiple cores per socket?
Below we look into the best practices and when to use which option…