Jump to content

Recommended Posts

Posted

Hi,

We use opk for years now, and it work perfect, but my

employer want to use RIS, but i don't know why, he thinks

it's better.

What is the difference and advantages?

We have now a preinstall that automaticly installs

drivers, windowsupdates, and applications.

I don't understand ris. Or is it just a way of

distributing the opk image?

Thanks


Posted

RIS works over network. Ris works with PXE standard NICs (the client needs PXE-support) and it will boot from lan, so you don't need any cd-rom or any floppydrive :rolleyes:. You can add many images (versions like xp home ENG xp pro ENG, win 2003 server, w2k and so on) and you can choose whitch OS you want to be installed to the client system. Images are easy to update, because the install files are in RIS servers harddisk.

I am running the RIS system and i can tell that atleast 90% here at MSFN-forum advices will work straight with RIS.

There are few basic things what you have to learn about RIS. (like oem directory difference between cd-rom and RIS and so on ) But after you have totally understand how the ris works and how to configure it then all the driver and other slipstreaming should be easy.

I am just fighting with those hotfixes to get them all work but i think i will give up and wait SP2 and start with "clean table".

If someone has got those hotfixes to work with RIS, please contact me or reply to this topic :) ... Maybie i will need your cmdlines.txt and runonce.cmd :D

The problem is simple - when i am trying to add and run those fixes they will be shown in windowsupdate as not to be installed :D.

I have tried to use qchain.exe, but it will not work.. And yes, i have read all those main topics about hotfixes too...

More about RIS:

http://www.microsoft.com/resources/documen...cc_ris_rvvt.asp

Posted
If someone has got  those hotfixes to work with RIS, please contact me or reply to this topic :)  ... Maybie i will need your cmdlines.txt and runonce.cmd :D

The problem is simple - when i am trying to add and run those fixes they will be shown in windowsupdate as not to be installed :D.

I have gotten the hotfixes to install using Windows 2000 RIS. In Windows Server 2003 there's usually one hotfix that fails and I don't understand why. The $oem$ directory needs to be at the same level as the i386 directory in your flat image directory structure. RunOnceEx will work as does cmdlines.txt. I have installed XP Pro and Windows 2000 Pro using this setup.

The other advantage of RIS that your silent install of apps is only limited by the hard drive partition size! :rolleyes:

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...