Testking-TESTINSIDE-FREE EBOOK-FREE VIDEO ENTRENAMIENTO LIBRE DE TODOS

El 2000 Microsoft ® Windows ® Remote característica Instalación de sistema operativo, basado en los Servicios de instalación remota (RIS), la tecnología, proporciona a los administradores la capacidad de desplegar un sistema operativo en toda la empresa, sin necesidad de visitar físicamente cada equipo cliente.

Una de las funciones más difíciles y costosas realizadas por el personal de TI de hoy es el despliegue de un nuevo sistema operativo en equipos cliente. La función de Instalación de SO remoto PXE utiliza la nueva tecnología basada en el arranque remoto para ayudar al personal de TI con la implementación de Windows 2000 Professional de forma remota, reduciendo así los gastos de soporte de TI para lograr nuevos ordenadores en línea, y en la reinstalación de sistemas operativos en el campo.

Prefacio

Remota del sistema operativo (OS) de instalación y tecnologías de gestión de IntelliMirror ™ son cambios importantes y la gestión de configuración de las funciones incluidas en el sistema 2000 Microsoft ® Windows ®. Instalación remota del sistema operativo permite a los administradores de sistemas a utilizar el nuevo Pre-boot Execution Environment (PXE)-remota basada en tecnología de arranque, y basada en servidor para instalar el software de copias locales del sistema operativo Windows 2000 Professional en equipos de toda la empresa. Después de que Windows 2000 está en funcionamiento en un equipo, los administradores de red, utilizando la tecnología de IntelliMirror, puede proporcionar la política de gestión basada en los usuarios de Windows '2000-basado en computadoras de escritorio, incluyendo los datos, configuraciones y software de aplicación.

La siguiente tabla pone de manifiesto el cambio de configuración de Windows 2000 y características de gestión y los beneficios, así como las tecnologías subyacentes que soportan estas características.

Introducción

Una de las funciones más difíciles y costosas realizadas por el personal de TI de hoy es el despliegue de un sistema operativo (OS) para los equipos cliente nuevo o existente. En la actualidad, las organizaciones gastan una gran cantidad de tiempo y planificación de gastos, el diseño y el despliegue de la última versión del sistema operativo en toda la organización. A menudo este proceso se realiza manualmente, lo que requiere un servicio de asistencia profesional para visitar físicamente cada equipo.

Servicios de instalación remota (RIS), un componente opcional del sistema operativo Windows 2000 Server, funciona con Windows 2000 otras tecnologías para implementar la función de Instalación de SO a distancia, ofreciendo a las empresas con la capacidad de instalar una copia del sistema operativo Windows 2000 Professional en los equipos de apoyo en toda la empresa. Ahora, un administrador puede lanzar una nueva versión del sistema operativo a cientos, incluso miles de clientes en un tiempo, y hacerlo desde una ubicación remota.

Los equipos que se PC98-buque, conforme con un arranque remoto PXE ROM, que es necesario para utilizar la función de Instalación de SO remoto. (PC98 se refiere a la guía anual para desarrolladores de hardware co-escrito por Microsoft con Intel, incluyendo las contribuciones de Compaq y otros fabricantes de hardware de la industria. PC98 tiene como objetivo proporcionar estándares para el desarrollo de hardware que la plataforma PC y permitirá avanzar Microsoft para incluir funciones avanzadas, como RIS, en la plataforma Windows.) Para equipos de la organización que no contengan un PXE basado en la ROM de arranque remoto, Microsoft proporciona al administrador con una herramienta para crear un disco de arranque remoto para RIS. El disco de inicio RIS remoto se puede usar con una variedad de PCI apoyo basado en tarjetas adaptadoras de red. El PC de red a un versión reducida de un ordenador personal sin un disquete o CD-ROM-será uno de los equipos cliente primero en tomar ventaja de los RIS. Debido a su falta de unidad externa de disco, el PC Net requerirá el uso de la función de Instalación de SO a distancia para la instalación del sistema operativo de estación de trabajo.

Vista general de la tecnología y terminología

Esta sección proporciona una visión general de los Servicios de instalación remota (RIS) de la arquitectura y otros componentes y servicios de Windows 2000 que se requieren para aprovechar la característica de la instalación del SO remoto. Esta sección también describe los componentes de cliente y servicios que se requieren para la aplicación de instalación remota en el sistema operativo de su organización.

Instalación remota del sistema operativo Vista general

La Figura 1 ilustra los servicios y componentes que conforman la función de Instalación de SO remoto.

Instalación remota del sistema operativo utiliza algunos de los servicios existentes, que ya puede ser desplegado y en uso dentro de su organización, y agrega algunos servicios adicionales que pueden o no estar familiarizados. Windows 2000 Server con el servicio de directorio Active Directory ™, una actualización de Dynamic Host Configuration Protocol (DHCP), y una versión compatible de Dynamic Domain Name Server (DDNS) que es requerido por el Active Directory. Cuando se instalan Servicios de instalación remota, estos servicios adicionales se agregan al servidor:

• Capa de negociación de información de inicio (BINL)-El servicio BINL se agrega durante el proceso de instalación de RIS. El servicio BINL se encarga de responder equipo cliente solicita servicios de red, consulta de Active Directory en nombre de la computadora del cliente, así como garantizar que la política correcta y opciones de configuración se aplica al equipo cliente durante la instalación del sistema operativo.
• Trivial File Transfer Protocol Daemon (TFTPD)-Este servicio del lado del servidor TFTP es responsable por haber acogido las solicitudes de descarga de archivos específicos realizados por el equipo cliente. El servicio Este ejecutable se utiliza para descargar el asistente de instalación de clientes (CIW) y todos los cuadros de diálogo de cliente que figura en el CIW para una sesión determinada.
• Almacenamiento de instancia única (SIS)-Single Instance Store es el servicio responsable de la reducción de los requisitos de espacio en disco en los volúmenes utilizados para el almacenamiento de imágenes de instalación de RIS. Al instalar RIS como un componente opcional, se le pide para una unidad y el directorio donde desea instalar RIS: Este es el volumen RIS. El servicio de SIS se une con el volumen de RIS, y los monitores de que el volumen en busca de los archivos duplicados que se colocan en ese volumen. Si se encuentran los archivos duplicados, SIS crea un vínculo con los duplicados, reduciendo así el espacio en disco necesario.

Instalación remota del sistema operativo utiliza el nuevo Pre-boot Execution Environment (PXE) DHCP basado en la tecnología de arranque remoto para iniciar la instalación de un sistema operativo desde un origen remoto en un disco duro del cliente. El origen remoto de un servidor que soporte Servicios de instalación remota (RIS)-proporciona el equivalente de una red basada en CD de instalación de Windows 2000 Professional o un pre-configurado de preparación de instalación remota (RIPrep) imagen de escritorio. El sistema operativo Windows 2000 Professional es actualmente la opción de instalación sólo con el apoyo de Servicios de instalación remota.

• Basada en CD de instalación, la opción CD-basada es similar a la creación de una estación de trabajo directamente desde el disco compacto de Windows 2000 Professional, sin embargo, los archivos de origen residen en toda la red disponible en los servidores RIS.
• Formato de imagen RIPrep-La opción de imágenes RIPrep permite a un administrador de red para clonar una configuración estándar de escritorio corporativo, con las configuraciones del sistema operativo, las personalizaciones de escritorio y las aplicaciones instaladas localmente. Después de la primera instalación y configuración del sistema operativo Windows 2000 Professional, sus servicios, y cualquier aplicación estándar en un equipo, el administrador de red ejecuta un asistente que prepara la imagen de instalación, y se replica a un servidor de RIS disponible en la red para la instalación en otro clientes.

Una vez que las imágenes se han publicado en el servidor RIS (s), los usuarios finales disponen de arranque remoto PXE basado habilitado (o el disco de arranque compatible) Los equipos cliente puede solicitar para instalar las imágenes desde cualquier servidor de RIS disponible en la red. El hecho de que el usuario puede instalar el sistema operativo sin la ayuda del administrador: el administrador es libre para completar otras tareas que requieran su atención, lo que ahorra tiempo y gastos que normalmente se asocian con las instalaciones del sistema operativo.

Cómo funciona el arranque remoto PXE Tecnología

Una nueva forma de tecnología de arranque remoto se ha creado dentro de la industria de la computación. La nueva tecnología de arranque remoto, Pre-boot Execution Environment (PXE), proporciona a las empresas la capacidad para utilizar su red TCP / IP de la infraestructura de red con el Dynamic Host Configuration Protocol (DHCP) para descubrir servidores de instalación remota de la red. Net PC/PC98-compliant sistemas y ordenadores equipados con tarjetas de interfaz de red (NIC) soportada por el disco de inicio RIS remoto puede tomar ventaja de la tecnología de inicio remoto incluido en el sistema operativo Windows 2000.

Cuando un PXE equipo cliente está encendido, el PXE basado en ROM o solicitudes de inicio RIS remoto de disco de una dirección IP de un servidor DHCP mediante el proceso normal de descubrimiento de DHCP. Como parte de la primera solicitud de descubrimiento de DHCP, el equipo cliente se identifica como PXE ser habilitado, lo que indica a los servidores de instalación remota de la red que está mirando para ser reparado. Cualquier servidor de RIS disponible en la red puede responder mediante el suministro al cliente con su dirección IP y el nombre de un archivo de inicio el cliente debe solicitar si ese cliente quiere servicio desde ese servidor.

