Some Hyper-V VM remote management commands:
For that to work right the VM has to be shut down.

Here a list of Hyper-V Commands
https://technet.microsoft.com/en-us/library/hh848559(v=wps.630).aspx

– Shut down VM

– Set the amount of Cores assigned to the VM

– Set Amount of RAM assigned

– Start VM back up

 

Since we are still moving things, we had to update the home drive location.

1. Get a list with all users who have a Home Drive set.

2. I cleaned the list out and saved it as a .txt file

3. Then go through the list and update the Home Directory for each user in the list.

 

We were moving data with a tool called Syncedtool. It works pretty good, however the biggest downfall is, it does not copy NTFS permissions… UGG!

So here my Batch fix for it. Since PowerShell is a pain to be used to that…

 

A quick rundown how to NIC Team in Server Core:

1. We connect to the remote host and check what NICs are available to Team. We want to make a not of the adapter names.

2. We create a new team and specify a name. Then we add NIC01 and NIC02 to the team.

3. Once we do that, the it will ask if it is ok and it will add the default settings:
TeamingMode:’SwitchIndependent’ and LoadBalancingAlgorithm:’Dynamic’

TeamingMode

In this “Switch Independent Mode” the switches are not aware that different interfaces on the server comprise a team. Instead, all the teaming logic is done exclusively on the server.

There is also the option for “Switch Dependent Mode”, wherein all NICs that comprise the team are connected to the same switch for aggregation rather than redundancy.

LoadBalancingAlgorithm

— Dynamic:
Uses the source and destination TCP ports and the IP addresses to create a hash for outbound traffic. Moves outbound streams from team member to team member as needed to balance team member utilization. When you specify this algorithm with the TeamingMode parameter and the SwitchIndependent value, inbound traffic is routed to a particular team member.
— TransportPorts:
Uses the source and destination TCP ports and the IP addresses to create a hash, and then assigns the packets that have the matching hash value to one of the available interfaces. When you specify this algorithm with the TeamingMode parameter and the SwitchIndependent value all inbound traffic arrives on the primary team member.
— IPAddresses:
Uses the source and destination IP addresses to create a hash, and then assigns the packets that have the matching hash value to one of the available interfaces. When you specify this algorithm with the TeamingMode parameter and the SwitchIndependent value, all inbound traffic arrives on the primary team member.
— MacAddresses:
Uses the source and destination MAC addresses to create a hash and then assigns the packets that have the matching hash value to one of the available interfaces. When you specify this algorithm with the TeamingMode parameter and the SwitchIndependent value, all inbound traffic arrives on the primary team member.
— HyperVPort:
Distributes network traffic based on the source virtual machine Hyper-V switch port identifier. When you specify this algorithm with the TeamingMode parameter and the SwitchIndependent value, inbound traffic is routed to the same team member as the switch port’s outgoing traffic.

4. Once that is done you should have a team

We can check which NICs are the member, the status it is in, if it is up , or degraded
(mine was degraded since I only connected one NIC :oP)

Sources:
– https://technet.microsoft.com/en-us/library/jj130849(v=wps.630).aspx
http://www.windowsnetworking.com/articles-tutorials/windows-server-2012/windows-nic-teaming-using-powershell-part1.html