When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Computer & Technology RelatedPost here for help and discussion of computing and related technology. Internet, TVs, phones, consoles, computers, tablets and any other gadgets.
We have been depolying w2012r2 for ages and the network connection identifier has always been Ethernet. And this is an identifier set in my unattend.xml file so that I can get HP Server Automation to deploy VMs.
However I am now getting w2012r2 machines being deployed with the network connection identifier coming up as Ethernet0 which is screwing up my automated installs.
I have changed this in my xml file but it now fails the Specialize pass.
Whenever I add in this component, < component name="Microsoft-Windows-DNS-Client" I get the failure.
I have removed the component and everything works fine, but when I re-add it even with modifications I get the following error.
Anyone got any ideas why I am suddenly getting Ethernet0 instead of Ethernet?
Last edited by Wurzel; 29 February 2016 at 03:18 PM.
Can you post up your unattend file (sanitise it first).
Ensure the [Identifier/] element is the first entry after the [Interface] element for both TCPIP and DNS-Client. Replace the square brackets with less than greater than symbols - I'm sure you know what I mean.
Why don't you use Local Area Network to identify the NICs, allowing multiple NICs to be enumerated as 2, 3, 4 etc?
More to the point, why have you posted this here in Other Marques, when it should obviously be in Scoobynet General?
Funilly enough I did post it in computer related and once I submitted it half the message was missing and it was in the Scoobynet General.
Then I edited it to readd the missing part and another bit vanished.
The reason I did not use Local Area Network was when I first installed Win2012R2 this was set to "Ethernet" and the xml config fell over when I had "Local Area Network" I used the Windows Kit thing to get the components in the right order and this has passed verification.
I have this script running on another HP SA Server and it works fine so I have no idea why "Ethernet" has switched to "Ethernet0"
Great all the XML code has been stripped out, so that was a waste of time writing that wasn't it.
29 February 2016, 01:59 PM
Windows 2012 R2 network Connection Identifier
