krnewell2011101's Posts

Do you have any idea what the timeline is on getting a 5.8 rev or Update Manager? or is it far enough out that the two will only meet again at a later revision (6.0?) We had assumed that Updat... See more...
Do you have any idea what the timeline is on getting a 5.8 rev or Update Manager? or is it far enough out that the two will only meet again at a later revision (6.0?) We had assumed that Update Manager would at least be compatible with Powershell 3.0 since it's been around for 2 1/2 years. Ken
I agree that matched versions are one requirement, but from what I'm experiencing a second requirement is that you have to run it all in Powershell 2.0. Currently in all my production environment... See more...
I agree that matched versions are one requirement, but from what I'm experiencing a second requirement is that you have to run it all in Powershell 2.0. Currently in all my production environments I use PowerCLI 5.8, but it appears now that if I want to use Update manager I have to back down to PowerCLI 5.5. Also in doing so I have to force powershell to execute in V2.0 mode which means no access to 3.0 commands. Specifically the command I'd really love to have would be out-gridview for filtering/creating baselines from patch lists. That's why I ask,"is that really the most current functioning state?" Is the only answer that there is no version of update manager compatible with either PowerCLI 5.8 or Powershell 3.0? Ideally I'd like to have both, but at this point I'd accept powershell 3.0.
By reading some other threads I've managed to figure out that I can run the latast update manager by backing down both my powerCLI version (to 5.5 R2 patch 1) and my powershell version to 2, but ... See more...
By reading some other threads I've managed to figure out that I can run the latast update manager by backing down both my powerCLI version (to 5.5 R2 patch 1) and my powershell version to 2, but is that really the most current functioning state? We're trying to build some update manager automation to synchronize dev/stage/prod tiers and it's really upsetting to see that I have to turn the clock beck a year or more in order to just run some commands. Here is the version info where I'm getting the crash: PowerCLI Version ----------------    VMware vSphere PowerCLI 5.8 Release 1 build 2057893 --------------- Snapin Versions ---------------    VMWare AutoDeploy PowerCLI Component 5.5 build 1983942    VMWare ImageBuilder PowerCLI Component 5.5 build 1983942    VMware vCloud Director PowerCLI Component 5.8 build 2031582    VMware License PowerCLI Component 5.5 build 1265954    VMware Storage PowerCLI Component 5.8 build 2057894    VMware VDS PowerCLI Component 5.8 build 2031581    VMware vSphere PowerCLI Component 5.8 build 2031581    VMware vSphere Update Manager PowerCLI 5.5 build 1302474 Thanks
Have you tried testing with HA admission control turned off? I have recently started looking into DPM w/vCD and haven't started active testing yet, but at a glance I would assume this is the hang... See more...
Have you tried testing with HA admission control turned off? I have recently started looking into DPM w/vCD and haven't started active testing yet, but at a glance I would assume this is the hangup. With HA admission control turned on you'll probably hit that wall from the vCD side. If you shut off admission control I would assume it would let your power-on succeed, add too many resources for the existing hosts, and trigger DPM to start another host to reduce contention afterwards based on load rules. If you have spare hosts (required for DPM already) then admission control shouldn't be a big deal unless you can't sustain the temporary contention you may cause while waiting for a new host to boot up and rebalance.