@rnmixon wrote:
[Edit by xrobau: Moved this into a new thread, it had nothing to do with the old one]
I just ran across this thread I know it's old.
We've leveraged Hyper-V at a number of customers to eliminate a dedicated hardware appliance that has to be taken care of. We do not have any of the issues others are reporting with Hyper-V. That said, none of our systems have more than 30 extensions - so we well might hit problems as we grow, hope not. We've also been able to successfully run other network appliances under Hyper-v without too much grief.
What was an unpleasant surprise was when we went to upgrade from 6.12.65-32 to 10.13.66. We are unable to boot after the upgrade, had to restore back to a snapshot. This has happened on two systems and I've got three more that also need the upgrade.
The FreePBX distro is supposed to be based on CentOS 6.5 or 6.6 - we have not had any issues upgrading our Centos 6.5 web servers to CentOS 6.6 under Hyper-V, so I'm trying to figure out what's different about the FreePBX distro that causes this.
Any ideas?
Posts: 2
Participants: 2