NIC Intel(R) Ethernet Connection I217-LM Deployment Driver

Intel(R) Ethernet Connection I217-LM Deployment problems

HP Zbook, Probook 650G1 (See below for full range info)

 

OS Deployment problems with Intel NIC i217-V (I217V) under Windows 7 64BIT and different Deployment Software Like Frontrange-Enteo, SCCM, Symantec and also with Windows Deployment.

Main problem is that the Windows PE 3.X that most Deployment solutions use accepts a less DEVICEID (A shorter). Also the NIC somehow seems to have timing problems and just behaves different than others during unattended setup.

 

Your Windows PE will work with any driver DeviceID:

PCI\VEN_8086&DEV_153B

But the Windows 7 Setup that your Deployment does need is more specific driver and checks behind that base DeviceID:

PCI\VEN_8086&DEV_153B&SUBSYS_00008086 (Sample)




06.09.2013, 12.8.33.9427 < GEHT NICHT
06.06.2014, 12.11.77.2 < GEHT NICHT
31.07.2014, 12.12.50.7205 (
REV: A PASS: 4
) < GEHT von HP Carepaq, sp68420

Check! VERSION: 12.12.50.7205 REV: A PASS: 4

ftp://ftp.hp.com/pub/softpaq/sp68001-68500/sp68420.html

 

Screenshot shows Driver 12.8.33 from original HP factory setup W7 64BIT which DOES not work for Deployment.


The HP Factory NIC Setup shows following Device-ID (W7 64BIT) which does not work for deployment

NIC

PCI\VEN_8086&DEV_153B&REV_04

PCI\VEN_8086&DEV_153B

PCI\VEN_8086&CC_020000

PCI\VEN_8086&CC_0200

PCI\VEN_8086

PCI\CC_020000

PCI\CC_0200

 

Errors your will see in c:\windows\panther with wrong driver (No NIC in OS phase / Not Windows PE)

Setuperr.log

