@p4ntb0y:

"I was told that HP would not bother with winpe 2.0 until longhorn comes out, which is silly as its obvious that m$ are pushing for winpe 2.

:-("

Once Longhorn has officially released, we should have the PSP, Insight Manager Agents, and tools for our SmartStart Scripting Toolkit. I haven't asked around, but I would not imagine official WinPE 2.0 support until we have a version of the SSSTK that supports WinPE 2. Keep in mind that Longhorn is just now coming out as an RC build, and not every vendor supports Longhorn on their servers. Our support for Longhorn, and quite frankly WinPE 2.0, is in Beta. WinPE 2 is bundled in the WAIK for Vista (and Longhorn when released) distribution.

For now, we only officially support WinPE 1.6 (WinPE 2005) with our SSSTK and Rapid Deployment Pack (RDP) solutions.

@Jazkal

I keep you informed on what works and doesn't on the HP toolkit and winpe 2.0

I creating an offline dvd like the BDD SMS version so I test it with that.

I have not been able to make "sysmgmt service" run so I can't use the tools as it requires this service to run (But not 100% sure)

@chrislynch

Who ever did the documetation for the SSSTK needs a bit of a slap it allways seamed 90% complete saying that it works fine. I ve nearly solved the stupid restart after the diskpart section.

Is there any chance where I can test betas etc? I am part of a large IT Org.

Thanks for the response

Jazkal...

As you noticed already, v2.0 does not see the same devices as v1.6.

One of the biggest omissions that I see is the PCI to PCI Bridge (among others), which is most likely why you are not able to see the Broadcom NIC (or anything else on the PCI Bridge)...I'm working a case currently where we are not able to see the NIC or a fiber card...

You are correct; the issue seems to not be with the actual NIC driver, but with another device "up the chain". I am able to load WinPE 2.0 without any issues on the ML570 G4, which uses the same NC371i NIC as the DL585 G2.

I am currently working this issue and performing test in my lab...I will let you know what I find.

Cheers....

MJV

That would be great, we are down to 2 final issues before we can roll out WinPE2 to our production systems. This issue is one, and the other is WinPE2 x64 not working right on the HP boxes.

Please give this workaround a try and let me know how it works.

1 - Open an elevated command prompt

2 - Type

bcdedit /set CONFIGACCESSPOLICY DISALLOWMMCONFIG

3 - Reboot

The NIC should now be seen by WinPE 2.0

Type this command to change back to normal settings (if needed):

bcdedit /set CONFIGACCESSPOLICY default

hi guys,

i am in the same unfortunate situation..i can load the NIC drivers for the DL380G5 (NC373i) using broadcom's RIS drivers for the netxtreme II card. but, like in the post, winpe 2.0 cannot even see the embedded NC371i's. Has anyone succeeded yet ?

No, I'm waiting for a fix from HP

It looks like HP finally figured out what was wrong with the 585 G2.

http://h18004.www1.hp.com/products/servers...=reg_R1002_USEN

The firmware fix (beta) listed, does work on my tests with WinPE v2.0

Hopefully they will release a new scripting toolkit for these.

However I better test to see if the toolkit can work ok with these drivers.

Hopefully they will release a new scripting toolkit for these.

However I better test to see if the toolkit can work ok with these drivers.

Any luck getting the tools to work? I can boot to pe and load all the hardware drivers but cant get the tools to work.

My results so far:

The new HPDiscovery from the SSTK 1.7 gives some dll -1 info but appears to run and create the hardware file.

Have not trie ifhw to parse the discovery xml file.

v2.3 of statemgr included with SSTK 1.7 gives an error but outputs the saved variable state however when trying to read that variable it always returns a null value.

These are really the only tools i use so I have not tried to use any of the others. Any way to run exe's from PE 2.0 in compatability mode?

Do you have any documentation on what you did to get these models to work? I have not been able to get my DL385-G2 to work with network support.

I sent you a PM.

I have WinPE v2.0 working on the following HP servers:

DL380-G5 (32 and 64 bit)

DL580-G5 (32 bit only, issues with 64 bit)

DL385-G1 (32 and 64 bit)

DL585-G1 (32 and 64 bit)

DL385-G2 (only tested 32 bit so far, works)

DL585-G2 (only tested 32 bit so far, doesn't work)

@Jazkal: What did you do to get the DL380-G5 network support to work?

I've tried "peimg /inf=bxnd.inf mount\Windows". I've tried adding bxnd.inf to the windows\inf folder and the sys files to the windows\system32\drivers folder. Tried renaming the inf to netbxnd.inf. No luck what so ever.

Edited July 9, 200719 yr by zorphnog

Are you using the Broadcom NetXtreme II - RIS drivers?

Just off the top of my head, that was the way to get Network working on my NetXtreme NIC's

Nope. The cards show up as HP NC373i which are supposed to be covered in the beta drivers on that ftp site. I'll look into the NetExtreme II drivers though, who knows...

Here is the devcon output on my devices for the DL380-G5

PCI\VEN_0E11&DEV_B203&SUBSYS_3305103C&REV_03\4&2014205D&0&20F0: Base System Device

PCI\VEN_0E11&DEV_B204&SUBSYS_3305103C&REV_03\4&2014205D&0&22F0: Base System Device

PCI\VEN_1002&DEV_515E&SUBSYS_31FB103C&REV_02\4&2014205D&0&18F0: Video Controller (VGA Compatible)

PCI\VEN_103C&DEV_3230&SUBSYS_3234103C&REV_01\4&3028BA6E&0&0018: RAID Controller

PCI\VEN_103C&DEV_3300&SUBSYS_3305103C&REV_00\4&2014205D&0&24F0: Universal Serial Bus (USB) Controller

PCI\VEN_103C&DEV_3302&SUBSYS_3305103C&REV_00\4&2014205D&0&26F0: PCI Device

PCI\VEN_1166&DEV_0103&SUBSYS_00000000&REV_C2\4&110C88BD&0&00E1: PCI to PCI Bridge

PCI\VEN_1166&DEV_0103&SUBSYS_00000000&REV_C2\4&187919FE&0&00E0: PCI to PCI Bridge

PCI\VEN_14E4&DEV_164C&SUBSYS_7038103C&REV_11\5&2EADD4B0&0&0000E0: Broadcom BCM5708C NetXtreme II GigE

PCI\VEN_14E4&DEV_164C&SUBSYS_7038103C&REV_11\5&DE7916A&0&0000E1: Broadcom BCM5708C NetXtreme II GigE #2

PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_D9\3&61AAA01&0&F0 : PCI to PCI Bridge

PCI\VEN_8086&DEV_25D8&SUBSYS_00000000&REV_93\3&61AAA01&0&00 : PCI HOST Bridge

PCI\VEN_8086&DEV_25E2&SUBSYS_00000000&REV_93\3&61AAA01&0&10 : PCI to PCI Bridge

PCI\VEN_8086&DEV_25E3&SUBSYS_00000000&REV_93\3&61AAA01&0&18 : PCI to PCI Bridge

PCI\VEN_8086&DEV_25E5&SUBSYS_00000000&REV_93\3&61AAA01&0&28 : PCI to PCI Bridge

PCI\VEN_8086&DEV_25E7&SUBSYS_00000000&REV_93\3&61AAA01&0&38 : PCI to PCI Bridge

PCI\VEN_8086&DEV_25F0&SUBSYS_00000000&REV_93\3&61AAA01&0&80 : PCI HOST Bridge

PCI\VEN_8086&DEV_25F0&SUBSYS_00000000&REV_93\3&61AAA01&0&81 : PCI HOST Bridge

PCI\VEN_8086&DEV_25F0&SUBSYS_00000000&REV_93\3&61AAA01&0&82 : PCI HOST Bridge

PCI\VEN_8086&DEV_25F1&SUBSYS_00000000&REV_93\3&61AAA01&0&88 : PCI HOST Bridge

PCI\VEN_8086&DEV_25F3&SUBSYS_00000000&REV_93\3&61AAA01&0&98 : PCI HOST Bridge

PCI\VEN_8086&DEV_25F5&SUBSYS_00000000&REV_93\3&61AAA01&0&A8 : PCI HOST Bridge

PCI\VEN_8086&DEV_25F6&SUBSYS_00000000&REV_93\3&61AAA01&0&B0 : PCI HOST Bridge

PCI\VEN_8086&DEV_25F8&SUBSYS_00000000&REV_93\3&61AAA01&0&20 : PCI to PCI Bridge

PCI\VEN_8086&DEV_25F9&SUBSYS_00000000&REV_93\3&61AAA01&0&30 : PCI to PCI Bridge

PCI\VEN_8086&DEV_2670&SUBSYS_00000000&REV_09\3&61AAA01&0&F8 : PCI to ISA Bridge

PCI\VEN_8086&DEV_2688&SUBSYS_31FE103C&REV_09\3&61AAA01&0&E8 : Universal Serial Bus (USB) Controller

PCI\VEN_8086&DEV_2689&SUBSYS_31FE103C&REV_09\3&61AAA01&0&E9 : Universal Serial Bus (USB) Controller

PCI\VEN_8086&DEV_268A&SUBSYS_31FE103C&REV_09\3&61AAA01&0&EA : Universal Serial Bus (USB) Controller

PCI\VEN_8086&DEV_268B&SUBSYS_31FE103C&REV_09\3&61AAA01&0&EB : Universal Serial Bus (USB) Controller

PCI\VEN_8086&DEV_268C&SUBSYS_31FE103C&REV_09\3&61AAA01&0&EF : Universal Serial Bus (USB) Controller

PCI\VEN_8086&DEV_2690&SUBSYS_00000000&REV_09\3&61AAA01&0&E0 : PCI to PCI Bridge

PCI\VEN_8086&DEV_2692&SUBSYS_00000000&REV_09\3&61AAA01&0&E1 : PCI to PCI Bridge

PCI\VEN_8086&DEV_269E&SUBSYS_31FE103C&REV_09\3&61AAA01&0&F9 : IDE Controller

PCI\VEN_8086&DEV_3500&SUBSYS_00000000&REV_01\4&276E5639&0&0010: PCI to PCI Bridge

PCI\VEN_8086&DEV_350C&SUBSYS_00000000&REV_01\4&276E5639&0&0310: PCI to PCI Bridge

PCI\VEN_8086&DEV_3510&SUBSYS_00000000&REV_01\5&36FA8587&0&000010: PCI to PCI Bridge

PCI\VEN_8086&DEV_3514&SUBSYS_00000000&REV_01\5&36FA8587&0&080010: PCI to PCI Bridge

PCI\VEN_8086&DEV_3518&SUBSYS_00000000&REV_01\5&36FA8587&0&100010: PCI to PCI Bridge

39 matching device(s) found.

This was pulled off WinPE 1.6, but it douldn't matter where the devcon scan was run.

Edited July 9, 200719 yr by Jazkal