Disk Management, Backup and Restoration, and Disaster Recovery (стр. 7 )

·  Message Queuing Internet Messaging. Message Queuing supports Internet Messaging, a feature that allows the sending of messages to queues on the Internet or an intranet. This is accomplished by introducing a URL-style format name DIRECT=HTTP://sitename\msmq\queuename. Message Queuing Internet/intranet messaging using URL-named queues requires configuration of the Internet Information Services.

·  Message Queuing Real-Time Message Multicasting. Message Queuing allows message delivery to IP multicast groups using the PGM IP multicast protocol. Two new operators are introduced: (1) a new queue formatname with syntax: "MULTICAST=<multicast IP address>[:<port address>]"; (2) a new queue property with a multicast address: MSMQQueueInfo. MulticastAddress.

Postscript on Message Queuing

Since Message Queuing and networking, the Active Directory, and other computer management topics are interwoven, we chose not to replicate much of that information here but instead provide a summary view of this application. When installing and deploying Message Queuing, refer to the latest release notes and appropriate sections in this book.

Message Queuing can be used to connect with Exchange Server. Additional information on this feature is available from online Help.

SYSTEM MANAGEMENT SERVER

System Management Server (SMS) 2.0 and 2003 are useful add-on products for system administration. It is one of three primary auxiliary management tools; the others are Application Center 2000 and Microsoft Operations Manager (described in the next section).

SMS is not part of the core Windows Server 2003 operating system, but some of its features can be very valuable in deployment and administration. Since SMS is an optional component, we provide a review of its key features rather than in-depth "how to" instructions. Despite its summary treatment here, however, SMS should be considered seriously for relatively large and complex enterprises.

The five primary SMS features that can be used effectively in the administration of a Windows Server 2003 enterprise are:

·  Software and hardware inventory gathering and management

·  Software installation and distribution

·  Remote tools

·  Software metering

·  Network diagnostics

System Management Server 2.0 depends on Microsoft SQL Server 6.5 or 7.0 (or later) to store and manage SMS data. SQL Server is available as an independent database. Whether you license SMS independently or as part of the BackOffice suite, you must still calculate the use and cost of installing a local or remote SQL Server.

System Management Server 2.0 supports administrative snap-ins to the Microsoft Management Console (MMC). SMS service pack 2 must be employed.

Software and Hardware Inventory

In Chapter 4 we underscored the importance of inventorying hardware and software as part of Server planning and deployment. SMS can streamline this necessary step by automatically collecting software and hardware data and creating a dynamic inventory database. Moreover, it permits filtering of information so that both global and very granular inventories can be maintained. Through the use of SMS, specific software versions can be obtained, which permits rapid evaluation of enterprise upgrade status. For example, the hardware inventory evaluates a system's components according to processor manufacturer, revision levels, and type.

Software Installation and Distribution

The problems associated with centralized software installation and distribution to a remote computer or groups of computers are greatly reduced by SMS because it automates and schedules installation for minimal impact on the end user. Through the use of SMS's software inventory features, it is possible to create what is known as collector groups. The system administrator should use these to gather systems with the same processor, user group, or existing software, and then, with this information in hand, apply specific software upgrades to define collector groups automatically. In this way, the inventory database is automatically updated.

The SMS installer creates application-specific scripts to support this distribution The SMS installer creates application-specific scripts to support this distribution process. Physical distribution can be direct to the client disk or through the posting of the application to a Web or FTP site.

Remote Administrative Tools

Using SMS, the system administrator can gain access to a remote client system and display the contents seeing exactly what is displayed on the user's end, the administrator can troubleshoot system problems. Moreover, an interactive chat feature permits the administrator and end user to discuss problems on screen. Client computer commands and applications can be executed with Remote Execute. Remote Boot restarts the client computer.

Software Metering

