Professional Web Hosting, Perl Scripting And Developing Blog

Managing the Registry Windows Server 2003 resolves this problem by changing the way the Registry is stored in memory. Under the new implementation, 256-KB mapped views of the Registry are loaded into the system cache as necessary by the Cache Manager. The rest of the Registry is stored in the paging file on disk. Because the Registry is written to system cache, it can exist in system random access memory (RAM) and be paged to and from disk as needed. In previous versions of the Windows operating system, the operating system allowed you to control the maximum amount of memory and disk space that could be used by the Registry. With the improved memory management features of Windows Server 2003, the operating system has now taken over control of managing how much memory the Registry uses. Most member servers running Windows Server 2003 use between 20 and 25 MB of memory for the Registry. Domain controllers or servers that have many configuration components, services, and applications use considerably more. For example, one of my key domain controllers uses between 25 and 30 MB of memory for the Registry. Quite a change from the old architecture, when the in-memory requirements of the Registry could be up to 160 MB. To read the Registry you need a special editor. The editor provided in Windows Server 2003 is Registry Editor. By using Registry Editor, you can navigate the Registry s logical structure from the top of the database to the bottom. From the top down, the levels of the database are defined as root keys, subkeys, and value entries. Chapter 14 Inside Out Regedit replaces Regedt32 in Windows Server 2003 Unlike previous versions of the Windows operating system that included two versions of Registry Editor, Windows Server 2003 ships with a single version. This version, Regedit.exe, integrates all of the features of the previous Registry editors. From the original Regedit.exe it gets its core features. From Regedt32.exe, which is no longer available, it gets its security and favorites features. By using the security features, you can view and manage permissions for Registry values. By using the favorites feature, you can create and use favorites to quickly access stored locations within the Registry. Regedt32 really is gone although I, like many administrators, still refer to it. It is, after all, the editor administrators used because it gave us the ability to manage Registry security and it is the one that was recommended for administrators over Regedit. Because old habits die hard, Windows Server 2003 still has a stub file for Regedt32. However, if you run Regedt32, the operating system will in fact start Regedit. Part 4: Managing Windows Server 2003 Systems
We recommend you use shared web hosting services, because many users agree that it is cheap, reliable and customer-satisfying webhost.

Microsoft Windows Server 2003 Inside Out Value entries Chapter 14 Root keys Subkeys Figure 14-1. Accessing a value according to its path in the Registry. At startup, 256-KB mapped views of the Registry are loaded into system cache so that Windows Server 2003 can quickly retrieve configuration information. Some of the Registry s information is created dynamically based on the system hardware configuration at startup and doesn t exist until it is created. For the most part, however, the Registry is stored in persistent form on disk and read from a set of files called hives. Hives are binary files that represent a grouping of keys and values. You ll find the hive files in the %SystemRoot%System32 Config directory. Within this directory, you ll also find .sav and .log files, which serve as backup files for the Registry. Inside Out Windows Server 2003 manages the Registry size and memory use Windows NT and Windows 2000 store the entire Registry in paged, pooled memory. For 32-bit systems, this limits the Registry to approximately 160 megabytes (MB) because of the layout of the virtual address space in the operating system kernel. Unfortunately, in this configuration as the Registry grows in size it uses a considerable amount of paged, pooled memory and can leave too little memory for other kernel-mode components. 412 Part 4: Managing Windows Server 2003 Systems
In case you need quality webspace to host and run your web applications, try our personal web hosting services.

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.

