Difference between revisions of "RIS"

From Syslinux Wiki
Jump to: navigation, search
(Retrieved from archive.org with minor modifications for wiki formatting.)
 
m (Minor wiki formatting. Add links.)
 
Line 1: Line 1:
 +
[[Category:Examples]]
 +
[[Category:PXELINUX]]
 +
[[Category:TFTP]]
 +
__NOEDITSECTION__
 +
<!-- KEYWORDS:
 +
--><!-- Windows Remote Install System
 +
--><!-- Windows Remote Install Services
 +
--><!-- Windows Remote Installation Services
 +
--><!-- PXELINUX and Micro RIS
 +
--><!-- PXELINUX and Microsoft RIS
 +
-->
 +
See also
 +
* [https://en.wikipedia.org/wiki/Remote_Installation_Services <!--
 +
--> Remote Installation Services], RIS (wikipedia)
 +
* [https://en.wikipedia.org/wiki/Windows_Deployment_Services <!--
 +
--> Windows Deployment Services], WDS (wikipedia), <!--
 +
--> the successor/replacement of RIS <!--
 +
-->
 +
* [[WDSLINUX]]<!--
 +
-->
 +
 
== RIS and PXELINUX ==
 
== RIS and PXELINUX ==
 
<br />
 
<br />
<!-- Retrieve from http://web.archive.org/web/20080224051158/http://syslinux.zytor.com/ris.php -->
+
<!-- Retrieved from  
<!-- with minor modifications so to match wiki formatting and to correct some minor typos -->
+
--><!-- http://web.archive.org/web/20080224051158/http://syslinux.zytor.com/ris.php  
 +
--><!-- with minor modifications so as to match wiki formatting  
 +
--><!-- and to correct some minor typos.
 +
-->
  
 
Christian "Dr. Disk" Hechelmann writes the following about using PXELINUX  
 
Christian "Dr. Disk" Hechelmann writes the following about using PXELINUX  
in conjunction with the '''Windows Remote Install System''':
+
in conjunction with the  
 +
'''Windows Remote Install <font color="lightgray"><small><s>System</s></small></font> Services''':
 
<br />
 
<br />
 
----
 
----
 
<blockquote>
 
<blockquote>
 
Hi,
 
Hi,
<br /><br />
 
  
 
I'm in the process of creating a remote install/boot environment at the  
 
I'm in the process of creating a remote install/boot environment at the  
 
company I work and choose PXELINUX for the Linux part. We use a mixed  
 
company I work and choose PXELINUX for the Linux part. We use a mixed  
 
environment of W2K/Linux Servers and W2K/XP Clients. In the PXELINUX FAQ  
 
