Table of contents
|
PRINTER SERVICE I-179 NT doesn�t use DOS-style interrupts in printing. If this feature causes you problems, enable them with this change.
Change the following value under the Windows key.
Reboot for this change to take effect. I-180 Your network contains a few Novell servers and you think printing is a pretty good job for them. The problem is that every time you print on that printer, you get a pop-up message telling you about your print job. To turn off the message, change the following registry entry.
Change the NetPopup value to 0; you may have to add it under the Providers key if it doesn�t exist. Reboot the machine for the changes to take effect. I-181 During installation, NT opted to use a slow drive for your print spooling. You have recently installed a bigger and faster drive and want to change the drive NT uses for print spooling By default, NT uses the %systemroot%\system32\spool folder. The following registry entry lets you specify an alternate path for all printers. Change the value for DefaultSpoolDirectory under the Printers key to your new path and directory.
SECURITY I-182 Are you worried that someone will see who logged into a system last? This registry entry disables that feature.
Add the following value under the WinLogin
Make sure you restart the machine for these changes to take effect. I-183 You want to add a corporate message or disclaimer before people log on to their machines. The next two registry entries let you display a message before the user logs on.
Change the following values under the Winlogon key.
I-185 If you have a Windows NT machine and you don�t really care about security, you can have the system log on for you automatically by modifying or adding the following registry entries. Set the DefaultDomain and the DefaultUserName to the domain and user name that you want the system to use to log on.
Next, add these two values:
Be sure to set the AutoAdminLogon value to 1. Remember, your system is now quite insecure. Anyone with access to the registry can read the password. NOVELL 4.0 I-186 If you have NetWare 4.0 servers on a network with Windows NT servers and you�re trying to synchronize user accounts via the Directory Service Manager for NetWare (DSMN), you may run into problems. First, make sure your NetWare 4.0 server is running in bindery emulation mode, then add the following registry value:
Restart the machine for this change to take effect. LOGON SCRIPTS I-187 If your logon scripts aren�t working correctly, you may want to verify the following value on your server � it�s the fully qualified path to the directory where the Logon Scripts are stored.
DOMAIN CONTROLLERS I-188 If you need to verify the list of trusted domains on a machine from a remote location, look at the following registry value.
I-189 If you are having database problems with your primary domain controllers (PDCs), you may want them to completely synchronize every time they boot. This value lets you control the behavior of individual domain controllers. Change the Update value to Yes.
I-190 If you apply large-scale changes to your domain user accounts all at once, you can cause network congestion. Tuning the following parameters can help reduce that congestion.
Add the ChangeLogSize value.
This value defines the size of the Change Log (%systemroot%\Netlogon.chg). The default value is 64K. Changing this value to the maximum 4 MB helps congestion on systems that are very volatile or frequently have large changes. In testing this value, we noted little impact on overall system performance.
Add the Pulse value.
The pulse value defines how often (in seconds) a pulse is sent to a backup domain controller (BDC) that needs to be updated with SAM or LSA changes. By default, the NetLogon service determines the optimal frequency for pulses. If you are doing lots of updates, you may need to increase this value. Frequent updates clog the network, and decreasing the value would reduce clog. However, decreasing the value means you could lose more data if your system crashes, because it�s been longer since a backup. The range is 60 to 172,800. Restart the server for this value to take effect.
Add the PulseConcurrency value.
This value determines the maximum number of concurrent pulses the PDC sends to BDCs. This value lets you control how many BDCs are being updated at any one time, which can reduce network traffic. I-193 This value determines the absolute longest interval that a BDC goes without receiving a request for update (pulse), even if the BDC is up-to-date.
Add the PulseMaximum value.
The default is 7200 seconds (2 hours). Reboot the machine for any changes to take effect.
Add the PulseTimeout1 value.
This value tells the PDC how long to wait before giving up on a BDC that has failed to respond. Once a PDC sends a pulse to a BDC, the BDC must respond within this time frame; if it doesn�t, it is considered unavailable. The PDC then sends a pulse to another BDC. If this value is set very high and you have many BDCs on your network, network updates can take a long time. However, if you have a heavily congested network, setting this value too low causes the PDC to give up on the BDC prematurely. The default value is 5 seconds, and the range is 1 to 120 seconds.
Add the PulseTimeout2 value.
This value determines how long a PDC waits for a BDC to finish replication. Even if a BDC has responded correctly to a pulse, it is still possible for BDCs to have problems during replication. If the PDC doesn�t hear from the BDC in the interval specified by PulseTimeout2, the PDC determines that the BDC is having trouble. The default is 300 seconds, and the valid range is 60 to 300 seconds.
When the BDC receives a pulse, it waits the number of seconds specified in the Randomize value before answering. You should keep this value small. If you tune the value in PulseTimeout1, remember to set the Randomize value smaller. If this value is not in the registry, Netlogon figures out the best value depending on server load. Restart the machine for any changes to take effect.
This value sets the frequency with which the PDC transfers data to the BDC and the amount of data it sends at a time. If the replication governor is set to 50, the BDC has a replication call pending only 50 percent of the time and uses a 64K buffer instead of the 128K buffer it uses for a 100 setting. A value of 0 causes Netlogon to never replicate, which gets the databases on the PDC and BDC completely out of sync. ENVIRONMENT VARIABLES I-198 If you want to set certain environment variables for all the users on a particular machine, try this registry entry.
Here you will find some environment variables such as ComSpec and Path. You can add more variables or change existing ones.
You must restart the machine for any changes to take effect. I-199 The default system font NT uses is not very readable on high-resolution displays. You can change the system fonts by editing the following registry values. You can substitute any .fon file from your %systemroot%\SYSTEM directory for the default fonts.
Restart your system for these values to take effect. I-202 When you reboot your Windows NT system, you sometimes get popup warning messages. Most of the time, these messages are very helpful and point to potential problems. However, when you are debugging a system, you often don�t need to be reminded each time. This registry entry disables these messages, including event errors.
I-203 When you�re debugging a server problem or configuring new systems, it is often expedient to have the system complete its boot process as quickly as possible. This registry entry lets you reboot the system without going through all the BIOS checks (i.e., perform a warm boot).
Reboot your machine for these changes to take effect. I-204 Holding down the shift key when Windows NT boots keeps any programs located in the Startup folders from executing. As an administrator, you may want these programs to execute for a variety of reasons. This registry entry lets you disable the option of holding down the shift key during the boot process.
A value of 1 enables the shift override mechanism. The default is 0. I-205 Do you want to disable the Autorun feature of the CD-ROM? Does it annoy you that every time you insert a CD, it runs its little splash screen and install program? This registry disables the Autorun feature.
Restart Windows NT for this change to take effect.
When this value is set to 0, it disables the automatic startup acceptance. This registry entry is used in conjunction with the Bootvrfy.exe program, which lets you verify the startup of a system from a remote system. To correctly implement the procedure, change the following keys and values as well. See the Windows NT Resource Kit for more information on this procedure.
Restart Windows NT for these changes to take effect. I-212 Do you need to reinstall Windows NT, but you�ve lost your CD Key? This registry entry stores the value.
Ignore the first five numbers. The next ten are your CD Key. Ignore the last five numbers, too. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Page: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 |
next page 
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||