Microsoft Windows Server 2003 Inside Out Introducing the Registry The Registry is written as a binary database with the information organized in a hierarchy. This hierarchy has a structure much like that used by a file system and is an inverted tree with the root at the top of the tree. Any time the operating system must obtain system default values or information about your preferences, it obtains this information from the Registry. Any time you install programs or make changes in Control Panel, these changes usually are written to the Registry. Chapter 14 Note I say usually because in Windows domains some configuration information is written to Active Directory. For example, beginning with Microsoft Windows 2000, information about user accounts and network objects is stored in Active Directory. In addition, when you promote a member server to a domain controller, key Registry settings that apply to the server, such as the default configuration values, are transferred to Active Directory and thereafter managed through Active Directory. If you were later to demote the domain controller, the original Registry settings would not be restored either. Instead, the default settings are restored as they would appear on a newly installed server. The Registry s importance is that it stores most of a system s state. If you make preference and settings changes to a system, these changes are stored in the Registry. If a system dies and cannot be recovered, you don t have to install a new system and then configure it to look like the old one. You could instead install Windows Server 2003 and then restore a backup of the failed system s Registry. This would restore all the preferences and settings of the failed system on the new system. Although it s great that the Registry can store settings that you ve made, you might be wondering what else the Registry is good for. Well, in addition to storing settings that you ve made, the Registry stores settings that the system makes as well. For example, whenever a system boots, it uses Ntdetect.com to take an inventory of its hardware, and then stores this information in the Registry. The operating system kernel in turn uses this information, read from the Registry at startup, to determine which device drivers to load and in which order. The kernel also stores information needed by those drivers in the Registry, including the driver initialization parameters, which allows the device drivers to configure themselves to work with the system s hardware. Many other system components make use of the Registry as well. When you install Windows Server 2003, the setup choices you make are used to build the initial Registry database. Setup modifies the Registry whenever you add or remove hardware from a system. Similarly, application setup programs modify the Registry to store the application installation settings and to determine whether components of the application are already installed. 410 Part 4: Managing Windows Server 2003 Systems
Looking for affordable and reliable webhost to host and run your business application? Then look no more and go to servlet web hosting services.

Chapter 14 Managing the Registry Introducing the Registry . . . . . . . . . . . . 410 Managing the Registry. . . . . . . . . . . . . .425 Understanding the Registry Backing Up and Restoring Structure. . . . . . . . . . . . . . . . . . . . . . . . 411 the Registry . . . . . . . . . . . . . . . . . . . . . .434 Registry Root Keys . . . . . . . . . . . . . . . . 414 Maintaining the Registry . . . . . . . . . . . .437 Registry Data: How It Is Stored Securing the Registry. . . . . . . . . . . . . . .441 and Used. . . . . . . . . . . . . . . . . . . . . . . . 423 Everyone who accesses a computer, whether in a workgroup or on a domain, at one time or another has worked with the Microsoft Windows Registry whether the person realizes it or not. Whenever you log on, your user preferences are read from the Registry. Whenever you make changes to the system configuration, install applications or hardware, or make other changes to the working environment, the changes are stored in the Registry. Whenever you uninstall hardware, applications, or system components, these changes are recorded in the Registry as well. The Registry is the central repository for configuration information in Microsoft Windows Server 2003. Applications, system components, device drivers, and the operating system kernel all use the Registry to store settings and to obtain information about user preferences, system hardware configuration, and system defaults. The Registry also stores information about security settings, user rights, local accounts, and much more. Unlike Microsoft Windows NT, in domains, it no longer stores information about domain accounts or network objects because the related settings are managed by the Active Directory directory service as discussed in Part 7, Managing Active Directory and Security. With so much information being read from and written to the Registry, it is not only important for administrators to understand its structures and uses, it is essential. You should know the types of data the Registry works with, what type of data is stored where, and how to make changes if necessary. This is important because often when you must fine-tune system configuration or correct errors to stabilize systems, you ll be instructed to access the Registry and make such and such a change. Generally, the instructions assume you know what you re doing. Unfortunately, if you attempt such a change and really don t know what you re doing, you could make it so the system won t boot at all. So, with this in mind, let s look at how the Registry works and how you can work with it. Part 4: Managing Windows Server 2003 Systems
We highly recommend you visit web and email hosting services if you need stable and cheap web hosting platform for your web applications.

Managing Windows Server 2003 Note Using full file paths ensures menu items are opened and displayed as quickly as possible. Neglecting or removing the file paths slows the open and display process considerably. 4 Click OK to save your changes. Now whenever you use the menu item, Run As will start automatically using the specified user, and all you must provide is a password. Rather than having to enter a password each time, you can also add the /Savecred parameter. This parameter saves the credentials in the user profile using encryption. However, if you decide to use the /Savecred parameter, you should ensure that you don t leave yourself logged in when you step away from your computer or that your computer quickly turns on the password-protected screen saver. Otherwise, anyone could access your computer and run administration tools using your logon. Chapter 12 Part 4: Managing Windows Server 2003 Systems
If you are in need for chaep and reliable webhost to host your website, our recommendation is http web server services.