A continuación se muestra un diagrama, figura 2, que describe el paso a paso el proceso de la ROM de arranque remoto PXE pasa a través de la red en cada solicitud de inicio del servicio.

Después del procedimiento alcanza el paso 7, la experiencia del lado del cliente será diferente, dependiendo del proveedor del servidor de instalación remota que está respondiendo a la solicitud del cliente para el servicio. La sección siguiente detalla la aplicación de instalación remota sistema operativo que se incluye en el sistema operativo Windows 2000 Server.

¿Cómo la instalación del SO remoto proceso funciona

Una representación gráfica de cómo funciona el proceso de instalación remota del sistema operativo se encuentra en la Figura 3. Cada paso del proceso se define en detalle a continuación de la ilustración

El proceso de ponerse en contacto con un servidor de RIS y seleccionar una imagen de sistema operativo se realiza en unos pocos pasos. Los siguientes pasos detalle la secuencia de acontecimientos que ocurren cuando un PXE equipo cliente se inicia en la red, y es atendida por un servidor de RIS.

Para realizar una instalación remota del sistema operativo

1. Un PXE cliente conectado a la red se inicia, y durante el encendido, el equipo inicia una solicitud de servicio de red. Como parte de la solicitud de servicio de red, un paquete de descubrimiento DHCP se envía a la red solicitando una dirección IP desde el servidor más cercano de DHCP, la dirección IP de un servidor de RIS disponible, y como parte de dicha solicitud, el cliente envía el Identificador único global (GUID). (El GUID está presente en los equipos cliente que PC98-o PC Net-denuncia y se encuentra en el BIOS del sistema de la computadora.). El servidor DHCP responde a la solicitud y se proporciona una dirección IP al cliente. Cualquier servidor de RIS disponible puede responder con su dirección IP y el nombre del archivo de arranque el cliente debe solicitar si el cliente selecciona que el servidor RIS para el servicio. El usuario se le pide que presione la tecla de función, F12, para iniciar el servicio de ese servidor de RIS.
2. El servidor RIS (utilizando el servicio BINL) debe comprobar en Active Directory para la existencia de un pre-posicionados cuenta de equipo cliente que coincide con este equipo cliente. BINL controles de la existencia de un equipo cliente mediante la consulta de Active Directory de un equipo cliente que coincide con el GUID envió en el paso 1.
3. Una vez que RIS ha comprobado la existencia de una cuenta de equipo cliente, el asistente de instalación de clientes (CIW) se descarga en el equipo cliente, y pide al usuario que inicie sesión en la red.
4. Una vez que el usuario inicia sesión, RIS controles Active Directory para obtener una cuenta de usuario correspondiente, la verificación de la contraseña. RIS comprueba entonces la específica configuración de Directiva de grupo de los RIS para saber qué opciones de instalación, el usuario debe tener acceso. RIS también comprueba que las imágenes del sistema operativo del usuario específico debe ser ofrecido, y el asistente de instalación de clientes hace que las opciones disponibles para el cliente.
5. Si el usuario sólo se permite una opción de instalación simple y la elección de sistema operativo, el usuario no se le pide que seleccione algo. Por el contrario, el asistente de instalación del cliente advierte al usuario de que la instalación se formatear su disco duro y la información previamente almacenada se borrará, y luego le pide al usuario para iniciar la instalación remota del sistema operativo.
6. Una vez que el usuario confirma la configuración de la instalación en la pantalla de resumen, la instalación del sistema operativo. En este punto, si una cuenta de equipo cliente no estaba presente en Active Directory, el servicio BINL crea la cuenta de equipo cliente, lo que proporciona automáticamente un nombre para el equipo. El sistema operativo está instalado localmente como una instalación desatendida, lo que significa que el usuario final no se ofrece todas las opciones de instalación durante la fase de instalación del sistema operativo.

El proceso de instalación de sistema operativo remoto es directa desde una perspectiva del usuario final. El administrador puede guiar al usuario a través de una correcta instalación del sistema operativo de pre-determinar qué opciones de instalación, en su caso, un usuario final tiene acceso. El administrador también puede restringir el que la imagen del sistema operativo o las imágenes que un usuario tiene acceso a, asegurando así el correcto funcionamiento del sistema de tipo de instalación se ofrece al usuario para una instalación exitosa.

Servicios de instalación remota de componentes

La característica de Windows 2000 remoto de instalación de sistema operativo simplifica la tarea de instalar un sistema operativo, proporcionando un mecanismo para que los ordenadores conectarse a un servidor de red cuando se comenzó inicialmente, y al permitir que el servidor de conducir una instalación local de Windows 2000 Professional. Hay varios componentes que conforman el Servicios de instalación remota (RIS), la tecnología que soporta la función de Instalación de SO remoto. Esta sección explica los diferentes componentes que el administrador o los usos profesionales de TI a instalar, configurar y poner en práctica RIS dentro de su organización con el fin de implementar el sistema operativo Windows 2000 Professional.

Hay cinco componentes principales que conforman RIS:

• Servicios de instalación remota de instalación (Risetup.exe).
• Administración de Servicios de instalación remota.
• El asistente de instalación de cliente (OSChooser.exe).
• Asistente para preparación de instalación remota (Riprep.exe).
• Disco de inicio de instalación remota (RBFG.exe).

Nota: Para obtener información adicional acerca de la instalación, configuración y aplicación de instalación remota OS, consulte la instalación remota de Windows 2000 OS paseo por enumerados en la sección Para obtener más información de este documento.

Servicios de instalación remota de instalación

RIS está instalado uno de dos maneras, y requiere un proceso de dos etapas de instalación. RIS es un componente opcional del sistema operativo Windows 2000 Server, y puede ser instalado durante la instalación de Windows 2000 Server, o después de la instalación mediante la opción Agregar o quitar programas del Panel de control.

La primera fase de instalación se produce cuando RIS es seleccionado como un componente durante la instalación de Windows 2000 Server o después de la instalación del servidor mediante la opción Agregar o quitar programas. Aparece el asistente de componentes de Windows Servicios de instalación remota como un componente opcional para la instalación, y se ilustra en la Figura 4.

Después de Servicios de instalación remota está seleccionada como un componente opcional, la primera etapa de las copias de instalación de RIS los archivos necesarios para la unidad de disco duro en el servidor. Después de la configuración del servidor se ha completado, el administrador se le pide que apagar y reiniciar el servidor antes de instalar Servicios de instalación remota.

Para instalar Servicios de instalación remota

1. En el menú Inicio, seleccione Programas y, a continuación, Herramientas administrativas y, a continuación, haga clic en Configurar su servidor.
2. En el cuadro de diálogo para configurar su servidor, haga clic en Finalizar instalación.
3. En los Servicios de instalación remota Configurar el cuadro de diálogo, haga clic en Configurar para iniciar la instalación de los Servicios de instalación remota asistente.
4. En los Servicios de instalación remota Asistente para la instalación cuadro de diálogo, haga clic en Siguiente.

Servicios de instalación remota asistente de instalación le pide al administrador para obtener información acerca de la configuración específica utilizada en la instalación de RIS. El asistente le pide al administrador para proporcionar los siguientes elementos:

• Un lugar en el servidor en el árbol de directorios de RIS se creará.
• Si el servidor RIS debe reparar los equipos cliente después de completar la instalación.
• La ubicación del CD de Windows 2000 Professional, o una ubicación en la red que contiene los archivos de instalación.
• Una descripción y un texto de ayuda asociados que describe la imagen del sistema operativo para los usuarios del asistente de instalación de clientes.

Después de la instalación de Servicios de instalación remota asistente, dependiendo de la configuración elegida, el servidor RIS o servicios de los equipos cliente, o se detiene mientras el administrador configura los ajustes avanzados de la administración con la configuración de RIS. La sección siguiente describe las opciones de configuración disponibles para el administrador de RIS.

Servicios de instalación remota Administración y Configuración de Opciones de

De forma predeterminada, un servidor de RIS no está configurado para servicio a los equipos cliente inmediatamente después de la instalación de RIS se ha completado. Si el administrador desea configurar el servidor para servicio a los equipos cliente en la realización del programa de instalación de RIS, el administrador puede aceptar simplemente los ajustes de configuración, y comenzar ofreciendo a los usuarios imágenes de instalación del sistema operativo sin cambiar una opción de configuración.

RIS proporciona al administrador con una variedad de opciones y ajustes de configuración. Esta configuración proporciona flexibilidad con respecto a situaciones específicas, tales como el tipo de equipo automático de nombres de la política de usar, que las cuentas de cliente de Active contenedor Directory equipo se crean en, y que las imágenes del sistema operativo El usuario final tiene acceso. Para obtener más detalles acerca de las opciones de configuración individuales, consulte el documento de tutorial de RIS en la sección Para más información, o comprobar el Servicios de instalación remota de Ayuda en el CD de Windows 2000 Server, que también está disponible en el sitio de Windows Server 2000 Web (http:/ / www.microsoft.com/technet/prodtechnol/windows2000serv/default.mspx).

