Documentation, Hacking, Hardware, Microsoft, Server Technologies

How To: Intel 82579V Gigabit Network Connection – Windows Server 2008 R2

Clearly Intel doesn’t want us to install server OS onto desktop motherboards nowadays.

Look at your driver CD. Navigate to the PRO1000 folder; depending on whether you have 32bit or 64bit OS, you will then want either Win32 or Winx64 (not Win64 which is for Itanium).
The choice for the next folder will depend on your OS; NDIS5x is Server2003 or XP, NDIS61 is Server2008 or Vista, NDIS62 is Server2008R2 or 7, I presume NDIS63 is for Windows 8, Server 2012.

Copy the correct folder to your desktop.

In either case once you have chosen the correct folder you need to find the .inf starting e1c ; so for Server 2008 R2 64bit it will be called e1c62x64.inf. Ensure you are doing this on the copy that now exists on your desktop.

Open the file in notepad;

;******************************************************************************
; e1c62x64.INF (Intel 64-bit extension Platform Only,
; Windows 7 64-bit extension and Windows Server 2008 R2 64-bit extension)
;
; Intel(R) Gigabit Network connections
;******************************************************************************
;
[Version]
Signature = "$Windows NT$"
Class = Net
ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}
Provider = %Intel%
CatalogFile = e1c62x64.cat
DriverVer = 06/21/2012,11.16.96.0
[Manufacturer]
%Intel% = Intel, NTamd64.6.1, NTamd64.6.1.1, NTamd64.6.2
[ControlFlags]
ExcludeFromSelect = \ 
 PCI\VEN_8086&DEV_1502,\ 
 PCI\VEN_8086&DEV_1503
[Intel]
[Intel.NTamd64.6.1.1]
; DisplayName Section DeviceID
; ----------- ------- --------
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_80001025
%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&SUBSYS_04911025
[Intel.NTamd64.6.1]
; DisplayName Section DeviceID
; ----------- ------- --------
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_00011179
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_00021179
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_80001025
%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503
%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&SUBSYS_00011179
%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&SUBSYS_00021179
%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&SUBSYS_80001025
%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&SUBSYS_04911025

Open the file in notepad;

If you look in [ControlFlags], you see that there are two device IDs listed. DEV_1502 and DEV_1503.
If you go back to the new computer you built (with no NIC driver installed 🙂 ), in Device Manager, you should see “Ethernet Adapter” listed as an unknown device. Go into the Properties of that, then Details, Hardware Ids. Now, you see that the device should be DEV_1503. Great.

Go back to the notepad file you have open, you can see that under the second section within [Intel] you don’t have anything listed for DEV_1503 under [Intel.NTamd64.61]. Ironically, every other section has Server 2008 R2 provided for. Sneaky Intel, sneaky.

Anyway, copy and paste the two lines that provide for DEV_1503 in the [Intel.NTamd64.6.1.1] section to the new section, like above. Save the file.

Go back to the other computer that still has device manager open (it might be the same computer..), click Driver -> Update Driver, then manually select the desktop location of your NDIS62 directory you copied and then edited.

Driver should install successfully. Hit me up if your mileage varies.

Advertisements
Microsoft, Server Technologies

ADMT computer migration to new domain.

When using ADMT 3.1 (Active Directory Migration Tool) to migrate a computer from a domain to a new domain you may experience the error – “The security database on the server does not have a computer account for this workstation trust relationship.”

My environment is 2003 forest -> 2008 forest and 2008 child domain at 2003 native. I think this is irrelevent in this instance though.

However, it’s pretty important that if you ARE migrating between domains that you update (or set manually on the computer’s nic) DHCP server so that the DNS points at the new DNS server. If you have trusts and DNS configured properly this shouldn’t matter too much, but it certainly is best practice.

Also, probably more importantly. If you have any group policy configuration that sets the primary DNS suffix to OLDDOMAIN then this will stay in effect after the migration and probably cause the breakage discussed here.

Anyway, onto the fix.

If you fire up ADSIEdit.msc on the target domain after migration, check out properties of the computer object that you migrated and look for the variable – servicePrincipalName

You need to make sure that there are values in there of:
HOST/THECOMPUTERNAME
HOST/THECOMPUTERNAME.NEWDOMAIN
TERMSRV/THECOMPUTERNAME
TERMSRV/THECOMPUTERNAME.NEWDOMAIN

.. chances are only the TERMSRV records will exist.

This solved the trust issues here.