vmEck's Posts

Take a look at this blog post by one of my colleagues. It should answer most of your questions but if there's anything outstanding let me know. What is vCenter Server Watchdog? - VMware vSpher... See more...
Take a look at this blog post by one of my colleagues. It should answer most of your questions but if there's anything outstanding let me know. What is vCenter Server Watchdog? - VMware vSphere Blog - VMware Blogs
I've not seen or heard of this issue occurring. Would you mind sending your SR # to aeckerle at vmware dot com so I can take a look and keep up to date as this progresses (especially since there ... See more...
I've not seen or heard of this issue occurring. Would you mind sending your SR # to aeckerle at vmware dot com so I can take a look and keep up to date as this progresses (especially since there are two instances of this issue). Thanks!
If you look at the networking configuration of the host itself do you see any physical adapters? Perhaps this isn't a vCenter issue but an issue with the host not seeing the physical NICs in the ... See more...
If you look at the networking configuration of the host itself do you see any physical adapters? Perhaps this isn't a vCenter issue but an issue with the host not seeing the physical NICs in the first place. Since these are UCS blades using the VIC modules there could be a driver problem.
Which version of vCenter Server 6.0 are you running? 6.0 GA or U1/a/b? Are you running an embedded or external PSC? Since SSO runs as part of the PSC it is expected to see "SSO is not initiali... See more...
Which version of vCenter Server 6.0 are you running? 6.0 GA or U1/a/b? Are you running an embedded or external PSC? Since SSO runs as part of the PSC it is expected to see "SSO is not initialized" when logging into the vCenter VAMI. When you log into the PSC VAMI (https://<psc fqdn>/psc) do you see everything as healthy? Is time synchronized between the PSC and Active Directory?
You're spot on with your 100ms max latency between PSCs. BTW, max latency for long distance vMotion is 150ms RTT. These are not hard technical limits but what we are comfortable supporting based ... See more...
You're spot on with your 100ms max latency between PSCs. BTW, max latency for long distance vMotion is 150ms RTT. These are not hard technical limits but what we are comfortable supporting based on our own testing. Would things technically work with higher latencies? Probably. But don't put yourself in a risky position that may prevent you from getting support if there is an issue. Having said that, what many large customers are doing today is consolidating down to one SSO domain per region. It would be great if we could get down to one global SSO domain, but today, in vSphere 6.0, we would really advise not going over 100ms. The higher the latency between PSCs, the higher the risk of conflicting changes within the SSO domain. Also, from a UI performance perspective, if you are managing multiple vCenters via Enhanced Linked Mode, it is going to get slower and slower as that latency increases. We're definitely collecting feedback from customers and we would like to allow our customers to architect their SSO domains as they see fit. But today we have these guidelines we need to work within. Hope this helps!
What was the original error message (looks like it got cut out of your post or didn't paste properly). Are you running an embedded PSC? If not, did you upgrade your PSC first? Its a long sh... See more...
What was the original error message (looks like it got cut out of your post or didn't paste properly). Are you running an embedded PSC? If not, did you upgrade your PSC first? Its a long shot, but did you do a CRC check on your ISO to make sure it matches? Or try to use the URL patching method instead of the ISO?
Have you updated to the latest version of the Client Integration Plug-in? You can find download links in the Resolution section of this KB article: VMware KB: vSphere Web Client integration pl... See more...
Have you updated to the latest version of the Client Integration Plug-in? You can find download links in the Resolution section of this KB article: VMware KB: vSphere Web Client integration plug-in fails in Google Chrome 45 or later
Hmm, you're right. I'm able to do this in my lab. The weird thing is that it presents a different certificate than when I access via 443. I'm not sure this is expected. This is off-topic but I'm ... See more...
Hmm, you're right. I'm able to do this in my lab. The weird thing is that it presents a different certificate than when I access via 443. I'm not sure this is expected. This is off-topic but I'm going to look into it. Thanks SavkoorSuhas‌!
Port 9443 is for the 5.x Web Client. For 6.0 the URL to get to the inventory is https://<vcenter fqdn>:443/vsphere-client For example: https://mgmt01vc01.sddc.local/vsphere-client
JamieGator32 That KB is only applicable to vCenter Server 5.1/5.5. netwatcher_s1 Here is a great blog that illustrates what you need to do: http://blogs.vmware.com/vsphere/2015/10/reconfigurin... See more...
JamieGator32 That KB is only applicable to vCenter Server 5.1/5.5. netwatcher_s1 Here is a great blog that illustrates what you need to do: http://blogs.vmware.com/vsphere/2015/10/reconfiguring-and-repointing-deployment-models-in-vcenter-server-6-0-update-1.html It sounds like you didn't quite get the entire process completed. Also note, you need to be running at least vCenter 6.0 Update 1 in order to perform this repoint operation. And to clarify your vCenter Database does not live on the PSC. It still lives on the vCenter Server. To learn more about the PSC you should take a look at this article: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2113115 If you have other questions that aren't answered by the 2 articles just let me know.
Could be an issue with the CIP (Client Integration Plugin). Give this a try: VMware Client Integration Plugin (CIP) v6.0 Issue on Mac OS X
The script runs successfully without any errors. The issue is with the report.  Because of changes between the HW versions (see section in the script regarding how it deals with differences in... See more...
The script runs successfully without any errors. The issue is with the report.  Because of changes between the HW versions (see section in the script regarding how it deals with differences in HW4 and HW7) the script does not correctly report the VMDK to logical drive mapping for VMs with HW8 (or newer).  At least not for my customer. For example, they have a Windows 2008 R2 VM that has quite a few logical drives - 10.  Each of those drives is assigned a drive letter in Windows.  The script correctly maps some of the VMDK's to drive letter but most of them list a blank drive letter. I'm sorry I can't provide a screenshot at this time but I'm working on it. I know that would help.
Sure, it's a bit tough since this came from the book (i.e. no easy way to copy/paste) so indentation and line breaks may be wrong.  File is attached.
Hey all, I'm trying to help a customer map some VMDK's to logical drives in Windows.  We were trying to use Get-VMDiskMapping from Alan & Luc's book but just as there was an update required for H... See more...
Hey all, I'm trying to help a customer map some VMDK's to logical drives in Windows.  We were trying to use Get-VMDiskMapping from Alan & Luc's book but just as there was an update required for HW7 there seems to be some changes required for HW8 because the script does not report correct information.  Has anyone tried and successfully used the script on vSphere 5.1+ with HW8+? Thank you!