Existen cuatro métodos utilizados para configurar las opciones disponibles de RIS.

El primer método consiste en especificar qué servidores RIS están autorizados a circular por la red. Esta opción evita que no autorizado (a menudo denominada Rogue), servidores de RIS, garantizando sólo a los servidores RIS autorizada por los administradores pueden atender a los clientes. Si se intenta iniciar un servidor de RIS no autorizada en la red, se cierran automáticamente y por lo tanto incapaz de servicio a los equipos cliente. Un servidor RIS debe ser autorizada antes de que se puede dar servicio a los equipos cliente.

El segundo método utiliza el Active Directory Usuarios y equipos de complemento para establecer las propiedades en los distintos servidores de RIS que el control de cómo el servidor presta servicios de instalación remota para clientes que lo solicitan. Este complemento está disponible, vaya al menú Inicio, seleccione Programas, Herramientas administrativas y, a continuación, haga clic en Active Directory de usuarios y equipos .. El complemento que aparece se ilustra en la Figura 5. Los administradores que deseen administrar de forma remota los servidores de las estaciones de trabajo Windows 2000 Professional pueden acceder a las herramientas administrativas de instalar el paquete de herramientas de administrador se encuentra en el CD de Windows 2000 Server.

Nota: Al utilizar herramientas de administrador en un sistema que no sea el servidor de RIS, el administrador no puede añadir más imágenes del sistema operativo o verificar la integridad del servidor de RIS. Todas las otras opciones de configuración disponibles.

Después de que el servidor de RIS está seleccionado, haga clic derecho para abrir el cuadro de diálogo Propiedades y haga clic en la ficha Instalación remota para acceder a la configuración de las opciones de servidor de RIS. El cuadro de diálogo Propiedades se ilustra en la Figura 6.

La siguiente lista describe las opciones de configuración importantes disponibles en el cuadro de diálogo de Propiedades para el servidor de RIS

Co-existencia de los servidores de instalación remota de múltiples proveedores: Para las empresas que han de arranque remoto de servidores de la instalación de otros fabricantes que operan en la misma red física, los servidores de RIS se puede configurar para responder únicamente a las solicitudes de servicio de los clientes que han sido ensayados previamente en Active Directory. Cuando se establece a ignorar las solicitudes de arranque de clientes desconocidos, los servidores RIS pueden ser introducidos en una red sin interferir con la pre-existente de instalación remota de servidores que utilizan el mismo protocolo de inicio remoto.

• Lo que los clientes del servidor RIS debe responder a estas opciones permiten al administrador especificar si el servidor RIS debe responder a los equipos cliente, y en caso afirmativo, si deben responder cuando no hay conocimiento previo del equipo cliente en Active Directory (el cliente no ha sido ensayados previamente). Ensayo previo permite a los clientes para la co-existencia con los servidores de instalación remota de varios proveedores en la misma red física, equilibrio de carga opcional, y el aumento de la seguridad sobre qué sistemas se puede realizar una instalación del sistema operativo remoto. La configuración por defecto también se puede cambiar durante la instalación del asistente de configuración remota de Servicios (Risetup.exe).
  

  Escenario	Ubicación	Predeterminado
  Responder a equipos cliente que solicitan servicio	Remote ficha Instalar	Personas de movilidad reducida
  No responder a equipos cliente desconocidos	Remote ficha Instalar	Personas de movilidad reducida

• Equipo automático de cliente formato de nombre: Cuando el nombre del equipo cliente se genera automáticamente, esta opción determina el nombre debe ser formateado. Varios regímenes de nombres están disponibles, incluyendo la posibilidad de utilizar una costumbre nombrar formato específico a la organización. Esta opción ofrece una flexibilidad en el nombramiento de nuevos equipos cliente durante la instalación del sistema operativo, sin la necesidad de que el usuario final o la participación del administrador.
  

  Escenario	Ubicación	Predeterminado
  El equipo cliente formato de nombre de	Configuración avanzada, los nuevos clientes ficha	Nombre de usuario

• Ubicación predeterminada de Active Directory para la creación de nuevas cuentas de equipo del cliente: esta opción permite al administrador seleccionar una ubicación predeterminada de Active Directory en el que todos instalado de forma remota las cuentas de equipo cliente, se creará durante la instalación del sistema operativo. El administrador puede elegir cualquiera de los contenedores por defecto o unidades organizativas (OU), o crear una nueva unidad organizativa específica a RIS-instalado los equipos cliente.
  

  Escenario	Ubicación	Predeterminado
  Consideración la ubicación del cliente	Configuración avanzada, los nuevos clientes ficha	Contenedor Equipos

• Disponible imágenes del sistema operativo: esta opción permite al administrador para añadir nuevas versiones del sistema operativo o imágenes RIPrep a los actuales servidores RIS para la instalación de los clientes. Además, los administradores pueden asociar una gran variedad de plantillas de instalación desatendida imágenes basadas en CD de instalación, proporcionando así una mayor flexibilidad en las opciones de instalación. Por ejemplo, un administrador puede optar por añadir sólo un único Windows 2000 Professional imagen basada en CD en el servidor RIS, pero puede asociar varias secuencias de comandos diferentes instalaciones desatendidas archivos, todos apuntando a la unidad de CD única imagen.
  

  Escenario	Ubicación	Predeterminado
  Lista de imagen del sistema operativo	Configuración avanzada, ficha Imágenes	Basada en CD de Windows 2000 Professional imagen

• De terceros ISV herramientas de mantenimiento y solución de problemas de personal presta apoyo administrativo, y si los usuarios finales aplicable, el acceso a la pre-mantenimiento del sistema operativo y herramientas de solución de problemas de los proveedores de terceros. Estas herramientas pueden ser utilizadas para mantener y solucionar problemas de los equipos cliente antes de cargar o instalar el sistema operativo. Por ejemplo, el BIOS del sistema antes de la instalación del sistema operativo. Otros ejemplos son los escáneres de virus de la memoria, las herramientas informáticas de diagnóstico e inventario basado en los servicios públicos.
  

  Escenario	Ubicación	Predeterminado
  Listado de Herramientas	Configuración avanzada, pestaña Herramientas	No hay herramientas instaladas

  Si las mejores prácticas de instalación automática es la opción de instalación sólo está disponible para un usuario (como está por defecto), el menú de opciones de instalación no se mostrará, reduciendo la probabilidad de error de usuario final o confusión.

  El tercer método implica el uso de la configuración de Directiva de grupo para especificar las opciones de instalación se presentan a los diferentes grupos de usuarios durante el asistente de instalación de clientes (CIW). Por ejemplo, puede no ser apropiado para los usuarios para acceder a la opción de instalación personalizada o las herramientas disponibles en el menú de mantenimiento y solución de problemas. Por el contrario, un administrador puede permitir a los usuarios normales acceso a la única opción de configuración automática, y restringir el acceso a todas las otras opciones para ayudar a los administradores o personal de caja.

  Escenario	Ubicación	Predeterminado
  Las opciones de instalación CIW	Directiva de dominio predeterminada-Configuración de usuario-Configuración de Windows-Servicio de instalación remota	Instalación automática sólo para todos los usuarios del dominio

  De mejores prácticas para automatizar la imagen del sistema operativo para ser instalado por algunos usuarios, garantizar que los usuarios tengan acceso a la única imagen que se debe instalar. Cuando sólo una única imagen disponible, la pantalla de selección de la imagen no se muestra y la imagen disponible solo se selecciona automáticamente.

  El método de configuración de la cuarta y última utiliza descriptores de seguridad, o las listas de control de acceso discrecional (DACL) para especificar los usuarios o grupo de usuarios deberían tener acceso a las imágenes del sistema operativo disponible en el servidor RIS. Los administradores pueden utilizar este método para guiar a los usuarios a través de la selección de la instalación del sistema operativo sin supervisión adecuada para su papel dentro de la empresa. De forma predeterminada, cuando una imagen de sistema operativo se agrega a un servidor de RIS, la imagen estará disponible para todos los usuarios atendidos por el servidor de RIS.

  Escenario	Ubicación	Predeterminado
  La disponibilidad de imagen del sistema operativo a los usuarios de CIW	En DACL. Sif archivo en la carpeta de plantillas de imagen	Disponible para todos los usuarios

  Mejores prácticas para reducir el trabajo que supone el mantenimiento de la seguridad aplicada a las imágenes, siempre que sea posible establecer la seguridad en la carpeta de plantillas de la imagen y no en el individuo. Sif mismas, y el uso de grupos de usuarios para otorgar y restringir el acceso en lugar de usuarios individuales .

  Después de las opciones necesarias de configuración de RIS se han fijado, el administrador está listo para el servicio para inicio remoto o en equipos cliente compatibles. Una visión general del asistente para instalación de clientes (CIW) se presenta en la siguiente sección, así como una descripción de las opciones de instalación disponibles que pueden ser ofrecidos a los usuarios finales. Como se señaló anteriormente, a fin de solicitar el servicio desde un servidor RIS, los equipos cliente o bien puede utilizar una PXE basado en la ROM de arranque remoto, o una tarjeta de red que es compatible con el disco de inicio RIS remoto.

Asistente para la instalación del cliente

