No console for customer in VMware module???

[tallship]

Is there no console for the customer in the VMware module? Customer's really need a console access feature - for example, in case they lock themselves out of SSH, or in case they brick they're RDP by switching to ports they can't access, etc.



It looks like all they get is the ability to stop and reboot their server - not even a start option? And reboot *should/probably* require that they have installed VMware Tools on the client machine too, otherwise, they would, under vSphere client anyway, only have the ability to stop the machine (crash it).

We never got the VMware 5 module to work. We thought so, until we actually tried to provision a machine and found out the hard way that it didn't work, then updated HostBill, and it was completely broken, and then it was no longer free. Other people who opened tickets were told that they had to pay money to get it to work again - apparently some did, and found out that it was still broken.

IIRC, they changed the price to something outrageous, and at $99.00 (I think they lowered the price again? I can't tell, remember, keep up with these prozac changes) it's still outrageous - especially for a module that is known not to work, as per a couple of threads here already, but who even knows for sure. I didn't see anything mentioned on the changelog about a fix, but I'm becoming weary of the pinball game and not paying as close attention.

I know VMware has offerings that provide local virtual console access for the customer, but does anyone know of other alternatives so that we can supply local console access to customer's machines so we don't have to ask for their admin/root passwords and intervene via our console capabilities in vCenter?

Oh how I'm looking forward to seeing what ModuleGarden comes up with!

Thanks. 

[UCG_Keith]

sorrt for the brevity as I reply on my phone.  An option to consider which requires some manual intervention if you use vCenter (web version), put the clients vm into a specific directory and create a user for that folder as a vm manager. Its basically what vcloud does. We did this prior to vcloud director.

I personally would rather see hb build a real, functional, bugless vxloud director module. This is the main reason we left whmcs. But vcd with hb does not work, as usual. I contacted Matt at whmcs and will asked for a quote to build it.

id rather put the system that complete controls my business in the hands of developers that will talk to you.  I am very concerned that we will find in a hb update some form of a malware or hack.  At this point hb cannot be trusted. He has a very good track record of inconsistencies, boarderline dishonesty. This titanic is going down and I don't want to be with the orchestra until its too late.

[tallship]

Hey thanks a bunch Keith


I can do that, and it would solve a lot of issues involving us to intervene on self-managed accounts.