If you’ve already read my previous post on checking the NIC bind order on all your servers, please read it again.

I have corrected the script after discovering the previous version was not finding all misconfigurations in our environment. Now it return a collection containing both the IP-addresses of the first and second NIC in the bind order instead of just the first one. This allows for better checking for misconfigurations. It also uses the Tcpip bind order instead of the lanmanworkstation bind order for more consistent results.

http://www.peetersonline.nl/index.php/powershell/check-nic-bind-order

 Any questions? Please leave a comment.

Related posts:

  1. Calculate vSphere 5 Licenses with Powershell (UPDATED)

 Leave a Reply

(required)

(required)

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="" highlight="">

   
© 2012 PeetersOnline Suffusion theme by Sayontan Sinha