Jump to content


Way2New

Troubleshooting WDS

Recommended Posts

Hello All,

 

I have struggled for the last 3 weeks on imaging. Here is the story, August 10th 2010 I have 300 PC's being dropped in a remote location with ONE PC tech on the ground. The dream is, have the image (I do have a 2 PC test lab set up and the PC's are from the same build) ready to go with multicast on WDS so the PC Tech set's up the 300 PC's and presses F12. :)

 

So, here is my problem ... over the last 3 weeks I have gotten the boot and install images set ... it took a while but my 'test' image is ready to be deployed. I deploy and I recieve the following error:

 

WdsClient: An error occurred while starting networking: a matching network card driver was not found in this image. Please have your Administrator add the network driver for this machine to the Windows PE image on the Windows Deployment Services server.

 

I do have admin rights on our 2008R2 WDS server ... I know the above error wants me to manually inject the drivers ... I have this nifty CD provided by my builders ... with 207 drivers on it :). So I take the notes that ANYWEB created on 'Guide: Adding drivers to a custom WinPE 3.0' I have ruined 3 boot files because when I inject the drivers I then get a command prompt that says Administrator X:\ and it just sticks there, if I type in EXIT and press enter the computer just re-boots. I would rather troubleshoot the WdsClient error ... can anyone help?!?!

 

 

THANKS!

Kates

Share this post


Link to post
Share on other sites

Hello All,

 

I have struggled for the last 3 weeks on imaging. Here is the story, August 10th 2010 I have 300 PC's being dropped in a remote location with ONE PC tech on the ground. The dream is, have the image (I do have a 2 PC test lab set up and the PC's are from the same build) ready to go with multicast on WDS so the PC Tech set's up the 300 PC's and presses F12. smile.gif

 

So, here is my problem ... over the last 3 weeks I have gotten the boot and install images set ... it took a while but my 'test' image is ready to be deployed. I deploy and I recieve the following error:

 

WdsClient: An error occurred while starting networking: a matching network card driver was not found in this image. Please have your Administrator add the network driver for this machine to the Windows PE image on the Windows Deployment Services server.

 

I do have admin rights on our 2008R2 WDS server ... I know the above error wants me to manually inject the drivers ... I have this nifty CD provided by my builders ... with 207 drivers on it smile.gif. So I take the notes that ANYWEB created on 'Guide: Adding drivers to a custom WinPE 3.0' I have ruined 3 boot files because when I inject the drivers I then get a command prompt that says Administrator X:\ and it just sticks there, if I type in EXIT and press enter the computer just re-boots. I would rather troubleshoot the WdsClient error ... can anyone help?!?!

 

 

THANKS!

Kates

 

 

Hi Kate

 

I don´t really understand your problem. Are you getting errors while trying to run this command in the "Deployment Tools Command Prompt"?

 

Dism /image:C:\winpe\mount /Add-Driver /driver:C:\temp /recurse

 

What OS are you trying to deploy?

What does the log say? Found here: C:\Windows\Logs\DISM\dism.log

Share this post


Link to post
Share on other sites

Hi Kate

 

I don´t really understand your problem. Are you getting errors while trying to run this command in the "Deployment Tools Command Prompt"?

 

Dism /image:C:\winpe\mount /Add-Driver /driver:C:\temp /recurse

 

What OS are you trying to deploy?

What does the log say? Found here: C:\Windows\Logs\DISM\dism.log

 

 

Hi Wmmayms,

Thank you for the response! No, I do not get any errors while running the commands, I am deploying Win 7. When I PXE boot the new computer into the Install, it goes into 'setting up windows' then I get the WdsClient error. My log states the following:

 

c:\windows\logs\dism\dism.log

 

2010-07-27 08:11:32, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->

2010-07-27 08:11:32, Info DISM DISM.EXE:

2010-07-27 08:11:32, Info DISM DISM.EXE: Host machine information: OS Version=6.0.6002, Running architecture=amd64, Number of processors=1

2010-07-27 08:11:32, Info DISM DISM.EXE: Executing command line: dism /unmount-wim /mountdir:C:\winpe\mount /commit

2010-07-27 08:11:32, Info DISM DISM Provider Store: PID=580 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection

2010-07-27 08:11:32, Info DISM DISM Provider Store: PID=580 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2010-07-27 08:11:32, Info DISM DISM Provider Store: PID=580 Loading Provider from location C:\Program Files\Windows AIK\Tools\AMD64\Servicing\WimProvider.dll - CDISMProviderStore::Internal_GetProvider

2010-07-27 08:11:32, Info DISM DISM Provider Store: PID=580 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\AMD64\Servicing\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2010-07-27 08:11:32, Info DISM DISM Provider Store: PID=580 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2010-07-27 08:11:32, Info DISM DISM Provider Store: PID=580 Loading Provider from location C:\Program Files\Windows AIK\Tools\AMD64\Servicing\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider

2010-07-27 08:11:32, Info DISM DISM Provider Store: PID=580 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\AMD64\Servicing\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2010-07-27 08:11:32, Info DISM DISM Provider Store: PID=580 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider

2010-07-27 08:11:32, Info DISM DISM Provider Store: PID=580 Loading Provider from location C:\Program Files\Windows AIK\Tools\AMD64\Servicing\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider

2010-07-27 08:11:32, Info DISM DISM Provider Store: PID=580 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\AMD64\Servicing\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider

2010-07-27 08:11:32, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.

2010-07-27 08:11:32, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager

2010-07-27 08:11:32, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager.

2010-07-27 08:11:32, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager

2010-07-27 08:11:32, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider

2010-07-27 08:11:32, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager

2010-07-27 08:11:32, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.

2010-07-27 08:11:32, Info DISM DISM Provider Store: PID=580 Getting Provider WimManager - CDISMProviderStore::GetProvider

2010-07-27 08:11:32, Info DISM DISM Provider Store: PID=580 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider

2010-07-27 08:11:45, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.

2010-07-27 08:11:45, Info DISM DISM.EXE:

2010-07-27 08:11:45, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->

2010-07-27 08:11:45, Info DISM DISM.EXE:

2010-07-27 08:11:45, Info DISM DISM Image Session: PID=580 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect

2010-07-27 08:11:45, Info DISM DISM Provider Store: PID=580 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider

2010-07-27 08:11:45, Info DISM DISM Provider Store: PID=580 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider

2010-07-27 08:11:45, Info DISM DISM Provider Store: PID=580 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

2010-07-27 08:11:45, Info DISM DISM Provider Store: PID=580 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider

2010-07-27 08:11:45, Info DISM DISM Provider Store: PID=580 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

 

I can definitely add more if you need it, however this was the last DISM session from this morning. The WHOLE log is attached ...

Share this post


Link to post
Share on other sites

To me this sounds like your networkdrivers (injected to the winpe) does not work properly.

 

What happens if you run a "ipconfig /all" from the commandprompt after it has failed loading?

 

are you running WAIK for win7?

Share this post


Link to post
Share on other sites

To me this sounds like your networkdrivers (injected to the winpe) does not work properly.

 

What happens if you run a "ipconfig /all" from the commandprompt after it has failed loading?

 

are you running WAIK for win7?

 

 

I am running Waik on my WDS Server which is a 2008 R2, I think I am missing a step when attempting to inject the drivers ...

 

@ the x:\Windows\system32>wpeinit cmd prompt I put in ipconfig /all everything looks good ... dhcp is Enabled, I get a 192.168.1.65(Preferred) IP Address, which everything in this office should be on the 1 network ... The DHCP server is good too a 1.1 ... DNS Servers are good as well ... the default gateway is 192.168.1.254 ...

 

Can you help me inject the drivers? I used the post you made on July 23rd 2010 Guide: Adding drivers to a custom winPE (3.0) by using Dism ... I did the commands EXACTLY as they were written ... but for some reason it's not working correctly ... they are being added to my orginal boot.wim fil right? or does it need to go into the Image that I am deploying?!?! Maybe that is what I am missing ... still VERY new at this.

Thank you so much for your help!

Share this post


Link to post
Share on other sites

Hm this seems to be a strange one ..

 

I would suggest reading through this post:

http://social.technet.microsoft.com/Forums/en-US/itprovistadeployment/thread/d70a8258-9dd3-4868-9e06-d25de427f3cc

 

And when you have done this (if possible) connect one of the clients directly to your server just to try it out.

 

 

Share this post


Link to post
Share on other sites

Hm this seems to be a strange one ..

 

I would suggest reading through this post:

http://social.technet.microsoft.com/Forums/en-US/itprovistadeployment/thread/d70a8258-9dd3-4868-9e06-d25de427f3cc

 

And when you have done this (if possible) connect one of the clients directly to your server just to try it out.

 

Hey!

I don't think this is the same error that I am getting. It looks like the error you sent was to make sure that computer is connecting to DHCP, my computer is connecting ... I just don't have the proper drivers installed ... and when I install the drivers (I think I install them incorrectly). Does that make sense?

 

I need help installing the drivers into my WIM file :)

Share this post


Link to post
Share on other sites

Hm okay

 

lets try this:

 

Boot your winpe through PXE..

In the commandprompt type:

 

Notepad.exe x:\Windows\INF\setupapi.app.log

 

Does this logfile say that your network controller faild to load?

 

If it does try inserting your drivers cd into the dvd. And use this command:

 

drvload.exe d:\Folder\Driver.inf

 

Followed by this command:

 

wpeutil InitializeNetwork

Check the log again. If you still get the same error you proberbly need another driver....

 

It is strange however that you recive a DHCP adress if your network drivers are not working properly.

 

 

Share this post


Link to post
Share on other sites

Okay, I tried that on the command line on the PC that I am using to boot through PXE ... PE is on the WDS Server ... maybe that is an issue?

 

The first cmd 'notpad.exe x:\windows\inf\setupapi.app.log

 

says that notpade.exe is not recognized as an internal or external command, operable program or batch file.

 

I just spoke to our Network Admin and our senior network admin that we use as a contractor and both say that the drivers should have been captured in my first image ... the computer had the drivers installed and so they should have been in my image ... is that right?!?!

 

Maybe this will help clarify, I recieved a PC from our builders, when it is given to us ... it is already set up, drivers are installed you just have to go through the initial keyboard layout set up and choosing a network, then I have to join it to our domain. I did that, and I installed 3 simple programs, then captured that image ... that is the image I am using ... my inital boot.wim file is from the installation CD that is provided to us from our builders ...

 

I am using Waik on our Windows 2008 R2 server that has WDS on it ... this server has imaged before however, the guy that did all of our imaging is no longer with us ... so I am missing that knowledge base on how to complete this project :)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...