@scottalanmiller said:
@garak0410 said:
@scottalanmiller said:
Can you ping it? Is the firewall open?
Pings fine. Turned on Public Remote Desktop TCP-IN and it works. Thanks...
That firewall will get you every time
Now I am truly ready to go out of town today at 12. 
Yeah...had a scare when someone called to say a 6MB file took 4 minutes to server but was a local PC issue. He rebooted and it was fine.
I'd like to find out why the host had problems before it happens again. All part of learning the Virtualization world. The ONLY thing that happened this week was a freak power surge on Monday (the debut of the new Virtual File Server) and we do have battery backups so I didn't reboot the host. I do not think that had ANYTHING to do with it but so far, it is the only factor.
@scottalanmiller said:
Can you ping it? Is the firewall open?
Pings fine. Turned on Public Remote Desktop TCP-IN and it works. Thanks...
I am sure this is easy but I still can't seem to connect to my Hyper-V host via remote desktop. The server is on a WORKGROUP and not the domain but it has been assigned an IP in our networks range. I was given a hint on here to know where it is "listening" and I've even used the listening port when trying to connect and still can't. Remote desktop is enabled. Any suggestions or "best practices"? Going out of town this weekend and would like to reach this server when I VPN.
Thanks...
@Nara said:
@garak0410 said:
The domain controller VM is now at 10 minutes for waiting for it to shut down. This point more now toward the host? Because it just isn't the file server now.
Hyper-V's a little slow, but it's not that slow. I'm still interested in seeing what the middle section of the disk part of Performance Monitor looks like. While CPU may be an issue, some of what you're describing sounds like storage latency. Do you have any snapshots going?
Well, I can do another screen shot of the Performance Monitor if needed but it is running fine now and appeared to be a host issue but I've not found the root cause.
Thanks as always for the suggestions...I think I can sleep now...and perhaps take that 1/2 day off tomorrow too!
@scottalanmiller said:
Odd, keep an eye on it but maybe something odd, like a driver failure happened or something had not updated yet and it was freaking out. Can happen.
Bad RAM perhaps? I did add some server certified RAM but not a "major" brand...
@scottalanmiller said:
@garak0410 said:
Rebooting the host has seemed to improved performance, even with Symantec running. The last time I rebooted the VM, it was at 99% CPU the entire time and took forever to do a thing...now, it seems "normal." Heck, even down to 1% at the moment.
SO troubleshooting is going to be on the host right?
Perhaps. Maybe the control environment. Do you have anything installed there?
THis is what I look like now on the VM:
Nothing but Hyper-V installed on the host. Absolutely nothing. Just a Hyper-V role that that's it...
Rebooting the host has seemed to improved performance, even with Symantec running. The last time I rebooted the VM, it was at 99% CPU the entire time and took forever to do a thing...now, it seems "normal." Heck, even down to 1% at the moment.
SO troubleshooting is going to be on the host right?
The domain controller VM is now at 10 minutes for waiting for it to shut down. This point more now toward the host? Because it just isn't the file server now.
@scottalanmiller said:
Spybot?
The program Spybot? I removed it once I used it to scan tonight. The DC VM is taking forever to shutdown too as I try to reboot the host...
@scottalanmiller said:
THis is at night with no one using it?
Yes... Right now, I am attempting to reboot the host...but the file server VM is not shutting down well. 
@Nara said:
If you bring up performance monitor, what files are being written/read? Even if the disk activity is relatively low, it gives you an idea of what the process is doing by the files it's interacting with.
It had no malware.
So, powered it off and took away a virtual CPU.
It took forever and a day to boot up and even when I finally got a login screen, it takes forever to get its services started (Welcome, Policy Registration, Local Session Manager takes forever to come up). Then a black screen for a good while and finally the desktop. And waiting and waitng for it to let me input. Server Manager creeps to a start. The right click I did on the task bar so I could get the task manager took over a minute to give me the context menu...finally got task manger up and for sure, back to 99% CPU with Symantec and Service Host taking most of it.
This is terrible It has to be some kind of VM setting wrong. But it wasn't this bad yesterday.
I am about to bring up resource monitor but it is taking forever as well...
@scottalanmiller said:
@garak0410 said:
@PSX_Defector said:
You should be giving less vCPUs, not more.
So perhaps try one tonight?
@garak0410 said:
@PSX_Defector said:
You should be giving less vCPUs, not more.
So perhaps try one tonight?
very unlikely to be the culprit but doesn't hurt to try.
Got to try something...because I am taking 1/2 day off tomorrow...LOL. Will try tonight...
Should I give it 4 CPU's? Is that not excessive for just a file server, albeit heavily used one?
@Bill-Kindle said:
Are you doing full scans or targeted scans? Do you have any files/folders in the exclusion list?
Currently, Anti-Virus services are off. Going to check the settings again tonight when I turn it back on after hours...
