Transcript • 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-AACC-EE-11-22"

• 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-AACC-EE-11-22"
get-netadapter
get-netadapter NIC2ISP | select *
get-netadapter | select * | ogv
• new-netLbfoTeam –name MyNicTeam
–teammembers Internal1,Internal2
–confirm:$false
22
Always choose this!
Invoke-IpamGpoProvisioning Domain bigfirm.com -GpoPrefixName PamGPOs
-IpamServerFqdn pamserver.bigfirm.com
-Force
33
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!
34
• set-dhcpserverv4failover scope1clus
–autostatetransition $true –StateSwitchInterval 02:00:00 –
maxclientleadtime 00:20:00
• set-dhcpserverv4failover scope1clus
–partnerdown –computer
Dhcp1.bigfirm.com
• Dunno why this stuff's not in the GUI, but
DHCP failover's pretty nice anyway
http://aka.ms/WS2012R2
http://aka.ms/SC2012R2
http://channel9.msdn.com/Events/TechEd
www.microsoft.com/learning
http://microsoft.com/technet
http://microsoft.com/msdn