Please provide your feedback in this short Flings' survey.
Sep 05, 2019

Does in take into consideration if Hot add is enabled or not ?

Oct 17, 2019

Suraj v2.0.0 was just uploaded and includes additional information that I identified below. Sorry for the delay!

Sep 10, 2019

Suraj, I'm currently working on a 2.0 version that takes into account CpuHotAdd, vHW version, and vCPUs <9, and vCPUs < Host Cores/Socket in calculating whether or not the pNUMA of the host is exposed to the guest OS. Should be done by early next week.

Aug 30, 2019

Would like to see the cluster identified for aach VM as well if this can be included in future.

Oct 17, 2019

Glenn, v2.0.0 was just uploaded, and includes cluster information, including if the cluster has hosts that are inconsistent. The findings are assigned a priority, and include details on what was found.

Sep 04, 2019

Thanks for the feedback Glenn! I am planning on building that into the next version along with a few other enhancements. Now that VMworld is done, hopefully I can dedicate some time to it!

Aug 20, 2019

Nice work on v1.0.4. It's a lot faster. One thing that I noticed is that the A Column (vCenter) shows both the FQDN and short DNS names. This of course duplicates the output. I entered the short DNS name when deploying the script and that quadrupled the rows. It's an easy Find/Replace/Remove Duplicates in Excel, but wanted to point it out. Keep up the good work.

Aug 20, 2019

Thanks for the feedback Tank. There should only be 1 line per VM in the output. It gets the vCenter name from the VM's "ServiceUrl" value, so it shouldn't matter whether you use the FQDN or short name, as long as they are resolvable from the machine you are running the script on. With that said, if you are getting duplicates under "VMName" with a short name and FQDN value in the vCenter column, you most likely are already connected to vCenters in the same session you are running the script in. The script will disconnect your vCenters when it completes, but only the ones you specify. One quick way to check: at a Powershell command line, type in "$global:DefaultVIServers". If you are showing connected vCenters, they will get added to your report, and they are seen as different vCenters if the name does not match, which is the case between FQDN, shortname, or IP address.

Easiest solution: start with a new Powershell session, so there will be no existing connections to vCenters.

I will add that to my list of changes, as it can easily happen to others! I'll plan to filter the output so it only includes vCenter names that are specified in the script input.

Thanks for your feedback!

Aug 20, 2019

Good call. I was messing with Tags earlier and never disconnected.

Aug 04, 2019

Hey guys, nice work on this. I was looking at the code and I'm confused about something. Version 1.0.3, line 151 there's a var $hostCPUs but I can't tell where that value is coming from - can you clarify that this is the number of sockets? Seems like that's what it should be if I'm not mistaken.

Aug 09, 2019

John, apologies for the slow reply. I understand your confusion, and that IF statement should have been commented out. I had started to build in logic to calculate the total number of host CPUs to ensure that the VM couldn't possibly be configured with more than what the host had, but I need to capture hyperthreading settings as well. I'm planning that for the next update.

In theory, that IF statement should never hit, as the variable is undefined, so it doesn't affect the output, but I appreciate you calling it out, as I forgot that it was in there!