PXE deployment not working on Dell E series

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 1

Hi All,

I have recently purchased Snap deploy 4 and as yet I have not been able to get a succesful deployment via PXE to any Dell E series laptop. Even if I add the MAC manually it still doesnt work.
Our fleet comprises of Latitude E 4310, 6220, 6320, 6530, 6330.
I have a large number of new machines waiting to be imaged and as such can only deploy via standalone method. As you can imagine this is not good due to the time taken to image machines in this manner.
Is there a hotfix available that will allow snap deploy to see the NIC's on these machines?
See attached:
Please help

Attachment Size
acronis_error.txt 1.75 KB
Mon, 07/23/2012 - 04:06
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 3
Comments: 23

Have you tried creating your own custom PE image to upload to your PXE server? Ive been unsuccessful using the stock setup, and ive had to create my own image using Windows AIK 3.0 and downloaded winPE drivers from dells site for each system. They are usually under System Management on dells site. That package should have all that you need to get the nics recognized.

Mon, 07/23/2012 - 15:53
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 1

Hi, Sorry could you be more specific.
I have SOE images that I have created with Acronis that we use for our fleet.
How do I create a PE image and what is the difference between that and what I already have?
Sorry but I'm new to this

Thu, 07/26/2012 - 07:19
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 3
Comments: 23

To create a PE image, you first should download and install Windows AIK 3.0 on the server where Acronis resides. After that you can download from dell WinPE drivers. Extract the cab with what ever utility you have handy. This should give you a package of the drivers needed to at least get the NIC and storage recognized. Most dell pcs have this under "System Management" in the driver section.

From the Management Console, click Tools, then Create PE image.
Select Use WinPe files located in the folder I specify, then navigate to the \Tools\PETools\x86 directory of the Windows AIK install.
Select Network Settings and put in the Server IP or DNS name of your Acronis server
Select Acronis PXE Server for media type (make sure there isnt one already there as well, as mine would give errors if I didnt remove the previous PE image)
Put in DNS or IP address of PXE server as well as credentials for access
Password protect this if you desire
click on add at the bottom and navigate to the PE driver package you downloaded and extracted.
Click Create on the next page and if all goes well you will have a working PE image for a 390. If need be add other driver packages to get all of your other systems to work.

I copied and pasted this from a previous post of mine..

As for the difference, im not sure. All I know is this works for me. I dont know what drivers you are putting into the system with your other method, but this should do the trick. I hope this helps.

Thu, 07/26/2012 - 15:44
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 88
Comments: 4769

Hello Everyone,

Thank you for posting and thank you for your help bbam support.

Eireannjon, I apologize for the issues that you experienced with our software. From what I can see in the case, we are currently investigating this issue.

Please let us know if there is anything else we can do for you.

Thank you.

Fri, 07/27/2012 - 11:39
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.