@Mike-Davis said in switch and NIC teaming in Hyper-v:

Good points. Now that I think about it, in this case it's pointless since they have a 1GB uplink to the main switch. Since all ports go in to one switch and there is only one 1GB uplink nothing is gained in terms or redundancy or bandwidth.

You always gain redundancy you can have 3 links fail.

@wirestyle22 updates were applied only in the VM's not the host.. everything is ok, just for a vm an error about integration services

@Dashrender said in Windows Server 2012 R2 Licensing:

@JaredBusch said in Windows Server 2012 R2 Licensing:

@Dashrender said in Windows Server 2012 R2 Licensing:

@JaredBusch said in Windows Server 2012 R2 Licensing:

Server 2016 have a install method called Core.

Actually it doesn't. The install options are

standard standard with desktop experience datacenter datacenter with desktop experience

The ones without desktop experience are what used to be called Core installs. I think MS does have the term Core still sprinkled around inside the OS and documentation though.. just adding more to the confusion.

They changed again? I have not installed 2016 yet.

Yep. And this time I actually agree. The whole idea, I think, being that MS is moving toward a non GUI on the servers being the standard way of installing/using Windows Server going forward.

They made that very public as their goal when PowerShell was released long ago.

The thing that points to there not being anything to worry about, while lacking the "unlimited" is a bit odd, is that those with limits say that there are limits. It doesn't say unlimited, but it does give a limit, either.

0_1485979989423_upload-eac96def-3233-451e-94e1-38891c8ca962

@Dashrender said in XS 7 or HyperV 2016:

@FATeknollogee said in XS 7 or HyperV 2016:

@Dashrender said in XS 7 or HyperV 2016:

Wouldn't that mean exposing your XS to the internet? I suppose not if you lock the inbound ports to the IP of the XO, where ever it's hosted. So from a management point of view, that's great, but I don't think most would end up using the backup portion in that situation, soooo...

How is this different from using (as an example) the built-in replication tool in Hyper-V? Either way you still need the 'net?

I've never tested this, so I am working from an assumption. But upon the assumption here is my explanation.

You have a XS host in your office in Dallas, 100 Mb internet connection.

The MSP has a XO VM running in a hosted DC in Cali that's used to manage the XS host. How does the data flow to the backup target? Does it flow through the XO system then to the target? I know that Veeam works this way. Assuming it does flow through the XO box, the data would flow out the 100 Mb connection to the XO, and then to where ever the backup target is. Assuming that's at the customer site, that would also be on that single 100 Mb connection.

Again - I admit to an assumption here - if my assumption is wrong, please don't be an ass about it, just inform me, and the rest here.

So with that assumption, assuming you want your first backup target to be onsite, then you'd either need a separate backup solution, or another copy of XS locally that runs backups inside the network.

Actually, no, Veeam does not work that way.

By default, the paid version of Veeam installs proxy stuff on each host as well as the box that Veeam is installed on. When a backup job runs, it chooses the best place to run through each time unless you specify a specific option in the backup job.

Old thread but I just found this out after wasting a few hours last evening trying to get Hyper-V 2016 on my Dell 2950 lab server. Processors need to support SLAT
http://www.nodefinity.net/post/hyper-v-on-poweredge-2900-2950-the-end-of-the-road-is-windows-server-2012-r2

@JaredBusch said in Storage Provisioning For a Single Hyper-V Server Setup:

@scottalanmiller said in Storage Provisioning For a Single Hyper-V Server Setup:

@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:

I installed Hyper-V Core, and I'm facing a though time configuring... The server is at a remote location, and connect to the remote network via VPN, and am trying to use tools like Server Manager, Hyper-V manager, and even 5nine.. Server Manager itself works fine, but when I launch tools (such a Computer Management) from within Server Manager, I get random access denied messages .. Even after adding it as a Trusted host

Why are you doing things over a VPN? Stop doing that, that's likely your problem.

Even better, this sounds like a MSP office he is working from, so they probably have all these VPN connections to various clients open.

That's super scary, MSPs using VPNs is how malware is going to suddenly take over the world. Cross contamination all over the place.

@JaredBusch said in How to Install the Atera RMM Agent on Hyper-V Server 2012 R2:

DISM /online /enable-feature /featurename:NetFx3 /all

i do this all the time on Windows 10, except I include the /source:location of files since it's not on my WSUS system.

@thwr said in storvsp.sys - Hyper V question:

@scottalanmiller said in storvsp.sys - Hyper V question:

@thwr said in storvsp.sys - Hyper V question:

But, TBH, do we have such a List for GNU/Linux, BSD or MacOS?

MacOS, no. Proprietary and gone since the 1990s.
Mac OSX, no. Proprietary and not that documented.

my bad

