Administering Microsoft Windows Server 2003 in Visual C#

Print ANSI/AIM Code 39 in Visual C# Administering Microsoft Windows Server 2003

2

Off the Record Spend a few minutes analyzing your daily tasks and group them by type of function and frequency of use. Build two or three customized consoles that contain the tools that you use most often. You will save quite a bit of time not needing to open, switch among, and close tools as often.

Console options determine how an MMC operates in terms of what nodes in the console tree may be opened, what snap-ins may be added, and what windows may be created. You configure console options in the Options dialog box, which you can open by clicking Options on the File menu.

When you save a console in Author mode, which is the default, you enable full access to all of the MMC functionality, including:

Adding or removing snap-ins Creating windows Creating taskpad views and tasks Viewing portions of the console tree Changing the options on the console Saving the console

If you plan to distribute an MMC with specific functions, you can set the desired User mode and then save the console. By default, consoles will be saved in the Administrative Tools folder in the users profile. Table 2-2 describes the user modes that are available for saving the MMC.

Table 2-2

Type of User Mode Description Full Access Limited Access, Multiple Windows Limited Access, Single Window Allows users to navigate between snap-ins, open windows, and access all portions of the console tree. Prevents users from opening new windows or accessing a portion of the console tree but allows them to view multiple windows in the console. Prevents users from opening new windows or accessing a portion of the console tree and allows them to view only one window in the console.

MMCs, when saved, have an *.msc extension. Active Directory Users And Computers, for example, is named Dsa.msc (Directory Services Administrator.msc).

Create administrative consoles for your administrators by saving customized consoles, optionally in a restricted User mode, and distributing the resulting .msc files. Any snap-in used in a custom console must be installed on the system. This means, for example, that you must have installed the Windows Server 2003 administrative tools, Adminpak.msi, on a system for a console with the Active Directory Users And Computers snap-in to function.

1. Click Start, and then click Run. 2. In the Open text box, type mmc, and then click OK. 3. Maximize the Console1 and Console Root windows. 4. From the File menu, choose Options to view the configured console mode. In what mode is the console running

5. Verify that the Console Mode drop-down list box is in Author mode, and then click OK. 6. From the File menu, click Add/Remove Snap-In. The Add/Remove Snap-In dialog box appears with the Standalone tab active. Note that there are no snap-ins loaded. 7. In the Add/Remove Snap-In dialog box, click Add to display the Add Standalone Snap-In dialog box. 8. Locate the Event Viewer snap-in, and then click Add. The Select Computer dialog box appears, allowing you to specify the computer you want to administer. You can add the Event Viewer snap-in for the local computer on which you are working, or if your local computer is part of a network, you can add Event Viewer for a remote computer. 9. In the Select Computer dialog box, select Local Computer, and then click Finish.

2

10. In the Add Standalone Snap-In dialog box, click Close, and then in the Add/Remove Snap-Ins dialog box, click OK. Event Viewer (Local) now appears in the console tree. You may adjust the width of the console tree pane and expand any nodes that you want to view. 11. On your own, add a snap-in for Device Manager (local). 12. Save the MMC as MyEvents.