»¿2015-04-15 09:57:35, Error [DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [1355]

2015-04-15 09:57:35, Error [DJOIN.EXE] Unattended Join: DsGetDcName test failed: 0x54b, last error is 0x0, breaking if debugger attached...

2015-04-15 09:57:35, Error [DJOIN.EXE] Unattended Join: Unable to join; gdwError = 0x54b

 

DSJOIN error in Logfiles (C:\Windows\Panther\UnattendGC\UnattendedJoinDCLocator.etl)

2015-04-15 09:50:34, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...

2015-04-15 09:50:39, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...

2015-04-15 09:50:44, Warning [DJOIN.EXE

 

 

Working Driver, 07/31/2014,12.12.50.7205

 

You need the INF file with the three DeviceID:

%E153BNC.DeviceDesc% = E153B.6.1.1, PCI\VEN_8086&DEV_153B

%E153BNC.DeviceDesc% = E153B.6.1.1, PCI\VEN_8086&DEV_153B&SUBSYS_00008086

%E153BNC.DeviceDesc% = E153B.6.1.1, PCI\VEN_8086&DEV_153B&SUBSYS_00011179

 

Extract File: e1d62x64.inf (Working Driver which should work for the PHASE after Windows PE Format/Copies the Disk with your deployment. {Unattended phase}) (NOT Windows PE)

[Version]

Signature = "$Windows NT$"

Class = Net

ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}

Provider = %Intel%

CatalogFile = e1d62x64.cat

DriverVer = 07/31/2014,12.12.50.7205

 

 

[Manufacturer]

%Intel% = Intel, NTamd64.6.1, NTamd64.6.1.1, NTamd64.6.2

 

[ControlFlags]

ExcludeFromSelect = \

PCI\VEN_8086&DEV_153A,\

PCI\VEN_8086&DEV_153B

 

[Intel]

 

[Intel.NTamd64.6.1.1]

; DisplayName Section DeviceID

; ----------- ------- --------

%E153ANC.DeviceDesc% = E153A.6.1.1, PCI\VEN_8086&DEV_153A

%E153ANC.DeviceDesc% = E153A.6.1.1, PCI\VEN_8086&DEV_153A&SUBSYS_00008086

%E153ANC.DeviceDesc% = E153A.6.1.1, PCI\VEN_8086&DEV_153A&SUBSYS_00011179

%E153BNC.DeviceDesc% = E153B.6.1.1, PCI\VEN_8086&DEV_153B

%E153BNC.DeviceDesc% = E153B.6.1.1, PCI\VEN_8086&DEV_153B&SUBSYS_00008086

%E153BNC.DeviceDesc% = E153B.6.1.1, PCI\VEN_8086&DEV_153B&SUBSYS_00011179

%E155ANC.DeviceDesc% = E155A.6.1.1, PCI\VEN_8086&DEV_155A

%E155ANC.DeviceDesc% = E155A.6.1.1, PCI\VEN_8086&DEV_155A&SUBSYS_00008086

%E155ANC.DeviceDesc% = E155A.6.1.1, PCI\VEN_8086&DEV_155A&SUBSYS_00011179

%E1559NC.DeviceDesc% = E1559.6.1.1, PCI\VEN_8086&DEV_1559

%E1559NC.DeviceDesc% = E1559.6.1.1, PCI\VEN_8086&DEV_1559&SUBSYS_00008086

%E1559NC.DeviceDesc% = E1559.6.1.1, PCI\VEN_8086&DEV_1559&SUBSYS_00011179

%E15A0NC.DeviceDesc% = E15A0.6.1.1, PCI\VEN_8086&DEV_15A0

%E15A0NC.DeviceDesc% = E15A0.6.1.1, PCI\VEN_8086&DEV_15A0&SUBSYS_00008086

%E15A1NC.DeviceDesc% = E15A1.6.1.1, PCI\VEN_8086&DEV_15A1

%E15A1NC.DeviceDesc% = E15A1.6.1.1, PCI\VEN_8086&DEV_15A1&SUBSYS_00008086

%E15A2NC.DeviceDesc% = E15A2.6.1.1, PCI\VEN_8086&DEV_15A2

 

Device ID from working I217V for Deployment Driver, 12.12.50.7205, 2014, HP Softpaq68420

PCI\VEN_8086&DEV_153A;PCI\VEN_8086&DEV_153A&SUBSYS _00008086;PCI\VEN_8086&DEV_153A&SUBSYS_00011179;PC I\VEN_8086&DEV_153A&SUBSYS_1909103C;PCI\VEN_8086&D EV_153A&SUBSYS_190A103C;PCI\VEN_8086&DEV_153A&SUBS YS_2253103C;PCI\VEN_8086&DEV_153A&SUBSYS_2255103C; PCI\VEN_8086&DEV_153B;PCI\VEN_8086&DEV_153B&SUBSYS _00008086;PCI\VEN_8086&DEV_153B&SUBSYS_00011179;PC I\VEN_8086&DEV_1559;PCI\VEN_8086&DEV_1559&SUBSYS_0 0008086;PCI\VEN_8086&DEV_1559&SUBSYS_00011179;PCI\ VEN_8086&DEV_155A;PCI\VEN_8086&DEV_155A&SUBSYS_000 08086;PCI\VEN_8086&DEV_155A&SUBSYS_00011179;PCI\VE N_8086&DEV_155A&SUBSYS_198F103C;PCI\VEN_8086&DEV_1 55A&SUBSYS_1991103C;PCI\VEN_8086&DEV_155A&SUBSYS_1 993103C;PCI\VEN_8086&DEV_155A&SUBSYS_2101103C;PCI\ VEN_8086&DEV_155A&SUBSYS_213E103C;PCI\VEN_8086&DEV _15A0;PCI\VEN_8086&DEV_15A0&SUBSYS_00008086;PCI\VE N_8086&DEV_15A1;PCI\VEN_8086&DEV_15A1&SUBSYS_00008 086;PCI\VEN_8086&DEV_15A2;PCI\VEN_8086&DEV_15A2&SU BSYS_00008086;PCI\VEN_8086&DEV_15A2&SUBSYS_0001117 9;PCI\VEN_8086&DEV_15A2&SUBSYS_2216103C;PCI\VEN_80 86&DEV_15A2&SUBSYS_221B103C;PCI\VEN_8086&DEV_15A2& SUBSYS_225A103C;PCI\VEN_8086&DEV_15A2&SUBSYS_22701 03C;PCI\VEN_8086&DEV_15A2&SUBSYS_2271103C;PCI\VEN_ 8086&DEV_15A2&SUBSYS_22DA103C;PCI\VEN_8086&DEV_15A 2&SUBSYS_22FB103C;PCI\VEN_8086&DEV_15A3;PCI\VEN_80 86&DEV_15A3&SUBSYS_00008086;PCI\VEN_8086&DEV_15A3& SUBSYS_00011179

 

 

INF file HP CVA / Softpaq 68420 Infos

TITLE: Intel I217LM/V and I218LM Gigabit Ethernet Driver

VERSION: 12.12.50.7205 REV: A PASS: 4
DESCRIPTION:
This package contains the driver installation package for the Intel I217LM/V and
I218LM This build has post-beta drivers that are Intel-Signed Gigabit Ethernet
Controller in the supported notebook models and operating systems.

PURPOSE: Routine
SOFTPAQ FILE NAME: SP68420.exe
SOFTPAQ MD5: a369c6b348bb54a453afae2435f988a3
SUPERSEDES: SP67164
EFFECTIVE DATE: August 26, 2014
CATEGORY: Driver-Network
SSM SUPPORTED: Yes

PRODUCT TYPE(S):
Notebooks

HARDWARE PRODUCT MODEL(S):
HP ZBook 17 G2 Mobile Workstation
HP ZBook 17 Mobile Workstation
HP EliteBook Folio 9480m Notebook PC
HP EliteBook Folio 1040 G1 Notebook PC
HP EliteBook 840 G1 Notebook PC
HP ZBook 14 Mobile Workstation
HP EliteBook 740 G1 Notebook PC
HP EliteBook 850 G1 Notebook PC
HP EliteBook 750 G1 Notebook PC
HP ZBook 15 G2 Mobile Workstation
HP ProBook 640 G1 Notebook PC
HP ProBook 650 G1 Notebook PC
HP ZBook 15 Mobile Workstation

 

Links:

http://www.symantec.com/connect/forums/ghost-loop

https://downloadcenter.intel.com/search?keyword=Intel%28R%29+Ethernet+Connection+I217-V

http://serverfault.com/questions/649507/mdt-deployment-issue-driver-not-loading-i217-lm-on-mdt

https://communities.intel.com/thread/43218

http://forum.enteo.com/showthread.php?t=15396&page=2

ftp://ftp.hp.com/pub/softpaq/sp68001-68500/sp68420.html

 

 

 


 

IE11 IEAK 11 Setup 9 PRE Deployment Patches + 1 Hotfix

Internet Explorer 11 Setup with IEAK11 for Deployment

We have seen several posting on Social MSDN but also deployment blogs with people struggling with the IEAK Setup of IE11 or better the 9 PRE patches the IE setup 10/11 needs.

Technet http://support.microsoft.com/kb/2847882 describes the Updates that have to be installed before you can Install IE11 silent.

Error Source 1, Setup tries to fetch updates in the back and fails because of Proxy

If these are not on the machine the Setup will try to fetch them from internet. Because the "Computer account" (Not the user) mostly has no PROXY information this will fail. I will not show you how you change that here; Target would be to have all files ready from deployment.

Error Source 2, Reboot OR WMI Update for Patches after installing PRE Patches

If you install the 9 patches with a batch or script you should:

a) Reboot the client which makes it a Reboot and advance package which some deployment can't handle