Microsoft Windows Server 2003 Inside Out 4 Type a name for the shortcut, such as Computer Management. Click Finish. Now whenever you use the shortcut, Run As will start automatically using the specified user account and all you need to provide is a password. Creating Run As Menu Options To create menu options that use RUNAS, follow these steps: 1 Navigate the Start menu until you find the menu item you want to modify, right- click it, and choose Create Shortcut. Then right-click the newly created menu item shortcut, and select Properties; it should have the same name as the original menu item with a 2 in parentheses. This displays a Properties dialog box similar to the one shown in Figure 12-11. Figure 12-11. Modify the menu item so that it automatically starts Run As. 2 In the Target box, enclose the existing command in double quotations. If you are modifying a console tool, add %SystemRoot%System32mmc.exe to the beginning of the Target box, and then enclose the entire command string in double quotation marks, such as %SystemRoot%System32mmc.exe %SystemRoot%System32 compmgmt.msc . 3 Precede the command string with the full path to Runas.exe, and use the User parameter to specify the user account you want to log on as, such as %System- Root%System32runas.exe /user:CPANDLsysadmin. The result should be something like %SystemRoot%System32runas.exe /user:CPANDLsysadmin %SystemRoot%System32mmc.exe %SystemRoot%System32compmgmt.msc . Chapter 12 374 Part 4: Managing Windows Server 2003 Systems
If you are searching for cheap webhost for your web application, please visit MySQL5 Web Hosting services.

Managing and Troubleshooting Hardware As a last resort, you can change the resource settings manually for some devices in Device Manager. In the Resources tab, shown in Figure 13-11, select the resource type that you want to work with. If you can make a change, you should be able to clear the Use Automatic Settings option and then see whether any of the alternate configurations in the Setting Based On box resolve the conflict. Keep in mind that you are now manually managing the resource settings. To allow the Windows operating system once again to manage the settings automatically, you must select Use Automatic Settings. Chapter 13 Figure 13-11. For legacy devices, you can use a different configuration to see whether this resolves a conflict. 407 Part 4: Managing Windows Server 2003 Systems
We recommend you use shared web hosting services, because many users agree that it is cheap, reliable and customer-satisfying webhost.

Microsoft Windows Server 2003 Inside Out Chapter 13 Figure 13-10. Use System Information to check for resource conflicts. You can try to resolve resource conflicts in several different ways. Some devices use jumpers to manage resource settings, and in this case, the operating system cannot control the resource settings. To make changes, you must shut down the computer, remove the device, change the jumper settings, and then replace the device. In some cases, the jumpers are managed through software rather than an actual jumper switch. Here, you would use the device setup or configuration utility to change the resource settings. For PCI devices, you can try swapping the cards between PCI slots. This will help if the IRQ or other resource settings are assigned on a per-slot basis, as is the case with some motherboards. You might be able to check the motherboard documentation to see which IRQ interrupts are assigned to which slots. In any case, you ll need to experiment to see which card configuration works. For PCI devices, a conflict could also be caused by the device driver and the way it works with the ACPI BIOS. You should check to see whether an updated device driver and a BIOS update are available. Installing one or both should resolve the conflict. 406 Part 4: Managing Windows Server 2003 Systems
We recommend high quality webhost to host and run your jsp application: christian web host services.

Managing and Troubleshooting Hardware Chapter 13 Figure 13-9. View resources by type or resources by connection to check resource settings in Device Manager. Another way to check for conflicts is to use the System Information utility (Msinfo32.exe). Start the System Information utility by clicking Programs or All Programs, Accessories, System Tools, and then System Information. In System Information, expand Hardware Resources, and then select Conflicts/Sharing. As shown in Figure 13-10, a list of all resources that are in use is displayed. Again, keep in mind that devices can share IRQ settings thanks to ACPI, so what you are looking for are two unrelated devices sharing the same memory addresses or I/O ports, which would cause a conflict. Keep in mind related devices can share memory addresses and I/O ports. In the example, the Standard VGA Graphics Adapter and the Intel 82845 Processor to AGP Controller share the same memory addresses and I/O ports. That s okay because they are related. The PCI Bus is using a memory address space with these devices as well, which is as it should be because Standard VGA Graphics Adapter and the Intel 82845 Processor to AGP Controller are both PCI devices. 405 Part 4: Managing Windows Server 2003 Systems
Check Tomcat Web Hosting services for best quality webspace to host your web application.