Table of contents
This value is where Exchange stores the log files that are
created during a POP3 transaction.
This value is the working system directory for Exchange.
This value is the location of the database for the Exchange private store. NOVELL NETWARE You can enable your Windows NT client to log on to your Novell server unattended. If you do, your server is no longer secure; however, you can do it. Change these entries to give the Novell client a default server, user name, and password to use for unattended logon.
Add the following value under the Parameters key:
Add the following value under the Parameters key:
Add the following value under the Parameters key:
Add the following value under the Parameters key:
Add the following value under the Parameters key:
Add the following value under the Parameters key:
NETSCAPE 3.0 III-45 If you want to fiddle with the Netscape Navigator bookmark file or address book, these registry entries show you where the values are stored.
You can change the names of these files or verify that a particular registry entry points to the correct files. This information is very useful in debugging missing bookmarks and address books or creating a common set of bookmarks and address books to distribute. III-49 If Netscape Navigator’s caching feature doesn’t work properly, be sure these registry entries refer to the correct directory for caching and match the settings displayed on the navigator administration screens.
This value is the directory where Navigator stores cached images and files.
This value shows how much disk space Navigator can use to store cached information.
This value determines whether Navigator caches Secure Socket Layer (SSL) pages.
This value determines how much memory Navigator uses to keep objects cached. CITRIX WINFRAME III-53 If your Winframe server runs certain applications slowly, don’t fret. WinFrame is actually trying to do you a favor — it spots bad software and tries to reduce the resources it allocates to these bad applications. To modify this feature, change these registry entries.
Add a key under the Applications key with the name of your applications.
Add the following values under the key you just created (whatever you called your myapp key).
Restart the machine for these changes to take effect. RIGHTFAX III-57 If your client gets an RPC error message when using RightFax, you need to make sure that both the client and the server machines are using the same maximum IPX packet size. This registry entry lets you set the size.
If the value is not present or the data is set to 0, it is up to the network adapter to set the MaxPktSize. You need to consult your user manual for your specific network card. III-58 To test RightFax without installing a fax card, try this registry entry.
Now you can simulate fax operations without having any hardware installed. III-59 To change the separator value for an e-mail or fax address, use the following registry entry.
Restart the gateway for this value to take effect. HOTSYNC 1.1 Are you having problems updating from HotSync 1.0 to 1.1? You may need to delete these registry keys for the new version to install properly.
After deleting these keys, install the new version of HotSync. MICROSOFT INDEX SERVER
This value determines whether Microsoft Index Server filters both the contents and properties of a file or only the properties of the file. A value of 0 specifies that the contents are not filtered. Otherwise, the contents and properties are both filtered.
This value specifies, in minutes, a period during which the CiDaemon process should provide an appropriate response. The CiDaemon might time out by trying to index a corrupt file.
This value identifies whether Index Server filters directories for system properties and displays them in query results. When this value is not 0, directories are filtered.
This value identifies whether Index Server filters files with extensions that have not been registered. When this value is set to 0, only registered file types are filtered.
This value identifies the maximum number of times Index Server tries to filter a file if the initial attempt to filter the file fails.
This value identifies the time, in minutes, between forced scans on directories with no notifications.
This value controls the automatic generation of file characterizations (abstracts).
This value controls whether Index Server automatically indexes all virtual roots within Internet Information Server.
This value identifies the default directory that contains the content index catalog.
This value identifies the maximum number of cached queries.
This value identifies the maximum number of rows to fetch for a single query.
This value identifies the maximum number of rows that are returned in a single fetch (get) operation. You can combine multiple fetches to make up a result set.
This value identifies the time interval during which a query cache item remains active.
This value identifies the maximum number of Web query requests to queue during periods of high server activity.
This value specifies a number of threads per processor; when processors reach this threshold, remaining query requests are queued.
Each key in this section associates a virtual server with a specific catalog. The key name is the IP address of the virtual server (NULL is used for the default server), and the value is the location of the catalog as you would enter it in the CiCatalog parameter of an .idq file.
This value identifies the interval at which Index Server conducts checkpoints during master merges. This parameter determines how often data is written to the new master index and is critical when a master merge is paused and restarted.
This value specifies when a master merge occurs. This value is the number of minutes after midnight.
This value identifies the maximum number of asynchronous query threads that are processed concurrently.
This value identifies the maximum number of characters in the automatically generated characterization (abstract).
This value identifies the maximum size of a single file filtered with the default filter. If a file exceeds this size, only file properties are filtered. This limit does not apply to registered file types; that is, to those file types that do not use the default filter.
This value identifies the maximum amount of data that can be generated from a single file, based on its size. This value is a multiplier used in conjunction with the current file size to determine the maximum file size after content indexing. For example, a value of 2 means that a file can generate up to 2 times its size in content index data.
This value identifies the maximum number of newly indexed files that cause a master merge to start.
This value identifies the maximum number of indexes considered acceptable in an ideal system. If the number of indexes exceeds this value and the system is idle, an annealing merge brings the total count of indexes to this number.
This value identifies the maximum number of persistent indexes in the catalog. If this number is exceeded, a shadow merge brings the total below this number.
This value identifies the sleep time between merges. Index Server often activates this to determine whether an annealing (most common), shadow, or master merge is necessary.
This value identifies the maximum number of pending documents that are filtered before the content index is considered out-of-date for property queries.
This value identifies the maximum execution time of a query. If a query takes more than this amount of CPU time, its processing is stopped and an error is returned.
This value identifies the maximum time allowed for Index Server to execute a query in a single CPU time slice. If more asynchronous queries are active than allowed query threads, Index Server puts a query back in the pending queue after this time interval. CPU time slicing is performed only after a matching row is found, so the time spent in a time slice may overrun this and a considerable number of rows may be examined in the time slice.
This value identifies the maximum number of in-memory buffers (queue chunks) allotted to keep track of pending documents. The higher the number, the less frequently the memory buffers are written to disk. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Page: 1, 2, 3, 4, 5 |
next page  |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||