b) Solution > Rebuild the Patch Inventory by "c:\windows\system32\wbem\wmic.exe qfe" (Does not work on 19.03.2015)

 

The IEAK 11 Version from March 2015 does actualy check the Version of the files AS they are in place. So no Patches are checked to decide if add. Updates are downloaded. Thus the Reboot may be needed IF in use FIles are present.

> THUS only working solution would be on march 2015 to do a 3 STEP package

1) Install PRE Deployment Patches (Reboot)

2) Install IEAK (Reboot)

3) Install Post Deployment Patches (may need Reboot)

 

00:01.841: INFO:    Version Check for (KB2834140) of C:\Windows\System32\d3d11.dll: 6.1.7601.17514 >= 6.2.9200.16570 (False)
00:01.841: WARNING: Checking version for C:\Windows\System32\api-ms-win-downlevel-user32-l1-1-0.dll.  The file does not exist.
00:01.841: INFO:    Version Check for (KB2639308) of C:\Windows\System32\Ntoskrnl.exe: 6.1.7601.17803 >= 6.1.7601.17727 (True)
00:01.841: INFO:    Version Check for (KB2533623) of C:\Windows\System32\api-ms-win-security-base-l1-1-0.dll: 6.1.7600.16385 >= 6.1.7601.17617 (False)
00:01.841: INFO:    Version Check for (KB2731771) of C:\Windows\System32\conhost.exe: 6.1.7601.17514 >= 6.1.7601.17888 (False)
00:01.841: INFO:    Checking for correct version of C:\Windows\Fonts\segoeui.ttf.
00:01.856: INFO:    Version Check for (KB2786081) of C:\Windows\System32\taskhost.exe: 6.1.7601.17514 >= 6.1.7601.18010 (False)
00:01.856: INFO:    Version Check for (KB2888049) of C:\Windows\System32\drivers\tcpip.sys: 6.1.7601.17514 >= 6.1.7601.18254 (False)
00:01.856: INFO:    Version Check for (KB2882822) of C:\Windows\System32\tdh.dll: 6.1.7600.16385 >= 6.1.7601.18247 (False)
00:02.621: INFO:    Download for KB2834140 initiated. Downloading http://go.microsoft.com/fwlink/?LinkID=303935 -> KB2834140_amd64.MSU.
00:02.636: INFO:    Download for KB2533623 initiated. Downloading http://go.microsoft.com/fwlink/?LinkID=254722 -> KB2533623_amd64.MSU.
00:02.636: INFO:    Download for KB2731771 initiated. Downloading http://go.microsoft.com/fwlink/?LinkID=258387 -> KB2731771_amd64.CAB.
00:02.636: INFO:    Download for KB2786081 initiated. Downloading http://go.microsoft.com/fwlink/?LinkID=273751 -> KB2786081_amd64.CAB.
00:02.652: INFO:    Download for KB2888049 initiated. Downloading http://go.microsoft.com/fwlink/?LinkID=324542 -> KB2888049_amd64.MSU.
00:02.668: INFO:    Download for KB2882822 initiated. Downloading http://go.microsoft.com/fwlink/?LinkID=324541 -> KB2882822_amd64.MSU.

 

