Actually that's an idea....these are SCCM builds so we'd probably need to find a way of doing this programatically as part of the task sequence.
Probably be Monday before I can get any update on this, time differences and passed-through information will limit the turnaround of info, unfortunately. Sounds like a idea to start from though, cheers Despatched via Blackberry. Mock if you will, but it gets my email without a fuss. -----Original Message----- From: Charles F Sullivan <[email protected]> Sender: [email protected]: Fri, 17 Oct 2014 15:25:10 To: <[email protected]> Reply-To: [email protected] Subject: RE: [NTSysADM] Multiple NICs in tablets giving problems with management software Are the clients using a typical dynamic DNS, where the DNS record gets updated when the computer name or IP address change? It might be interesting to get the IP address of each NIC on one affected client, then do nslookup on each one to see if each has a DNS record. I’m kind of surprised that the machines seem to be favoring the Wireless Ethernet and updating DNS records based on that IP address (if in fact they are using dynamic DNS). If it does turn out that they are in fact choosing to update DNS using the Wireless address even when plugged in, you could go to Network Connections > (Show the Menu bar if it’s not there) Advanced menu > Adapters and Bindings tab > Check the order of NICs and put the Wired on top of the Wireless if it isn’t already set that way. This can probably be done programmatically if it needs to be done on a bunch of devices. Or, you may want to disable dynamic DNS on the Wireless NIC on each device. *From:* [email protected] [mailto: [email protected]] *On Behalf Of *James Rankin *Sent:* Friday, October 17, 2014 1:22 PM *To:* [email protected] *Subject:* [NTSysADM] Multiple NICs in tablets giving problems with management software Got some Win 8.1 tablets with several network interaces (wired, wireless, bluetooth, etc.) When I come to deploy management agents, the IP address which is resolving to the hostname is one that is bound to the wireless NIC, not the wired one. Therefore I can't deploy agents until I disable the wireless NIC, flush the DNS cache, and reconnect. Is there a best practice around configuring multiple NIC devices in this way so they are accessible via the LAN (for remote access, management, AV)? Normally the places I go to are on top of this sort of thing already, but this particular client seems to not have a clue, so I'm reaching out for some advice to pass on to them (this being an area out of my specialist zone) Shout for more info - this request is coming to me second-hand, and I'm on a train trying to play Football Manager :-) Cheers, -- *James Rankin* --------------------- RCL - Senior Technical Consultant (ACA, CCA, MCTS) | The Virtualization Practice Analyst - Desktop Virtualization http://appsensebigot.blogspot.co.uk
