I normally avoid sage at all cost, but they seem to have quite the offering for construction.

was the company happy with those products? how was supporting them?

one of my clients who has the WORST ehr on the planet uses macro's in word and have to be enabled by default and it's very insecure. anyway....i've warned them of this disease, and will filter out doc/docx

yeah, i've never not had issues with it. for atleast a year or so now.

GFI does it as well.

well, max focus or whatever it is this year

Bringing this back up to the top. Just in case y'all were hungover last week

or if anyone knows a pbx distro that has a built in faxing (email/portal) setup.... i'll take that as well. #googlling

you should ask the legal dept
paging @KOOLER or @Jason

#flamesuit

i'm gonna download and play with AV. I see open source and then i see pricing. what am i going to miss out on using the "free" ISO?

@JaredBusch you reckon it's the 60xx port problem that we've both run into?

Put the phones back on network. And under the reporting tab in Fpbx check your devices. See if the two devices that are not working are getting super high ports. If so you can manually assign a sip port within range and they will work. Sorry typing from my phone at a client so I don't have my specific notes or anything. @JaredBusch helped me with this problem in the past.

@fuznutz04 you can manually assign ports and it will fix this problem. 6051,2,3,4,5 etc if I'm not mistaken. Make sure not to duplicate any. That will get them functioning until you replace their shotty router.

their bridge mode isn't a true bridge either. just FYI

@scottalanmiller Scott you dont live in the real world bud. I've got two servers on site, and one colo'd, hyper-v replication to the colo'd server. on site altaro VM backups, on site Data backups, AND Code42 HIPAA off site data backups.... the customer is fine. Their data is fine. I dont even know what we're talking about, but your responses usually just get me keyed up. HEY NOW

Hey now,

I've got a 2016 server I've stood up in a sbs2011 domain, added it as a DC, moved all FSMO roles to the new server since the goal is to murder the sbs2011 machine, verified replication is healthy, migrated exchange to o365. Here's where the fun starts.....

In order to test the server, I've shut down the SBS2011 box and reboot a domain joined computer, and hope that hey.... it's gonna use the new DC as the logon server... nope. any ideas what I'm lacking here folks?