Network setup - Hyper-V
-
@ccwtech said in Network setup - Hyper-V:
@pmoncho said in Network setup - Hyper-V:
Just trying to get your setup correct, Multiple 2016 VM's on one 2016 Hyper-V host. 1 RDS, 1 FS and 1 DC?
Is app installed on RDS or FS server?
1 Physical Box with 2 VM's
1 - DC/DNS/DHCP
1 - File Server/RDS Server (Application resides here)I am guessing they are are all on the same vswitch?
Is it slow when you access the app from the DC?
-
OLD vs. New
OLD:
Intel Xeon E5245 2.33Ghz (DUAL) / 16 GB Ram / 7,200 hard drives in RAID 1 / Broadcom BCM5708C NetXtreme GigE
VM1 - DC/DHCP/DNS - 8 Virtual Processors, 4 GB Static RAM, - Application resides on this box (file server)
VM2 - RDS Server - 5 Virtual Processors, 6 GB Static RAM - Used to remote into and run the application from VM1NEW:
Intel Xeon E5-2640 v4 2.4 Ghz / 64 GB Ram / 10,000 hard drives in RAID 10 / Intel I210 GB
VM1 - DC/DHCP/DNS - 1 Virtual Processor, 4 GB Static RAM
VM2 - RDS Server - 4 Virtual Processors, 24 GB Static RAM - This is RDS box and also where the application resides -
Maybe the issue is that SMBv1 is not available anymore for Server 2016 could be affecting the performance accessing over the network.
-
@black3dynamite said in Network setup - Hyper-V:
Maybe the issue is that SMBv1 is not available anymore for Server 2016 could be affecting the performance accessing over the network.
But you can enable just to test.
-
I'll give that a shot. Thank you!
-
What is the name of the application you are using? Have you tried to reach out to their support or Google around the issues you are having?
-
Also, don't forget to check the Event Viewer to see if there may be an error related to SMBv1/2/3.
-
@i3 It's a very proprietary veterinary software that was developed in the 80's and hasn't been updated since.
And... It's the industry leader. Their support is < worthless
Maybe not exact quote but @scottalanmiller said something to the effect of 'software developed by my uncle 20 years ago on a weekend when he was bored.'
-
So, old setup:
Win7/Win 10 using RDP to connect to RDS server (was it full desktop or published app?), and the RDS server connected via SMB to the File Server share to access the application?
No changes to the physical network switches?
-
And the current setup is:
Win 7/Win 10 PCs connect via RPD to RDS Server, where the application is now. So there is no need for the RDS to talk to the File Server?
-
OLD: Full desktop, and yes access to the file server share
New/Current: Yes, some are RDS and some are through SMB. I have always put the application closest to the users as possible. RDS the application is fast, via file share is slow.
-
@ccwtech said in Network setup - Hyper-V:
OLD: Full desktop, and yes access to the file server share
New/Current: Yes, some are RDS and some are through SMB. I have always put the application closest to the users as possible. RDS the application is fast, via file share is slow.
So RDS is for remote workers, and launch via SMB is for onsite users?
I'd double check the VMQ settings on the host.
-
No, all are onsite. Some are PC's and connect with file share. Some are thin clients and use RDS.
-
I am wondering if the best solution is just use RDS all around if you have enough licenses. Heck, W2016 is good for the next 10 years. I don't bother with SMB for my local file based app. Doing SMB cost to much in time with sporatic SMB issues (every few months) that would dork up DB files. Going RDS all around saved our company a bunch of money over the last 20 years.
-
@pmoncho Not a bad idea. Some of them must be via the file share or things like lab equipment won't work. The software isn't officially supported over RDS, the file share is the preferred method. I wouldn't waist much time if I wasn't going to be setting up another 30 or so of these in the next year or two.
The biggest thing that is different here (that I can think of) is the version of Windows Server.
-
@ccwtech said in Network setup - Hyper-V:
@pmoncho Not a bad idea. Some of them must be via the file share or things like lab equipment won't work. The software isn't officially supported over RDS, the file share is the preferred method. I wouldn't waist much time if I wasn't going to be setting up another 30 or so of these in the next year or two.
The biggest thing that is different here (that I can think of) is the version of Windows Server.
RDS isn't a supported or not supported thing. It's llike saying that book is not supported for "reading through a window".
-
@scottalanmiller said in Network setup - Hyper-V:
@ccwtech said in Network setup - Hyper-V:
@pmoncho Not a bad idea. Some of them must be via the file share or things like lab equipment won't work. The software isn't officially supported over RDS, the file share is the preferred method. I wouldn't waist much time if I wasn't going to be setting up another 30 or so of these in the next year or two.
The biggest thing that is different here (that I can think of) is the version of Windows Server.
RDS isn't a supported or not supported thing. It's llike saying that book is not supported for "reading through a window".
You remember which software you are talking about. That's their logic. (Beyondvet???)
-
This is a bit like old school Quickbooks from the sounds of it. No real DB interface, instead it's just an exe that's being pulled across the network, executed on the PC, then the data is also pulled over that same network connection.
In the case of RDS, everything is local, no network involvement at all, so any performance issues cause by the network overhead are gone.
-
@dashrender said in Network setup - Hyper-V:
This is a bit like old school Quickbooks from the sounds of it. No real DB interface, instead it's just an exe that's being pulled across the network, executed on the PC, then the data is also pulled over that same network connection.
In the case of RDS, everything is local, no network involvement at all, so any performance issues cause by the network overhead are gone.
Yes.
-
@dashrender said in Network setup - Hyper-V:
This is a bit like old school Quickbooks from the sounds of it. No real DB interface, instead it's just an exe that's being pulled across the network, executed on the PC, then the data is also pulled over that same network connection.
In the case of RDS, everything is local, no network involvement at all, so any performance issues cause by the network overhead are gone.
I'd expect RDS to use SMB just the same as any other end point.