environment of W2K/Linux Servers and W2K/XP Clients. In the PXELINUX FAQ  
you write (based on [[PXELINUX#How Should I Setup my TFTP server?|Eric Cook's report]]), not to configure RIS with the GUI  
+
you write  
 +
(based on [[PXELINUX#How Should I Setup my TFTP server?|Eric Cook's report]]),  
 +
not to configure RIS with the GUI  
 
for ''"you end up with the MS PXE stuff, which is ugly to get rid of"''. Well,  
 
for ''"you end up with the MS PXE stuff, which is ugly to get rid of"''. Well,  
 
PXELINUX just works great on a fully configured RIS (And thereby keeping  
 
PXELINUX just works great on a fully configured RIS (And thereby keeping  
Line 25: Line 51:
 
gets the directory you specify as the <tt>remoteinstall</tt> share as its root.
 
gets the directory you specify as the <tt>remoteinstall</tt> share as its root.
 
<br /><br />
 
<br /><br />
For example when you set up an RIS on RISSERV and specify  
+
For example when you set up  
 +
a<font color="lightgray">n</font> RIS on RISSERV and specify  
 
<code>D:\RemoteInstall\</code> as the server root you end up with this:
 
<code>D:\RemoteInstall\</code> as the server root you end up with this:
  
 
* The share <code>\\RISSERV\REMINST</code> pointing to <code>D:\RemoteInstall\</code>
 
* The share <code>\\RISSERV\REMINST</code> pointing to <code>D:\RemoteInstall\</code>
 
* The tftproot being <code>D:\RemoteInstall\</code>
 
* The tftproot being <code>D:\RemoteInstall\</code>
* having the usual directory tree below that <br />
+
* having the usual directory tree below that <br /><!--
<code>  ...\Setup\<language>\{Images,tools}\whatever\<arch>\templates</code>
+
--><code>  ...\Setup\<language>\{Images,tools}\whatever\<arch>\templates</code><!--
<br /><br /><br />
+
--><br /><br /><br />
 
I just gave it a try and did the following:
 
I just gave it a try and did the following:
 
<br />
 
<br />
# Made <code>Setup\German\Tools\PXELinux\i386\templates\</code> and <br /><code>\Setup\German\Tools\PXELinux\i386\templates\pxelinux.cfg\</code> <br />(The latter since I didn't want to mess with DHCP just now)
+
# Made <!--
# Copied <tt>pxelinux.0</tt> to <br /><code>Setup\German\Tools\PXELinux\i386\templates\</code>
+
--> <code>Setup\German\Tools\PXELinux\i386\templates\</code> and <br /> <!--
 +
--> <code>\Setup\German\Tools\PXELinux\i386\templates\pxelinux.cfg\</code> <!--
 +
--> <br />(The latter since I didn't want to mess with DHCP just now)
 +
# Copied <tt>pxelinux.0</tt> to <br /> <!--
 +
--> <code>Setup\German\Tools\PXELinux\i386\templates\</code>
 
# Put a <tt>pxelinux.sif</tt> in the templates directory
 
# Put a <tt>pxelinux.sif</tt> in the templates directory
# Put a default config in the <tt>pxelinux.cfg</tt> dir
+
# Put a <tt>default</tt> config in the <tt>pxelinux.cfg</tt> dir
 
# Put the message files, kernel and initrd images in the templates directory
 
# Put the message files, kernel and initrd images in the templates directory
 
# Let a PXE client (Intel EEPro 100+ with BA 4.1.09) try what happens.
 
# Let a PXE client (Intel EEPro 100+ with BA 4.1.09) try what happens.
Line 52: Line 83:
 
I had to modify the file <code>\OSChooser\German\tools.osc</code> though, to have the  
 
I had to modify the file <code>\OSChooser\German\tools.osc</code> though, to have the  
 
''Client Installation Wizard'' actually display the ''"Maintenance and Tools"''  
 
''Client Installation Wizard'' actually display the ''"Maintenance and Tools"''  
menu instead of just giving an ''"no os choices here"'' display. Don't know if  
+
menu instead of just giving  
 +
a<font color="lightgray">n</font> ''"no os choices here"'' display. Don't know if  
 
this is an error I made, or a bug in the stuff MS ships. "CMDCONS" seems  
 
this is an error I made, or a bug in the stuff MS ships. "CMDCONS" seems  
 
to indicate that it may be possible to boot the rescue console off RIS but  
 
to indicate that it may be possible to boot the rescue console off RIS but  
 
I didn't find anything useful on the MS Knowledgebase until now.
 
I didn't find anything useful on the MS Knowledgebase until now.
<pre style="overflow:auto; width:auto;">
+
{|
 +
|
 +
<pre>
 
--- tools.osc      Thu Mar 27 21:04:42 2003
 
--- tools.osc      Thu Mar 27 21:04:42 2003
 
+++ tools.osc.modified    Thu Mar 27 21:00:46 2003
 
+++ tools.osc.modified    Thu Mar 27 21:00:46 2003
Line 80: Line 114:
 
------ pxelinux.cfg/default ------
 
------ pxelinux.cfg/default ------
 
DEFAULT bootnet
 
DEFAULT bootnet
prompt 1
+
PROMPT 1
display netboot.msg
+
DISPLAY netboot.msg
timeout 100
+
TIMEOUT 100
  
 
LABEL bootnet
 
LABEL bootnet
Line 93: Line 127:
 
------ pxelinux.cfg/default ------
 
------ pxelinux.cfg/default ------
 
</pre>
 
</pre>
 +
|}
 
Ciao Chris
 
Ciao Chris
  

Latest revision as of 16:44, 22 December 2020


See also

RIS and PXELINUX


Christian "Dr. Disk" Hechelmann writes the following about using PXELINUX in conjunction with the Windows Remote Install System Services:


Hi,

I'm in the process of creating a remote install/boot environment at the company I work and choose PXELINUX for the Linux part. We use a mixed environment of W2K/Linux Servers and W2K/XP Clients. In the PXELINUX FAQ you write (based on Eric Cook's report), not to configure RIS with the GUI for "you end up with the MS PXE stuff, which is ugly to get rid of". Well, PXELINUX just works great on a fully configured RIS (And thereby keeping nosy co-workers from booting into Linux via network and wiping the local machine, since you need to login to the RIS first with the right credentials to do anything).

When you use the GUI Tools to set up RIS on the Server, the MS TFTP Server gets the directory you specify as the remoteinstall share as its root.

For example when you set up an RIS on RISSERV and specify D:\RemoteInstall\ as the server root you end up with this:

  • The share \\RISSERV\REMINST pointing to D:\RemoteInstall\
  • The tftproot being D:\RemoteInstall\
  • having the usual directory tree below that
    ...\Setup\<language>\{Images,tools}\whatever\<arch>\templates


I just gave it a try and did the following:

  1. Made Setup\German\Tools\PXELinux\i386\templates\ and
    \Setup\German\Tools\PXELinux\i386\templates\pxelinux.cfg\
    (The latter since I didn't want to mess with DHCP just now)
  2. Copied pxelinux.0 to
    Setup\German\Tools\PXELinux\i386\templates\
  3. Put a pxelinux.sif in the templates directory
  4. Put a default config in the pxelinux.cfg dir
  5. Put the message files, kernel and initrd images in the templates directory
  6. Let a PXE client (Intel EEPro 100+ with BA 4.1.09) try what happens.



Well, it works. PXELINUX happily boots of the RIS server, gets Setup\German\Tools\PXELinux\i386\templates\ as pathprefix and fetches its config, the kernel and initrd images from there and starts up the kernel.

I guess that one only needs to send the pxelinux.* options via DHCP if one would hit the 63 character filename limit or one needs/wants to specify special options for a single machine or subnet.

I had to modify the file \OSChooser\German\tools.osc though, to have the Client Installation Wizard actually display the "Maintenance and Tools" menu instead of just giving an "no os choices here" display. Don't know if this is an error I made, or a bug in the stuff MS ships. "CMDCONS" seems to indicate that it may be possible to boot the rescue console off RIS but I didn't find anything useful on the MS Knowledgebase until now.

--- tools.osc      Thu Mar 27 21:04:42 2003
+++ tools.osc.modified     Thu Mar 27 21:00:46 2003
@@ -2,7 +2,7 @@
 <META KEY=F3 ACTION="REBOOT">
 <META KEY=F1 HREF="TOOLSHLP">
 <META KEY=ESC HREF="CHOICE">
-<META SERVER ACTION="ENUM TOOLS CMDCONS">
+<META SERVER ACTION="ENUM TOOLS">
 <TITLE>  Client Installation Wizard Tools</TITLE>
 <FOOTER>  [ENTER] continue     [ESC] go back     [F1] help     [F3] restart computer</FOOTER>
 <BODY left=5 right=75>

------ pxelinux.sif ------
[OSChooser]
Description = "Boot RH73 Networkinstaller"
Help = "This option runs the RedHat 7.3 netwoek installer."
LaunchFile = "Setup\German\Tools\pxelinux\i386\templates\pxelinux.0"
ImageType = Flat
Version="1.01"
------ pxelinux.sif ------

------ pxelinux.cfg/default ------
DEFAULT bootnet
PROMPT 1
DISPLAY netboot.msg
TIMEOUT 100

LABEL bootnet
  KERNEL rh-bootkrnl73
  APPEND initrd=rh-bootnet.img

LABEL bootnet-all
  KERNEL rh-bootkrnl73
  APPEND initrd=rh-bootnet-all.img
------ pxelinux.cfg/default ------

Ciao Chris

--