Los caracteres extendidos en el CIW: Debido a que el asistente se ejecuta en un entorno de ejecución de pre-arranque, no hay soporte para caracteres extendidos en el texto o bien la muestra o los campos de entrada (nombre de usuario, contraseña, dominio o todos los parámetros personalizados de entrada). La consideración cuidadosa debe tomarse antes de la creación de usuario o nombre de dominio que contienen caracteres extendidos, ya que no se podrán usar con RIS.

Once the client computer establishes a connection with the RIS server, the user is prompted to initiate a network service boot by pressing the F12 function key. The Client Installation wizard (CIW), illustrated in Figure 7, is then automatically downloaded to the client computer. The user is prompted to enter their user name, password, and domain. After authenticating the user in Active Directory, the CIW optionally provides the end user or IT administrator with the ability to select from a menu of installation options and operating system images to control how and which operating system image will be installed. If the user running the CIW has only been granted access to the Automatic installation option and a single operating system image, neither menu is displayed, and the user proceeds directly to the confirmation and summary screens.

The following installation options are included in the Client Installation wizard. Automatic setup is available by default. RIS uses Group Policy settings to allow access to the automatic setup option only, and to restrict all users and administrators from the rest of the installation options described below.

To control the setup options displayed to users in the CIW, use Group Policy as described in the “Administration and Configuration Options” section.

• Automatic Setup —This option provides the easiest operating system installation path. It allows the user to choose which operating system to install, but does not prompt the user for specific configuration settings. If only one operating system option is offered, the user is not prompted, and an unattended installation of the operating system image starts automatically.
• Custom Setup —This option allows the user running the CIW to override the automatic computer naming process, as well as the default location within the Active Directory where client computer accounts will be created. Help desk or administrators can use this option to pre-install a client computer for someone else within the enterprise.
• Restart a Previous Setup Attempt —If selected, this option automatically restarts the operating system installation process when an installation attempt fails before completion. This option does not copy files from where the previous installation attempt failed, however the user is not required to answer any questions answered within the CIW from the previous setup attempt.
• Maintenance and Troubleshooting —This option provides access to third-party maintenance and troubleshooting tools that can be used before operating system installation. Examples of these tools include system flash BIOS updates, computer diagnostic tools, and virus scanning utilities. See the For More Information section for ISV and OEM vendors that provide utilities for use with RIS.

If the user has more than one operating system image available to them for installation, the list of images is displayed for selection. The user is then presented with confirmation and summary screens, after which the installation of the image on the client computer begins immediately.

The screens and text displayed in the CIW can also be customized, and additional screens can be displayed to the user if desired. For example, if users must enter a specific configuration parameter during the CIW, a custom screen can be created and linked to those already displayed. Such parameters can then be passed to the .sif file of the selected operating system installation image. For more information on customizing the CIW screens, see the Windows 2000 Server Resource Kit (available in Microsoft TechNet).

Remote Installation Preparation Wizard

Note: See the “Remote OS Installation Usage Scenarios” section later in this document for details on how to combine the Windows 2000 Group Policy and Software Installation and Maintenance features with Remote OS Installation to create standard desktop images that include applications.

There are two types of operating system images supported by Remote OS Installation: CD-based images and RIPrep images. The CD-based option is similar to setting up a client operating system directly from the Windows 2000 Professional CD, but in this case, the source files reside on an RIS server. However, more companies are beginning to implement a corporate standard desktop policy. This policy requires that users install only approved versions of an operating system and associated applications or application suites. These desktop standards have a variety of names, such as Standard or Common Operating Environments (SOEs or COEs), but all usually involve packaging the operating system, required service packs, a set of applications, and appropriate operating system and application configuration settings into a single, tested, and supported unit.

In order to build and maintain standard desktops, many companies use disk imaging or cloning software that allows an administrator to configure a client computer exactly how he or she wants it, following company standards and software policies, and then make a copy of that image for installation on client computers on the network. Remote OS Installation supports creation and installation of standard desktop images using the RIPrep feature.

One of the biggest limitations in most imaging technologies is the requirement that the destination computer (the computer that will receive the image) contain identical hardware to that of the source computer used to create the image.

An important element of the RIPrep feature is the fact that the destination computer (the computer that installs the image posted to the RIS server) is not required to contain hardware identical to that of the source computer that was used to create the image. RIPrep uses the Plug and Play support in the computer running Windows 2000 Professional to detect differences between the source and the destination computers' hardware during image installation. The exception is that the hardware abstraction layer (HAL) drivers must be the same between the source computer and all destination computers that later install the image. However, in most cases, workstations do not require the unique HAL drivers that servers require. The primary difference in HAL drivers for workstations is whether systems contain Advanced Configuration Power Interface (ACPI) support versus a non-ACPI supported computer. When using RIPrep, you must create and maintain separate installation images for systems that have ACPI or other features that require the use of specific HAL drivers, but other hardware differences, such as video or disk controllers, can be automatically accommodated for hardware compatible with Windows 2000.

Note: If the source computer contains a 1 gigabyte (GB) disk drive and the destination computer contains a 2-GB disk drive, by default RIS will format the destination computers drive as a 2-GB partition in the same file system format as the source computer used to create the image.

The Remote Installation Preparation wizard (RIPrep.exe), which is part of the Remote OS Installation feature, is illustrated in Figure 8. The RIPrep wizard provides the combined ability to prepare an existing Windows 2000 Professional installation for use as an image to be installed on other computers, including any locally installed applications and/or specific configuration settings, and to replicate that image to an available RIS server on the network. The RIPrep feature currently supports replicating a single disk-single partition (C partition only) Windows 2000 Professional installation to an available RIS server. This means that the operating system and all of the applications that make up the standard installation must reside on the C partition prior to running the RIPrep wizard.

Creating the Source Computer

To create the source computer, the administrator first uses the Remote OS Installation feature to remotely install the base Windows 2000 Professional operating system. Once the operating system is installed, the administrator can install applications or application suites including in-house line of business (LOB) applications. The administrator then configures the workstation to adhere to company policies. For example, the administrator may choose to define specific screen colors, set the background bitmap to a company-based logo, remove any games installed by the base operating system, and set Internet Explorer proxy settings.

Configuring the Workstation

When creating RIPrep images, it is important to understand the relationship of user profiles, the changes made to a RIPrep source computer, and the desired result for users that log on to computers that are installed using the RIPrep image. Windows 2000 Logo-compliant applications properly separate user-specific and computer-specific configuration settings and data, and can therefore be installed computer-wide so that they are available to all users of the system. Such applications would also then be available to all users of systems later installed with the resulting RIPrep image. Non-Windows 2000-compliant applications may perform and/or rely on per-user configurations that are specific to the profile of the user actually installing the application prior to running RIPrep (typically a local administrator), rather than to all users of the system. Such configurations remain specific to that user, which may result in the application or configuration setting not being available or not functioning properly for users of computers installed with the RIPrep image. In addition, some non-application configuration changes, such as the wallpaper specified for the user desktop, are by default applied only to the current user's profile, and will not be applied to users of systems installed with the RIPrep image.

Therefore, you must thoroughly test any applications or configuration settings desired for use in a RIPrep image to ensure they will work properly with your organization's implementation of user profiles. To do so, make the change as one user (typically a local administrator of the computer), log off, and log on as a user account that is representative of your organization. If the changes you made are applied to the second user, the changes should also apply to users that log on to systems installed with a RIPrep image that contains the same change. To complete the test, create a RIPrep image, restore it to a different computer, and log on as a different representative user. Verify that the changes are applied and fully functional.

Some configuration settings can be copied directly from the profile they were applied to (the local administrator in the above example) to the All Users profile, such as the desktop wallpaper, some Start menu options, and shortcuts. However, all such changes must be tested carefully to verify that their functionality is not broken by the manual adjustments.

Running the Remote Installation Preparation Wizard

Once the workstation is configured exactly the way the administrator likes, they are ready to run the Remote Installation Preparation wizard.

El asistente de RIPrep comienza por preguntar al administrador de configuraciones específicas relativas a la imagen que están a punto de publicar en el servidor RIS. El administrador se le pide que la imagen debe ser replicado, es que el servidor RIS, y proporcionar un nombre de directorio en el servidor RIS, donde la imagen debe ser replicada. El asistente le pedirá al administrador de proporcionar una descripción y un texto de ayuda asociados a describir el contenido de esta imagen a los usuarios finales de ejecutar el asistente de instalación de clientes. Después de las preguntas imagen inicial han sido contestadas, el asistente configura la estación de trabajo a un estado genérico, de eliminar algo único para la instalación del cliente como el único del equipo identificador de seguridad (SID), nombre del equipo, y cualquier configuración del Registro único para ese sistema. Una vez que la fase de preparación es completa, la imagen se replica automáticamente en el servidor RIS siempre. Después de la imagen se replica en el servidor de RIS, se añade a la lista de opciones disponibles instalación del sistema operativo aparece en el CIW. En este punto, cualquier habilitados para inicio remoto o en equipos cliente compatibles con PXE que utilizan la tecnología basada en el arranque remoto se puede instalar la imagen.

Servicios de instalación remota del disco de arranque

Hay dos tipos de arranque remoto equipos cliente habilitados para:

