@coliver I have read that a lot of NIC drivers do the VMQ implementation poorly in drivers which can kill performance, so I usually disable it, just to be safe. Most notably, this problem is especially prevalent on the Broadcom chipsets... I see you have intel.

It may be worth a shot, but there will be a brief blip if you use the powershell command to disable VMQ.

get-help VMQ

will list the commands.

get-netadaptervmq|where {$_.Name -eq 'NIC1'}|disable-netadaptervmq

Just replace NIC1 with whichever NIC is currently running your PBX VM.

Have you considered disabling VMQ ?

counts non-broken fingers

I'm not lucky enough to have a real test environment at home. I've got a Windows 8 system that I use to run a couple of Hyper-V VMs... but that's about it.

@coliver have you checked to see if the NICs in your Hyper-V server actually have VMQ enabled or not?

In Powershell (assuming Server 2012 / R2) try

get-netadapter-vmq

@garak0410 Can you recreate the old emails and do a password reset then?

@Dashrender I'd upvote that comment 10,000 if I could.

@g.jacobse Tea. Definitely Tea. Or coffee in large quantities.

@Dashrender said:

Wow.. you two live in a wonderful world! (snip)

I did have a relatively good childhood, lol. No major catastrophes struck, and I learned a lot from my old man. 8-) My kid is only 4, so he's not quite ready to start fixing his own problems yet. But I still let him try and teach him to ask for help when he needs it!

I completely agree with where this article (and Scott) are going with this, and I see the trend every day in my office.
(snip)... is that they just don't care to learn it, even after asking 10 times and learning it would get them resolved in half the time or better.

By and large, especially in a corporate setting, i will agree with this as well. I hilighted the real problem... Most of the time they just don't really care to learn anything outside of their job.

@Carnival-Boy said:

I think it's the other way round. In households where one person is tech savvy there is a tendency to tinker, fiddle, experiment and ultimately break things. The non-IT person then has to either wait for it to be fixed, or give up waiting and fix it his/herself.

Or in the case of my house (both growing up and after getting married) -- whoever doesn't do the technical work starts trying to fix it themselves, and soon they become proficient at doing at least some level of tech work -- even if they only do it for themselves.

@art_of_shred Details details... I still call it useful for fish bait, lol... It doesn't make such a good drum stick now.

I'd never even played Rockband, I don't think.... or Guitar Hero, lol.

@scottalanmiller I would argue that about MSSQL and MySQL. We ran those on the Same box (as part of the same cluster) for a number of years. The only minor issue that would happen is that the SIS that the Campus used would throw an error message and wouldn't automatically reconnect. The error message I can understand. But not automatically reconnecting? That is an application issue and not a problem with Failover.

Our MySQL applications never had this problem.

We were probably just lucky, but we never lost any data in MSSQL Server due to a failover event.

@thecreativeone91 said:

This looks like something I'd use to get fish bait in the areas of my yard where the grass grows the thickest.

@scottalanmiller -- Just so I understand... In most cases, Application Level Clustering > Windows Failover Clustering ?

@MattSpeller I don't think he's talking about getting them P3's with 512MB RAM... But does your Receptionist really NEED an Intel i7 with 16GB or RAM?

No? Get her an i3 with 4GB or 8GB of ram and a 256GB SSD drive... Don't have to buy that new.

@MattSpeller In other words: Party at your parents' place this weekend?

@scottalanmiller said:

Playing around with Cockpit for the first time. At first glance, pretty sweet interface.

What is Cockpit?

@Dashrender said:

It's less me having a problem with this cost, and more the administrator. Management often doesn't see value in something they can't see directly having an effect on production or productivity.

If it breaks after it has been EOL'd can they still next day you one to replace it with?

@Dashrender said:

How is this better? Especially since leasing no longer gets you the tax breaks it used to. If I was going this route I might as well just buy a new unit every three years.

Less up front damage to your IT budget is one (depending on how big of a hit that is to your budget!)... It seems like I may have misread that bit about being EOL'd after only 3 years. I read it to be EOL'd every 3 years.

@scottalanmiller said:

The major issues with SonicWall are around undocumented features and high cost for low value.

I would argue that Fortigate is worse in this department. Granted, I haven't done business with them for several years, so maybe they got their act together.

@Dashrender I would get them to lease it over 3 years... at the end of the 3rd year, just upgrade to the latest model that meets your needs (if they have released a new one). Especially if you are happy with them!