Error Source 3

KB2670838, Blurry Fonts Patch

KB2898202, Hotfix for Blurry Fonts Patch

 

If you take a closer look at the patches in KB2847882 you will see that thy want to install the "blurry Fonts patch / KB2670838" which caused a lot of trouble a few months ago. On most WSUS this is denied. However the IE11 needs that Patch. Even worse if you UNINSTALL the Blurry Fonts patch IE will get uninstalled fully.

Solution is to install KB2670838 and then KB2898202 the HOTFIX.

 

Thanks to Karen HU from Pactera/china for pointing us in that direction.

https://social.technet.microsoft.com/Forums/de-DE/0bb37a16-f8a3-4648-897e-6a1a5986a437/not-wanted-fonts-patch-kb2670838-and-ieak11-silent-last-status?forum=ieitprocurrentver

 

Here is how a Failed Logfile will look for the IE11 Setup c:\windows\IE11_main.log

01:52.679: ERROR:   WMI query for Hotfixes timed out. Query string: 'Select HotFixID from Win32_QuickFixEngineering WHERE HotFixID="KB2729094"'  Error: 0x00040004 (262148).
01:52.711: INFO:    Download for KB2729094 initiated. Downloading http://go.microsoft.com/fwlink/?LinkID=258385 -> KB2729094_amd64.MSU.
01:52.726: INFO:    Waiting for 1 prerequisite downloads.
02:23.880: INFO:    Prerequisite download processes have completed. Starting Installation of 1 prerequisites.
02:23.880: ERROR:   Error downloading prerequisite file (KB2729094): 0x800b0109 (2148204809)
02:24.098: INFO:    PauseOrResumeAUThread: Successfully resumed Automatic Updates.
02:24.114: INFO:    Setup exit code: 0x00009C47 (40007) - Required updates failed to download.

 

 

Here is a list of Binaries:

  

KB

Bei IE11 normal downlad link zu

Binary vorhanden

 

1

KB2834140

JA ZWINGEND

Windows6.1-KB2834140-v2-x64.msu

 

2

KB2670838

JA mit Hinwis bei UNINSTALL IE11 auch weg

Windows6.1-KB2670838-x64.msu

http://support.microsoft.com/kb/2670838/en-us

LOESUNG zweiter HOTFIX: http://support.microsoft.com/kb/2898202

Ach beachten: https://support.microsoft.com/de-de/kb/2834140 und ev. nach dem 838 installieren (Bluescreen bei INTEL VGA)

HOT

KB2898202

JA HOTFIX zu Blurry Fonts Patch

Windows6.1-KB2898202-x64.msu

http://support.microsoft.com/kb/2898202

3

KB2639308

JA ABER OPTIONAL

Windows6.1-KB2639308-x64.msu

http://www.microsoft.com/de-de/download/confirmation.aspx?id=28902

4

KB2533623

JA ZWINGEND

Windows6.1-KB2533623-x64.msu

  

5

KB2731771

JA ZWINGEND

Windows6.1-KB2731771-x64.msu

  

6

KB2729094

JA ZWINGEND

Windows6.1-KB2729094-v2-x64.msu

  

7

KB2786081

JA ZWINGEND

Windows6.1-KB2786081-x64.msu

  

8

KB2888049

JA ABER OPTIONAL

Windows6.1-KB2888049-x64.msu

http://www.microsoft.com/de-de/download/confirmation.aspx?id=40611

9

KB2882822

JA ABER OPTIONAL

Windows6.1-KB2882822-x64.msu

http://www.microsoft.com/de-de/download/details.aspx?id=40500

 

Uninstall described with IE10 but also valid for IE11

 

 

----------

 

WMI Hotfixes to date 29.07.2015

 

During IE11 projects we have seen problems with some WMI and WUSA.EXE KB installations. It sometimes seems that the WMI provider

 

who offers that info hangs or is out of date. Even with some command to refresh it0s stuck. This is a list of Hotfixes we found in that direction

 

For Existing Windows 7 64BIT Deployments with SP1.

 

 

 

YES = Installs on W7 SP1 64BIT with all Updates from WSUS do date 29.07.2015

 

NO  = Does not install on same system

 

 

 

001 (YES)

 

https://support.microsoft.com/en-us/kb/2705357

 

2705357

 

Windows6.1-KB2705357-v2-x64.msu

 

 

 

002 (YES)

 

http://support.microsoft.com/kb/2692929

 

2692929

 

Windows6.1-KB2692929-x64.msu

 

 

 

003 (YES but choose 2617858)

 

Unexpectedly slow startup or logon process in Windows Server 2008 R2 or in Windows 7

 

http://support.microsoft.com/kb/2465990

 

