Video Screencast Help

Unable To Create Image Receive Restarting DHCP client Service Error

Created: 16 Jul 2013 | 10 comments

Hello all.  I'm working on grabbing an image of a Lenovo M70e Desktop system running Windows 7 64 bit.  Using Altiris 7.1.  I created a job that runs 3 tasks:

Prepare for Image Capture

Create Image

Reboot to Production.

I was able to run this job on another system just fine but now with thie system I pass step one but on the second one it boots to Windows PE and I get the following on the screen

Initializing network…

Starting the network…

Loading drivers…

Using dynamic IP…

Configuaring WinPE firewall…

                Firewall disabled.

Establishing network connection…

Vailidating network connection (-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…

                Restarting DHCP client service: retry 5…

                Restarting DHCP client service: retry 6…

                Restarting DHCP client service: retry 7…

                Restarting DHCP client service: retry 8…

                Restarting DHCP client service: retry 9…

                Restarting DHCP client service: retry 10…

                Restarting DHCP client service: retry 11…

                Restarting DHCP client service: retry 12…

                Restarting DHCP client service: retry 13…

                Restarting DHCP client service: retry 14…

                Restarting DHCP client service: retry 15…

                Restarting DHCP client service: retry 16…

                Restarting DHCP client service: retry 17…

                Restarting DHCP client service: retry 18…

                Restarting DHCP client service: retry 19…

                Could not aquire IP address.

Upon some research I found suggestions regarding the NIC drivers not being setup.  So I went to lenovo and extracted the drivers into a folder.  I then went into the console and under Driver Management in the preboot tab clicked ADD and pointed to that folder.  It seems like it worked as I can now see the Marvel driver in the list.

Afte that I went to Preboot Configurations and clicked Recreate Preboot Environment. 

After that I ran the job again but it keeps getting stuck in the spot above.  Any help on what i'm missing would truly be appreciated.

Operating Systems:

Comments 10 CommentsJump to latest comment

andykn101's picture

You need to use the Vista drivers for the WinPE with Symantec.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

oscarc619's picture

Thanks for the follow up.  Should I delete what I uploaded?  I just pointed to the root and it picked it up.

andykn101's picture

Probably best to delete what you imported and make sure you use the Vista drivers. If it's an all-in-one type driver package, make sure you browse to the Vista section.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

oscarc619's picture

Thansk.  I don't see a delete option within the console.  Where do I need to go to remove them?

I did try to upload the Vista drivers and when I do it shows them in the Deployment Solution tab even though I was in the preboot tab.  

Indrek_K's picture

Hello,

First I would be sure that the driver you are going to upload will work (will save time finding the correct driver, and as previously told the WinPE only accepts Vista drivers)

http://www.symantec.com/docs/HOWTO9542

 

After we know that the driver works, we need to upload it into the preboot section. Next step is to recreate the preboot (after we clicked the re-create close the windows using the red x in the corner do not click save changes).

Now we open Symantec Management Agent on the Notification Server and go into settings to update the configuration (both request and changed time will change) we should now see in Task Manager that Bootwiz is running. If you have any other PXE server then same thing needs to be done on those also.

Now if Bootwiz.exe is finished the new WinPE is ready to be used.

Thomas Baird's picture

Question: Are you using automation folders or PXE?

 

Updating the PXE servers with a new build of PE and with new drivers is pretty quick and relatively painless as Indrek indicated.  Automation folders howerver are a very different story, so please let us know.  We have an exhaustive article on how to make sure Automation Folders update correctly because out-of-the-box they do NOT.

 

Adding drivers to both is the same in the console though.

 

Removing bad drivers can be very simple: find the driver in the DriversDB folder on the NS and delete the folder if you don't like it. Then re-launch Driver Manager from the console.  You may want to delete the DriverManifest file in the root of DriversDB.  In the link at the top of this forum, there are some additional videos and such helping you troubleshoot DA.

 

IMO - just add the right driver to Driver Manager via the Console, and then make sure your preboot environment is up-to-date.  IF you are using automation folders, please use the article all about them found here:

http://www.symantec.com/docs/HOWTO83910

 

Thomas Baird
Private Consultant

 

oscarc619's picture

Yes the task is set to sysprep and then reboot to Folder Automation.  Thanks so much for the help.

oscarc619's picture

Well still no luck.  I event changed the task to boot into PXE and it still has trouble getting passed that DHCP error.  I'm thinking maybe the driver is the issue.  It's a Marvell Yukon Driver version 11.44.1.3 and in my Preboot Database the driver is listed in that way.  I updated the configs from the NS and it still doesn't grab.  We have other models of Lenovo's and haven't had this issue. 

Now in the article you sent it mentions that the packages update on their own at 3am.  Where can I find the pack refresh schedule to manually refresh to try that?  I can't seem to find that option.  

Thanks

oscarc619's picture

I went ahead and removed all the marvel drivers i had uploaded from the NS.  I then added them again in the Preboot folder using the console on the NS.  Then updated the configuration.  I tried again and same result.  

How can I make sure that the Site Server is synched and as the drivers?  

How and I force a synch? 

Thanks guys.