The software-monitoring feature is used primarily to manage licenses and identify unsupported or unregistered packages. Monitoring concurrent software usage throughout an enterprise makes it easy to determine if too many or too few licenses exist for a given software title. The monitoring tool is set to access and restrict use of applications by the individual user, user group, computer, quota, or license. Mobile users can also use it to check software licenses when not connected to the network.

Network Diagnostics

SMS extends Windows Server 2003 network administrative and monitoring with its network discover and trace functions. These functions provide a framework of the network structure in a dynamic enterprise environment by discovering and tracing network using SMS, a network topology map can be easily generated.

The Network Monitor is used primarily to troubleshoot a network by capturing packets or frames and "sniffing" them. The information revealed is then displayed and filtered. The system administrator can edit network packets (see Figure 17.9).

Figure 17.9. The SMS Network Monitor

MICROSOFT OPERATIONS MANAGER

Microsoft Operations Manager is the most recent of the optional management suites offered to support Windows 2000 and Windows 2003 servers. The focus of MOM is to provide event and performance monitoring. This product is particularly useful for administrators charged with monitoring Active Directory, Exchange Server, and SQL Server. The relatively open API has also permitted third parties to develop add-ons for cross-platform monitoring from within MOM. The primary architectural features touted by Microsoft include:

·  Enterprise-class scalability. MOM uses a three-tier architecture designed to handle hundreds of millions of fully redundant and load-balanced events per day.

·  Intelligent agents. MOM's agents are based on the rule sets defined by the administrators at a central console. The local agents filter, aggregate, and consolidate event streams. They will also trigger local actions.

·  Automated agents and rule deployment. MOM monitors Active Directory and Windows NT domains to automatically detect and report new servers, applications, and services. MOM loads only appropriate rule sets. Deployment of agents and rule sets can then be set to occur automatically. MOM updates local rule sets as applications are installed and removed.

·  Interoperability. The integration of Windows Management Instrumentation (WMI) and MOM allows the intake of a wide range of events and performance data from Windows Server 2003, Windows 2000, or Windows NT systems. Additionally, MOM can monitor SNMP event data (traps) for any specified devices. These SNMP trap messages can be generated as part of any defined rule and then delivered to a third-party SNMP management products like HP OpenView. Through the Syslog protocol, MOM can even monitor live events from UNIX systems and many network devices.

NOTE

It is important that administrators understand the relationship of the Microsoft optional management tools. Application Center 2000 performs the classic role of managing software applications and licenses. It is targeted at enterprises that manage Web-based and component-based applications. As described in the previous section, SMS provides change and configuration contrast, MOM delivers operational management functions for servers and applications. These products are designed to work in tandem and are generally a good investment for medium to large enterprises.

 

Microsoft Operations Manager Features

MOM uses the Microsoft Management Console by default to provide a consistent administrative interface. Through the MMC, status and configuration nodes should be snapped in along with other related management tools and applications. This allows administrators to move through the hierarchical tree to access events, rules, reports, and configuration activities. Additionally, MOM's MMC snap-in supports context-sensitive tasks directly from the Alert box or event being viewed. This means that tasks such as Terminal Services sessions or command-line functions can be launched directly from MOM.

DISTRIBUTE EVENT MANAGEMENT

MOM captures system and applications events from Windows-based systems distributed throughout the enterprise and aggregates them into a central event repository. This allows the administrator to consolidate events so that a view of server and service availability can be reviewed easily. In addition to event summaries, a detailed event stream can be obtained for specific troubleshooting activities.

ADMINISTRATIVE DEFINED RULES MANAGEMENT

Once established by the administrator, MOM reacts automatically to incoming message streams. The system can be configured to respond with a predefined action to a specific fault scenario. Alternatively, MOM will consolidate messages so the analysis can be made of broader based events. MOM's rules can be made to react intelligently to anticipated event patterns. These patterns trigger actions including sending alerts to the *****les may be linked to an event sequence of the Microsoft Knowledge Base articles, thereby providing guidance on probable causes and approved responses to a specific problem.

ALERT MANAGEMENT

