Now as a general recommendation (really never do this), don't install Windows Server onto the bare metal, install your hypervisor to the bare metal. In this case Hyper-V.

Apply your licensing to the 2 VM's that you are allowed to create with Standard (and up licensing) then you'll be allowed to move your VM's around every 90 days or sooner for hardware failures etc.

@tim_g said in question about Hyper-V resource management?:

@wirestyle22 said in question about Hyper-V resource management?:

@tim_g said in question about Hyper-V resource management?:

@wirestyle22 said in question about Hyper-V resource management?:

@tim_g said in question about Hyper-V resource management?:

@wirestyle22 said in question about Hyper-V resource management?:

@dave247 said in question about Hyper-V resource management?:

@dashrender said in question about Hyper-V resource management?:

@net-runner said in question about Hyper-V resource management?:
http://hv-manager.org/.

zEE4HQh.png

At least you get 5 VMs, but the 5Nines gives you 6..

I'll bring it back around and say that now that I've gotten past the couple of annoying obstacles with Hyper-V and remote management, Hyper-V is freaking awesome. It seems lightning fast.

The annoying thing for me is the versioning needed to manage hyper-v. Example: For Hyper-V 2016 you need a windows 10 machine to manage it.

No you don't.

You can pay for stuff to manage it, but I mean it doesn't automatically allow that

Windows 7+ with RSAT.

I just did that at my last job and it didn't allow it

I used Hyper-V 2016 with Win7 RSAT before I loaded Win10.

Hm. I should try it again I guess at home

@dustinb3403 said in Cross-Post Hyper-V and Backup recommendations:

My question is, should I also run backup agents (I use Veeam), on the Hyper-V environments and back them up as if they were physical boxes? Or is the daily backup fine.

General practice is to not back up the host itself. You should have a process to rebuild the host and, in theory, this should be incredibly fast and simple. Since restoring bare metal is always a pain because you have to get the restore going without an agent, rebuilding a nearly stateless host is generally faster and simpler and doesn't require storage and management.

@tim_g said in Hyper-V Network card setup?:

@dave247 said in Hyper-V Network card setup?:

Thanks. And this isn't for testing. I actually want to use this server for some production servers.

Sorry, didn't know. I mistakenly assumed testing and lab because of the time frame.

But you can't go wrong with doing it that way.

If you have no need for an extra NIC you could do a 3-NIC team. If you are fine with no management NIC, do a 4-port team and share it with your management OS if for some reason you need that many NICs in a team. Though you probably don't.

Yeah well it is for some low-risk servers, so, kinda almost testing, but not really, if that makes sense. lol

I don't believe a GUI played a role in my issue, but I won't completely dismiss the possibility either.

@JaredBusch said in KVM VM Replication:

@scottalanmiller said in KVM VM Replication:

Just using the search is best

Tags.

yeah, having tags on the topics makes them better than pinning.

Right, NIC Teaming is not a Hyper-V feature. There is almost no reason to do it that way.

Also, you don't want to use "Hyper-V" load balancing after Windows Server 2012. Starting with 2012 R2, Dynamic is the preferred algorithm. Only in super rare cases would you use any other algorithm.

IMHO, dispersing the storage between the hosts and configuring data replication between them would be the best option.

Creating several tiers for the migration of your VMs is always nice to have - downtime strikes unexpectedly.

good article thanks and handy script

@nerdydad said in Hyper-V Host - Member of the domain or not:

@jaredbusch said in Hyper-V Host - Member of the domain or not:

@tim_g said in Hyper-V Host - Member of the domain or not:

@jaredbusch said in Hyper-V Host - Member of the domain or not:

@jmoore said in Hyper-V Host - Member of the domain or not:

I enable the local admin and set a secure password for everything here as sometimes machines quit responding to the Windows domain controller and I have to have a way to reset things.

By stating that you enable local admin, I want to know how it was disabled in the first place.

I don't know what the issue is here.

When you install Hyper-V Server, you can't log in any way other than local admin. Maybe after you join it to the domain you can disable the local admin account, which is weird to do...

That is entirely my point.

This was supposed to be more of a "Best Practices" question. I really don't have a problem situation in front of me, but wanted to better understand best practices when setting up a Hyper-V host.

