Did you try the FreePBX v17 ISO ?
Or standard Debian then manually run the FreePBX v17 shell installer ?
Also what kind of VM infrastructure ?
Yes, though I imagine the ISOs aren’t going to be my friend for much longer, I wager. I guess I’m just old school like that, but I always use ISOs where I can.
I’m afraid I don’t understand, as I’d be lying if I said I did, but if it means what I believe it means, I use Oracle VirtualBox, complete with HyperV and all the fancy virtualization stuff
EDIT: The write-up mentions
apt-get install build-essential fakeroot devscripts
My machine reports No package build-essential available Do I ignore this? Or…?
Just got a lunch break, I suppose you might want to share the VM settings you have, anything that may seem important. Additionally, if you aren’t googling it right now, see what the Red Hat equivalent to those tools are, being a former teacher for about five years, having worked with people such as yourself, I can understand the frustration of getting stuck when an error is being thrown your way, especially one you don’t already know how to counter, but it’s all worth a shot, I suppose.
Right, so the base memory is set at 2GB, figured that’s all it needed, PIIX3 chipset, EFI Boot enabled, Clock in UTC (Duh, because Unix), I/O APIC enabled, 2/8 processors are use at 100% exec cap, PAE/NX enabled (VT-x is grayed out) Paravirtualization set to defailt with Nested Paging on, VRAM maxed at 128MB, Graphics are VMSVGA, no 3D accel (don’t need it), bridged adapter type for network, and no serial port.
As for the equivalent tools, I’ll look into that now
EDIT: 64GB Disk drive
EDIT 2: Stuck on apt-get source tftp-hpa. Of course I know my system comes with its own TFTP server, but I’m going to guess this one isn’t good enough, though I’m not 100% sure why this might be, or what to do and whatnot
We’ll keep 'em coming 
along with the change!
Missed that in one of your earlier posts, oops.
There’s reports of it working, eventually, despite not working, at first: This FreePBX 17, ISO Install Is Not Working on Hyper-V
Anyhow, getting off-topic a bit, mind if we split out the Hyper-V stuff into a new thread ? Curious where it is failing exactly…
Fabulous, thank you!
No worries, always glad to clarify, more clarity is more better (and better than less)
Gladly, pubbo (Public) or private is your call
You are trying to change the TFTP server ? Probably not necessary, until things are up and running; however, even if you do want to change, apt install tftp-hpa is likely closer to what you want.
Mehbeh, but using a CentOS-based system makes that tough…
Just noticed the title, is this future-proofing? Or for the current situation? Because right now I’m on FPBX 16
OH I KNOW WHAT I COULD DO! I could make another VM and run the install process again!
That’s good to know – if no issues running v16 in Hyper-V, then the communicator thread this current thread was forked from is probably the better place to discuss the communicator issues.
But, it sounds like you were encountering some v17 issues in Hyper-V, thus the thread fork.
With v17 
Exactly! Working it as we speak
So future-proofing in a sense, copy that
EDIT: Felt the need to mention this; wasn’t sure where to mention it, but here felt appropriate. I typically don’t like going directly to the NEWEST version for THESE reasons, because if I go a version or so back, then I get a very good feeling that it’ll work for what I need it to do, without having to constantly uninstall/reinstall the system, and I typically find it’s easier to do on a VM because then I get to host it at-will and I have rapid access to it, but even this has its drawbacks, as we’re seeing now
EDIT 2: Installing FPBX 17 this go around has been really scary, Steam went down for maintenance as the VM was installing a module, right now it’s going pretty slowly… and i also can’t seem to figure out the IP for the system either, unless it hasn’t gotten there yet…
So I guess it installed correctly? But I can’t get to the webUI, “ifconfig” and “if” anything comes back not found… and it’s just not getting an IP, I guess…
Found it, now the command is ip a s
Also, for the record, I liked the older FPBX splashscreen/motd/bash screen better…
Alright, update. Instead of a TFTP Timeout, now I’m getting a TFTP Error, so progress…
That’s, umm, great news !?
Back to the original thread ?
Or are there some additional Hyper-V tips/tricks for FreePBX v17 installation that you might be able to share ?
Since this was marked as the solution, for anyone tuning in: If you’re having install troubles, just re-make the VM, sometimes it’ll work, and sometimes you should go into the host machine UEFI/BiOS and ensure that the virtualization stuff is on, if not that, make sure the VM has all the correct virtualization settings on as well
Back to the original thread, the issues I thought I was having with the install are apparently no longer present, but can’t say the same about the IP Communicator as of now
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.