Solved

WDS: Cannot add captured image as boot image

Posted on 2014-04-24
3
510 Views
Last Modified: 2014-04-25
Good day all,

I have installed WDS 2012 and successfully captured an image from a win7 pc. Now my question is how to push this image to all my network computers through wds?

When I pxe boot form a pc I can only choose from 'boot' images. Now my captured image can only be added as an 'install' image not 'boot' so I'm baffled.

What am I doing wrong?

Thanks
0
Comment
Question by:Euronav
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 9

Accepted Solution

by:
Red-King earned 500 total points
ID: 40019847
The boot image is used to start the computer into the Windows installation environment.
The install image is what you actually install on the computer.

So PXE boot the PC and select your boot image.
Once you've booted into the install environment (Windows PE as it's called) you will get the choice to select the install image (after you've entered username and password to log into the WDS server).

Did you run Sysprep on the computer that you took the capture from?
Doing this wipes system specific information such as the computer name and the SID.
0
 
LVL 1

Author Comment

by:Euronav
ID: 40021934
Might be high jacking my own question now. I proceeded after having understood how it works but once I booted to my boot image I got error ‘wdsclient: An error occurred while starting networking’. I injected the network driver for the specific hardware pc to the boot image and it worked.
Once I tried another type of hardware pc I got the error again. Now my question is, can I inject the different network driver to the same boot image and each time it will know which one to push out or do I have to create different boot images for each specific hardware pc with different network drivers each?

Thanks again
0
 
LVL 9

Expert Comment

by:Red-King
ID: 40022058
You can add multiple network drivers into the boot image.
They will all be downloaded to the PC as part of the boot image and the most appropriate one will be used by Windows PE.
So if you were to collect the network drivers for each of the different NICs across your hardware base and add them all to your boot image you should then be able to boot on any hardware.
0

Featured Post

Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I have put this article together as i needed to get all the information that might be available already into one general document that could be referenced once without searching the Internet for the different pieces. I have had a few issues where…
Experts-Exchange users below are the steps you can follow to upgrade your Lync server to latest CU's or cumulative updates. Note: Perform it during non-production hours.   Step 1: Backup your lync and SQL server database. Follow below article: h…
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question