I am trying to rebuild 2 machines on to our CC3 network, both keep sitting at the "scanning for drivers page", the one machine I have left on over the weekend and its still at the same screen!
Any ideas, its been working fine as I have rebuilt a load of machines already last term. Could it be a problem with the rebuild area on the server??
I'd kick the rebuild off with another pc name so it isn't looking at the same .ini file as before.
I know its a mess on the console but it is sometimes the easiest way and then if successful delete the old name
I have given this PC a different name on the network but i'm still getting the same problem.
The one machine is an RM machine and the other a Fuji but both have been loaded on the network before without any problems. Both are doing the same thing now, "scanning for drivers"
Have you definately got all the drivers loaded into the RMMC (CC4)?
Have you put any hardware support packs on the network since you last rebuilt these machines?
Sometimes new HSP can 'knock out' existing/older drivers.
If so, two things to try - first reload into the build area the required drivers for these machines, or second remove the HSP you had put on and see if that resolves your issue.
I am guessing other machines are still building ok??
Have you tried creating a new build disk with the legacy option?
All I did over the half term was to install the windows security hotfixes, HFXCC3240, 241 & 242. Other than that I haven't changed anything else on the server.
It was rebuilding fine before so am a bit confused as to why it has suddenly stopped working. It does obviously see the network as it connects using the network driver to the system and gets as far as the scanning for drivers section. Just will not go any further.
I have tried using a different station name, and also putting into different areas (eg package build) but get the same result.
As I said before both machines were installed previously on our network which is why I can't understand why they are not working!
You may want to run a few tests on your hardware as the 'scanning for drivers' problem can be down to faulty hardware.
Run a disk scan and memory test to check.
It also might be worth trying to build another, completely different workstation to see if its PC or server related. To have two workstations with the same problem seems odd - guessing they both have different kit inside them?
If its server related try the info in TEC1446127 from the RM site - it might be helpful?
Also, I guess you have rebooted the server since the updates, sorry if you have - just checking!:p
Hi thanks for the info, yeah they are completely different machines, one is an RM and the other a Fuji (both desktops), the updates were installed and each server restarted following each installation. Yeah it is odd they both have the same prob, I did originally think it was just something a miss with one machine!
Will have a look the link, thanks
try rebuilding from your replica server; edit the boot disk to point to the replica server.
if it works then your rebuild area will be corrupt.
I would also try a different room (physically) in the school, preferably one that doesn't use the same switch etc.
Thanks for all the info guys, checked out this link (TEC1446127) and moved the this folder D:\RMNetwork\RMmanage\RMRebuild\XPBuild\CUDRV into a temp folder and it now works, there's obviously something in there that it doesn't like, the RM machine is now rebuild and working perfectly, just working on the Fuji one now! How can I find out what is causing the problem in the above folder??
Thanks for all your help!
It might be a trial and error process, put some drivers back in and see if the build breaks, if not, put some more and so on.
You could load all of the drivers fresh into the build area, if there aren't too many?
Glad the link helped!