I have setup a number of Windows 10 client devices and noticed that the local admin is disabled. I assumed (though never experienced) that the situation would be the same for a Hyper-V host.

Local Administrator account in Windows Servers and Hyper-V is enabled by default. Windows desktops has the local administrator account disabled by default.

@scottalanmiller said in MS Licensing - 3rd:

Just search "Windows 7 vdi licensing" and the MS PDF is the first hit.

So that's where they hide it... in the EULA of a separate product or whatever you want to call it.

But yeah, it's pretty clear in there.

@matteo-nunziati said

this is the list of things provided by the full agent

I wish that chart broke it down by

MS LIS and agent

@tim_g said in Port - Storage Spaces Direct (S2D): SCSI Enclosure Services (SES) needed only on HBA?:

@dashrender

RAID would be provided by SS.

He would need a controller that is pass-through.

Technically S2D is designed to be used by DAS systems (or JBODs if you like to make Scott facepalm), and not internal server storage... even though it works just fine.

There's no problem to use RAID controller instead of a basic HBA as long as you a) patch the registry (see my link below) or use special "filter" driver to report "RAID" bus (sic!) as SATA or SAS, and b) disable write-back cache on BOTH controller and disk itself, so all writes become atomic.

Storage Spaces Direct: Enabling S2D work with unsupported device types (BusType = NVMe, RAID, Fibre Channel). Part 1: Registry hack

https://www.starwindsoftware.com/blog/resolving-enable-clusters2d-bus-type-support-issue-on-some-storage-controllers

P.S. It's a BAD idea to use anything like that in production because as long as Microsoft support will discover your S2D configuration isn't supported they will pull out and walk away with a grin face.

@luismc said in Port - How to go about setting up a client to be virtualized?:

@dashrender said in Port - How to go about setting up a client to be virtualized?:

As for Sharepoint - You don't get that much storage in Sharepoint in O365, so you'll likely be paying for more storage there. Sharepoint also has a number of files per site limit, just something else to watch out for.

For future reference to anyone wondering, I spoke to three different O365 reps today and they said the limit has been bumped to 1 million items so we'll be good for a while!

That's a bit more!

@jaredbusch said in How to Approach Installing Hyper-V SAMIT Video:

@scottalanmiller you really need to think about your still image on these.

Also. I broke down and clicked on this one.

The lead in music was significantly louder than the audio after the lead in. that is bad.

That's been since addressed. Actually both things have. The videos from today (not posted yet) are with a still camera and audio tweaking. My dad does the final edits, and he added the intro music. So hopefully those two things are taken care of in about two videos from now.

@dashrender said in Configuring Windows Server 2016 Core. Part1: Installation:

@jaredbusch said in Configuring Windows Server 2016 Core. Part1: Installation:

@wirestyle22 said in Configuring Windows Server 2016 Core. Part1: Installation:

@aidan_walsh afaik there is no reason to install it as a role. All it does is create unnecessary licensing dependencies.

The main reason some people do it is for auto activation of guest windows machines. That is no reason to ever do it IMO.

If every physical server is a Datacenter license then it is pretty transparent also.

But I still do not feel that Installing in this way makes sense.

Yep, KMS server to the rescue.

Correct. If you are big enough to have Datacenter licensing, spin up another VM and setup KMS.

Open a crontab for the apache user

crontab -u apache -e */15 * * * * php -f /var/www/html/nextcloud/cron.php

@emad-r said in Hyper-V 2016 Server free file server included ?:

@dustinb3403 said in Windows 2016 Server free file server ?:

Not legal. You can't legally use Windows Server for production purposes without it being licensed.

Also I dont see any licensing options for file server role, FYI.

It's not a role. To license the use of any non-hypervisor functionality the license is a full Windows Server license.

@nerdydad said in What Type of Hypervisor is Hyper-V? SAMIT Video:

Guess what version of Hyper-V I have.

0_1501287894163_tick box Hyper-v.PNG

The tick box version and not the right kind. Plus, I can't change this because this is the ERP system. I could just smack somebody.

You can change it by getting a PC set up with hyper V 2016 migrate to that then format the machine reinstall 2016 on the server hardware in migrate back.