Deployment Solution

Hi All,

I'm currently trying to boot into WinPE from an Altiris 7.1 server. When I get to trying to validate a network connection. It brings up a message saying

Validating network connection <validation criteria = -169.254>

Restarting DHCP client service: retry 1...

Restarting DHCP client service: retry 2...

Restarting DHCP client service: retry 3...

Restarting DHCP client service: retry 4...

I have tried downloading the vista drivers specific to the netbook I'm trying to image also.

I have included a not so clear image of the error.

Cheers

This is most definitely a NIC driver issue.  You might try using Windows 7 drives instead of Vista with that version of WinPE to see if that helps your cause.

Client machine in Automation is not able to get ip address. so it keep on retrying ...

Whether the drivers have just deleted themselves or it's an issue with Altiris 7.1 but I am yet again having the Restarting DHCP Client message again. I have imported the Win7 and Vista drivers into the Driver Management Database but still have this issue. Have recreated the Preboot Configuration after importing them.

Anyone anymore ideas please?

i'm having the same issue, how can we be sure the drivers are actually loaded since we don't see anymore the process of recreating the whole winpe image?

i'm trying to boot with vmwnet3 as i do on 7.1

The process to update automation drivers is different than the other drivers.

Browse to \\localhost\deployment\task handler\BootWiz

1. Launch BootWiz.exe with administror privilegies.

2. In the tool bar select Tools and then Add Preboot-device Driver...

3. Once the preboot driver is installed your preboot boot files need to be recreated this for PXE and for automation boot.

Nelson V.

After running this update schedule it allowed me to boot into the WinPE environment and then select my Initial Deployment Task.

Now I have the issue where my task won't actually complete. Basically I want to capture an image and then copy that image to the Deployment Server share. This is the client job that I've created so far.

• Prepare for Image Capture
• Create Image
• Reboot to Production

It fails on the create image step, on the log it says that I need to check the Advanced Settings for the Create Image step. Only thing I can think of is that I'm missing some command line code which I haven't entered. I've attached the various pictures. Not had much luck with creating jobs for client computers anyway so if anyone has any tips or advice that would be great.

Have attached images or task error and command line option.

Not sure, i doubt if this will update the Automation Folder in DS 7.1

Post the logs here, remove your company info before though :)

the logs are located in x:\program files\altiris\altiris agent\logs

there should be a pectagent.log, agent.log and a task specific log.

nelo

The folder logs doesn't exist there at all and I cant find it anywhere on the machine at all, anywhere else they could possibly be.

while in Winpe type "ping nsservername" if it does not reply u might have a DNS issue.  try ping by IP and see u could see the NS.  Also, ipconfig gives u result?

I am having the same problem, seems that the 82579LM drivers are not supported, I have downloaded some from the HP website and gone through the process of Driver management and installing the drivers and then recreating the PreBoot but its still not working.. am just getting the same message..

Validating Network Connection (validation criteria = -169.254)...

Restarting DHCP Client service: retry 1...
Restarting DHCP Client service: retry 2...
Restarting DHCP Client service: retry 3...
Restarting DHCP Client service: retry 4...

.. and so on, until it says could not get an IP address

V.

Same problem here, but with DS 6.9. I loaded the new drivers as one person suggested using PXE Config, and that didn't work. I re-generated the Boot Images and that didn't work either. I created a new Boot Option with the new drivers, and that didn't work.

Then I loaded the drivers as another suggested using BootWiz, it didn't work either.

These are new Dell e6420/e6320 laptops with the 82579LM Chipset/network cards.

Any suggestions other than those that have been tried?

I am also having the same issue. The driver doesn't seem to show up after I add it to the database. I have tried both the NS console and BDC.

Also having this problem with Latitude E6420's with the 82579LM NICs, on DS7.1. I've tried every driver under the sun. I can't get them to load. Has anyone got this model/NIC to work yet?

