Community
cancel
Showing results for 
Search instead for 
Did you mean: 
tb549
Beginner
110 Views

vPro SOL & RIS

Jump to solution
Hi,

I sortof fudged a way to "F12" into RIS by forcing a client to remote boot to a custom PXE image that pointed to the "n12" startrom.com file (all our clients default to PXE so it can't be changed globally) which loads to the RIS OSChooser fine... from there I can remotely using SOL choose an operating system image to build on the remote PC... whereupon it gives me the following error -

"The operating system image you selected does not
containt the necessary drivers for your network adapter.
Try selecting a different operating system image..."

Which is the standard "you haven't added the NIC drivers to your image correctly" message...

The images build fine when I go into oschooser manually (and indeed are well tested & used) so it's got to be something to do with the SOL connection - Either the PXE boot image redirect or the presence of the active terminal are confusing RIS...

RIS being that it is there's not a lot of useful info it gives me! Has anyone else come across this problem?

Hardware -

Client is DQ35JO motherboard provisioned in SMB mode.
I'm using Radmin viewer 3 on the remote PC (I know this is an Intel forum & I'm aware it could be something funny it's doing... )

*EDIT* - I'm thinking this may be down to the custom PXE image as there are some problems reported with it & RIS... thanks for looking anyway!

Many thanks, Tom.
0 Kudos
1 Solution
tb549
Beginner
110 Views
Yes I did really... I get some slight variation on the reported PCI id for the NIC when using the PXE boot which is the same when using vPro network redirect as a physical disk -

Standard JO NIC -

Checking PCI\VEN_8086&DEV_10BD&SUBSYS_00018086
Checking PCI\VEN_8086&DEV_10BD
Found PCI\VEN_8086&DEV_10BD in e1e5132.inf

gPXE -

Checking PCI\VEN_8086&DEV_10BD&SUBSYS_FFFFFFFF
Checking PCI\VEN_8086&DEV_10BD
Found PCI\VEN_8086&DEV_10BD in e1e5132.inf

gPXE remote (vPro)

Checking PCI\VEN_8086&DEV_10BD&SUBSYS_FFFFFFFF
Checking PCI\VEN_8086&DEV_10BD
Found PCI\VEN_8086&DEV_10BD in e1e5132.inf

Which I'm assuming RIS is taking exception too... so not a vPro problem...

Regards, Tom.

View solution in original post

2 Replies
Gael_H_Intel
Moderator
110 Views
Tom, did you just answer your own question?
tb549
Beginner
111 Views
Yes I did really... I get some slight variation on the reported PCI id for the NIC when using the PXE boot which is the same when using vPro network redirect as a physical disk -

Standard JO NIC -

Checking PCI\VEN_8086&DEV_10BD&SUBSYS_00018086
Checking PCI\VEN_8086&DEV_10BD
Found PCI\VEN_8086&DEV_10BD in e1e5132.inf

gPXE -

Checking PCI\VEN_8086&DEV_10BD&SUBSYS_FFFFFFFF
Checking PCI\VEN_8086&DEV_10BD
Found PCI\VEN_8086&DEV_10BD in e1e5132.inf

gPXE remote (vPro)

Checking PCI\VEN_8086&DEV_10BD&SUBSYS_FFFFFFFF
Checking PCI\VEN_8086&DEV_10BD
Found PCI\VEN_8086&DEV_10BD in e1e5132.inf

Which I'm assuming RIS is taking exception too... so not a vPro problem...

Regards, Tom.

View solution in original post

Reply