- Moving VMs from ESX to Workstation
- vCloud Director and guest customization
- vCenter Orchestrator appliance 5.5 : error 500 a.k.a re-licensing vCO
- Find orphaned.vmx files (VMware Powershell)
- "300 out of 500" : What is a passing score?
- PSExec command-line parameters
- BGinfo for RDP sessions
- vCenter Storage Status "unknown"
- vSphere 6.x Observed IP range
- My snapshots are where?
Subscribe to Blog via Email
Tag Archives: troubleshooting
I tried to log into my demo Orchestrator 5.5 appliance today and got rejected by the webclient, downloaded Orchestrator client (“Cannot connect to host.”) and configuration pages. Going to http://ipaddress gave me a error 500 – Internal Server Error. A … Continue reading
I’ve been having a problem with my iPod where it would not load the proper drivers in my Windows7 64-bit desktop. It worked for a long time, then suddenly it didn’t. I found links at apple.com and other places of … Continue reading
[Update] As mentioned in the comments below, the bug shown here was fixed in a previous release (apparently U1) of the vSphere client. The trick seems to be the bug only existed in the client and unlike previous versions the … Continue reading
I had an issue today where the secondary instance of a virtual machine with Fault Tolerance enabled was registered to a host (vSphere 5 ESXi) – even tho the original VM wasn’t in inventory at all. Sorry, no screen shots … Continue reading
More of a list of common troubleshooting solutions than “best practices” but an interesting series of reads nonetheless Troubleshooting ESX virtual machine performance issues
“The vNetwork Distributed Switch configuration on some hosts differed from that of the vCenter Server.” If you see this message, don’t panic. Distributed switches are managed by vCenter, but there is a database copied to each host with information on … Continue reading
I’ve seen a few cases where storage devices (specifically iSCSI or FCP datastores) return a gray “unknown” for a status:
“The systemId does not match the current system or the deviceID, and the vendorId does not match the device currently at 006:08.” Nice descriptive message. If you add a PCI passthrough device to a VM (ie dedicate a PCI device … Continue reading