TBKing's Posts

A restart didn't do it, neither did the "reset-authentication" ... HOWEVER I got an email from support. The process that did fix it was: Stop configurator Reset-authentication Start configurator That got me into the Configurator GUI So the steps were correct, just a bit out of order (or not clarified) From there I was able to verify that the authentication was pointing to the PSC we took down. And of course I couldn't "Unregister" because it was down, but a RESET allowed me to enter the new PSC Thanks

OK, I got one hint .. Something with the Resource Pools? In the Lab, I have only one cluster When I move it to Prod, we have multiple clusters, and I had to repoint the "VC:ResourcePool" attribute I pointed it to the first cluster - the one that works. How do I make that attribute value valid for all clusters? Or a different approach? the "pool" attribute is in the getRelocateSpec action (com.vmware.library.vc.vm.spec)

Still at 6.0 and using c# for most things.  But on occasion we have to fire up the web pos. On one such occasion, the web client was hosed - again.  I called for support and they said Use the thick client until they figure out what's wrong. Dreading the day we move to 6.5 or 6.7 and all will have to be web.

We have AD DCs permanently living at our recovery site as well. The past few tests we shut down the DCs and created clones to stand up during the test. When the test was over, we destroyed the clones, along with the VMs created. This last time around, because we have so many other systems living permanently at the recovery site (PSC, vCenter SRM, other systems) that also need AD, we didn't do anything with the DCs. The site was isolated from production, we stood up recovered servers via SRM, while leaving the other systems online.  When the test was over, the recovered systems were destroyed, link re-established and all seems well. We did not have to make any changes within AD (password changes, add accounts/machines, change permissions) so we did not have to move/seize any FSMO roles. AD seems pretty resilient to disconnects and isolation events.

We're in the process of migrating to 6.0. From what I recall of the 5.5 web client, the 6.0 performance is improved some. Now I can get frustrated more quickly when I can't find something. like ...why does "Hosts and Clusters" show me Clusters and Guests, and not the individual hosts under the cluster? Once in a while I've stumbled across the familiar Cluster-Hosts tree, but haven't figured out the trick yet. Setting up SRM, I need 3 clients open - c# for real work at Protected, c# for real work at Remote, and web for SRM

(Off topic: Let's have a guessing game on how many products VMware will rename this year, my $.50 is on 5 products) If you include Dec 2014: You can start with vRealize 6.0 - The product formerly known as vCOps

Dynamic Thresholds. If running at 100% all the time is fine and expected, vCops won't see it as an Anomaly. Possibly .. probably - if the server drops utilization low, it will see that as outside of its Dynamic Threshold, register an anomaly, and decrements the health. If the other server picks up a load, that will also be an anomaly.

"Hire a dozen usability engineers and just redo the whole thing top to bottom.  The technology works.  The administrative interfaces and docs and support sites are just beyond brutal." That will also give them another opportunity to re-name and re-bundle the products like they are so fond of doing!

"And more if necessary. Heck, if you really wanted, you could deploy it to a gaming console and manage your VMware from your couch using your Xbox, or PS4, or whatever." Or more justification to purchase an Xbox for the break room!

Are you planning a larger environment?  Joining more departments together? It wouldn't be bad to get it in the door and familiar with it before there is a perceived need. There's a lot in it, but pretty straight forward for the basic set up, and not much overhead to maintain it. However, if there is a significant cost I would question the value for such a small environment at the moment.