Deploying software with Windows2003

As a network administrator, one of the most common tasks is the deployment of various software, including system software and application software. In a wide range of network environment, the installation disk for the local installation method to deploy software, not only inefficient, impact work, and may be errors, so in this case the common installation method is to do network installation. However, the current network installation is generally installed using a shared installation disk, there are two main drawbacks to this installation: one is that the client must be networked with the server, otherwise it cannot access the shared resources, such as a new machine without any system, which cannot use the shared resource, or even after the client is connected to a server-side share, There is still the presence of an administrator involved in the installation process, or some installation options cannot be determined and the installation process cannot continue. So the administrator must master some effective methods in order to efficiently complete the day-to-day work of software subordinates.

To address the problem of deployment in a software network, Windows Server 2003 provides RIS and installer two technologies, the Remote Installation service, which provides remote installation of the operating system for clients on the network through Windows Server, The latter is specifically designed to address the need to publish applications in a Windows networking environment. In addition, Windows Server 2003 provides the ability to quickly deploy changes.

Remote Installation Services

Remote Installation Services (RIS) is a network service built into Windows Server 2003 that enables clients to access the server through the Boot Information Negotiation Protocol (BINL) in a domain environment and requests the server to provide the operating system for it, and the server responds to the request with the Simple File Transfer Protocol (TFTP) "The required installation files are passed to the client. At the same time, the RIS server uses "single Instance Storage (SIS)" technology to ensure that when handling a large number of customer installation requests, the system resources are not consumed too much, thus providing a system guarantee for the software deployment within the large network. The following describes the specific process.

1. Configuring the RIS server

As with other Windows services, the installation of the RIS service can be done through the Windows Components Wizard, which requires a system installation CD for Windows Server 2003.

2. Specify the rights of the user

In a security system such as Windows Server 2003, the completion of any work is subject to resource permissions and user rights, so after you install the RIS service, you should also define which users can use this service on the client to install the operating system, that is, you need to specify the rights of the user. There are two main powers: one is the power to add computers to the network, and the other is the power to bulk process the installation tasks. As shown in Figure 1, these two rights are assigned to users in the domain controller's Active directory Users and Computers.

(1) Specify the right to add a computer

First, in the Active Directory users and Computers manager, right-click the domain or organizational unit where you need to install the client, as shown in Figure 2, select Delegate Control (E) in the pop-up menu. Then, in the Delegate Control Wizard, specify the users who authorize the installation of the client and assign them the power to add computers to the domain, as shown in Figure 2, and follow the wizard's prompts to complete the operation.

(2) Specify the power to bulk process installation tasks

After assigning the user the power to add a computer, return to the Active Directory users and Computers manager and continue to define the power to bulk process installation tasks. Again, as shown in Figure 1, right-click the desired domain or organizational unit, select Properties (R), and select Edit Group Policy in the Properties window of Figure 3.