1. Verifying Application and Role Status Using the OCList Utility
The OCList utility
provides the means of determining the installation status of roles and
features on your server. Since there isn't any other way of determining
installation status, you need to use this utility to track component
information. Always use this utility before you install or uninstall a
role or feature to ensure the role or feature is actually in the state
you expect. This utility doesn't have any command line switches. You
simply type OCList and press Enter to obtain the status information, which may require a few seconds to appear on screen. Figure 1 shows typical output from the OCList utility.
2. Adding and Removing Servers with the RegSvr32 Utility
Your machine has a
wealth of Component Object Model (COM) servers installed on it. These
servers perform a broad array of tasks too numerous to mention here. In
all cases, these servers make a lot of registry entries; even a simple
server makes a lot of entries and you won't want to add or delete them
manually. Fortunately, the RegSvr32 utility makes it easy to add and
remove COM server entries. This utility uses the following syntax:
RegSvr32 [/u] [/s] [/i[:Arguments] /n] Filename
The following list describes each of the command line arguments.
Filename
The name of the file
that contains the COM server. In most cases, the file will have a DLL
extension, but it could have a number of other extensions including EXE
and OCX.
/u
Unregisters a server.
/s
Suppresses any informational messages. Using this option lets you create an installation batch file.
/i[:
Arguments]Calls a special
function within the COM server named DllInstall. You may optionally pass
command line arguments. The server vendor provides you with a list of
command line arguments that you can pass the COM server.
/n
Suppresses
the call to the standard DllRegisterServer function within the COM
server. This special function normally registers the server for you,
making all of the required registry entries. You can only use this
command line switch with the /i switch.
3. Managing Compatibility Databases with SDBInst
The SDBInst utility
helps you manage and maintain application databases. In fact, these
databases often support application patches. Microsoft often uses the
SDBInst utility to provide patches for all their products including
Office and Windows. As an example of one of these patches (and there are
many) check the Knowledge Base article at http://support.microsoft.com/?kbid=328597. Lest you think that this utility is a Microsoft invention, check the MySQL Web site at http://dev.mysql.com/doc/maxdb/en/1f/906b3c12904d04e10000000a114084/content.htm.
You'll notice that not only does SDBInst have a place in other vendor
application deployments, it exists on both the Windows and the Linux
platforms (as shown by the instructions for both platforms on the Web
site) as well.
The SDBInst program
supports a special Solution Database (SDB) (or Support Database) file.
Many vendors provide utilities for creating these files. For example,
you'll find the instructions for producing SDB files using a utility
from SoftwareBisque at http://www.bisque.com/tom/Createown/SDB/sdb.asp.
You can use SDBInst to
install and uninstall SDB files. Uninstalling an SDB usually results in
removing the patch that you applied to an application or operating
system. This utility uses the following syntax (the first syntax
installs a file, while the second uninstalls it):
SDBInst [-q] SDBFilename
SDBInst [-q] [-u SDBFilename] [-g GUID] [-p] [-n "Name"]
The following list describes each of the command line arguments.
-q
Forces the utility to rely on quiet mode. The utility doesn't display any dialog boxes to the user.
SDBFilename
Specifies the name of the SDB file that you want to install on the system.
-u
SDBFilenameSpecifies that you want to uninstall an SDB patch using a reference to the original SDB file.
-g
GUIDSpecifies that you want to uninstall an SDB patch using the GUID of the patch as defined in the registry.
"Name"
Specifies that
you want to uninstall an SDB patch using the patch name. The patch name
often appears in the Add or Remove Programs dialog box that you can
access using the Add or Remove Programs applet in the Control Panel.
-p
Allows SDB files to contain patches.
4. Configuring Windows Error Reporting with ServerWEROptin
The
ServerWEROptin utility lets you adjust error reporting for your Server
Core setup. The default setting sends information about every error your
server encounters automatically. Of course, you might not want
Microsoft knowing about every error or you may simply not have this
server connected to the Internet. In these and other situations, you'll
want to adjust your error reporting strategy. You can learn more about
the information Microsoft collects about your server at http://go.microsoft.com/fwlink/?linkid=50163. This utility uses the following syntax:
ServerWerOptin /q[uery] | /s[ummary] | /de[tailed] | /d[isable]
You can only use a single command line switch. The following
list describes each of the command line arguments.
/query
Displays the
Windows error reporting status. For example, if you disable the error
reporting, then the output says disabled. This command line switch also
provides the latest URL you can use to learn more about this utility and
the error reporting feature.
/summary
Configures the
error reporting feature to send summary reports automatically. A summary
report contains only the most basic error information and it's the safe
option to use when you want to provide information to Microsoft, but
want to keep the information you provide to a minimum. You set this
level of error reporting by typing ServerWEROptin /summary and pressing Enter.
/detailed
Configures the
error reporting feature to send the maximum amount of information to
Microsoft. This is the option you should use on less critical servers
that don't contain confidential information that you're concerned about
compromising. Although Microsoft does guarantee your privacy, you'll
still only want to use this option on less critical servers to prevent
accidental data revelations. You set this level of error reporting by
typing ServerWEROptin/detailed and pressing Enter.
/disable
Disables
the error reporting feature on the server. This is the option to use if
you have any doubts as to how Microsoft collects or uses the
information you provide. It's also the option you should select if your
server doesn't have an Internet connection. You set this level of error
reporting by typing ServerWEROptin /disable and pressing Enter.