I'm experiencing this same issue. Restarting DHCP client service: retry........ I have an HP 8200 w/ an 82579LM NIC. I've downloaded the latest drivers from HP & Intel. I was on DS 6.9 w/ SP4 and now have upgraded to SP5 but, still no luck. Grrrrrrr......Argghhhhhh!

So, here are a few thoughts.

1) There is no automatic method of updating automation folders at this time.  This is a known limitation in the product and yes, one of our list of items to fix.  There is a KB that discusses how to update automation folders, but the key thing to remember is that you have to essentially remove them and re-install them.  The Linux PE and Windows PE "default" items that always show up on the list of preboot configurations are the automation folders.  Many delete these thinking "Oh, I don't need them!"  Well, yeah, you do.  If you add drivers, you then update those, then remove the automation folders, and reinstall them. (not too efficient, but hey, it works.)  Alternatively, you can build a SWD job to push a new set of automation folders down to the client, which is what the KB discusses.

Assuming we're dealing with Automation folders, I suspect all we've done is NEVER updated the automation folder directory on the client, no matter how often we re-build the WIM file on the server.  It's sounding like that now.

2) There are some drivers that do NOT work in WinPE 2.1.  This is a sad but true fact, and is the main reason we have such a big push to get WinPE 3.x supported in the upcoming SP (I hope we make it).  There is also a KB that discusses getting a WinPE 3.x WIM file to work in DS 7.1.  Basically, you end up replacing the WIM with the new one.

3) As with 6.9, there are times when a driver is "recognized" by the OS but is not correct and doesn't work.  In these cases, sometimes moving the driver UP the list within BootWiz will resolve the issue.  The bad news is that you have to actually launch BootWiz AND COMPILE in there to get this process to work.  <sigh>  

4) Personally, I'd test PXE, even if in a limited environment.  Why?  Because you have a faster time getting to a build of the WIM that you KNOW has been updated.  Once you know you have a valid WIM, then send that down to replace the automation folders, and bam - should be good to go.

Anyway, there are some thoughts.  If you can't find the KB's, I'll try to revisit this and dig those up as well.

Just a thought - no clue who to even ask for it - can we get a link to the KB for this product stickied to the top of this forum? I'll be the first to admit, I completely forget to check the Knowledge Base. When I couldn't find the answers I needed there, I started turning to the Connect forums. I never looked back. I only ever go to the KB when I get linked to it from a posting here. I find the Symantec site a bear to search. (I found these forums to be a bear at first, but I'm learning.) Also - I see that there are links to Connect from the KB site; it only makes sense that the reverse be true.

Poor Thomas is probably the wrong person to ask - but where does one go to request such a thing?

Respectfully, DustinW

I'm happy to make useful information like KBs "sticky" - with the help of the product team and your recommendations we can keep some of the more helpful KBs readily available to you.

Thanks,
Cheryl

Give us about a week to come up with something useful instead of qukc and ugly.  :D

I'm having the same problem with the 82579LM drivers. See this thread here: https://www-secure.symantec.com/connect/forums/ds71-preboot-drivers-latitude-e6420-intel-82579lm-nic

It does sound like DS does have a problem with these drivers. Hopefully we'll get a resolution soon? In the meantime, I have been loading the drivers manually in automation. A pain, I know, but at least it's a workaround.

Thre is a better to update drivers now.  It is done via the NS console | settings | all Settings | under deployment there is a Driver Database. There is a section for preboot driver.  Pretty cool.

--nelo

We currently connect to 100mb switches.  What I am seeing is that even in the OS on the E6420 you will not connect to any network resources unless you manually set the nic to 100 full duplex.  Same issue with dos boot disks.  If I take the laptop to a gig connection (set as auto) everything works fine (dos, PE, Win XP).  So now I am trying to figure out how to manually set WinPE 2.1 nic drivers to 100 full.  The 6420 uses the 82579LM nic.