4. rename-netadapter –name ethernet –newname "hypervinternal1" new-netipaddress -interfacealias "ethernet" - ipv4address "10.1.1.1" -prefixlength 24 –defaultgateway 10.1.1.1 get-netadapter|where {$_.linkspeed -eq "10 gbps"} disable-netadapter ethernet1 set-netadapter ethernet –macaddress "00-FF-AA- CC-EE-11-22"

22. 22

31. Always choose this!

33. 33

34. 34 The keys to troubleshooting IPAM are -Use the PowerShell command to create the policies and keep track of the prefix you picked -Double-check that it LINKED the policies to the domain -Run gpupdate/force and run RSOPs to ensure that (1) the policies didn't hit a snag and, again, (2) the policies are actually linked and error-free (no Sysvol mismatches) -If it breaks, just delete the policies, remove the IPAM feature, and try again… the wizard's pretty helpful -Never give up. Never surrender. Once you're sure the policies are in place, re-run discovery, and you will triumph!

51. set-dhcpserverv4failover scope1clus –partnerdown –computer Dhcp1.bigfirm.com Dunno why this stuff's not in the GUI, but DHCP failover's pretty nice anyway

54. http://microsoft.com/msdn www.microsoft.com/learning http://channel9.msdn.com/Events/TechEd http://microsoft.com/technet