• Computadoras con PXE basado en ROM de arranque remoto.
• Computadoras con tarjetas de red compatible con el disco de arranque de instalación remota.
  Figura 9: El control remoto del generador disco de arranque

El mando a distancia del disco de arranque del generador de RIS (Rbfg.exe), que se ilustra en la Figura 9, se puede utilizar para crear un disco de arranque para apoyar a los equipos cliente existentes que no tienen un PXE basado en la ROM de arranque remoto, pero que tiene un adaptador de red compatible . Usando el disco de inicio RIS elimina la necesidad de modernizar los equipos cliente existentes con tarjetas de red nuevos que contienen una ROM de inicio PXE con el fin de aprovechar la característica de la instalación del SO remoto. El disco de arranque PXE RIS simula la secuencia de arranque remoto, y soporta tarjetas de red de uso frecuente. El disco de inicio RIS funciona como el proceso de arranque PXE: encender el ordenador, arrancar desde el disco de inicio de RIS, presione F12 para iniciar el inicio de un servicio de red, y el asistente de instalación personalizada (CIW) se descarga y se inicia. Una vez que el asistente se inicia, el resto del proceso RIS es idéntico independientemente de si el cliente se inicia con una ROM de arranque PXE o el disco de inicio RIS remoto. Para la lista completa de las tarjetas de red soportados actualmente por el disco de inicio de RIS, vea el Apéndice B.

Uso de instalación remota OS en una Organización

Las empresas de hoy tienen una variedad de implementación de sistemas operativos y los mecanismos de instalación en su lugar. Esta sección explica cómo se puede utilizar la función de Instalación de SO remoto, además de los mecanismos de implementación para reducir aún más los costos asociados con sistema operativo y despliegue de aplicaciones.

La siguiente lista de escenarios de cubrir la mayoría de estos mecanismos de despliegue en uso hoy en día:

• Manual (asistieron) instalación del sistema operativo con un CD-ROM.
• Automática (sin intervención) instalación del sistema operativo mediante una cuota de servidor.
• OS de terceros además de tecnologías de la imagen de aplicación.

Manual (Asistieron) Instalación de SO de uso de un CD-ROM

Este escenario es uno de los mecanismos más caros para el despliegue de un sistema operativo dentro de una organización. Muchas empresas hoy en día enviar un técnico para el escritorio del usuario para realizar una instalación del sistema operativo con un CD-ROM. Or the technician pre-installs the computer before it's delivered to the end user. This installation type is manual in nature, requiring a technician to physically visit the end user, and manually install the operating system. The technician must be skilled enough to answer technical questions during the installation, specifically regarding the hardware contained within the computer. The cost associated with just one computer installation using this method varies from approximately $180.00 to more than $300.00 depending on the success or failure of the installation process, and can result in variance from corporate standards for system configurations.

By setting up a single Windows 2000-based RIS server, a company can reduce the costs associated with this deployment method and ensure standardization of client computers. RIS can be used to reduce the costs associated with this OS deployment method in these two ways:

• First, the technician would use RIS to initiate an unattended installation of the Windows 2000 Professional operating system over the network using either the built in remote boot capabilities of the computer, or by using the easy to create RIS boot disk. By employing RIS, the company reduces the time required by the technician, as well the required skill of the technician needed to install the OS. The technician would not be required to carry around the CD and boot disks, and since the installation is fully unattended, the technician could initiate the OS installation, and then move on to the next user.
• As another option, the company could choose to forgo the necessity of the technician altogether by allowing the end user to install the OS on their own computer. As noted above, the administrator can guide the user through the correct OS selection, or choose an OS image to be selected for installation automatically when the user logs on to the Client Installation wizard. If the end user need only press F12 , enter their username and password, and then press ENTER , substantial costs can be avoided when deploying the operating system company wide.

Automatic (Unattended) OS Installation Using a Server Share

This deployment mechanism involves the creation of a boot disk containing, in most cases, a copy of the MS-DOS® operating system, a network card driver specific to the computer being booted, and networking software that connects the computer to a network server share containing the OS installation files. This mechanism is also very costly, and requires a substantial amount of technical knowledge, and understanding of the hardware in use throughout the company.

By adding a RIS server to the mix, the technician can use the RIS boot disk, which is created with a single click by the administrator or end user. The RIS boot disk supports a variety of network cards in use today. You can use the RIS boot disk with computers that contain supported PCI-based network adaptors. The RIS boot disk does is not MS-DOS-based, and does not require specific MS-DOS-based networking software to connect to an available RIS server. Rather, the RIS boot disk simulates the PXE boot ROMs described earlier in this paper, and all necessary network card drivers are contained within the single RIS boot disk.

No longer will a technician have to create NIC-specific LAN-enabled boot disks, configure an MS-DOS-based boot disk with regard to conventional memory management, or configure networking settings specific to the organization or division. If your company already uses DHCP and TCP/IP, there is nothing more that needs to be configured to implement Remote OS Installation. Add to this the ability of the administrator to offer base CD unattended installations and/or fully populated RIPrep images that include applications and configuration settings, and you can see the cost saving potential.

Third Party OS Plus Application Imaging Technologies

Many companies have switched to implementing image-based OS deployment technologies. Companies are investing a substantial amount in the creation of hardware specific images that contain both the OS and applications used within the company. There are several third party imaging vendors that provide solutions for deploying the Microsoft Windows family of operating systems. These technologies can be less expensive, require less time to install, and in some cases, require less technical expertise than the deployment methods listed above. In some cases, companies actually perform hardware-based drive duplication, where the hard disk of the source computer is duplicated with a hardware disk duplicator. The resulting hard disk is then installed in a computer and shipped directly to the end user. Other companies can use the existing network for image replication from the source computer to the destination, using a form of boot disk that loads and connects to the network.

All of the imaging technologies available today require that the destination computer (the computer that will install the image) contain the exact same hardware as the source computer used to create the image. These technologies also require in most cases the use of an MS-DOS-based boot disk, which requires some knowledge of the network card hardware in existing computers. By using the RIPrep component of Remote OS Installation, companies can create a single image, and deploy that image across different types of computer hardware within the company. If the existing computers within your organization do not contain a compatible PXE boot ROM, the RIS boot disk can be used to initiate the installation of the RIPrep image.

Given the substantial investment in existing images, Microsoft is working with several of the third party imaging companies to provide integration support that will allow using the existing OS images with RIS. For more information on which vendors are integrating with RIS, see the For More Information section.

The following examples show how Remote OS Installation can reduce costs and increase productivity in an enterprise environment. The scenarios below may be useful in determining the best way to use the Remote OS Installation feature within your organization if you do not already have an OS deployment mechanism in place. The section below will cover the following scenarios:

• Fresh OS Installation on new or existing computers.
• Disaster OS recovery.
• Pre-installing vs. prestaging.
• Using Client Installation wizard options.

Remote OS Installation Usage Scenarios

Scenario 1: New or Existing Computers: A Fresh OS Install

When companies order a computer from an original equipment manufacturer (OEM) or independent hardware vendor (IHV), the computer arrives pre-installed with an operating system. In many cases, the installed OS violates the company's standard desktop policies. As a result, many companies erase the existing OS, and install a version that meets their corporate desktop standards. Companies might also have existing computers on which they want to install a new operating system, and avoid the upgrade process altogether.

Net PC and PC98-compliant computers support the DHCP-based PXE remote boot technology. You can use this technology to install the new OS image on these computers. For pre-Net PC/PC98 computers, the Windows 2000 Server operating system includes a remote boot disk generator that creates a floppy disk, which simulates the PXE remote boot ROM.

Remote OS Installation is configured to install the Windows 2000 Professional operating system by first repartitioning and formatting the hard disk. Once the repartition and format are complete, the operating system is installed in an unattended manner. The administrator can create customized, unattended .sif files that perform OS installations with different settings and features based on specific organization or company standards. For example, a company may require its sales teams to install their computers with only the TCP/IP protocol, yet allow the finance department to install both the TCP/IP and the IPX/SPX protocols due to their in- house accounting system. By using two types of unattended .sif files, the administrator can use a single CD-based operating system image for two different types of OS installations.

RIS also provides the ability to install a RIPrep-based OS image, complete with locally installed applications and configuration settings that the administrator has determined meet the company's desktop standard. The administrator first uses Remote OS Installation to install a client computer with the base Windows 2000 Professional operating system. Then they can install the application or full application suite, and any line of business applications specific to the company or division. The administrator may customize the installation to include a company specific background bitmap, and links on the desktop to relevant corporate resources. After the administrator tests the installation to ensure everything works and is compliant, they then replicate that installation (only a single disk/single partition is supported) to an available RIS server on the corporate network.

Once the OS image replication completes, it is now available for installation by any user the administrator has determined should have access to install that image.

Scenario 2: Disaster OS Recovery

