Windows 2019 Slower Than Windows 2012 R2
-
@scottalanmiller said in Windows 2019 Slower Than Windows 2012 R2:
@DustinB3403 said in Windows 2019 Slower Than Windows 2012 R2:
Scott migrated a legacy application from 2012 to 2019. That's 7 years of change
Only five. 2012 R2 is from 2014.
SMH, 2 years is still a long time.
-
@scottalanmiller said in Windows 2019 Slower Than Windows 2012 R2:
@DustinB3403 said in Windows 2019 Slower Than Windows 2012 R2:
Assuming the customer didn't actually update the client software, which was likely developed with SMB1 only in mind.
the client software is regularly maintained, but not "updated" very much.
So very likely a culprit, do you know what the client software is setup to use?
-
And more to the point did enabling SMB1 resolve the issue?
-
Last question for now, is the client software QuickBooks?
https://media.tenor.com/images/7629d456b68179bebc19e525c8aeb051/tenor.gif
-
@DustinB3403 lol, no, it is not. It is an obscure vertical scheduling package.
-
@DustinB3403 said in Windows 2019 Slower Than Windows 2012 R2:
And more to the point did enabling SMB1 resolve the issue?
Won't know till we get a window to reboot it.
-
@scottalanmiller said in Windows 2019 Slower Than Windows 2012 R2:
@DustinB3403 said in Windows 2019 Slower Than Windows 2012 R2:
And more to the point did enabling SMB1 resolve the issue?
Won't know till we get a window to reboot it.
On SW (emoji's won't work for some reason), a post seems slightly related because it was dealing with SMB shares on 2019.
It linked to MS site for the fix -
It mentioned Disabling RCS on the vswitch and/or the NIC itself.
-
@JaredBusch said in Windows 2019 Slower Than Windows 2012 R2:
You might look at VMQ.. it is supposedly not a problem anymore. but meh...
I would second this -- both at the HOST and inside the VMs (if it's there).
-
What data (not user feedback) do you have from before the migration that you're comparing to now to validate the issue? Knowing this can help identity the issue
-
What windows version is on the client? It's not 10 / 1803 or newer is it?
-
Did you get this resolved?
-
@JasGot said in Windows 2019 Slower Than Windows 2012 R2:
Did you get this resolved?
I was going to followup and ask this myself.
-
Safe to assume that any other moving parts have been taken out of the picture / accounted for (change in AV for instance)?
-
@scottalanmiller that's hardly any difference than Intuit Quickbooks. I have the same issue. However, it's more than likely SMB that causes that crap.
-
I wonder if the new feature in Server 2019 called SMB WriteThrough would help in this situation. https://www.veeam.com/blog/new-smb-client-parameter-windows-server.html
-
@scottalanmiller just read this post from Intuit support which I know what your talking about is different. But I recall Intuit not even supporting NAS/SAN unless it was built on a Windows or Linux system. But some reports from intuit say defragmentation causes the problem, even when on an SSD. I smell fish.
![alt text]( image url)
-
@DustinB3403 said in Windows 2019 Slower Than Windows 2012 R2:
And more to the point did enabling SMB1 resolve the issue?
It did a ton, but going to see what more can be done. But it was a great start.
-
@krisleslie said in Windows 2019 Slower Than Windows 2012 R2:
But I recall Intuit not even supporting NAS/SAN unless it was built on a Windows or Linux system.
Intuit can't even tell if it is built on one of those. Effectively, they are all built on one or the other, alternatives are super rare and limited to the crazy high end. MOstly it just rules out NetApp, which of course works better than pretty anyone. So that's how dumb that is.
-
@JaredBusch said in Windows 2019 Slower Than Windows 2012 R2:
You might look at VMQ.. it is supposedly not a problem anymore. but meh...
Testing this tonight.
-
@scottalanmiller said in Windows 2019 Slower Than Windows 2012 R2:
@JaredBusch said in Windows 2019 Slower Than Windows 2012 R2:
You might look at VMQ.. it is supposedly not a problem anymore. but meh...
Testing this tonight.
I'd disable VMQ anywhere you can find it. At the host level and the guest os level.