RIS disaster 1

[sam1981]

I've got 12 new Dell machines and decided to use RIS to install them.
They'll all need the same programs as each other so I created one machine with all the required programs and the latest patches. I then used riprep to copy the image to the RIS server.

All seemed to go ok and it copied over fine.

I then installed a compatible NIC (the on-board NICs aren't recognised by the RIS boot floppy) and began the remote installation. It installed fine, but when the new machines boot up, I enter the product key and registration info, but then it accepts it and reboots and then goes through the process all over again, so the machine never properly boots up!

Worst of all, the original machine that I made the image from is doing the same thing, so I'll have to start completely from scratch to get it working.

Anyone know how I can get over this prob?

 

[AlexIT]

I guess you are installing XP Pro as the OS? You needed to run the sysprep tool before the riprep...

Delete the RIS image, run the tools on the one machine, re-image.

Alex

 

[sam1981]

Hi Alex, yes I am using XP Pro.

Just rebuilt one of the machines (this time using a volume licening disc - the last one was built with the OEM discs that came with the machine), ran sysprep and then riprep again.

I even did it on a different RIS server, but the same thing happened!!

What option am i supposed to use in sysprep? I ticked to autogenerate SIDs and then clicked the 'reseal' box. Any advice on what I should be doing?

 

[qtin]

A couple of things:

1- Why are you installing a different NIC in the machine? This statement leads me to believe that you are working on a new desktop (since it would be hard to install a new NIC in a laptop and PCMCIA cards are not supported by RIS). Why not just add the NIC drivers as instructed in:

http://support.microsoft.com/default.aspx?scid=kb;en-us;315279

? This way you don’t need the boot disk anymore.

2 – Why are you trying to run sysprep before you run riprep? Granted, I have never used sysprep, but I use RIS for XP Pro images and just run riprep w/o any problems. Since you have a volume license CD you can add the key into the riprep.sif
w/ ProductID=(your key here) in the user data section. It seems to me running sysprep would only cause problems. Again, I don’t know what you are trying to accomplish by doing this.

 

[sam1981]

Hu qtin,

1, I am installing a new desktops, yes. I'm installing a different NIC because the onboard one isn't on the HCL so it won't boot if I don't. I'll take a look at your link though.

2, I was running sysprep first because a couple of people had suggested it, I will try your suggestions for the ripref.sif though and see if I have any luck.

Thanks for the help,
Sam

 

[AlexIT]

If its happening on the primary machine it is not a RIS problem. On this first machine you are installing the OS, answering the BS, restarting and it keeps asking for the BS? Or it works fine until after you run Sysprep? (or Riprep?)

What is supposed to happen is the riprep.sif has your ProductID and when you run riprep and it strips the SID (and registration BS) out of the primary machine then uploads the image to the RIS server, including the riprep.sif. Now the primary machine needs to be restarted and the BS re-entered. This machine should work fine now. The next is to image a machine from the RIS server and it will boot (ask for whatever is missing from the .sif file) restart and run fine.

What could be happening is, since XP is tied to a series of hardware (the volume CD still does this, it just doesn't require "activation"), your dual-NIC is confusing the OS. Try adding the driver as Qtin suggests.

On another note with Win2000Pro you could just riprep and it would work on (almost) every machine with a similar HAL. If you do this on XPPro it will fail to install correctly on about 1 per 10 machines (even if they are identical.) Sometimes you will RIS a batch of desktops and later have one machine that acts funny, loosing printer connections, etc. and you will troubleshoot it and find that the RIS install carried some settings from the original image and that setting is in conflict with this machine.

Use sysprep before riprep to clear some of these specific settings XP stores...

 

[sam1981]

I build the primary machine and install all the programs and patched I want on it. After running riprep on it, the machine doesn't boot up again. It's just get's stuck in the same old cycle of wanting the product key and registered user as the other machines. The original machine only has one NIC therefore I can't see that the dual NIC is the problem.

I've tried running it with and without sysprep and it does the same thing everytime.

I'm starting to wonder if the hardware is just odd. These are 12 identical Dell Optiplex 170Ls. Maybe there is just an odd problem with them and RIS???

 

[AlexIT]

Which version of RIPREP are you using? Check out Q313069 from M$...


Alex

 

[sam1981]

I'm doing it on a 2003 server straight from the install disc, so i don't think that update applies, thanks for the suggestion though...

 

[AlexIT]

I am a Dell fan from way back. You might check their boards to see if this is a known issue with this particular unit. I assume that all the components are built on the motherboard?

Did you try running SYSPREP alone? Take the built machine and run sysprep then reboot, does it get stuck?

Alex

 

[sam1981]

I've decided to cut my losses.

This was taking so long that I may as well have not used RIS at all.

I've used RIS to build the machines with the dodgy image, I then botted from the CD and repaired the installation. I have to add in service packs and patches, but all my programs are there ok.



Cheers for your help...

 

[ReddLefty]

If your only problem now is the registration key in your RIS Server when deploying Windows XP or 2003 machines, then just follow this:

How to Use Sysprep with Windows Product Activation or Volume License Media to Deploy Windows XP:

http://support.microsoft.com/default.aspx?scid=kb;en-us;299840&Product=winsvr2003

Also, check with the Dell Forums. I had a batch of OptiPlex GX270's and their latest BIOS revision (A03) no longer worked with RIS servers (this is in W2K). I can no longer downgrade BIOS anymore to A02. The case is still unresolved.



"In space, nobody can hear you click..."