[boot cd] Trouble with RM build disk

[TurtleMan]

Shortly before my colleague went on holiday he created a new RM build disk for us as 100 new computers and 30 new laptops need setting up.

Whilst he was away we had our servers upgraded from 2003 to 2012 and since then i cant get the computers to build. I originally tried the disk he made which failed almost automatically so was told by the network manager to make a new one (something I haven't done before).

 

I followed the guide in RM's knowledge library on how to make a build disk and it all seemed to go OK.

I popped the disk in one of the computers and ran through the usual set up, choosing which version of windows to install etc.

All seemed to be going well and it got past the place where the original build disk was failing. However once it got to the stage where it retrieves drivers it got stuck and timed out after roughly an hour and a half.

 

Anyone else experienced issues 'retrieving drivers' when imaging a computer using an RM build disk?

Am i likely missing something obvious?

[jswanson]

I've had a similar issue before where it drops the connection (and therefore times out) because I had the wrong Windows PE driver installed. I would start by checking this, you can refer to the tech article TEC1274876 for help.

Failing that do you have a user with the username drivers because that will cause it to fail whilst retrieving drivers - TEC1562348

[synaesthesia]

Would very strongly suggest ditching the build disks and follow the instructions via RM's support system for setting up WDS for full network build of your machines.

[rad]

Log a call with RM and get them to help you out.

 

It is a simple case of recreating a build image, but as suggested a network boot is much better and once set up it makes life easier

[CommodoreS]

I am using WDS for deployment but having the same problem. Its getting stuck on Receiving Drivers and timing out. I am using Win PE3.1 to try and built a Windows 7 32 Bit machine with a Realtek LAN Card. The odd thing is this was working, no changes have been made and now it is not working.

 

I don't have access to TEC1562348.

 

Any advice or help would be appreciated as to how others resolved this problem.

[CommodoreS]

I am still having this problem and wondered if anyone had any ideas please. I had managed to resolve it by removing the LAN cable at that point during the build where it was then continuing with the build process, but it is now displaying an error if it times out or a LAN cable is removed at that point of the build.

[GeekyPete]

Try making a boot disk with just the drivers for that particular model computer on it. Then create the disk as a file collection. It should but it in \\Servername\Bootdisks by default.

 

Then in WDS create a new boot image browsing to the boot disk you just made. Call the boot image something obvious like "Toshiba C50 - Windows 7 SP1 PE 3.1 (X86)". When you then PXE boot from the network you'll get the option to use the correct boot image along with the right drivers.

 

Hope this helps.

 

I am using WDS for deployment but having the same problem. Its getting stuck on Receiving Drivers and timing out. I am using Win PE3.1 to try and built a Windows 7 32 Bit machine with a Realtek LAN Card. The odd thing is this was working, no changes have been made and now it is not working.

 

I don't have access to TEC1562348.

 

Any advice or help would be appreciated as to how others resolved this problem.

[steve_forbes]

Hi,

 

Have you had any luck resolving this issue? If not, please let me know and I will see what we can do to help.

 

Regards,

Steve

 

Steve Forbes

Head of Network Solutions

RM Education

 

E: [email protected]