Managing the Registry Then, when you run applications,
Managing the Registry Then, when you run applications, the applications store any changes you make to the default settings in the Registry. Beyond this, many administration tools are little more than friendly user interfaces for managing the Registry, especially when it comes to Control Panel. So, rather than having you work directly with a particular area of the Registry, Microsoft provides a tool that you can use to make the necessary changes safely and securely. Use these tools that s what they are for. Caution The importance of using the proper tools to make Registry changes cannot be overstated. If there s a tool that lets you manage an area of the Registry, you should use it. Don t fool around with the Registry just because you can. Making improper changes to the Registry can cause a system to become unstable, and in some cases, it could even make it so the system won t boot. As you can see, nearly everything you do with the operating system affects the Registry in one way or another. That s why it s so important to understand what the Registry is used for, how you can work with it, how you can secure it, and how you can maintain it. Understanding the Registry Structure The Registry is first a database. Like any other database, the Registry is designed for information storage and retrieval. Any Registry value entry can be identified by specifying the path to its location. For example, the path HKEY_LOCAL_MACHINESOFTWAREMicrosoft Windows NTCurrentVersionWinlogonAllowMultipleTSSessions specifies a Registry value that can be used to enable or disable the use of offline files with Terminal Services. Figure 14-1 shows this value in the Registry. Because of its hierarchical structure, the Registry appears to be organized much like a file system. In fact, its structure is often compared to that of a file system. However, this is a bit misleading because there is no actual folder/file representation on a system s hard disk to match the structure used by the Registry. The Registry s actual physical structure is separate from the way Registry information is represented. Locations in the Registry are represented by a logical structure that has little correlation to how value entries are stored. Unlike Windows 2000 and Windows NT, Windows Server 2003 supports larger Registry sizes than were previously possible and no longer keeps the entire Registry in paged pool memory. Instead, 256-kilobyte (KB) views of the Registry are mapped into system cache as needed. This is an important change from the original architecture of the Registry, which effectively limited the Registry to about 80 percent of the total size of paged pool. The new Registry implementation is limited only by available space in the paging file. Chapter 14 Part 4: Managing Windows Server 2003 Systems
If you are searching for cheap webhost for your web application, please visit MySQL5 Web Hosting services.