Any MOM rule can be configured to generate specific alerts that are associated with severity levels. An alert can represent a single event or multiple events from many sources. One of the nicer features is the ability to trace the history of a given alert. The events can be associated and then used to consult related Knowledge Base articles. Functionally, alerts can trigger e-mail messages, pages, and Simple Network Management Protocol traps. Scripts can even be used to notify administrators of emerging problems.

PERFORMANCE MONITORING

MOM monitors key performance thresholds. Administrators customize and add rules that allow them to monitor trends of system and application performance. These reports are useful for historical reporting and capacity planning. Local and aggregated thresholds are also used to generate alerts and actions. As system changes occur or application behavior demands intervention, the appropriate alerts are broadcast.

GRAPHICAL REPORTING TOOLS AND WEB REPORTING

MOM provides access to a broad range of preconfigured reports and charts. This allows administrators to review at a glance the status of systems and services on the quickly reviewing clean graphical output, the administrator can plan changes to the infrastructure. Alternatively, MOM can generate HTML-based snapshots of all generated reports. Instead of using MMC, these reports can be exported to a Web server to provide access from Web browsers.

OPTIONAL MANAGEMENT PACKS

To reduce an administrator's burden, Microsoft offers management packs that consist of preconfigured MOM rule sets and Knowledge Base articles. Each pack provides rules for a specific range of applications or services. Developed and refined by experts, the management packs provide an off-the-shelf solution plus a strong foundation for advanced administrators to customize and extend basic MOM functionality.

Most management packs are optional, but several are included with MOM including one that enables management of critical Windows services such as Active Directory service and Internet Information Services. Additional management packs are available from Microsoft and third-party vendors. Among the products and services optionally supported are BackOffice and Windows Server 2003 enterprise applications, plus a wide range of enterprise applications.

WINDOWS SCRIPTING HOST

Windows Scripting Host (WSH 2.0) is a language-independent scripting engine used to automate administrative tasks, such as controlling network connections. WSH supports Windows 2000, Windows NT, and Windows 9x environments. The earlier version of WSH supported only Microsoft languages, such as Visual Basic VBScripts and JScript.

Microsoft and third parties are now providing WSH 2.0 with an augmented list of scripts to support other environments, including Visual Basic, Java, HTML, Perl, and XML. Previously, only Windows native scripts such as the MS-DOS command language were supported.

NOTE

An abundance of scripts is available on the Internet and from specialized programming books. We have included only a few scripts here because they tend to be enterprise-specific or task-specific. Instead, we provide an overview of WSH that should give you sufficient information to host your own scripts.

For readers who would like to create scripts, we recommend the Microsoft Windows Scripting Host Programmer's Reference site. A number of sample scripts can be downloaded from http://www. /scripting.

Using WSH to Run Scripts

There is both a Windows version and a command-line version of WSH. The Windows version (wscript. exe) provides the standard GUI interface to set properties. The command-line version (cscript. exe) uses switches to do this.

RUNNING WSCRIPT. EXE

Scripts can be launched within the Windows environment in several ways. In Windows Explorer, simply double-click the icon identified as a script, as shown in Figure 17.10. Alternatively, from the Start Run command line or the command prompt, enter the name of the script and click OK or Enter, respectively, as shown in Figure 17.11.

Figure 17.10. Launching a Script from Explorer

Figure 17.11. Launching a Script from the Run Command Line

Setting Properties for the Wscript. exe Environment

Two properties can be set for a Wscript. exe-launched script. From Windows Explorer right-click the targeted script and select Properties, where you will see two tabs for scripts residing on a FAT/FAT 32 partition and four available for NTFS—common to both are the General and Script tabs. From the General tab, you can set the script to assume a readable or hidden attribute. From the Script tab, you can automatically stop the script after the specified (nn) number of seconds, and you can display a logo banner. The two additional NTFS partition tabs are Security for setting user permissions and Summary, as shown in Figure 17.12.

Figure 17.12. The NTFS Partition Summary Properties Tab

