Server down this morning...
VHDX File is just gone... It's missing...
I found out that Windows Defender had detected it was (or had) a virus and quarantined it...
How Windows defender even would ever quarantine a VHDX is beyond me.
Come on Microsoft!
That's odd. VHD/VHDX files are NOT ever scanned by the host, unless of course they are mounted in the same way as a disk or USB disk is to the host OS for example. Otherwise, they are treated like a black box. So something else had to have happened for it to be quarantined by the host OS. That doesn't just happen willy-nilly.
Additionally, VM files are automatically excluded when the Hyper-V server role is installed. So again, something isn't configured correctly or something weird is going on.
What happened to you isn't default behavior.
Not sure, we 'inherited' the server. We don't do HYPER-V any longer. Everything is KVM now. (Proxmox)
But it was for sure quarantiined. Funny thing is that Windows defender scan of the actual VM shows no virus... So weird.
My guess would be that the VM's AV cleaned it up separate from the host's AV killing the VM.
Just curious, when you chose UPD, did you choose to store all settings or just certain folders?
Some applications don't play nicely with roaming profiles.
UPDs mount at the usual C:\Users\user.name and the applications can't tell a difference.
Right. But, only when the user is logged in. After they logout, that path doesn't exist. I am trying to figure out how to work around that for adding the custom (for each user) erp shortcut on their desktop in their session.
Add the shortcut to C:\Users\Public\Desktop.
That way it will always show up on each user Desktop.
This would be nice and easy, but each user has a custom shortcut- It has a workstation ID in the target path.
... And I don't have to run a Windows server for vCenter server or upgrade manager anymore.
I haven't played around with VMware much. How does it work with vCenter? Does run in a VM on each hypervisor or completely separate from the hypervisors?
It is a virtual appliance. You can upgrade and migrate from an existing Windows version. You can run it on a single server.
On Server, no issue. SSH the same as with Linux. SSH on Windows 10 is "single user" just like anything else on Windows 10.
So then why would they have the statement about "usually to correct problems" as to me this would be a two person use. One who is using the desktop and the other administrator who is working on fixing an issue via ssh (presumably while the other user is using said system).
I'm not bothering to reread anything, but MS has long allowed admin connections.
Yes this has been a known fact for as long as i can remember... Admins are exempt for administrative purposes.