Linux and BSD, yes, because open source is natively documented by definition.

For the most part, yes. Just a little example: https://www.kernel.org/doc/Documentation/w1/slaves/w1_therm

Could you tell from just looking at this file how exactly a virtual sysfs w1-therm temperature data file or even the virtual file structure looks like for a DS18XXX sensor? I had to try it the hard way, because there was no such documentation a year ago.

That's just one simple example. I know, I could (and probably should) improve that on my own...

Spoiler:

cat /sys/bus/w1/devices/28*/w1_slave 62 01 ff ff 7f ff ff ff 91 : crc=91 YES 62 01 ff ff 7f ff ff ff 91 t=22125

@dafyre said in Windows Server 2016 - Discrete GPU:

I never quite gleaned from the article whether it was you could only pass 1 VM per GPU, or if you could do GPU sharing and let multiple VMs use the same GPU?

I haven't read the entire thing, so I may be mistaken. They were talking about two different modes of GPU pass through. One mode where you have 1GPU to 1VM, and another one where you can share 1GPU with many VM.

Bridging issue solved, kind of a Late-Friday-Problem: Promiscuous mode was turned on, but on the wrong interface - the DMZ facing one.

It worked instantly the second I switched it off on the DMZ and instead turned it on on the target network interface.

How to turn on MAC spoofing / Promiscuous mode on Hyper-V using PowerShell

Get-VM -Name XXXXX | Get-VMNetworkAdapter | Where-Object { $_.MacAddress -eq "XXXXXXXX" } | Set-VMNetworkAdapter -MacAddressSpoofing On

@BBigford said in Hyper-V homework question:

@Kelly said in Hyper-V homework question:

I posted this on that other site, but it appears that you do the teaming inside of Hyper-V, and not in the host OS: http://www.serverwatch.com/server-tutorials/configuring-nic-teaming-for-virtual-machines-with-hyper-v-3.0.html.

As soon as the team is added, connectivity is lost. Can't even get as far as adding the adapter before connectivity is lost.

So... once you create the virtual switch in Hyper-V Manager Virtual Switch Manager, using the NIC Team you created on the Host OS, all connectivity is lost?

At that point, what do the event logs say? Is there some kind of weird MAC conflict? When you look at the connection status of the virtual switch in Control Panel -> Network Connections, what does it look like? Are you getting a 169 address? Is it all 0's? What's actually going on and what does Event Viewer say?

@KOOLER said in The SMB Two Server Dilema, What to Do:

@whizzard said in The SMB Two Server Dilema, What to Do:

In scenarios such as these what would be the recommended backup approach: DAS, NAS, Backup Appliance, lower end server, removable disk storage, tapes (intentionally left out cloud)?

Should be separate (physically!) entity non-related to your production cluster. Cheap NAS is OK.

For the average scenario (and I really just mean average) it's Synology or ReadyNAS that I recommend. Easy, supported, cost effective, desktop or rackmount options, well known, good brands, nice features.

And patch management and software updates are taken care of for you.

@r0dISK said in I did a thing, have a quick Linux question:

22TB ? mdadm + RAID6...

That's a lot to have under RAID 6, but for a home lab is fine.

The Linux system gets the use 99% of the time and needs priority as to performance and what not. The Windows install is just for gaming and is not even my main gaming machine. Just a secondary one. And I've lived with zero Windows access for most of a year, not a big deal.

@coliver I know, I wasn't even included in the conversation at the time when we migrated to O365, and I wasn't included in the conversation when they setup Hyper-V.

Nor was I included when they built this VM, or the other reporting VM on Hyper-V to which 16GB of memory and 2 cores assigned to it...

#SweepItLikeAJanitor

@JaredBusch said in NIC teaming on Hyper-V:

Then you make you vSwitch. If you already have your vSwitch setup, make a team with the ports NOT on the vSwitch, move the vSwitch to the team and then add the final NIC to the team.

Not much to add here. SwitchIndependent mode is a big one on Hyper-V. Sure, Windows can easily use LACP and other means, but what if you want to use two or more uplink switches for redundancy? LACP can't handle this and there is just a handful of proprietary protocols that can. SwitchIndependent mode is doing exactly this by "load balancing" VMs and Host traffic between the available links and failover in case something goes south.

This way, like @JaredBusch said above, you can have LACP-like functionality (max single port speed for a single traffic source) over multiple inexpensive switches. In fact, the switch doesn't know anything about that type of teaming, you could even use unmanaged switches (but really, don't do that)

My hosts are running in this mode.

Question: have you tried setting up the DHCP server as the time master, and having the Centos system sync time to the DHCP server (with said DHCP server syncing to NIST or whatever time source you prefer) instead of the NTP Pool? That way theoretically DHCP server and Centos should be at the same time. Just a thought.