Table of contents
|
Abstract This chapter contains registry entries for all types of software, from Microsoft SQL Server to Netscape to Windows NT system information. In this chapter, you can find the details of customizing software for your particular users' needs. You will also find information that lets you troubleshoot problems that typically occur in a day-to-day IT environment. SMS 1.2 III-1 When SMS creates a package for distribution, it first compresses all the files in the package and then sends the package to the site server. The site server expands the compressed package into a Temp directory. By default, SMS creates the Temp directory on the biggest drive with at least 100 megabytes of available space. Changing this registry value lets you specify which drive SMS uses as the preferred drive. If the minimum conditions aren’t met (100 MB and NTFS), SMS searches for a more suitable drive.
Restart the machine for these values to take effect. III-2 SMS needs a directory to copy the decompressed package to. By default, it looks at the drive that contains the SMS_SHR and determines whether that drive has at least 100 MB of free space. If it does, SMS creates the SMS_PKGx directory there. SMS by default uses the NTFS volume with the most free space. To change the minimum drive space required for this process, change the following registry entry.
The value is in hexadecimal. Restart the machine for these values to take effect. III-3 Your most effective tools for troubleshooting SMS performance problems are the different service logs. These registry entries let you maximize the amount of logging SMS performs. By analyzing these logs, you can get a pretty good picture of where the SMS bottlenecks are on your system.
This value enables SMS to log its interactions with SQL Server. Restart the SMS Executive for this change to take effect.
This value enables SMS logging. When this value is set to 1, SMS logs the results for all SMS services. Setting this value to 0 disables logging. Restart the SMS Executive for this change to take effect. III-5 SMS stores individual packages in compressed form before it ships them for distribution. This entry gives you the location of important information about these packages. This information is incredibly useful when debugging site distribution problems.
SMS creates a key for each package. This key stays in the registry of the site server until the package is removed from the site server. See III-19 for more about SMS packages.
This value is the location where the compressed file for each job is stored; along with the directory, the value includes the filename in the format of JobID.wks. An example value is \\Machine_Name\SMS_SHRD\site.srv\ despoolr.box\store\< JobID >.wks. III-7 To change the number of inventory attempts SMS tries before rolling the client into another domain, change this registry value.
A common use for this value is when you upgrade SMS versions. If you inadvertently change the site code or site name, you can see problems. Reducing this value lets the clients roll over into the new domain faster. In effect, you are moving them from the old site to a new site.
When SMS cancels a job, it creates a key for each job under the CancelHistory key. The only value stored under these keys is the time stamp for when the job was canceled.
If you choose a server other than the site server to distribute a package, a key is created for each job under the Transfer Packages key. Under this key, you find a key for each server that has been designated to distribute the package.
This key stores information about the package.
This value determines where on the distribution server the site server copies the decompressed package files. The share is in the format SMS_PKGx, where x is a letter; for example, SMS_PKGD. III-12 This registry entry stores the name of the default servers that distribute SMS packages. This information is useful if certain servers are used as package servers when you do not want them performing this function.
You must restart the SMS services for these changes to take effect. III-13 Each of these values sets different aspects of SMS connections.
III-18 This registry entry stores a key for each SMS job that was canceled. If you can’t track the status of a particular job, be sure that it doesn’t have a corresponding key under the CancelHistory key.
In this example, NTL001 is a valid name for an SMS job. You need to know the name of the specific SMS job you want to track.
SMS creates a key for each job that is canceled. You can decipher the time stamp if you want, but the presence of a key means a job was canceled. III-19 This registry entry stores a key for each SMS Master package. This information lets you see different packages that have been created over time.
In this example, W_NTL00001 is a valid name for an SMS package. You need to know the name of the specific SMS package you want to track.
SMS creates a key for each job that is canceled. You can decipher the time stamp if you want, but the presence of a key means a job was canceled. PCANYWHERE32 III-20 Are you having either of these problems getting Windows NT to work with your PCAnywhere 7.0 client?
Add a 7.0 key after the pcANYWHERE key.
Add the System key after the 7.0 key.
SCHEDULE PLUS 7.0A III-22 To run your current Schedule Plus configuration in workgroup mode, change this registry entry.
Setting this value to 0 pops up a dialog box asking if you want to run Schedule Plus in workgroup mode. Exit Schedule Plus before changing this value. III-23 To find out where your critical Schedule Plus files are stored, check these two registry entries, which point you to their locations.
This value is the fully qualified path to your current Schedule Plus data file. Changing this value causes Schedule Plus to use data in the file contained in this value.
This value sets the fully qualified path to the current archive file. It is in the format ARCHIVEmmyy.SCD, where mm is the numeric representation of the month the data was archived and yy is the year. EXCHANGE INFORMATION STORE III-25 Do you need to tighten security on your Exchange Server? It is possible to force Exchange to assign specific TCP/IP ports to RPCs that access the directory or information store. By default, Exchange assigns ports randomly. To use a packet filter and force Exchange to use a specific port, change this registry entry.
Add the following values under the parameters key:
This change forces Exchange to use whatever port number you assign for access to the Directory Store.
Add the following values under the parameters key:
This change forces Exchange to use whatever port number you assign for access to the Information Store. Restart Exchange for either of these changes to take effect. III-27 Do you need to disable the circular logging Exchange Server 4.0 performs? If you have lots of disk and want to keep your logs for a longer time, use this registry entry to disable circular logging. You can disable circular logging for both the Directory Store and the Information Store.
Add the following values under the parameters key:
This change disables circular logging for the Directory Store.
Add the following values under the parameters key:
This change disables circular logging for the Information Store. Restart the Exchange server for either of these changes to take effect. III-29 If you need to find out where Exchange stores its files (information that’s very useful for moving files remotely or archiving files), the following registry values point you to the pertinent locations.
This value is where Exchange stores the log files for the Data Store.
This value is where Exchange stores the database file for the DSA (Directory Service Agent).
This value is where Exchange stores the hierarchy table file for the DSA.
This value is name of the temporary work file where Exchange stores the DSA.
This value is the directory where Exchange stores the temporary work file or files for the DSA.
This value is where Exchange stores the Information Store (IS) database file.
This value is the directory where Exchange stores the system log files.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Page: 1, 2, 3, 4, 5 |
next page  |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||