2465990 > SUPERSEEDED > Replaced by > 2617858 (https://support.microsoft.com/en-us/kb/2617858)

 

2465990 > Windows6.1-KB2465990-v3-x64.msu (Older)

 

2617858 > Windows6.1-KB2617858-x64.msu (Newer, Superseeds the old one)

 

 

 

004 (YES)

 

https://support.microsoft.com/en-us/kb/2492536

 

2492536

 

Windows6.1-KB2492536-x64.msu

 

 

 

005 (NO)

 

https://support.microsoft.com/en-us/kb/982293

 

982293

 

Windows6.1-KB982293-x64.msu

Check this LINK:

http://www.butsch.ch/post/IE11-IEAK-11-Setup-9-PRE-Deployment-Patches-2b-1-Hotfix.aspx

 

Windows 7 Unattended Files for Diagnostic \Panther

If you Deploy Windows 7 you may consult the folder Path: BOOT:\windows\panther for any problems. (Use SHIFT F10 to get Console). This may help finding errors or helping with the integration of NIC and mass storage drivers which may need to get integrated to support newer model of hardware.

When the Windows PE phase of Windows Setup is running, you can break into a command prompt window running under Local System context by pressing SHIFT+F10.

C:\windows\panther\UnattendGC\Setupact.txt

Here you can diag the DOMAIN JOIN and with which account or which OU this was planned .

2013-05-14 10:46:30, Info[DJOIN.EXE] Unattended Join: Begin

2013-05-14 10:46:30, Info[DJOIN.EXE] Unattended Join: Loading input parameters...

2013-05-14 10:46:30, Info[DJOIN.EXE] Unattended Join: AccountData = [NULL]

2013-05-14 10:46:30, Info[DJOIN.EXE] Unattended Join: UnsecureJoin = [NULL]

2013-05-14 10:46:30, Info[DJOIN.EXE] Unattended Join: MachinePassword = [secret not logged]

2013-05-14 10:46:30, Info[DJOIN.EXE] Unattended Join: JoinDomain = [CUST]

2013-05-14 10:46:30, Info[DJOIN.EXE] Unattended Join: JoinWorkgroup = [NULL]

2013-05-14 10:46:30, Info[DJOIN.EXE] Unattended Join: Domain = [CUST]

2013-05-14 10:46:30, Info[DJOIN.EXE] Unattended Join: Username = [delegate_admin]

2013-05-14 10:46:30, Info[DJOIN.EXE] Unattended Join: Password = [secret not logged]

2013-05-14 10:46:30, Info[DJOIN.EXE] Unattended Join: MachineObjectOU = [OU= l,OU=CUST,DC=CUST,DC=ch]

2013-05-14 10:46:30, Info[DJOIN.EXE] Unattended Join: DebugJoin = [NULL]

2013-05-14 10:46:30, Info[DJOIN.EXE] Unattended Join: DebugJoinOnlyOnThisError = [NULL]

2013-05-14 10:46:30, Info[DJOIN.EXE] Unattended Join: Checking that auto start services have started.

2013-05-14 10:46:30, Info[DJOIN.EXE] Unattended Join: Joining domain [CUST]...

2013-05-14 10:46:30, Info[DJOIN.EXE] Unattended Join: Calling DsGetDcName for CUST...

2013-05-14 10:46:31, Info[DJOIN.EXE] Unattended Join: DsGetDcName returned [CUSTDCW1]

2013-05-14 10:46:31, Info[DJOIN.EXE] Unattended Join: Constructed domain parameter [CUST\CUSTDCW1]

2013-05-14 10:46:32, Info[DJOIN.EXE] Unattended Join: NetJoinDomain succeeded!

2013-05-14 10:46:32, Info[DJOIN.EXE] Unattended Join: Exit, returning 0x1

 

C:\Windows\Panther\setupact.log

You can identify from where Windows 7 was installed and with what PE version.

2013-05-14 10:20:39, Info IBS InstallWindows:Successfully loaded resource language [de-DE]

2013-05-14 10:20:39, Info [0x0601c1] IBS InstallWindows:Install Path = W:\W7SP1ENT64.GER\sources

2013-05-14 10:20:39, Info [0x0601c2] IBS InstallWindows:Setup Phase = 2

2013-05-14 10:20:39, Info [0x0601e9] IBS CheckWinPEVersion:Compatible WinPE Version 6.1.7600 sp 0.0

2013-05-14 10:20:39, Info [0x0601c9] IBS InstallWindows:Starting a new install from WinPE

2013-05-14 10:20:39, Info IBS InstallWindows: Setup working directory = X:\windows\panther

2013-05-14 10:20:39, Info [0x0601ce] IBS Setup has started phase 2 at 2013-05-14 10:20:39

2013-05-14 10:20:39, Info [0x0601cf] IBS Install source is W:\W7SP1ENT64.GER\sources

2013-05-14 10:20:39, Info [0x0601d0] IBS Build version is 6.1.7601.17514 (win7sp1_rtm.101119-1850)

 

See if network is FROM within the Windows PE is running

 

2013-05-14 10:20:42, Info IBS STATUS: SUCCESS (0x00000001)

2013-05-14 10:20:42, Info IBS ==== Initializing Network Access and Applying Configuration ====

2013-05-14 10:20:42, Info IBS Found an smb connection.

2013-05-14 10:20:42, Info IBS Networking is currently in use and will not be restarted.

 

Check if the Windows PE gets a DHCP address (Maybe 802.X in place to protect unwanted network access)

 

2013-05-14 10:20:42, Info IBS QueryAdapterStatus: found operational adapter with DHCP address assigned.

2013-05-14 10:20:42, Info IBS Spent 0ms confirming network initialization; status 0x00000000

 

Find out where Windows PE searches for PNP drivers during setup

 

PnPIBS: Checking for pre-configured driver directory C:\$WinPEDriver$.

2013-05-14 10:20:43, Info PnPIBS: Checking for pre-configured driver directory E:\$WinPEDriver$.

2013-05-14 10:20:43, Info PnPIBS: Checking for pre-configured driver directory F:\$WinPEDriver$.

2013-05-14 10:20:43, Info PnPIBS: Checking for pre-configured driver directory G:\$WinPEDriver$.

2013-05-14 10:20:43, Info PnPIBS: Checking for pre-configured driver directory H:\$WinPEDriver$.

2013-05-14 10:20:43, Info PnPIBS: Checking for pre-configured driver directory I:\$WinPEDriver$.

2013-05-14 10:20:43, Info PnPIBS: Checking for pre-configured driver directory J:\$WinPEDriver$.

2013-05-14 10:20:43, Info PnPIBS: Checking for pre-configured driver directory W:\$WinPEDriver$.

2013-05-14 10:20:43, Info PnPIBS: Checking for pre-configured driver directory X:\$WinPEDriver$.

 

You can also retrieve and diag a lot of Driver related info from the same file.

\VEN_8086&DEV_0152&SUBSYS_339A103C&REV_09\3&11583659&0&10

2013-05-14 10:43:39, Info SYSPRP SPPNP: {Retrieving drivers used by device PCI\VEN_8086&DEV_1E3A&SUBSYS_339A103C&REV_04\3&11583659&0&B0}

2013-05-14 10:43:39, Info SYSPRP SPPNP: The device setup class for device PCI\VEN_8086&DEV_1E3A&SUBSYS_339A103C&REV_04\3&11583659&0&B0 is 4d36e97d-

 

Detailed Disk Info and Partition info and if hardware is compatible

 

2013-05-14 10:20:50, Info IBS DumpDeviceIDs: Compat ID [PCI\CC_010601]

2013-05-14 10:20:50, Info IBS DumpDeviceIDs: Compat ID [PCI\CC_0106]

2013-05-14 10:20:50, Info IBS IsDeviceIDPresent:Found device ID [PCI\CC_010601] in hwcompat list

2013-05-14 10:20:50, Info IBS IsDeviceSupported:Device [Serial ATA Controller] is supported

2013-05-14 10:20:50, Info IBS DumpDeviceIDs: H/w ID [ACPI\PNP0A08]

2013-05-14 10:20:50, Info IBS DumpDeviceIDs: H/w ID [*PNP0A08]

2013-05-14 10:20:50, Info IBS DumpDeviceIDs: Compat ID [*PNP0A03]

2013-05-14 10:20:50, Info IBS IsDeviceIDPresent:Found device ID [*PNP0A03] in hwcompat list

2013-05-14 10:20:50, Info IBS DumpDeviceIDs: H/w ID [IDE\DiskST500DM002-1BD142_______________________HP73____]

2013-05-14 10:20:50, Info IBS DumpDeviceIDs: H/w ID [IDE\ST500DM002-1BD142_______________________HP73____]

2013-05-14 10:20:50, Info IBS DumpDeviceIDs: H/w ID [IDE\DiskST500DM002-1BD142_______________________]

2013-05-14 10:20:50, Info IBS DumpDeviceIDs: H/w ID [ST500DM002-1BD142_______________________HP73____]

2013-05-14 10:20:50, Info IBS DumpDeviceIDs: H/w ID [GenDisk]

 

2013-05-14 10:20:50, Info [0x0606cc] IBS GetDisk: Querying VDS providers...

2013-05-14 10:20:50, Info [0x0606cc] IBS GetDisk: Finished querying VDS providers.

2013-05-14 10:20:50, Info [0x0606cc] IBS CreatePartition: Need to decide the type of the partition to create

2013-05-14 10:20:50, Info [0x0606cc] IBS ResolvePartitionTypeToCreate: <DiskConfiguration>: disk 0 already has 1 allocated partitions

2013-05-14 10:20:50, Info [0x0606cc] IBS GetDisk: Querying VDS providers...

2013-05-14 10:20:50, Info [0x0606cc] IBS GetDisk: Finished querying VDS providers.

2013-05-14 10:20:50, Info [0x0606cc] IBS FindFreeExtent: Trying to find extent matching these criteria (byte offset of 0 implies no offset preference): [WithinContainer = False] [Size >= 0x0 bytes] [Byte offset = 0x0]

2013-05-14 10:20:50, Info [0x0606cc] IBS FindFreeExtent: Found suitable extent: [WithinContainer = False], [Byte size of found extent = 0x745de06000], [Byte offset of found extent = 0x12d00000], [Return size of found extent = 0x745de06000], [Return offset of found extent = 0x12d00000].

2013-05-14 10:20:50, Info [0x0606cc] IBS CreatePartition: Requesting creation of partition with { offset = [0x12d00000], size [0x745de06000] }

2013-05-14 10:20:50, Info [0x0606cc] IBS CreatePartition: Successfully created partition on disk 0 at {offset = [315621376], size = [499791192064]}

 

C:\Windows\Panther\unattend.xml

 

This file reflects the parameters that the unattended setup has received to work with.

 

 

C:\windows\panther\DDACL.Sys

 

Is an interesting file for handling removable drives or even network drives in Logons cripts. You can easy see which drives are fixed and removable.

 

05/14 10:46:04    Info    

 

05/14 10:46:04    Info    Volume name is \\?\Volume{4ac6db0f-bc72-11e2-8074-806e6f6e6963}\

05/14 10:46:04    Info    Mount Point are :

05/14 10:46:04    Info    

05/14 10:46:04    Info    Volume is Fixed Drive

05/14 10:46:04    Info    Volume is ntfs

05/14 10:46:04    Info    Volume is system

05/14 10:46:04    Info    

 

05/14 10:46:04    Info    Volume name is \\?\Volume{4ac6db10-bc72-11e2-8074-806e6f6e6963}\

05/14 10:46:04    Info    Mount Point are :

05/14 10:46:04    Info    C:\    

05/14 10:46:04    Info    Volume is Fixed Drive

05/14 10:46:04    Info    Volume is ntfs

05/14 10:46:04    Info    Volume is not system

05/14 10:46:04    Info    Volume \\?\Volume{4ac6db10-bc72-11e2-8074-806e6f6e6963}\ has other OS 1

05/14 10:46:04    Info    

 

05/14 10:46:04    Info    Volume name is \\?\Volume{4ac6db24-bc72-11e2-8074-806e6f6e6963}\

05/14 10:46:04    Info    Mount Point are :

05/14 10:46:04    Info    E:\    

05/14 10:46:04    Info    Volume is Removable Drive

05/14 10:46:04    Info    

 

05/14 10:46:04    Info    Volume is Removable Drive

HP biosconfigutility.exe and password in BIOS options, error 10

HP this is absolue confusing! Not all syntax provided in the "Biosconfigutlity.exe" seem to work in a certain order!

Here is the correct syntax and a working example under Windows PE 3.X 32BIT boot media:

Biosconfigutlity.exe /cspwd:"youroldbiospassword" /cspws:"yournewbiospassword"

And an example to renew the existing BIOS password and write new BIOS Setting in one command:

BiosConfigUtility.exe /cspwd:"youroldbiospassword" /nspwd:"yournewbiospassword" /set:"%cd:~0,3%bios\6300\settings\6300.txt"

  • %cd:~0,3% = Current Drive letter your batch is on
  • bios\6300\settings\6300.txt (The config file with the new bios settings in some file Directory structure bios\modelltype\settings\modelltypeconfigfile.txt (Just an example)
  • Yes, you have to mention the "-chars (Quotation marks)
  •  "IF" you provider a existing password (cspwd), AND it does not match, it will be overseen and the NEW password written (cspws)
  • The exact syntax and ORDER of the options have to be followed

Make sure you don't mess UP with this tool. On certain newer laptops if you mess UP the BIOS password you "Can't" reset it with a jumper. There are two way (Send device to HP or buy a unlock key from russia for USD50). A cutomer from us has tried and did not understand the tool correct.

 If you don't want plain text passwords in your scripts you may have to use "HPQPswd.exe" which makes a password.BIN file from your entrys with the password encrypted.

 

Internet Explorer 10 (IE10) for Windows 7 (WIN7), download and block Auto install

 

  1. Download IE10 for Windows 7, http://windows.microsoft.com/en-us/internet-explorer/downloads/ie-10/worldwide-languages
  2. Block IE10 on all system which are NOT connected to Windows Update Server WSUS, http://www.microsoft.com/en-us/download/details.aspx?id=36512

     

Notes in German from the field:

  1. Kommt nicht automatisch WENN WSUS Anbindung vorhanden
  2. Kommt automatisch bei allen kleinen Kunden die KEIN WSUS haben da gestuft als "important Update"

 

Toolkit to Disable Automatic Delivery of Internet Explorer 10

http://www.microsoft.com/en-us/download/details.aspx?id=36512

 

  • For computers running Windows 7 or Windows Server 2008 R2, the Blocker Toolkit prevents the machine from receiving Internet Explorer 10 via Automatic Updates on the Windows Update and Microsoft Update sites.
  • The Blocker Toolkit will not prevent users from manually installing Internet Explorer 10 from the Microsoft Download Center, or from external media.
  • Organizations do not need to deploy the Blocker Toolkit in environments managed with an update management solution such as Windows Server Update Services or Systems Management Server 2003. Organizations can use those products to fully manage deployment of updates released through Windows Update and Microsoft Update, including Internet Explorer 10, within their environment.
  • Even if you used the Blocker Toolkit to block Internet Explorer 8 or Internet Explorer 9 from being installed as a high-priority or important update, you will still need to use the Internet Explorer 10 version of the Blocker Toolkit to block Internet Explorer 10 from being installed. There are different registry keys used to block or unblock automatic delivery of Internet Explorer 8, Internet Explorer 9 and Internet Explorer 10.

Files within the EXE

 

HKLM\SOFTWARE\Microsoft\Internet Explorer\Setup\10.0\

DoNotAllowIE10 =1

 

 

Toolkit to Disable Automatic Delivery of Internet Explorer 10

Overview

To help our customers become more secure and up-to-date, Microsoft will distribute Internet Explorer 10 as a high-priority update through Automatic Updates for Windows 7 Service Pack 1 (SP1) x86 and x64, and Windows Server 2008 R2 SP1 x64. This Blocker Toolkit is intended for organizations that would like to block automatic delivery of Internet Explorer 10 to machines in environments where Automatic Updates is enabled. The Blocker Toolkit will not expire.

  • For computers running Windows 7 or Windows Server 2008 R2, the Blocker Toolkit prevents the machine from receiving Internet Explorer 10 via Automatic Updates on the Windows Update and Microsoft Update sites.
  • The Blocker Toolkit will not prevent users from manually installing Internet Explorer 10 from the Microsoft Download Center, or from external media.
  • Organizations do not need to deploy the Blocker Toolkit in environments managed with an update management solution such as Windows Server Update Services or Systems Management Server 2003. Organizations can use those products to fully manage deployment of updates released through Windows Update and Microsoft Update, including Internet Explorer 10, within their environment.
  • If you used the Blocker Toolkit to block Internet Explorer 9 from being installed as a high-priority update, you need to use the Internet Explorer 10 version of the Blocker Toolkit to block Internet Explorer 10 from being installed. There are different registry keys used to block or unblock automatic delivery of Internet Explorer 9 and Internet Explorer 10.

Toolkit Components

This toolkit contains two components:

  • An executable blocker script
  • A Group Policy Administrative Template (.ADM file)

Supported Operating Systems

Windows 7 Service Pack 1 (SP1) x86 and x64 and Windows Server 2008 R2 SP1 x64 

Blocker Script

The script creates a registry key and sets the associated value to block or unblock (depending on the command-line option used) automatic delivery of Internet Explorer 10 on either the local machine or a remote target machine.

Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Setup\10.0

Key value name: DoNotAllowIE10

Value

Result

Key is not defined

Distribution is not blocked.

0

Distribution is not blocked.

1

Distribution is blocked.

The script has the following command-line syntax:

IE10_Blocker.cmd [<machine name>] [/B] [/U] [/H]

Machine Name

The <machine name> parameter is optional. If not specified, the action is performed on the local machine. Otherwise, the remote machine is accessed through the remote registry capabilities of the REG command. If the remote registry can't be accessed due to security permissions or the remote machine can't be found, an error message is returned from the REG command.

Switches

Switches used by the script are mutually exclusive and only the first valid switch from a given command is acted on. The script can be run multiple times on the same machine.

Switch

Description

/B

Blocks distribution

/U

Unblocks distribution

/H (or /?)

Displays the following summary help:

This tool can be used to remotely block or unblock the delivery of

Internet Explorer 10 through Automatic Updates.

   

------------------------------------------------------------

Usage:

IE10_Blocker.cmd [<machine name>] [/B][/U][/H]

B = Block Internet Explorer 10 deployment

U = Allow Internet Explorer 10 deployment

H = Help

Examples:

IE10_Blocker.cmd mymachine /B (blocks delivery on machine "mymachine")

   

IE10_Blocker.cmd /U (unblocks delivery on the local machine)

------------------------------------------------------------

   

Group Policy Administrative Template (.ADM file)

The Group Policy Administrative Template (.ADM file) allows administrators to import the new Group Policy settings to block or unblock automatic delivery of Internet Explorer 10 into their Group Policy environment, and use Group Policy to centrally execute the action across systems in their environment.

Users running Windows 7 (SP1) or Windows Server 2008 R2 (SP1) will see the policy under Computer Configuration / Administrative Templates / Classic Administrative Templates / Windows Components / Windows Update / Automatic Updates Blockers v3. This setting is available only as a Computer setting; there is no Per-User setting.

Note: This registry setting is not stored in a policies key and is thus considered a preference. Therefore if the Group Policy Object that implements the setting is ever removed or the policy is set to Not Configured, the setting will remain. To unblock distribution of Internet Explorer 10 by using Group Policy, set the policy to Disabled.