Although RIS is a fast, efficient automated installation technology, it has the following limitations:
Clean installation only
You can only use RIS to install a clean version of an operating system, with or without software applications. You cannot use RIS to upgrade an operating system or software configuration.
Limited configuration of server components
You might not be able to include all the server components that you want to provide with RIS installation. For example, some server components require that you install and configure them only after the RIS-based installation is complete. This can include components such as Certificate Services, the Cluster service, or software that is dependent on Active Directory.
No support for installing domain controllers
You cannot install a preconfigured domain controller using a RIS image. However, you can use RIS to install a stand-alone server and then configure the server as a domain controller by running the Active Directory Installation Wizard.
No support for configuring encryption and security settings
You cannot use RIS to deploy files that are encrypted with a system such as the Encrypting File System (EFS). Also, you cannot use RIS to deploy systems with preconfigured user-level security settings such as file and folder permissions. To configure these settings, you can run a script after completing your RIS-based installation.
No support for wireless networks
You cannot use RIS to deploy images over a wireless network. Wireless networks do not support remote-booting computers that use PXE technology.
Limited support for multihomed computers
Multihomed RIS servers are supported if the network adapters use multiple separate subnets or if all network adapters use the same subnet. In both cases, the RIS server must also be the DHCP server. The DHCP server must have active scopes for each subnet serviced and must be authorized for each IP address on the network adapters being serviced.
|