Booting new workstation to WDS server returns network driver error...

-

i'm trying setup new wds server upload , download our custom windows 7 images.  belive of wds server setup , ready.  grabbed generic boot.wim file windows 7 disk , uploaded wds server.  i've uploaded install.wim files have images ready pulled down.  every time boot the client , select first boot.wim file following error:

http://www.christiano.ch/wordpress/wp-content/uploads/2011/05/wds_winpe_wdsclient_an_error_occured_while_starting_networking_thumb.png

 

just error sayd figured i just need add some new network drivers boot.wim file , re-import wds server.
can instructions here:

http://www.christiano.ch/wordpress/2011/05/13/windows-deployment-servicesadding-drivers-to-boot-wim/

however after re-upload boot.wim file wds server after adding new drivers still have 1 boot option client.  i'm wondering why new boot.wim file should have new drvers, although listed @ boot image on wds server, not displaying client boot from.

not adding right drivers? i'm using hp 8200 small form factor. although don't think prevent new boot option displaying.  if problem same wds clieint error above talking not finding correct network driver.
so, though boot.wim file modification finishing successfully, boot.wim file corrupted causing not display new boot option?

any here appreciated.

greg

greg


hi,

 

from snapshot, need add network drive in boot.wim image make sure clients bootable via internet.

 

toward manage , deploy drivers packages, there link reference:

 

title: managing , deploying driver packages

url: http://technet.microsoft.com/en-us/library/dd348456(ws.10).aspx

 

i think use mdt deploy os more effective , efficiency. detailed information refer link below:

 

title: microsoft deployment toolkit

url: http://technet.microsoft.com/en-us/solutionaccelerators/dd407791

 

i hope information provided above helpful you.

 

regards,

james

james xiong

technet community support



Windows Server  >  Setup Deployment



Comments

Post a Comment

Popular posts from this blog

DCOM received error "2147746132" from...

-
hi everybody, i have dc (my windows essentials 2012 server) , windows 2012 server in network.  the windows server 2012 inside domain. on server, got "non stopping" error says in event logs : ===> dcom received error "2147746132" fromd computer xxxx(my dc computer) while server trying activation : {6df8cb71-153b-4c66-8fc4-e59301b8011b} it never stops, got 11000+ new events :s i found : http://support.microsoft.com/kb/971153/fr i'm not sure should ? does got idea ? matthieu. hi, please try solution mentioned in below link: http://www.eventid.net/display-eventid-10006-source-dcom-eventno-272-phase-1.htm regards, cicely Windows Server  >  Windows Server 2012 General ...
Read more

DFSR RPC replication errors 5014 1726 with large files over VPN

-
i have similar issue ryan in reply http://social.technet.microsoft.com/forums/en-gb/winserverfiles/thread/6d49fd71-2236-4fcb-9763-bf1c03459ee8 cited below. start additional thread here because other 1 related windows server 2003 (r2) , i'm (as ryan) on windows 2008 r2 x64. here first of post ryan: i've got same problem on 2008 r2 dfsr server.  the spoke server has 2x intel 1 gigb on-board nics in active/standby teamed configuration. the hub server (running on vmware using 10gbit vmnet3 nic driver) logs dfsr event 5014 every 2-15mins (usually around 5mins). the spoke server not log event. replication running slowly. initial sync/replication. had re-configure replication folder because of lost dfsr database on spoke server.  could teamed nic on spoke causing error on host? a note: last time did initial sync on folder processed @ 30k files , hour. time it's doing few hundred and hour. another note: hub server has several replication groups , conne...
Read more

ADFS 3.0 Event ID 4625 | An Error occurred During Logon | Status: 0xC000035B

-
we're getting these random errors on our adfs security logs, how can track down generating them? an account failed log on. subject: security id: null sid account name: - account domain: - logon id: 0x0 logon type: 3 account logon failed: security id: null sid account name: account domain: failure information: failure reason: an error occured during logon. status: 0xc000035b sub status: 0x0 process information: caller process id: 0x0 caller process name: - network information: workstation name: - source network address: - source port: - detailed authentication information: logon process: kerberos authentication package: kerberos transited services: - package name (ntlm only): - key length: 0 event generated when logon request fails. generated on computer access attempted. subject fields indicate account on local system requested logon. commonly service such server service, or local process such ...
Read more