@dashrender said in Network setup - Hyper-V:
@ccwtech said in Network setup - Hyper-V:
@dashrender On the RDS it's just a path off of the drive C:\Data\program.exe (with the exe and all data)
For non-rds it's the \servername\data\program.exe
so you are using a drive letter on RDS. It's only support that's being a pain about this.
If you connect to \servername\data\program.exe while on the RDS server, does it become slow?
Nope. Works great.
@dashrender On the RDS it's just a path off of the drive C:\Data\program.exe (with the exe and all data)
For non-rds it's the \servername\data\program.exe
@scottalanmiller said in Network setup - Hyper-V:
@ccwtech said in Network setup - Hyper-V:
@dashrender said in Network setup - Hyper-V:
@scottalanmiller said in Network setup - Hyper-V:
@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.
In the case of the OP, the application is in a folder on the RDS server. so no SMB needed.
A test would be accessing it via the share instead of via the local drive letter.
You can not use a drive letter with the software (according to the software vendor) - it's all via unc path.
So weird, the drive letter is just a perm UNC mapping.
I am aware, but if they see a drive mapped their support will walk away... To quote myself "You remember which software you are talking about."
@dashrender said in Network setup - Hyper-V:
@scottalanmiller said in Network setup - Hyper-V:
@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.
In the case of the OP, the application is in a folder on the RDS server. so no SMB needed.
A test would be accessing it via the share instead of via the local drive letter.
You can not use a drive letter with the software (according to the software vendor) - it's all via unc path.
@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.
@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???)
@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.
No, all are onsite. Some are PC's and connect with file share. Some are thin clients and use RDS.
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.
@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.'
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 VM1
NEW:
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
@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 was thinking that my last post may be very critical in solving this issue. Any ideas to help?
@scottalanmiller said in New Years Resolutions v2.0:
Selling my NY home.
Exactly how many houses do you have Scott?
Mixture of 7 and 10.
I should have tried this earlier, but I tried the application on my other VM (the domain controller - same physical box) and it's slow there as well. It's also slow on the physical box.
At least that eliminates a ton, but still doesn't tell me why it would be fast on the other VM itself.
20 MB/s seems horrible to me. My home network is much faster than that.
Going from 2008 R2 Standard to Server 2016 Standard
@dashrender said in Random Thread - Anything Goes:
@wirestyle22 said in Random Thread - Anything Goes:
@ccwtech Had an hour and a half conversation with my mother in law that was a complete waste of time relating to security. I actually said mid conversation "please don't give me an aneurysm"
An aneurysm would have been a saving grace from the situation.
LOL... be careful what you wish for!
Turning off firewalls and AV had no impact.
Initial launch and the app while in use is slow.
All PC's are impacted. All are hardwired 1 Gig cards and switches. Replaced all switches except the main switch
A ping -t shows <1 ms day or night
Transfer speed of a folder with files (about 300 Meg) is about 20 MB/s
I appreciate everyone's help here. It sucks when you set up a brand new server for a client and they want their 10 year old server back.