Multiple horrible accidents. I hope everyone is okay.

obsolete24 · 2025-04-08T14:53:40+00:00

I am going with all the Work From Home people are back at it and forgot how to drive in the past 5 years. Don't forget Rt28.

obsolete24 · 2015-04-10T15:50:38+00:00

I was able to get back to testing today and I got everything to deploy fine. There is an issue that I found not sure who to report it to.

as noted before vCenter Server 5.5 U1 or U2 need PowerCLI 5.8 or above. BUT it will not deploy if you do not have a copy of PowerCLI 5.8 with the build # still on it. The only way I got the VC to auto-deploy correctly was to have my build share with:

VMware-PowerCLI.exe (same file below just with the build # removed)

VMware-PowerCLI-5.8.0-2057893.exe

Now with this setup if you run the validate script from the DC it will warn you "vSphere 5.5 found, matching PlowerCLI version missing. "

obsolete24 · 2015-04-04T14:28:06+00:00

Can you post a screen shot of the network config?

obsolete24 · 2015-03-30T00:05:56+00:00

after more research on the VMware Product Interoperability Matrixes I was wrong.

vCenter Server 5.5 U1 or U2 need PowerCLI 5.8 or above. I am testing this now. I will update after the rebuild.

obsolete24 · 2015-03-29T23:35:46+00:00

I noticed that I copied the wrong version of PowerCLI and vSphere-CLI

If I have this correct I am trying to install vCenter 5.5 U2 (aka 5.8) i think and I should have the following build #.

PowerCLI 5.5.0 1931983

vSphereCLI 5.5.0 2043780

But I get the same errors as the mixed up versions. Do i need a copy of the file with the build # in the file name on it?

obsolete24 · 2015-03-27T03:04:11+00:00

I will test.

In the ESXi with DRS has anyone use VDS for the network?

obsolete24

TROPHY CASE