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.
-
@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.
-
@ccwtech said in Network setup - Hyper-V:
@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???)
Don't tell them. If they ask if it uses SMB, say yes, because it does.
-
@ccwtech said in Network setup - Hyper-V:
@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.'
That's pretty much what I said when I looked at it, yes.
-
@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.
-
@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.
Should slow it down, but would provide the "we don't use a shared local file" defense for support
-
@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.
-
@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 what is the path you're using to access it on the RDS? I assumed you were accessing locally - so perhaps I was totally off base there.
-
@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.
-
@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 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
-
@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?