At times, the hardware in a computer may fail beyond repair. In this situation, Remote OS Installation provides the ability to quickly and easily re-install the base operating system or RIPrep image on a computer that has failed completely. By combining the IntelliMirror technology, another change and configuration management feature of the Windows 2000 Server operating system, with the Remote OS Installation feature, a company can recover a large percentage of the entire user and computer configuration and data, including the user's personal data and settings. Once a new hard disk has been placed in the computer, the administrator or end user can initiate Remote OS Installation to install the base OS, or a RIPrep image complete with a base set of applications. After the image installation completes, the user logs on to the computer. At this point, any applications assigned to the user by the software installation and maintenance feature of IntelliMirror are available, as they were prior to the failure. Other Group Policy settings will be re-applied, the user's roaming profile is copied to the computer from the network, and user documents stored in a redirected My Documents folder are made available from the network. By separating the user state from the computer state, in a matter of minutes, the end user is up and running with everything they had prior to the hard disk failure, without the need for a help desk professional to re-install the operating system and the user's applications, and restore data from a backup.

Scenario 3: Pre-installing vs. Prestaging

Many companies today pre-install their client computers with an operating system before delivering the computer to the end user. Pre-installing the computer means that they have loaded the operating system and possibly applications, and have configured the system to meet company standards, before delivering to users. Pre-installation of the operating system by IT staff is a costly process, and increases the company's total cost of ownership. However by pre-installing, the administrator can manually enter a unique computer name and choose the specific Active Directory container the computer account will be created in. The administrator can use the RIPrep feature to install the OS and applications prior to delivery of the system.

Prestaging a computer account, on the other hand, is the process of creating a valid computer account object within the Windows 2000 Active Directory directory service. Prestaging a computer for use with Remote OS Installation allows the administrator the ability to deliver a blank computer directly to the user for OS installation. By prestaging the computer account in Active Directory, the administrator can configure the RIS servers to only respond to prestaged computers. This ensures that only those computers that have been prestaged as Authorized users are allowed to install an operating system from the RIS server. Prestaging can save both time and money by reducing, and in some cases eliminating, the need to fully pre-install the computer.

By prestaging the client computer, the administrator can define a specific computer name, and optionally, which RIS server will service the client computer. In order to prestage a client computer within Active Directory for use with Remote OS Installation, the administrator should follow the steps below.

To pre-stage a client computer

1. Locate the container in the Active Directory service in which you would like your client computer accounts to be created.
2. Right click the container, and then click New , and then Computer . The New Object-Computer dialog box appears, as illustrated in Figure 10.
   Figure 10: Pre-staging a client computer
3. Enter the computer name and authorize domain join permissions for the user or security group containing the user that will receive the physical computer this computer account represents.
4. In the next dialog box, illustrated in Figure 11, you are prompted for the GUID/UUID of the computer itself, as well as whether you intend to use this computer as a managed (Remote OS Install-enabled) client. Enter the GUID/UUID and select the This is a managed computer check box.

The GUID/UUID is a unique 32-character number that is supplied by the manufacturer of the computer, and is stored within the system BIOS of the computer. It should be posted on the case of the computer, or on the outside of the box it was shipped in. If not, locate the GUID by unpacking the computer and running the system BIOS configuration utility. The GUID should be stored as part of the system BIOS. Contact your OEM for a Visual Basic® Scripting Language (VBScript) that can be used to prestage newly purchased client computers within Active Directory for use with Remote OS Installation.

The next screen prompts you to indicate which RIS server this computer should be serviced by. This option can be left blank, which indicates that any available RIS server can answer and service this client computer. You can use this option to manually load balance clients across the available RIS servers within your organization, as well to segment the network traffic, if you know the physical location of the specific RIS server and where this computer will be delivered. For example, if a RIS server was located on the fifth floor of your building, and you are delivering these computers to users on that floor, then you could choose to assign this computer to the RIS server on the fifth floor.

Scenario 4: Creating Standard Desktops with RIPrep and Software Installation and Maintenance

If an Administrator wants to use Remote OS Installation to stage and standardize their computers, then they can consider installing the organization's key software at the same time.

The best way to describe this is to provide an example. Consider an organization that wants to bring in new computers, and customize both the Windows 2000 operating system and the Office 2000 suite of applications.

The administrator has Remote OS Installation set up and configured, and has the Software Installation and Maintenance feature of IntelliMirror configured. That is, there are existing Group Policy objects to manage the computers in the organization. The administrator has a Software Distribution Point for Office 2000, they have customized Office 2000, and then they have assigned Office 2000 to the computers in the appropriate GPOs. (For more information on how to do this, reference the Windows 2000 Software Installation and Maintenance Walkthrough listed in the For More Information section.)

Note: Care must be taken to configure the RIPrep source computer with applications from the same GPOs that apply to the destination computers (those that will install the RIPrep image) when they are deployed. The applications may be removed or removed and reinstalled if a different policy is applied to the computer when it is deployed.

The administrator installs the Windows 2000 operating system on a computer (that has the same HAL as the desired target systems), and configures the operating system the way that they want it. When Windows 2000 is installed and configured, the administrator adds it to the same Active Directory container where it will live when it is deployed. This container has a GPO with Office 2000 assigned to the computer.

The administrator starts the computer, and the Software Installation and Maintenance technology in IntelliMirror installs Office 2000 (applications assigned to the computer install when the computer starts).

After Office 2000 is installed, the administrator can take the computer running Windows 2000 with Office 2000 installed on it, and use the RIPrep tool of Remote OS Installation to build a Remote OS Installation image, and put this image on the Remote OS Installation server. Once this image is available, a person getting a new computer that supports Remote OS Installation only has to connect the peripherals (keyboard, mouse, monitor), connect to the network (plug a cable between the network card and the hub), turn on the computer, and press F12 when prompted to initiate a network boot.

The computer finds the Remote OS Installation server; download the operating system and the applications. When the computer restarts after remotely installing the OS, Windows Installer realizes that the software is already on the machine, and then only updates the application's advertisement information. This update of the advertisement information only takes a few seconds.

Note that when the user logs on to the computer, and selects the first Office 2000 application, the Windows Installer starts. ¿Por qué es esto? Office 2000 separates installation from user configuration to ensure proper separation between user-specific and machine-specific configuration. The Windows Installer starts each time a new user starts the application, in order to perform a small amount of user-specific configuration.

The key point is that Remote OS Installation and Software Installation and Maintenance allows administrators to rapidly and efficiently deploy both the operating system and applications, and still bring the applications into a state where they can be managed by Software Installation and Maintenance for future updates, and if necessary, removal.

Using the Client Installation Options

Using the Automatic Setup Option

The automatic setup option is the client installation option that all users of the Remote OS Installation feature have access to by default. The automatic setup option can be used to guide the user through a successful OS installation. The administrator is able to restrict the OS installation options in such a way that the user simply logs on, and the OS installation starts automatically. The user is not asked a single question during the OS install, which avoids lengthy calls to help desk professionals for assistance, thus saving the company additional expenses in support costs.

If the administrator decides, they can provide the user with multiple unattended OS choices. Remote OS Installation allows the administrator to provide a friendly description and associated help text that describes the OS options in such a way that an end user can choose the OS that best fits their need or role within the company. For example, the administrator can create several unattended answer files that install an OS tailored for the marketing users within the company. Each of the OS types provides a different subset of OS features given a specific type of marketing user. The administrator would restrict these OS types to only the marketing security group which ensures that only users that are members of that marketing security group are offered these OS choices. Now, the end users have a variety of OS installation types to choose from, but are able to make the choice based on the friendly description and help text provided when selecting each of the OS choices.

By pre-selecting the Remote OS Installation configuration options, the administrator predefines the automatic machine naming format and the location within Active Directory where client computer accounts will be created. IT staff will no longer have to manually preinstall computers for end users, ensuring that the computer account is created within the correct domain, or with the correct computer name. The administrator can simply define these attributes for a given RIS server and everything is done automatically during OS install.

Consideraciones:

• By default, end users are restricted to only see the automatic setup option by the settings in the Default Domain Policy Group Policy object. If necessary, the administrator can modify the settings in the Default Domain Policy, and/or create additional group policy objects that allow end users access to the other installation options. For more information, see the Windows 2000 Help regarding Group Policy settings.
• If you choose to offer end users multiple OS installation types, ensure the number offered is relatively small (a maximum of 3-5 is suggested). This will help to avoid confusion, and will assist in ensuring that end users select the OS that best meets their need and role within the company.
• Group individual end users into security groups and use those groups to restrict the available OS installation options. Setting permissions for individual users on the individual setup information files (.sif) can become an administrative burden. Instead, use security groups to restrict the choices and where possible apply security on the Templates folder itself (which will apply to all .sif files in the folder) rather than on the individual .sif files.

Using the Custom Setup Option

The custom setup option is very similar to the automatic setup option, yet provides the administrator or help desk professional with the ability to set up a computer for someone else within their organization. This option can be used to fully pre-install a client computer or to prestage the client computer by creating a corresponding computer account within the Active Directory service. This setup option in many cases will only be used when the IT or help desk professional must perform the initial setup or re-installation of an end user's computer.

The custom setup option lets the administrator or help desk professional override the automatic computer naming and where the computer account is created within Active Directory. By default, the RIS server will generate a computer name based on a format defined by the Remote OS Installation administrator. The administrator can also define where client computer account objects (CAO) will be created in the Active Directory service during the operating system installation. By default, the automatic computer naming policy is set to create computer names based on the person who logs on to the Client Installation wizard.

In the case where an administrator or help desk professional is pre-installing the OS on the computer for someone else within the organization, it may not be appropriate to name the computer after the help desk staff. In that case, the staff person would be provided access to the custom setup option through Group Policy, and would be offered the ability to override the automatic computer name and default Active Directory location.

