Keeping RIS images up to date

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am using a 2000 Server with RIS to image 2000 Pro and applications on 200+
machines. I can slipstream Service Packs and create new base images without
a problem, but what is the best way to handle individual security updates and
hotfixes? Can they be slipstreamed also? Is there an easy way to tell which
updates may affect the kernel files so I know which ones will affect my base
images? We use RIS to image systems weekly and would like them to be as up
to date as possible without having to do any manual updates after the
imaging.

Thanks for the help.
 
Hi,

I just did what you need to know. I have a Windows XP cd that I used to push
a cd based image to my RIS server.

I then built a system with all our applications and configurations. Also, I
installed XPSP1 and all updates/service packs. When attempting to push the
newly created image to my RIS server it told me that the version on the RIS
server did not match the version I was tring to push (RIPREP.EXE). This is
because the service packs and updated have changed the version on the
NTOSKRNL.EXE file on my RIPREP workstation. I wanted to be able to push out
systems as up-to-date as possiable just like you are trying to do.

I had to copy the NTOSKRNL.EXE from my RIPREP workstation to the cd based
RIS image of Windows XP (Under the i386 folder). Once I did that I was able
to upload a RIPREP image to the RIS server.

I tested the image by pushing it to a test workstation and indeed, all the
service packs/update are applied with no problem.

HTH

Drum On .. .. . . .
 
Back
Top