As a network administrator, one of the work that is often doing is the deployment of various software, including system software and application software. In a wide range of network environments, the mounting method is taken by the mounting disk to deploy software, the efficiency is low, the impact work, and there may be a mistake, so in this case, the common installation method is to perform network installation. However, the current network installation generally uses a shared installation disc for installation. This installation method has two main disadvantages: First, the client must have been connected to the server, otherwise the shared resource cannot be accessed, such as a new machine without any system. Use shared resources; Second, even after the client is connected to the server, there is still an administrator to participate at any time in the process of installing the application, otherwise some installation options cannot be decided, and the installation process cannot continue. So the administrator must master some effective methods to efficiently complete the work of the daily software.
In order to solve the problem of deployment in the software network, two technologies in Windows Server 2003 provide both RIS and Installer, the former is a remote installation service, and the remote installation of the operating system is provided by Windows Server to the network, the latter is specifically solved. Release the application's needs in the Windows network environment. In addition, Windows Server 2003 also provides a function of rapid deployment.
Remote installation service
Remote Installation Services (RIS) is a Windows Server 2003 network service, which enables the client to access the server through the Boot Information Convergence Protocol (BINL) "in the domain environment, and requests the server to provide an operating system, and the server After the response request, you can use the Simple File Transfer Protocol (TFTP) for the client to get the required installation file. At the same time, the RIS server uses "Single Example Storage (SIS) technology, ensuring that the system guarantee provides system guarantees for software deployments within large networks when handling a large number of customer installation requests. The specific process is described below.
1. Configuring a RIS server
Like other Windows services, the installation of the RIS service can be done through "Windows Component Wizard", and the Windows Server 2003 system installation disc is required during installation.
2. Specify the right of the user
In a security system such as Windows Server 2003, the completion of any work is subject to control of resource permissions and user power, so after installing the RIS service, which users should define which users can use this service to install operations. The system is required to specify the power of the user. This mainly has two powers: one is the power to add a computer to the network; the other is the power that can batch the installation task. As shown in Figure 1, the user assigns these two powers in the "Active Directory users and computers" of the domain controller.
(1) Specify the power to add a computer
First, in the Active Directory User and Computer Manager, right click on the mouse to install the domain or organizational unit, as shown in Figure 2, select "Delegation Control (E) ..." in the pop-up menu. Then specify the user of the client to install the client in the Delegation Control Wizard, and assigned to them to add a computer to the domain, as shown in Figure 2, follow the prompts of the wizard.
(2) Specify the power to batch processing installation tasks
After allocating the power of the user to add a computer, return to the Active Directory User and Computer Manager, continue to define the power of batch processing tasks. The desired domain or organizational unit is again taken as shown in FIG. 1, select "Attributes (R)", select the editing group policy in the attribute window as shown in Figure 3.
When editing group strategies, the Group Policy Editor will open "Group Policy Editor", in the position shown in Figure 4, the mouse double-click "Sign in as a batch job" to specify the network user and define policy settings. You can add the user or group (u) ... "button, then follow the prompts to add the user to the client to install the system installation operation to this policy. 3. Prepare the installer
Before installing the operating system on the client, you must first prepare your system installer on the RIS server so that the client can automatically obtain the desired source file from the server when installing. This work is done by the Risetup.exe Server Configuration Wizard provided by the RIS server, which can copy the required source file to the server and can be transmitted over the network when the client is installed. Run the risetup.exe program, start the Remote Installation Service Installer Wizard. The next operation is followed.
(1) Set the client installation location; (2) Specify the response to the client; (3) Define the location of the source file to be copied; (4) Specify a folder name; (5) Install the instructions.
4. Making boot disk
As the RIS, in addition to the hardware condition of the installed operating system, the only requirement is that its network card should support pre-start execution PXE technology, only this network card can match the function of RIS. Therefore, such a client must choose such a client, generally there are three possibilities, one is NetPC supported by Windows Server 2003; Second, the ordinary PC has a network card that supports PXE technology, and the NIC has a network launch chip, and the chip The version is at least 1.0; three, although the PXE technology network card is installed, there is no NIC launch chip, or the chip version is the version that Windows Server 2003 is not supported. For the first two cases, due to the network card startup feature supported by Windows Server 2003, as long as the RIS server is connected, it can be installed from the network and automatically request the system to install the server, and for the third client cannot Automatically start from the network, so the administrator must prepare a RIS boot installation floppy disk, and use it when booting.
Making the RIS boot installation floppy disk is provided by 3COM, it can imitate the boot process of the PXE chip. The RIS server of Windows Server 2003 contains this program - RBFG.exe. This file can be found in Reminst / Admin / I386 in Reminst / Admin / I386. Run RBFG.exe and insert a floppy disk to make a boot disk specifically for PXE remote installation.
5. Client installation
After these preparation, the client can start installation. The initial boot interface is shown in Figure 5, and the PXE system will automatically connect to the DHCP server and request the customer's network address. After the address application is successful, the RIS server passes the client installation file to the client through the TFTP protocol, and the client enters the Client Installation Wizard. After the authorized legal user enters the correct username and password to log in to the domain, you can select the required system to install it. The installation process can generally select automatic installation mode, which does not require administrators to participate, and automatically complete the next installation process.
It is also necessary to emphasize that the client's network card must support pre-start execution of PXE technology, otherwise the initial boot request cannot be successful, and the installation cannot continue. If you want to view the PXE network type, you can press the Adapter List (L) button during the process of running the RBFG.exe program, check if your PCI network card is in the supported list.
Installing the client via the RIS technology has a wide range of speed. If you want to automatically install the system file in the RIS server, you also want to install some applications to the client together, you need to install the appropriate operating system and application software in advance on one client. Then run the /reminst/admin/i386/riprep.exe program in the RIS server on this configured client, this file is also a wizard program similar to Risetup.exe, which will pass the system and the system in this client via the network. Application software makes a mirror, saved to the REMINST share of the RIS server. The so-called mirror is the same system as the system in the original client, but deletes some settings indicating the identity of the original client, such as security identifier SID, hardware drive settings, etc. Thus after other clients are installed by RIS, re-generate SID and corresponding hardware settings information according to the actual situation of the machine, not only the operating system is installed, not only the operating system is installed, so that the application and the system are installed together. This approach is very helpful for web applications that require a unified desktop environment. Quick deployment new application
In addition to the need for application software, in most cases, the specific client application is not necessarily determined when installing the operating system, but is installed according to the actual needs of the user. Therefore, administrators should also have another way to install application software through the network to address the rapid deployment of application software in daily work. Windows Installer supported by Windows Server 2003 is such a practical installation tool.
Windows Installer uses real-time installation technology to push the software to the client through the domain environment, thereby implementing the application automatic installation deployment. The installer using Windows Installer technology first requires packaging into MSI format so that it can be supported by Windows Installer. Now Windows's most software installation files already have this format, and this packaging tool can also be found in Microsoft's Server Resource Toolkit to resolve other software packages. The installer is to copy into a network shared folder on the server. The installation step is described below.
1. Specify configuration
In the Active Directory User and Computer Manager, the mouse is right-click, select "Attributes (R)", select the Edit Group Policy in the Domain Properties window shown in Figure 3, open the Group Policy Editor. As shown in Figure 6, there is a "software installation" item in the computer configuration and user configuration to serve the software in the domain. If the software is to be deployed into a computer in the domain, it is defined in the computer configuration. If the software is to be deployed to the domain, it is defined in the user configuration.
2. Specify how to deploy
Right click on "Software Installation" and select New Package, and set it according to the prompt of the system wizard. First, you will prepare the MSI file in advance within the network shared folder on the network. Then, the system will ask the software deployment, and Windows Installer provides both "release" and "assign" two deployment methods. The "release" method is not automatically installed in the domain, but put the installation options in the "Add or Remove Programs" of the client, for the user to choose the installation when needed; "Assign" mode directly install the software directly The domain user's start menu program group. The "release" method is generally used to provide users with a variety of software tools, and the user can choose or not install it by the user; "Assignment" mode can be used for the software forced installation, and the user has no right to uninstall the software.
For software already deployed, you can also modify the settings through advanced options. If the administrator wants to cancel the deployment of the program, as long as the deployed software is deleted in the Group Policy Editor, it is possible to prevent the customer from continuing to install the software, or even select the software that the user has installed is automatically removed.
3. Client configuration
After the deployment is complete, the "Assign" software, the user can find and use directly in the start menu after logging the field; "release" software, users only go to "Add or Remove Programs" Add new program (N) "It will be seen that if you want to install, press the" Add "button. In addition, Windows Server 2003 also provides a function of rapid deployment.
Deployment change
There are many reasons why the procedures is changed, such as security upgrades, upgrades, and functional enhancements or enterprise-wide versions.
In general, management updates is a cost of expensive and incorrect work. Upgrading the shared component requires the operation of the existing program because the operation of these programs requires the upgraded DLL. Before .NET appears, there is no way to install the same DLL in one system species. In addition, the web program cannot be upgraded during operation, which requires closing the service when installing an upgrade, even restarts the computer.
Windows Server 2003 provides a mature change management and deployment feature. These simple technologies (such as file replication) can be used to update the entire program or only part of the program. Although technology is more complicated, it is still very simple in use, such as Windows Installer and an automated upgrade application allows users to adjust the change management process as needed.
In the easiest case, if you upgrade the private components on a computer, you can copy the upgrade component to the private directory using FTP or XCOPY or any other file management tool. And previous systems share the same DLL, private program parts, such as NET DLL, can be placed in a local folder where an application is located, which is only accessed alone by this application. The program list is usually generated when compiling the exe file, you can tell the runtime version checker search for folders that contain the EXE file itself. You don't need to register a upgrade private component in a Windows group test form or global programcore cache (GAC). In any case, installing an upgraded private prime file does not interfere with the operation of other programs.
You can even deploy shared files on the client or server without interfering with multiple versions of the executable or the same DLL depending on. GAC is a centralized repository (Exe and DLL) of the program. Because each program is a clear version of a clear name, the GAC can contain multiple versions of the same program. You can use Windows Installer to upgrade the program parts in the GAC and the entire application.
.NET Framework installed the shell cache views extension in Windows Explorer to browse and edit the GAC. Windows Server 2003 also includes a command line tool (Gacutil.exe) that can be used to edit the GAC.
The upgrade can also be done from the client because the Windows Server 2003 architecture allows you to create an automatic updated Windows and other applications. You can automatically download the program components from the Windows Server 2003 when running next time. Alternatively, the program can regularly check the polic policy file on the server to see if there is a updated version of the program.
Comment
The network administrator applies the above technique to achieve convenient and fast software management deployment, which is especially obvious in the network of more nodes. This can guarantee working schedules, reduce configuration costs, and do not affect work quality, avoid mistakes, and system software and application software in the entire network can control the administrator to efficiently implement the Windows. Server 2003 management management.
Ni