The custom setup option also gives an administrator or help desk professional the ability to prestage the client computer. Prestaging a client computer simply creates a corresponding computer account object within the Active Directory for that computer. Once the computer account has been prestaged, the administrator is assured that this is an authorized Known client computer that can be serviced by any available RIS server. Prestaging a computer account using the Client Installation wizard is done by entering all the information necessary to perform the installation, which results in the CAO being created, but canceling the CIW just prior to the actual OS installation starting.

Note: The simplest way to prestage a group of client computer accounts for use with Remote OS Installation is by using the VBScript provided by Microsoft to system vendors. The script uses a Microsoft Excel spreadsheet containing the required information to prestage client computers for use with RIS. When placing orders for computers that you want to prestage, contact your system vendor to request this script and a copy of the spreadsheet pre-filled with the GUIDs of the new systems you will be receiving.

Consideraciones:

• If users are allowed to perform their own OS installations using Remote OS Installation, the custom setup option will not typically be used so that the standards defined for computer naming and location will always be followed. However, in cases where an IT or help desk professional must visit the end user, or perform a manual installation of the OS, the custom setup option can be used as appropriate.
• Use custom setup if your company has a policy that requires that all computers are preinstalled with an OS prior to delivery to end users. The Remote OS Installation feature should provide the ability to avoid pre-installs, but if it is company policy to do so, the custom setup option is provided.

Using the Restart a Previous Setup Attempt Option

The option to restart a previous setup attempt is provided in the event that the installation of the OS fails for any reason. The Client Installation wizard can be customized to ask a series of questions about the specific OS being installed. For example, if an administrator wants to create a version of the Client Installation wizard that asks the user which type of protocols should be installed, which video resolution, and what the specific company name was, when restarting a failed OS setup attempt, the end user would not be asked these questions again. Rather, Setup would already have this information, and would simply restart the file copy operation and complete the OS installation.

Consideraciones:

• Restarting a previous setup attempt does not restart the OS installation at the point where it failed. Rather, this option restarts the OS installation over from the beginning of setup.
• This option may not be appropriate to offer to end users. This option will not attempt to fix any problems that occurred with the previous setup attempt and as such should be used as a Remote OS Installation troubleshooting option for IT or help desk staff.

Using the Maintenance and Troubleshooting Option

The Maintenance and Troubleshooting tool provides access to third party hardware and software vendor tools. These tools range from system BIOS flash updates and memory virus scanners, to a wide range of computer diagnostic tools that check for hardware related problems. These tools are available before installing and starting the operating system on the client computer.

If the options to display the Maintenance and Troubleshooting Tools menu is enabled by Group Policy, user access to individual tool images is controlled in the same way as operating system options, by setting specific end user permissions on the individual answer file (.sif) for that tool. For example, the Remote OS Installation administrator can allow end users access to only one computer diagnostic tool, yet provide help desk professionals with access to the entire suite of diagnostic tools. When the user calls a help desk professional for assistance, the professional can guide them through the diagnostic tool for retrieval of information necessary to diagnose the problem being encountered. If the help desk staff must visit the end user for further investigation, they simply log on to the Client Installation wizard and, based on their credentials, can access the tools they need to resolve the problem.

Consideration:

• The maintenance and troubleshooting option may not be appropriate for end users. Make sure that if you allow access to this installation option, that you provide only those tools that cannot damage the computer or cause further problems.
• See the For More Information section for details on vendors working on RIS-enabled maintenance and troubleshooting tools. If you do not see the vendor of a tool you use listed, contact the vendor directly.

Resumen

The Remote OS Installation feature is one of the many features in the Windows 2000 Server operating system that helps reduce the costs associated with deploying a new version of an operating system throughout an enterprise. The Remote OS Installation feature provides an administrator with a number of options that both simplify and streamline the process of rolling out a new version of an operating system, and ultimately reduce the total cost of ownership.

Para obtener más información

