Windows 2000 zero Management

Introduction

Today's computer is becoming increasingly popular in business, and the tight IT budget has led many large companies to focus more on how to reduce TCO (total cost of owneership. Therefore, it is necessary to build an enterprise's information system to consider comprehensive and long-term computing solutions and to adapt to all organizations. Microsoft is committed to meeting these needs through Microsoft's customer policies. These policies will provide customers with a complete solution that can solve the core issue today-how to reduce TCO and increase ROI. Microsoft uses these solutions to maximize protection for customers' investments. At present, Microsoft's TCO reduction strategy has two main parts: Zero management and network PC specifications. Zero management is an important part of Microsoft's customer policy. IT uses a series of core technologies that give IT experts new control capabilities and convenient management of Windows-based clients. This capability is mainly implemented through automatic tasks, such as operating system upgrades, application installation, centralized management tools, and desktop system locking. These technologies enable users to no longer need to reinstall their applications and files when roaming between different PCs, thus reducing the workload of ordinary users, at the same time, problems caused by incompatibility of applications are greatly reduced. Zero management makes software installation of applications more convenient and can develop more extensive applications. All of these benefits do not have to sacrifice compatibility with existing Windows-based software.

Zero management capabilities:

Automatic System Upgrade and application installation
Persistent cache data and configuration information
Centralized management and system lock
Best solutions for application elastic adaptation Design
Automatic System Upgrade and application installation

Previously, software installation and maintenance were cumbersome and error-prone. In zero management, this process is completely automated and thus very simple. When you install a system component, a device driver, or a new version of the operating system, Windows 2000 can be configured to automatically upgrade the software. The system automatically guides and checks all Internet/Intranet updates. If you find a software to be upgraded, You can automatically upgrade it without interfering with the system. For example, if a user opens a wordfile, but a file (such as winword.exe) of the wordruntime is deleted, the system will automatically reinstall the file. In fact, zero management means that users do not need to perform management. The ability to establish a centralized policy means that the group's member users will have consistent hardware and software configurations, so they can eliminate the inconsistent components in a system from the technical support. Backup, search for viruses, and check for expired files are all performed on the server. The administrator can also prevent users from installing apps that are not clean (it will cause viruses or incompatible Dynamic Link Libraries and delete files they should not delete ). The entire system is protected to reduce the possibility of user errors. Zero management reduces the management burden on software and hardware. From a central server, the administrator can remotely install the operating system on the user's computer. This operating system can run an installation service by defining a software package for each application. When the File Installation starts, a system database will automatically track and find out who the application belongs to and where it is installed on the user's computer, as well as the version number and dynamic link library parameters. History records allow you to easily recycle an unsuccessful installation, reverse installation, or re-build a computer that is lost or damaged (especially for a notebook. It prevents the shared dynamic link library from being accidentally deleted by the reverse installation of other applications. It can also be used as an automatic upgrade trigger. When a user performs system boot, it checks the version number and application of the user's operating system based on the management policy. If an upgrade is required, it starts automatically. Users do not need to care about new software installation

Centralized management tools

Centralized Management tools are called Microsoft Management Console (MMC ). Microsoft tools and tools from other software vendors can be easily integrated into this console. The goal is to allow the Administrator to create a simple custom interface that can complete their own management work. This includes large hosts, computers, and common network operating systems. Just like managing Windows and Windows NT. In Windows 2000, MMC is integrated with Active Directory, which provides a simple place to monitor and access all management objects. With MMC, administrators can track and configure users and resources stored in AD. Through other distributed services in Windows 2000: Distributed Security, distributed file system, and distributed time sharing, AD can make separate physical servers act like a server, whether these servers exist in the same room or are distributed across multiple locations. Windows 2000 provides the required tools for administrators to centrally manage the entire physical network topology and its logical view (operations on the domain tree and all directory objects) in the Active Directory ). Therefore, even if the number of servers in a network increases significantly, the management burden does not increase.

Centralized management and system lock

In many organizations, users control their PCs and have the ability to install any hardware and software they are willing to install. When this level of control can meet user needs, it will lead to no two PCs in a system. To solve this problem, Windows 2000 enforces certain functions in some environments (for example, you are not allowed to install some software on your own ). Windows 2000 provides a variety of devices that are invisible to users. In the user's view, it is just a simple drive letter. In addition, any file that is not required by the user, such as a system file, will prevent tampering and unintentional destruction through the security of Access Control Lists (ACLs. Administrators can centrally control the application environment. They can specify the applications that users can access and perform detailed control on the premise that the user's environment needs are met. When integrated with Network PC Specification, IT administrators can restrict users to reconfigure the hardware environment to ensure hardware consistency and compatibility.

Persistent cache data and configuration information

Previously, in order to be able to install applications on a specified PC, they (applications) stored status and configuration information through the registry on the local PC. This will cause problems in a network environment, because these users can only access their applications and tools through their own computers rather than elsewhere. Win95 and NT Workstation use the user roaming configuration file to implement the system environment, but cannot locate the application configuration information. In zero management, the local PC status is automatically mapped to the server. This persistent cache ensures high data availability and allows mobile users to access information online and offline. In addition, users can roam between PCs and keep full use of their data, applications, and custom environments. In addition, if a user's hard disk is broken or the PC is broken, it is very easy to restore it, and there is no need to reinstall the application, configure the user's configuration file and other data.

Flexibility in designing the best solution applications

The Internet has divided business applications into three categories: database and backend servers are used to centrally store data, and intermediate devices implement logical and physical roles, finally, some thin clients, such as browsers, exchange information. Using this model, complex logic and data storage and maintenance can be centrally monitored by experts without end users having to perform configuration and management tasks, just give them the data they need. Zero management is closely integrated with three-layer development models on a complete open platform, allowing developers to develop HTML, open scripts, structural components, and background services. This allows you to use the integrated Microsoft Internet javase Shell as the user interface, and supports the development of service-based applications through the Windows NT Server and BackOffice family products. Developers and administrators can develop network-based thin client applications as flexible as developing personal products and client server applications on today's windows. When combined with other zero-management applications, the administrator can precisely adjust the environment of each user to meet their accurate needs and make changes according to business needs. Although the advantages of the operating system are introduced here, applications also need to adjust their behaviors to avoid wasting their TCO. For example, programmers should create plug-ins so that their applications can be managed in MMC, and they should use the latest API. Through Active Directory Service Interfaces (ADSI), an application can store the user's configuration information and the application's own configuration information. This allows users to access their custom environments at any time without considering which computer they log on. Storing configuration information in the directory also makes it easier for administrators to upgrade and change resources, such as database servers and printers, without upgrading the user configuration files or computers of each user. Most of the zero-management capabilities and remote automatic installation of applications need to be executed in an environment that requires locking (rather than being easily modified. The current application faces few restrictions. You can copy files to a user's system, and the user's configuration information (mobile) and computer configuration information (fixed) is also mixed together. Microsoft has been committed to setting clear guidelines for developing applications for Independent Software Vendors (ISVs. In zero management, application installation becomes an operating system service. Each application must create a software package for installation to install the service. Fortunately, it is easy to create such a Software package, even without programming. You only need to use a tool in the Windows Software Development Kit (SDK.