When properties are set on a script, a text file with the. wsh extension on its name is created as a control file for the script's settings. The. wsh file uses the same name as the script and can also be used to launch the script in the manner just described.

Running Cscript. exe

The command-line version of WSH is launched from the command prompt. It uses the following syntax:

Cscript [script name] [host options] [script options]

The only required item is the script name. The host options enable or disable WSH options. The script options are passed directly to the script and are preceded by a single slash (/).

Table 17.1 lists the functions available for the Cscript. exe tool.

Table 17.1. Cscript. exe Host Parameters
Option	Description
//I	The default setting; permits interactive prompts and the display of errors.
//B	Batch mode; suppresses command displays and user prompts.
//D	Enables the debugger.
//E:engine	Specifies the script language engine.
//Job:xxx	Specifies a batch script to execute.
//T:nn	Enables a time-out on script execution after (nn) seconds.
//logo	The default; displays a logo banner.
//nolog	Suppresses the logo banner.
//H:C script or //H:W script	Registers which version of WSH is the default—C for cscript, W for wscript.
//S	Saves the command-line options.
/?	Displays command usage.

SAMPLE WSH SCRIPTS

Example 1: Programming with the Windows Scripting Host allows direct access to the Active Directory via Active Directory Services Interface (ADSI).

'Display Objects in the Engineering Organizational Unit

Set ou = GetObject ("LDAP://OU=Engineering, DC=Entcert1,DC=Com")

For each obj in ou

WScript. Echo obj. Name

Next

Example 2: Properties relating to the Scripting Engine and executing script are accessible through script and argument properties.

'Display Script Properties

wscript. Echo Wscript. Application

wscript. Echo Wscript. Arguments(0)

WScript. Echo Wscript. FullName

WScript. Echo Wscript. Name

WScript. Echo Wscript. Path

WScript. Echo Wscript. ScriptFullName

WScript. Echo Wscript. ScriptName

WScript. Echo Wscript. Version

' Display script argument properties

WScript. Echo Wscript. arguments. Count

WScript. Echo Wscript. arguments. length

WScript. Echo Wscript. arguments. Item

Example 3: Environmental parameters from four environments are accessible by setting the environment context.

'Create shell object

Set WshShell = Wscript. CreateObject("Wscript. Shell")

' Set variables environmental variable access

' of system, User, Volatile, process

Set SystemEnvironment = WshShell. Environment("System")

Set UserEnvironment = WshShell. Environment("User")

Set VolatileEnvironment = WshShell. Environment("Volatile")

Set ProcessEnvironment = WshShell. Environment("Process")

' Display example parameters from each environment set

wscript. Echo SystemEnvironment("PATH")

wscript. Echo UserEnvironment("PROMPT")

wscript. Echo VolatileEnvironment("OS")

wscript. Echo ProcessEnvironment("PROCESSOR_ARCHITECTURE")

Example 4: Advanced dialog window capabilities are available and based on Win32 user interface programming. The Registry may be read and modified through shell methods.

' Registry reading and writing

Set WshShell = Wscript. CreateObject("Wscript. Shell")

' Simple Popup window

WshShell. Popup "Test Popup Window"

' Popup Window with advanced options following Win32 conventions

WshShell. Popup "Test Popup Window",10, "SysAdmin Tool", 4

' Read from the systems registry

str = WshShell. RegRead ("HKCU\Environment\TEMP")

WshShell. Popup str

Example 5: The network functions allow drives and printers to be mapped to users and systems throughout the network.

' Network methods can be used to add and remove printers and network drives.

Set WshNetwork = Wscript. CreateObject("work")

' Print out computer name

Wscript. echo puterName

'Add a printer

WshNetwork. AddPrinterConnection"Laser"."\\ecc3s\HP Printer"

'Map a network drive

WshNetwork. MapNetWorkDrive "M:","\\ecc3s\aaECC"

'Display Username and domain

Wscript. echo WshNetwork. Username

Wscript. echo WshNetwork. UserDomain

