Yes, that is primarily how it's used.

@tech1 said in If you are new drop in say hello and introduce yourself please!:

@scottalanmiller said in If you are new drop in say hello and introduce yourself please!:

Welcome @Tech1

Thank you,

Hello! My name is Angie and I am a complete newbie, I am currently working towards getting certified and get as much hands on experience as I can.

Welcome Angie!

@black3dynamite said in Network setup - Hyper-V:

@ccwtech said in Network setup - Hyper-V:

Odd to say the least. Their system requirements are low, we even purchased a new PC (for one of the workstations) to see if that would help.

The new PC is a I5-7400 CPU 2.4 Ghz with 8 GB Ram so it is more than sufficient.

Requirements:
Processor Intel Core i7, i5, i3 Intel Core 2 Duo 2.53 GHz
RAM 6 GB (64-bit) | 4 GB (32-bit) 2 GB
Hard Disk 160 GB available disk space 80 GB available disk space
Optical Drive DVD RW DVD ROM
Network Adapter Ethernet 100/1000 Ethernet 100/1000
Monitor 19 LCD/LED (or larger) 17 LCD/LED
Video Adapter 32-bit, 1024 x 768
or higher resolution capable
16-bit, 800 x 600
or higher resolution capable
Sound Standard sound card Standard sound card
USB 6 available USB 2.0 Ports 4 available USB 2.0 Ports
Operating Systems (32/64-bit) Windows 10 Professional
Windows 8.1 Professional
Windows 7 Professional

You can try setting up a Windows 10, 8.1 and 7 VM on the host and see if the performance is still slow.

Ran on both, same result (no output). I had them teamed but unteamed for testing to see if that was the issue.

@black3dynamite said in Network setup - Hyper-V:

@ccwtech said in Network setup - Hyper-V:

@black3dynamite said in Network setup - Hyper-V:

Get-NetAdapterVmq

Thanks.

Running that command produces no output. It just goes to the next line.

Vmq not enabled.

Well that's good and bad... Good that it's not enabled, but bad that that's not the solution.

@black3dynamite said in Network setup - Hyper-V:

Get-NetAdapterVmq

Thanks.

Running that command produces no output. It just goes to the next line.

I have also copied the application to the physical server to do some testing.

@dashrender said in Network setup - Hyper-V:

Get-NetworkAdapterVmq

I just get an error saying that's not a recognized command. That is for powershell right? (I also tried command line)

@black3dynamite said in Network setup - Hyper-V:

@ccwtech said in Network setup - Hyper-V:

@ccwtech said in Network setup - Hyper-V:

Transfer speed of a folder with files (about 300 Meg) is about 20 MB/s

20 MB/s which seems VERY slow to me.

Is that with IP or DNS?

DNS I will try via IP

@ccwtech said in Network setup - Hyper-V:

Transfer speed of a folder with files (about 300 Meg) is about 20 MB/s

20 MB/s which seems VERY slow to me.

@scottalanmiller said in Network setup - Hyper-V:

Ideally you'd want to use the very latest SMB protocol. But that doesn't appear to be the issue regardless.

Ok, it had been suggested here.

I'm just looking for anything else to try at this point.

@dashrender I have set up another VM (In this case Windows 7 Pro 64 bit with SP1)

It's slow on this machine as well.

Anything outside of the VM where this app runs is slow (virtual or physical machines).

I haven't enabled SMB 1, does that need to be done on the VM and Physical machine?

@dashrender said in Network setup - Hyper-V:

It would not hurt to set up a Windows workstation as a VM and do a test to make sure that you’re not having some kind of problem with that Windows server vm

I'm willing to try almost anything right now. I just was wondering what that would show... Booting up a VM shortly.

That's the $1,000,000 question...

@black3dynamite said in Network setup - Hyper-V:

@ccwtech said in Network setup - Hyper-V:

Odd to say the least. Their system requirements are low, we even purchased a new PC (for one of the workstations) to see if that would help.

The new PC is a I5-7400 CPU 2.4 Ghz with 8 GB Ram so it is more than sufficient.

Requirements:
Processor Intel Core i7, i5, i3 Intel Core 2 Duo 2.53 GHz
RAM 6 GB (64-bit) | 4 GB (32-bit) 2 GB
Hard Disk 160 GB available disk space 80 GB available disk space
Optical Drive DVD RW DVD ROM
Network Adapter Ethernet 100/1000 Ethernet 100/1000
Monitor 19 LCD/LED (or larger) 17 LCD/LED
Video Adapter 32-bit, 1024 x 768
or higher resolution capable
16-bit, 800 x 600
or higher resolution capable
Sound Standard sound card Standard sound card
USB 6 available USB 2.0 Ports 4 available USB 2.0 Ports
Operating Systems (32/64-bit) Windows 10 Professional
Windows 8.1 Professional
Windows 7 Professional

You can try setting up a Windows 10, 8.1 and 7 VM on the host and see if the performance is still slow.

I can try that, but how would that be different than running it on the other VM (Server 2016) that is the DC?

Odd to say the least. Their system requirements are low, we even purchased a new PC (for one of the workstations) to see if that would help.

The new PC is a I5-7400 CPU 2.4 Ghz with 8 GB Ram so it is more than sufficient.

Requirements:
Processor Intel Core i7, i5, i3 Intel Core 2 Duo 2.53 GHz
RAM 6 GB (64-bit) | 4 GB (32-bit) 2 GB
Hard Disk 160 GB available disk space 80 GB available disk space
Optical Drive DVD RW DVD ROM
Network Adapter Ethernet 100/1000 Ethernet 100/1000
Monitor 19 LCD/LED (or larger) 17 LCD/LED
Video Adapter 32-bit, 1024 x 768
or higher resolution capable
16-bit, 800 x 600
or higher resolution capable
Sound Standard sound card Standard sound card
USB 6 available USB 2.0 Ports 4 available USB 2.0 Ports
Operating Systems (32/64-bit) Windows 10 Professional
Windows 8.1 Professional
Windows 7 Professional

@dashrender said in Network setup - Hyper-V:

@ccwtech said in Network setup - Hyper-V:

@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.

Is it slow for PC (SMB Share) users right now?

Yes

@dashrender said in Network setup - Hyper-V:

@ccwtech said in Network setup - Hyper-V:

@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.

Remind me - Hyper-V 2016? RDS on Window Server 2016?

Yes

@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