<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Help with RIS + Unattended Installation Files in Windows Server 2003</title>
    <link>https://community.hpe.com/t5/windows-server-2003/help-with-ris-unattended-installation-files/m-p/3230313#M541</link>
    <description>Hello everyone,&lt;BR /&gt;&lt;BR /&gt;I am having issues with trying to create a custom unattended installation file for our RIS image.&lt;BR /&gt;&lt;BR /&gt;Our network consists of three servers:  a Windows 2000 Server computer as our DC, a Windows 2003 Server computer that runs Exchange and RIS, and a Windows 2003 Server that holds all the user data files.&lt;BR /&gt;&lt;BR /&gt;From what I have read the RIS server should be showing up in the Active Directory as such and from it's properties I should be able to associate unattended installation files with specific images.  Problem is that it doesn't show up as a RIS server, it just shows up as a normal computer in the Active Directory.&lt;BR /&gt;&lt;BR /&gt;RIS works fine though, but with the default unattended installation file, which is unacceptable.&lt;BR /&gt;&lt;BR /&gt;Any and all help in this matter is greatly appreciated, thanks :-).&lt;BR /&gt;&lt;BR /&gt;Richard.</description>
    <pubDate>Thu, 25 Mar 2004 16:05:57 GMT</pubDate>
    <dc:creator>Ricardo Zapato</dc:creator>
    <dc:date>2004-03-25T16:05:57Z</dc:date>
    <item>
      <title>Help with RIS + Unattended Installation Files</title>
      <link>https://community.hpe.com/t5/windows-server-2003/help-with-ris-unattended-installation-files/m-p/3230313#M541</link>
      <description>Hello everyone,&lt;BR /&gt;&lt;BR /&gt;I am having issues with trying to create a custom unattended installation file for our RIS image.&lt;BR /&gt;&lt;BR /&gt;Our network consists of three servers:  a Windows 2000 Server computer as our DC, a Windows 2003 Server computer that runs Exchange and RIS, and a Windows 2003 Server that holds all the user data files.&lt;BR /&gt;&lt;BR /&gt;From what I have read the RIS server should be showing up in the Active Directory as such and from it's properties I should be able to associate unattended installation files with specific images.  Problem is that it doesn't show up as a RIS server, it just shows up as a normal computer in the Active Directory.&lt;BR /&gt;&lt;BR /&gt;RIS works fine though, but with the default unattended installation file, which is unacceptable.&lt;BR /&gt;&lt;BR /&gt;Any and all help in this matter is greatly appreciated, thanks :-).&lt;BR /&gt;&lt;BR /&gt;Richard.</description>
      <pubDate>Thu, 25 Mar 2004 16:05:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/help-with-ris-unattended-installation-files/m-p/3230313#M541</guid>
      <dc:creator>Ricardo Zapato</dc:creator>
      <dc:date>2004-03-25T16:05:57Z</dc:date>
    </item>
    <item>
      <title>Re: Help with RIS + Unattended Installation Files</title>
      <link>https://community.hpe.com/t5/windows-server-2003/help-with-ris-unattended-installation-files/m-p/3230314#M542</link>
      <description>create your RIS unattend script with the setup manager from the deployment tools.  Choose to create script for Remote install, input your details you want for every machine then save it.  You should now have a file called remboot.sif, it is very similar to the unattend.txt file, so you can enter the same fields.  &lt;BR /&gt;&lt;BR /&gt;put this file into your RIS distribution folder .../i386/templates/  you can leave the default script alone.</description>
      <pubDate>Mon, 12 Jul 2004 10:28:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/windows-server-2003/help-with-ris-unattended-installation-files/m-p/3230314#M542</guid>
      <dc:creator>wien lam</dc:creator>
      <dc:date>2004-07-12T10:28:16Z</dc:date>
    </item>
  </channel>
</rss>