Example 6: Shortcuts can be added to the desktop and assigned properties.

' Shortcut properties allow the modification of a shortcut's arguments, Description

' Hotkey, Iconlocation, TargetPath, WindowStyle and WorkingDirectory.

'

Set WshShell = Wscript. CreateObject("Wscript. WshShell")

strFavoritespath = WshShell. SpecialFolders("My Documents")

Set NewShortcut = WshShell. CreateShortcut(strFavoritespath & "\short. lnk)

NewShortcut. TargetPath = "path to application here"

NewShortcut. Save

POSTSCRIPT

This chapter discusses the concepts and base-level use of five relatively unrelated services. Since, unlike other Windows Server 2003 features, these services will not be applied universally by system administrators, we provide a summary, not a comprehensive review. If you will be employing these technologies, we hope this chapter provides the foundation necessary to do so. Use the release notes and online Help with these products to fill in the necessary details.

Appendix Windows Server 2003 Commands and Utilities

This appendix is designed as a reference tool for users and system administrators. It defines and discusses a number of procedures and commands with options that are used in the day-to-day operation of a Windows Server 2003 system. The appendix begins with a review of command-line options available for the first time in 2003. The other commands covered in the appendix are common to both Windows 2000 and Windows Server 2003 products. These commands and utilities are listed alphabetically in the index. Here they have been broken down into several categories, as follows:

·  Command-line features new to Windows Server 2003

·  Backup

·  Batch

·  Comparison

·  Compression

·  Display

·  File management

·  File manipulation

·  Miscellaneous

·  Networking

·  Ownership

·  Print

·  Search

·  System management

·  Resource Kit support tools

We distinguish procedures and commands in this way:

·  Procedures are methods for accomplishing a task using the Windows Server 2003 graphical interface.

·  Commands are executed within the command prompt, which invokes the Virtual DOS Machine (VDM).

In some cases, we provide both procedures and commands to give the system administrator a broader view of the capabilities of Windows Server 2003.

Within Windows Server 2003 two methods are available to review the file hierarchy: one uses the My Computer icon and its accompanying windows and the other uses Windows Explorer. We have chosen to focus primarily on Windows Server 2003 Explorer, which is accessed via Start Programs Accessories Windows Server 2003 Explorer. Procedures that can be completed using the My Computer windows will be referenced as appropriate. The command prompt is accessed via Start Programs Accessories command prompt. In this mode, Windows Server 2003 is not case-sensitive, so commands and their parameters and options may be entered in either lowercase or uppercase. Here lowercase is used as a matter of style. In addition, Windows Server 2003 has a series of what are referred to as "net commands." These commands assist the system administrator in maintaining the network and are distributed among the other sections where appropriate.

The following syntax conventions are used in the appendix:

·  Command names are lowercase.

·  Lowercase italic represents variables that must be replaced in the command. For example, filename must be replaced with the actual file name on which the command will operate.

·  [Brackets] surround optional parameters.

·  {Braces} surround a list of items, options, or parameters from which one must be chosen.

·  The pipe symbol ( | ) separates options from which one must be chosen. In this case, it works like an "or"; that is, you must choose one or the other.

Navigating the command prompt is very similar to working in a "dumb terminal" environment. Keystrokes are generally interpreted individually. Special shortcuts, known as doskeys, facilitate navigation. The following the keys are used most often:

·  UP ARROW recalls the command used immediately before the command that brought the current screen.

·  DOWN ARROW recalls the command used immediately after the command that brought the current screen.

·  PAGE UP recalls the oldest command used in the session.

·  PAGE DOWN recalls the most recent command used.

·  LEFT ARROW moves the insertion point back one character.

·  RIGHT ARROW moves the insertion point forward one character.

·  CTRL-LEFT ARROW moves the insertion point back one word.

·  CTRL-RIGHT ARROW moves the insertion point forward one word.

·  HOME moves the insertion point to the beginning of the line.

·  END moves the insertion point to the end of the line.

·  ESC clears the command.

·  F1 copies one character from the same column in the template.

·  F2 searches forward in the template for the next key typed after F2 is pressed.

·  F3 copies the remainder of the template to the command line.

·  F4 deletes characters from the current insertion point position up to the character specified.

·  F5 copies the template into the current command line.

·  F6 places an end-of-file character (CTRL-Z) at the current point.

·  F7 displays all commands for this program stored in memory in a pop-up box.

·  F8 displays all commands in the history buffer that start with the characters in the current command.

·  F9 prompts for a history buffer command number, then displays the command.

For more detail on a particular command or procedure, please refer to Windows Server 2003 Help, which can be accessed from the Start menu or from the window in which you are working.

NEW COMMAND-LINE TOOLS WITH WINDOWS SERVER 2003

Windows Server 2003 enhances the command-line functionality for administrators. This section highlights administratively useful command-line functions that are new or significantly changed. This section lists many but certainly not all of the new command-line tools available with Server 2003. Also, look for Microsoft to add command-line tools to subsequent Service Packs.

The following command-line tools are available via Start More Programs Accessories command prompt or via Start Run cmd. exe.

bootcfg Command

Bootcfg. exe provides the viewing or sets the properties of the boot. ini file on a local or remote server. This tool is not available on 64-bit versions of the operating system.

The following are examples of the bootfg command:

BOOTCFG /Copy /?

BOOTCFG /Delete /?

BOOTCFG /Query /?

BOOTCFG /Raw /?

BOOTCFG /Timeout /?

BOOTCFG /EMS /?

BOOTCFG /Debug /?

BOOTCFG /Addsw /?

BOOTCFG /Rmsw /?

BOOTCFG /Dbg1394 /?

BOOTCFG /Default /?

BOOTCFG /?

Table A.1. bootcfg Command Options
Option	Description
/Copy	Makes a copy of an existing boot entry [operating systems] section for which you can add OS options.
/Delete	Deletes an existing boot entry in the [operating systems] section of the Boot. ini file. You must specify the entry # to delete.
/Query	Displays the current boot entries and their settings.
/Raw	Allows the user to specify any switch options to be added for a specified boot entry.
/Timeout	Allows the user to change the timeout value.
/Default	Allows the user to change the default boot entry.
/EMS	Allows the user to configure the /redirect switch for headless support for a boot entry.
/Debug	Allows the user to specify the port and baud rate for remote debugging for a specified boot entry.
/Addsw	Allows the user to add predefined switches for a specific boot entry.
/Rmsw	Allows the user toremove predefined switches for a specific boot entry.
/Dbg1394	Allows the user to configure 1394 port debugging for a specified boot entry.
/?	Displays this help/usage.

bitscli Command

The Bitscli. exe program manages Background Intelligent Transfer Service (BITS) downloads.

choice Command

Choice selects an option from a menu for batch file execution. The choice command prompts the user to make a selection in a batch program. It displays a prompt and pauses for the user to choose from among a set of user keys such as Yes, No, and Continue. The syntax is

choice [/c choices] [/n] [/cs] [/t nnnn /d choice] [/m text]

clip Command

Clip. exe redirects command-line output to the clipboard from where it can be copied and pasted into graphical user interface (GUI) applications. To copy the list of contents in the c:\Windows folder onto the Clipboard, at the C:\Windows prompt type

dir | clip

compress Command

Compress. exe compresses one or more files into a cab file. The syntax is

compress [-r] [-d] [-zx] [-z] [-zq[n]] Source Destination

compress - r [-d] [-zx] [-z] [-zq[n]] Source [Destination]

Table A.2. choice Command Options
Option	Description
/c choices	Defines the user option keys. When displayed, they appear in brackets ([]), and are followed by a question mark. If you do not specify /c choices, choice. exe displays [Y, N] by default.
/n	Hides the user option keys.
/cs	Specifies case default, user option keys are not case-sensitive.
/m text	Specifies the text to be displayed before the prompt.