"...their vision has been instrumental in our adoption of these technologies before they become buzzwords." - Network Manager at Nelson Mullins
"I would simply say that they do the work you need and do it very well." - Director of IT at Piedmont Healthcare
"Not only are the eGroup engineers extremely good, they have all been able to fit in with my existing staff and build relationships that are beneficial for all of our projects." - VP and CIO, Beaufort Memorial Hospital
We called around to other companies to see who they used and over and over the name eGroup was given. After the first meeting, I knew they had the knowledge and staff to meet our needs." - IT Director, MCAngus, Goudelocke and Courie
"I was skeptical about the amount of work they wanted to do in a short amount of time. But we were able to get it all accomplished in less time than they expected. Totally blew us away." - IT Manager, Horry Electric Cooperative
"With their expertise at our disposal, it is like having additional staff on hand. They have never made us feel like we were just another client. More like colleagues." - IT Manager, Horry Electric Cooperative
I see “one-to-one” configurations used for Management and vMotion networks way too often, where a vMotion network will use one physical uplink, and Management will use the other, that’s it–
It’s a common configuration, and exists in environments of all sizes. Unfortunately, it represents a single point of a failure, and the potential for a really bad day if the Management network drops and your HA configuration starts shutting down your virtual machines.
And it’s so easy to fix!! Check out the video below to see the “problem scenario” and how easy the solution is to implement.
Does your company have business issues or questions around operations management in your virtual and cloud environments?
vCenter Operations is a clear a quick way to identify VMware performance problems. You can maximize ROI by increasing VM density and also reduce the VMware Administrators time spent isolating performance problem by up to 80%.
VMware vCenter Operations is designed specifically to simplify and automate operations management in virtual and cloud environments. It’s tightly integrated with VMware vSphere and uses patented analytics to provide you with comprehensive and actionable intelligence across the stack. The focus of vCenter Operations is to provide the intelligence and visibility needed to proactively ensure service levels, optimum resource usage and configuration compliance in dynamic virtual and cloud environments.
I wanted to share some new thoughts and a new solution for a known issue when using PVS 5.6 and XenDesktop 5 deployed via vSphere 4.1.
By now we’ve all experienced the issue wherein any templates containing a network adapter configured to used a vNetwork Distributed Switch will cause the XenDesktop Wizard to crash when attempting to query available templates. The real kicker to this issue is that if any storage in the chosen DesktopController host configuration contains a template with a Distributed Switch then the behavior will appear. It does not matter if those templates are part of another vSphere installation, only that they are sharing the same storage.
Continue reading for more details and a PowerCLI based solution.
If you are in vSphere and click on Performance, you may end up running across this error:
After researching the issue I found a couple VMware KB Articles on the subject, but no conclusive fix to the issue that resolved the issue. After digging in I found that troubleshooting futher proved better results. Here’s the fix:
1. In my case the DB resides on a Server 2008 R2 box, so ensure you have the SQL 2008 Native Client Driver in place for your ODBC connection
2. Review the stats.log in the following location: C:ProgramDataVMwareVirtualCenter & look for anything that might catch your eye (failures, etc)
3. Ensure the following services are set to an active domain account (not a local system account):
* VMware VirtualCenter Management Webservices
* VMware VirtualCenter Server
Start those services with the proper network account, then log back into Virtual Center. You should not see the “Performance” tab Overview page displaying correctly.
One of the changes in the VNX platform from the previous generation EMC storage arrays is that the Failover Mode 4 is supposed to be the new default. And I say “supposed to be” because during the beta program, I did not find that this was the case. The ESXi hosts we connected in to the array all used the previously default Failover Mode of 1 (Active/Passive mode). But now I think I know why. There has been a little bit of forums/message board discussions on this and the popular thought is that “everything defaults to Failover Mode 4 now”– but I’ve found that is not true– kind of.