For the latest information on Windows 2000 Server, check out Microsoft TechNet or the Microsoft Windows 2000 Web site ( http://www.microsoft.com/technet/prodtechnol/windows2000serv/default.mspx ).

You can find the latest copy of the Remote OS Installation Walkthrough ( http://www.microsoft.com/windows2000/docs/RemoteOS.doc ), used to install, configure and use the Remote OS Installation feature on the Microsoft Windows 2000 Web site.

For information on the IntelliMirror Management features, and for a complete listing of the associated Walkthrough documents, please see Management Services ( http://www.microsoft.com/windows2000/technologies/management/default.asp ) on the Microsoft Windows 2000 Web site.

For more details on individual Remote OS Installation configuration settings, please see the Windows 2000 Documentation ( http://www.microsoft.com/technet/prodtechnol/windows2000serv/default.mspx ), Product Help, which can be found on the Windows 2000 Web site ( http://www.microsoft.com/technet/prodtechnol/windows2000serv/default.mspx ), and search for Remote Installation Services.

Several vendors have announced products or product plans for utilities that integrate with Remote OS Installation. For more details on tools compatible with the Maintenance and Troubleshooting option, search for integration papers on the Windows 2000 Web site under Management Services ( http://www.microsoft.com/windows2000/technologies/management/default.asp ).

Appendix A: Hardware Requirements

Remote Installation Server and Workstation Hardware Requirements

Server Hardware Requirements

• Pentium or Pentium II 166 MHz (200 MHz or larger processor recommended).
• 64 MB Ram minimum. If additional services such as Active Directory, DHCP, and DNS are installed, then the minimum amount of RAM required is128 MB.
• 2 GB hard disk dedicated for the Remote Installation Service directory tree.
• 10 or 100 mbps network adapter card (100mbps preferred)

Note: A partition separate from the system's boot partition is required to install the Remote Installation Services. To accommodate the operating system installation images, you may want to dedicate an entire hard disk specifically to the RIS directory tree.

Client Hardware Requirements

• Pentium 166MHz or faster processor.
• 32 MB Ram minimum.
• 800 MB hard disk drive.
• Supported PCI Plug and Play network adapter card. (See Appendix B for supported network cards for use with the RIS boot disk.)
• Optional: PXE-based remote boot ROM version .99c or later.

Appendix B: Network Cards Supported by the RIS Boot Disk

The following is a list of network card models that are supported by the RIS boot disk. The boot disk generator tool is available within the \Admin\i386 Subdirectory under the \Remoteinstall directory and is called Rbfg.exe.

Network Cards Supported by RIS Boot Disk:

3 Com Network Adapters:

• 3c900 (Combo and TP0)
• 3c900B (Combo, FL, TPC, TP0)
• 3c905 (T4 and TX)
• 3c905B (Combo, TX, FX)

AMD Network Adapters:

• AMD PCNet and Fast PC Net

Compaq Network Adapters:

• Netflex 100 (NetIntelligent II)
• Netflex 110 (NetIntelligent III)

Digital Equipment Corp (DEC) Network Adapters:

• DE 450
• DE 500

Hewlett Packard Network Adapters:

• HP Deskdirect 10/100 TX

Intel Corporation Network Adapters:

• Intel Pro 10+
• Intel Pro 100+
• Intel Pro 100B (including the E100 series)

SMC Network Adapters:

• SMC 8432
• SMC 9332
• SMC 9432

Note: The RIS boot disk generator only supports PCI-based network cards (ISA, EISA, and Token Ring cards not supported).

Appendix C: Frequently Asked Questions

Question: How do I know I have the correct PXE ROM version?

Answer: When the Net PC or client computer containing a remote boot ROM starts, the PXE ROM message appears on the screen. You should see which version of the PXE ROM code is displayed during the boot sequence of the client computer. Windows 2000 RIS supports .99c or later PXE ROMs, except in very few situations that will require the .99L version. You may be required to obtain a newer version of the PXE-based ROM code from your OEM in the event you are not successful with the existing ROM version installed on a client computer.

Question: How do I know if the client computer has received an IP address and has contacted the RIS server?

Answer: When the client computer starts, you see the PXE boot ROM begin to load and initialize. The following sequence occurs with most PC98 and Net PCs, PXE ROM-based computers, and computers using the RIS boot disk:

Remote boot ROM load sequence:

Step 1: The client computer displays the message DHCP . This message indicates the client is requesting an IP address from the DHCP server. This may also indicate the client has obtained an IP address from DHCP and is awaiting a RIS server response. To verify if the client is receiving an IP Address, you can check the IP leases that have been granted on your DHCP server.

Troubleshooting: If the client does not get past the DHCP message it may mean the client is not receiving an IP address or that the BINL server is not responding, things to check are:

• Is the DHCP server available and has the service started? DHCP and RIS servers must be authorized in Active Directory in order for their services to start. Check to ensure the service has started and other non-remote boot-enabled clients are receiving IP addresses on this segment.
• Does the DHCP server have a defined IP address scope and has it been activated?
• Is there a router between the client and the DHCP server that is not allowing DHCP packets through?
• Are there any error messages in the event log under the System Log for DHCP?
• Can other client computers—that is non-remote boot-enabled clients—receive an IP address on this network segment?

Step 2: When the client receives an IP address from the DHCP server, the message may change to BINL . This indicates the client successfully leased an IP address and is now waiting to contact the RIS Server. The client computer will eventually timeout, and post the error message “No Bootfile received from DHCP, BINL, or Bootp”

Troubleshooting: If the client does not get past the BINL message it means the client is not receiving a response from the RIS server. Things to check are:

• Is the RIS server available and has the BINL (BINLSVC) service started? RIS servers MUST be authorized to start on the network. Ensure the RIS servers are authorized to run on the network. Use the DHCPMGMT.MSC snap-in to authorize both DHCP and RIS servers within the Active Directory.
• Are other remote boot-enabled clients receiving the Client Installation wizard? If so, this may indicate this client computer is not supported or is having remote boot ROM-related problems. Check the version of the PXE ROM on the client computer. Also check in Active Directory to see if the administrator has prestaged this client computer to a specific RIS server that may be offline or unavailable to the client computer.
• Is there a router between the client and the RIS server that is not allowing the DHCP-based requests/responses through? The RIS server communicates using the DHCP packet type during the initial service request/response sequence. You may need to configure the router to forward the DHCP packets.
• Are there any error messages in the event log under the System or Application logs specific to RIS (BINLSVC), DNS, or the Active Directory?

Step 3: The client will then change to TFTP or will prompt the user to press the function key, F12 . This means that the client has contacted the RIS server and is waiting to TFTP the first image file, which is the Client Installation wizard. You may not see the BINL and TFTP message, because on some computers this sequence simply flashes by too fast.

Resolución de problemas:

If the client computer does not get a response from the RIS server, the client computer will timeout, and displays an error message saying that it did not receive a file from DHCP, BINL, or TFTP. In this case, the RIS server did not answer the client computer. Things to check are:

• Detenga y reinicie BINLSVC en el servidor RIS. On the Start menu, click Run , and then type CMD . In the CMD window, type:

   Net Stop BINLSVC
   Net Start BINLSVC 

• Check the RIS server properties to ensure that the Respond to Known client computers option is checked, and that the Do not respond to Unknown client computers is not checked, unless you have prestaged the client computers in the Active Directory prior to starting the client computer.
• Check in the event log to ensure no errors relating to DHCP, DNS, RIS (BINLSVC), and/or the Active Directory exist.

If the client computer does not receive an answer after attempting to stop and restart the service, and after checking the properties of the RIS server to ensure the correct settings have been set, you should check the Event Log on the RIS server for any errors relating to DHCP, DNS, or RIS (BINLSVC). If possible, capture the network activity between the server and the client with a network sniffer, and you can provide the Microsoft Product Support Services with this information.

Step 4: At this point, the client should have downloaded the Client Installation wizard, and been greeted with the Welcome page.

Question: Does Remote OS Installation support the older remote boot protocol Remote Program Load (RPL)-based ROMs?

Answer: The Remote OS Installation feature uses the new PXE DHCP-based remote boot ROMs. As such, there is no support in the Windows 2000 operating system for the older RPL-based remote boot.

Question: Does Remote OS Installation support remote installation of Windows 2000 Server CD-based or RIPrep OS images?

Respuesta: No. Remote OS Installation does not support remotely installing Windows 2000 Server.

Question: Does Remote OS Installation support remotely installing an OS image (RIPrep or CD Based) on laptop computers?

Answer: Yes and No. Remote OS Installation has been tested with laptop computers in docking stations that support the required PXE ROM code, and with laptop computers in docking stations that contain NICs supported by RIS boot floppy. The systems must be located within the docking station with the network cable plugged into the network adapter located with the docking station. The Toshiba Protégé 7010CT and Tecra 8000 are examples of laptops that support the PXE boot ROM when used with the Toshiba NetDock (docking station). In order for these systems to function with RIS, they require the 99L or later version of the PXE ROM code for the specific network card located within the NetDock.

RIS does not support laptop computers that contain PC Card or PCMCIA network cards.

Question: Is the pre-boot portion of the PXE remote boot ROM secure?

Respuesta: No. The entire ROM sequence and operating system installation/replication is not secure with regard to packet type encryption, client/server spoofing, or wire sniffer based mechanisms. As such, use caution when using Remote OS Installation on your corporate network. Ensure that you only allow authorized RIS servers on your network, and that the number of administrators allowed to install and/or configure RIS servers is controlled.

Question: Can RIPrep-based OS images be replicated to alternate media such as DVD, CD, and/or Zip drives?

Respuesta: No. In a Windows 2000-based system, you can only replicate the source image to a single available RIS server on the network.

Question: Does Remote OS Installation preserve the file attributes and security settings defined on the source computer when using the RIPrep image feature?

Answer: Yes. The file attributes and security settings that are defined on the source computer will be preserved on the destination computer that installs that image. However, be aware that the RIPrep feature does not support the encrypted file system if enabled and used on the source client computer.

Question: Does the RIPrep feature support different hardware between the source computer used to create the RIPrep-based OS image and the destination computer that will install the image?

Answer: Yes. The hardware between the source computer and the destination computer can be different. The one exception to this is the Hardware Abstraction layer (HAL) driver used. For example, if the source computer has Advanced Configuration Power Interface (ACPI) support it will use a specific ACPI HAL driver. If you attempt to install this RIPrep image on a computer without ACPI support, it will fail.

Question: Does the RIPrep wizard support multiple disks and or multiple partitions on a given client computer?

Respuesta: No. The RIPrep utility only supports a single disk with a single partition (C:\ Drive) in this release of Remote OS Installation.

Question: How does the RIPrep wizard deal with disks that differ in size between the source computer used to create the image and the destination computer that will receive it?

Answer: The destination computer's disk size must be equal to or larger than the source disk used to create the image. For example, if the source computer has a 1-gigabyte (GB) hard disk, when that image is installed on a destination computer that has a larger (for example 2-GB)hard disk drive, the full 2-GB drive will be partitioned and formatted prior to installing the OS image. You can also configure support for formatting the destination computer's hard disk to the same physical size of the source computer. For more information, see the online documentation for on the UseWholeDisk= parameter.

Question: How do I replicate all of the OS images currently located on one of my RIS servers to other RIS servers on the network for consistency across all client installations?

Answer: The Remote OS Installation feature does not provide a mechanism for replication of OS images from one RIS server to another. There are several mechanisms that can be employed to solve this problem. Use the strong replication features of the Systems Management Server product. This product provides for scheduled replication, compression, and slow link features. You can also employ third party vendor solutions for OS image replication. Ensure that the replication mechanism supports maintaining the file attributes and security settings of the source images.

Question: Can I have a RIS server and a third party remote boot server on the network at the same time? f so, what are the implications?

Answer: Yes, you can have multiple vendor Remote Boot/Installation (RB/RI) servers on one physical network. It is important to understand that currently the remote boot PXE ROM code does not know the difference between different vendor's RB/RI servers. Therefore, when a remote boot-enabled client computer starts and requests the IP address of a RB/RI server, all of the available servers will respond to that client. Thus, the client has no way to ensure it is serviced by a specific RB/RI server. Using Remote OS Installation, an administrator can prestage client computers in the Active Directory, and mandate which RIS server will service that client. By configuring the RIS server to only answer known (prestaged) client computers, the administrator is assured that the client will be serviced by the correct RIS server. Not all RB/RI vendors have implemented the ability to ignore service requests, and therefore, you may need to segment off the specific vendors servers on the network so that clients are not answered by these vendors RB/RI servers.

Question: Can I remotely manage the RIS servers from Windows 2000 Professional-based workstations on my network?

Answer: Yes. If you are an administrator in the domain, and you have installed the Administrator Tools package on your Windows 2000 Professional-based workstation, you can administer the majority of the RIS configuration settings. There are some items that you cannot manage, for example, you cannot remotely add additional operating system images to RIS servers from computers running Windows 2000 Professional.

Question: Can I add additional network adapter cards to the RIS boot disk?

Respuesta: No. The Rbfg.exe utility is hard coded with regard to the number of supported network card adapters for this release of Remote OS Installation. Updates to the Rbfg.exe utility will be made available through normal distribution channels such as the Microsoft Windows Web site ( http://www.microsoft.com/windows ), Windows Update, and future Service and Feature Pack updates.

Question: Can I use Active Directory object attributes to create a naming format for use with the Remote OS Installation automatic computer-naming feature?

Respuesta: No. Currently the existing attributes supported with the automatic computer-naming feature use the Active Directory service. However, not all of the Active Directory object attributes are currently supported.

Question: Where do I look on the client computer to find the GUID/UUID for prestaging clients in Active Directory for use with Remote OS Installation?

Answer: The GUID/UUID for client computers that are PC98 or Net PC compliant can in most cases be found in the system BIOS of the computer. Microsoft encourages OEMs to ship either a floppy disk containing a comma separated file or spreadsheet that contains a mapping of computer system serial number to GUID/UUID. This allows you to script prestaging client computers into the Active Directory directory service. Microsoft also encourages the OEMs to post the GUID/UUID on the outside of the computer case for easy identification and prestaging of computer accounts. If the GUID is not found in the above-mentioned locations, you can use a network sniffer to analyze the network traffic of the client, locate the client's DHCP discover packet, and within that field will be the computer's 32 byte GUID/UUID.

Tags: installation , operating , remote , system