Creating a RIS Image - Error message on any pc

[Melissa Schaefer]

I installed RIS on my server and then went to go create my image on a client pc, but when I run the RIPrep I keep receiving an error that it does not have the correct CD-Image.

I ended up purchasing Ghost as our solution. Anybody have any opinions on RIS or ideas on this issue? :shock:

[jonmr75]

We currently implement a RIS workstation/server deployment solution at 20 sites, covering around 5,000 clients. Whilst not involved in the initial infrastructure design/creation, I am now responsible for maintenance and development of the RIS infrastructure. In other words, I'm pretty close to the thing.

All in all, I'd say we're pretty pleased with it as a deployment tool. Maintenance is relatively light, deployment speed is not amazing but adequate for our needs (25 minutes for XP, extra for SMS apps, etc). Some user problems seen (mainly during rebuilds (and then generally AD integrated stuff)).

I've never used Ghost as an enterprise deployment tool so can't really compare, though we are starting to look at SMS imaging technology and that looks v interesting.

Regards

[clutch]

I like RIS because I can deploy systems straight to an OU, and it performs a clean installation onto the hardware of choice (not just an image from one hardware platform). I haven't had any problems using Server 2003 as my RIS box, but when 2000 first came out, groveler (grovel.exe, the app that searches for redundant files) was dragging my server down and tearing up my drive. I didn't use it for quite a while until I decided to upgrade my MCSE from NT to 2003, and started taking the server and XP exams. Since then, it's the only way I bother setting up both virtual and real machines at home (again, no HAL dependency issue) and will start using it in the lab. The only downside is that it is "limited" to deploying machines to your AD, rather than just deploying systems that can sit in workgroup status until you join them (that would be useful in a lab, but I can dig the AD dependency).

[Black Duck]

With the ripprep you need to have a 'normal ris image' that exists on the server. Lets say you want to install XP with intergrated SP2, you would slipstream a disc and then would create a default image on the RIS server. Once this is done you can either build a machine with the CD or Ris and then you will be able to use RipPrep to put the image on the server, once done you should be able to rip down. This is what I have found anyway after three years of using RIS.

As far as Enterprise ghost goes, I have used both and for speed go with ghost 15 min for os and apps, for stabiltiy and ease of use go with Ris normally 40 min with apps and riprep. If you get a new computer with a different HAL you only need to put the drivers in the driver section with Ris. With Ghost you need to attempt to install the existing image on the computer (does not work most of the time) and then you end up stuffing around trying to get it up and running before finally giving up and doing it manually. Yes Sysprep does sometimes work here (see stuffing around). Then you have to take an image which confuses your roll out because now you have two images and have to decide everytime you ghost a computer. With ris you just keep tacking on the drivers and can have you whole fleet installing of the one image. Love it.

[JLC]

I have encountered the same issue. We have been using RIS for about 4 years now. Usually when you get the error msg about the incorrect CD based image, your clients ntoskrnl.exe has been modified. Most likely from Windows Updates or hotfixes. Look at the properties of this file on the client to see what version it is and compare it to the CD based image on the RIS server.

I have found that if you make a copy of the CD based image on the RIS server and copy the ntoskrnl.exe from the client to the server, that you can now run the RIPrep.exe without error.