Professional Web Hosting, Perl Scripting And Developing Blog

Microsoft Windows Server 2003 Inside Out Figure 11-8. When you add a snap-in in the Add Standalone Snap-In dialog box, it appears on the Add/Remove Snap-In list. 4 Now close the Add Standalone Snap-In dialog box by clicking Close, and return to the Add/Remove Snap-In dialog box. You ll see the folders you ve added. Click OK to close this dialog box and return to the console you are creating. After you add folders, you must rename them. Right-click the first folder, and choose Rename. Type a new name, and then press Enter. If you are following the example, rename the folders: General, Policy, Security, and Support. When you are finished renaming the folders, follow a similar process to add the appropriate snap-ins to your console: 1 Choose Add/Remove Snap-In on the File menu in the main window. 2 In the Snap- Ins Added To list, choose the folder to use, and then click Add. 3 Use the Add Standalone Snap-Ins dialog box to add snap-ins to the selected folder. 4 When you are finished, click Close to return to the Add/Remove Snap-In dialog box. You ll find the snap-ins you ve chosen are added to the designated folder. 5 If you want to work with a different folder, select the folder in the Snap-Ins Added To list, and repeat steps 2 to 4. 6 When you are finished adding snap-ins to folders, click OK to close the Add/Remove Snap-In dialog box and return to the console you are creating. Chapter 11 320 Part 4: Managing Windows Server 2003 Systems
Note: In case you are looking for affordable and reliable webhost to host and run your j2ee application check Vision J2ee Web Hosting services.

Windows Server 2003 MMC Administration Again, think of snap-in types or categories, not necessarily specific snap-ins that you want to use. You might want to organize the snap-ins into groups by creating folders for storing snap- ins of a specific type or category. For example, if you are creating a console tool for managing Active Directory, you might find that there are four general types of snap-ins that you want to work with: General, Policy, Security, and Support. You would then create four folders in the console with these names. Folders are implemented as a snap-in that you add to the console root. To add folders to the console root, follow these steps: 1 Choose Add/Remove Snap-In from the File menu in the main window. As shown in Figure 11-7, you must now choose where to add the snap-in. At this point, it is possible only to add the snap-in to the console root (which is now called Active Directory Management or whichever other name you used), but after you add folders, you can add snap-ins to a folder below the console root by selecting it in the Snap-Ins Added To list. Figure 11-7. Choose where to add the snap-in. 2 Choose Add, which displays the Add Standalone Snap-In dialog box. Note that this dialog box is set so that you can see the previous dialog box as well. This is important because when you add snap-ins they appear in the Add/Remove Snap-In list. 3 The Available Standalone Snap-Ins list shows all the snap-ins that are available. Scroll through the list until you see the Folder snap-in, as shown in Figure 11-8. Click Folder, and then choose Add. The Folder snap-in is added to the list of snap-ins in the Add/ Remove Snap-In dialog box. Repeat this for each folder that you want to use. If you are following the example and want to use four folders, you would click Add three more times so that four Folder snap-ins appear in the Add/Remove Snap-In dialog box. Chapter 11 319 Part 4: Managing Windows Server 2003 Systems
From our experience, we can recommend PHP Web Hosting services, if you need affordable webhost to host and run your web application.

Microsoft Windows Server 2003 Inside Out Figure 11-6. Although consoles can have multiple windows, most consoles have a single window. Inside Out Using multiple windows in consoles Most console tools have a single window for a good reason: The tool creators wanted to keep the interface as simple as possible. When you introduce multiple windows, you create additional views of the console root, making the interface more complex, and often unnecessarily so. Still, there are times when a console tool with multiple windows could come in handy. For example, you might want to have multiple views of the console root where different areas of the tool are featured, and you could do this by using multiple windows. Step 2: Adding Snap-Ins to the Console While you are thinking about the organization of the tool and the possibility of using additional views of the console root, you should also consider the types of snap-ins that you want to add to the console. Each of the tools listed in Table 11-1 is available as a stand-alone snap- in that you can add to the console. If you ve installed any third-party tools on the computer, these tools might have stand-alone snap-ins that you can use. Many other snap-ins are available from Microsoft as well. Chapter 11 318 Part 4: Managing Windows Server 2003 Systems
Visit our web design programs services for an affordable and reliable webhost to suit all your needs.

Windows Server 2003 MMC Administration Step 1: Creating the Console The first step in building a custom console tool is to create the console that you ll use as the framework. To get started, open a blank MMC in author mode. Click Start, select Run, type mmc in the Open box, and then click OK. This opens a blank console titled Console1 that has a default console root as shown in Figure 11-5. Figure 11-5. A blank console with the default console root. If you want your custom tool to be based on an existing console, you can open its .msc file and add it to the new console. Select Open on the File menu, and then use the Open dialog box to find the .msc file you want to work with. As discussed previously, most .msc files are in the %SystemRoot%System32 directory. Any existing console you choose will open in author mode automatically. Keep in mind that you generally don t want to overwrite the existing .msc file with the new .msc file you are creating. Because of this, when you save the custom console, be sure to choose Save As rather than Save on the File menu. If you want to start from scratch, you ll work with the blank console you just opened. The first thing you ll want to do is rename the console root to give it and the related window a more meaningful name. For example, if you are creating a console tool to help you manage the Active Directory directory service, you could rename the console root Active Directory Management. To rename the console root and the related window, right-click the console root, and select Rename. Type the name you want to use, and then press Enter. The next thing you ll want to do is to consider how many windows the console tool must have. Most console tools have a single window, but as shown in Figure 11-6, a console can have multiple windows, each with its own view of the console root. You add windows to the console by using the New Window option on the Window menu. After you add a window, you ll probably want the MMC to automatically tile the windows as shown in the figure. You can tile windows by selecting Tile Horizontally on the Window menu. You don t have to do this, however; anytime there are multiple windows, you can use the options on the Window menu to switch between them. Chapter 11 Part 4: Managing Windows Server 2003 Systems
If you are in need for chaep and reliable webhost to host your website, our recommendation is http web server services.

Microsoft Windows Server 2003 Inside Out Chapter 11 . Internet Authentication Service, ias.msc . Local Users and Groups, lusrmgr.msc . Removable Storage Management, ntmsmgr.msc . Services, services.msc . Windows Management Instrumentation, wmimgmt.msc Several different hidden options are available with the Active Directory related snap-ins. For Active Directory Users and Computers, Active Directory Sites and Services, and Active Directory Domains and Trusts, you can use the /Server parameter to open the snap-in and connect to a specified domain controller. For example, if you wanted to start Active Directory Users and Computers and connect to the CORPSVR02 domain controller, you could do this by typing the following: dsa.msc /server=CorpSvr02 For Active Directory Users and Computers and Active Directory Sites and Services, you can use the /Domain parameter to open the snap-in and connect to a domain controller in the specified domain. For example, if you wanted to start Active Directory Users and Computers and connect to the cpandl.com domain, you could do this by typing the following: dsa.msc /domain=cpandl.com Building Custom MMCs If you find that the existing console tools don t meet your needs or you want to create your own administration tool with the features you choose, you can build your own custom console tools. This allows you to determine which features the console includes, which snap-ins it uses, and which additional commands are available. The steps for creating custom console tools are as follows: 1 Create the console for the tool. 2 Add snap-ins to the console. Snap-ins you use can include Microsoft console tools as well as console tools from third- party vendors. 3 When you are finished with the design, save the console in user mode so that it is ready for use. Each step is examined in detail in the sections that follow. Optionally, you can create one or more taskpad views containing shortcuts to menu commands, shell commands, and navigation components that you want to include in your custom tool. Techniques for creating task- pad views are discussed in the section entitled Designing Custom Taskpads for the MMC later in this chapter. 316 Part 4: Managing Windows Server 2003 Systems
Searching for affordable and reliable webhost to host and run your web applications? Go to our java web server services and you will be pleased.

Windows Server 2003 MMC Administration name. When the snap-in is working with a remote computer, you ll see the remote computer name in parentheses after the snap-in name, such as (CORPSERVER01). Generally, regardless of which type of snap-in you are using, you can specify the computer to work with it in one of two ways. Within the MMC, you can right- click the snap-in node in the console tree and then select Connect To Another Computer. This displays the Select Computer dialog box, as shown in the following screen: If you want the snap-in to work with the computer the console is running on, select Local Computer. Otherwise, select Another Computer, and then type the computer name or Internet Protocol (IP) address of the computer you want to use. If you don t know the computer name or IP address, click Browse to search for the computer you want to work with. Just about any snap-in that can be set to work with local and remote systems can be started from the command line with the focus set on a specific computer. This is a hidden feature that many people don t know about or don t understand. Simply set the focus when you start a console from the command line using the following parameter: /computer=RemoteComputer where RemoteComputer is the name or IP address of the remote computer you want the snap- in to work with, such as eventvwr.msc /computer=corpserver01 The following snap-ins use the /Computer parameter: . Certificates Authority, certsvr.msc . Computer Management, compmgmt.msc . Device Manager, devmgmt.msc . Disk Management, diskmgmt.msc . Event Viewer, eventvwr.msc . Indexing Service, ciadv.msc Chapter 11 315 Part 4: Managing Windows Server 2003 Systems
Go visit our java server pages services for a reliable, lowcost webhost to satisfy all your needs.

Microsoft Windows Server 2003 Inside Out Table 11-1. Key Console Tools and Their .msc File Names Tool Name .msc File Name Component Services compexp.msc Computer Management compmgmt.msc Device Manager devmgmt.msc DHCP Manager dhcpmgmt.msc Disk Defragmenter dfrg.msc Disk Management diskmgmt.msc Distributed File System dfsgui.msc DNS Manager dnsmgmt.msc Domain Controller Security Policy dcpol.msc Domain Security Policy dompol.msc Event Viewer eventvwr.msc Group Policy Editor gpedit.msc Indexing Service ciadv.msc Internet Authentication Service ias.msc Internet Information Services iis.msc Local Security Policy secpol.msc Local Users and Groups lusrmgr.msc Performance perfmon.msc Remote Desktops tsmmc.msc Removable Storage Management ntmsmgr.msc Resultant Set of Policy rsop.msc Routing and Remote Access rrasmgmt.msc Services services.msc Shared Folders filesvr.msc Telephony tapimgmt.msc Terminal Services tscc.msc Windows Management Instrumentation wmimgmt.msc Chapter 11 MMC and Remote Computers Some snap-ins can be set to work with local or remote systems. If this is the case, you ll see the name of the computer with focus in parentheses after the snap-in name in the console tree. When the snap-in is working with the local computer, you ll see (Local) after the snap-in 314 Part 4: Managing Windows Server 2003 Systems
Note: In case you are looking for affordable and reliable webhost to host and run your j2ee application check Vision J2ee Web Hosting services.

Windows Server 2003 MMC Administration This works because of the file association that specifies .msc files are executed using Mmc.exe. (You can examine file associations using the ASSOC and FTYPE commands at the command prompt.) Some console tools aren t in the %SystemRoot%System32 directory, or the search path for that matter. For these tools, you must type the complete file path. MMC Tool Availability Generally, the preconfigured MMC consoles available on a server depend on the services that are installed. As you install additional services, additional tools for administration are installed, and these tools can be both console tools and standard tools. You don t have to rely on service installation for tool availability, however. You can, in fact, install the complete administrative tool set on any computer, including servers, regardless of the services being used. The only requirement is that the computers are running Windows XP Professional Service Pack 1 or later or Windows Server 2003. Follow these steps to install the complete administrative tool set: 1 Log on to the computer using an account with Administrator privileges. 2 Insert the Windows Server 2003 distribution CD-ROM into the CD-ROM drive. 3 When the Autorun screen appears, click Perform Additional Tasks, and then click Browse This CD. This starts Windows Explorer. 4 Double-click I386, and then double-click Adminpak.msi. The complete set of Windows Server 2003 management tools is installed on the computer. These tools are then available from the Administrative Tools menu and can also be started quickly in the Run dialog box or at the command prompt by typing only their file name (in most cases). At times, you might find it quicker to open consoles from the command line. For example, on a server optimized for handling background services and not programs being run by users, you might find that navigating the menu is too slow. To help you in these instances, Table 11-1 provides a list of the key console tools and their .msc file names. Table 11-1. Key Console Tools and Their .msc File Names Tool Name .msc File Name Active Directory Domain and Trusts domain.msc Active Directory Sites and Services dssite.msc Chapter 11 Active Directory Users and Computers dsa.msc Authorization Manager azman.msc Certificate Templates certtmpl.msc Certification Authority certsvr.msc Certificate Manager certmgr.msc Part 4: Managing Windows Server 2003 Systems
We recommend cheap and reliable webhost to host and run your web applications: Coldfusion Web Hosting services.

Microsoft Windows Server 2003 Inside Out The first part of the target (%SystemRoot%System32Compmgmt.msc) is the file path to the associated Microsoft Saved Console (.msc) file. The second part of the target (/S) is a command parameter to use when running the MMC. It follows that you can run the MMC by specifying the file path to the .msc file to use and any necessary command parameters as well using the following syntax: mmc FilePath Parameter(s) where FilePath is the file path to the .msc file to use and Parameter(s) can include any of the following parameters: . /A Enables author mode, which lets you make changes to preconfigured consoles as well as other consoles previously set in user mode. . /S Prevents the console from displaying the splash screen that normally appears when the MMC starts in earlier versions of the Windows operating system. This parameter isn t needed when running on Windows Server 2003. . /32 Starts the 32-bit version of the MMC, which is needed only if you explicitly want to run the 32-bit version of the MMC on a 64-bit Windows system. . /64 Starts the 64-bit version of the MMC, which is available only on 64-bit Windows versions. Inside Out Chapter 11 Using 32-bit and 64-bit versions of the MMC The /32 and /64 parameters are meaningful only on 64-bit Windows versions. The 64-bit versions of the Windows operating system can run both 32-bit and 64-bit versions of the MMC. For 32-bit versions of the MMC, you use 32-bit snap-ins. For 64-bit versions of the MMC, you use 64-bit snap-ins. You can t mix and match MMC and snap-in versions, though. The 32-bit version of the MMC can be used only to work with 32-bit snap-ins. Similarly, the 64-bit version of the MMC can be used only to work with 64-bit snap-ins. In most cases, if you aren t sure which version to use, don t use the /32 or /64 parameter. This lets the Windows operating system decide which version to use based on the snap-ins contained in the .msc file you are opening. Most console tools are found in the %SystemRoot%System32 directory. This puts them in the default search path for executables. Because there is a file type association for .msc files, specified files of this type are opened using Mmc.exe; you can open any of the preconfigured tools stored in %SystemRoot%System32 by specifying the file name followed by the .msc extension. For example, you can start Event Viewer by typing the following: eventvwr.msc 312 Part 4: Managing Windows Server 2003 Systems
If you are searching for cheap webhost for your web application, please visit MySQL5 Web Hosting services.

Windows Server 2003 MMC Administration Figure 11-4. MMC windows have a console tree and a details pane. The right pane is the details pane, and its contents change depending on the item you ve selected in the console tree. When you are working with one of the lowest-level nodes in the console tree, you ll sometimes have two views to choose from: standard or extended view. The difference between the two is that the extended view typically provides quick access links to related, frequently performed tasks and a detailed description of the selected item. These are not displayed in the standard view. One way to start a console tool is to select it on the Administrative Tools menu or double- click its icon on the desktop or in Windows Explorer. You can also start console tools from the Run dialog box and the command prompt. The executable for the MMC is Mmc.exe, and you can run it by typing mmc in the Run dialog box and clicking OK or by entering mmc at the command prompt. Either way, you ll end up with a blank (empty) console that you can use to design your custom administration tool. To use an existing console, you can specify the console file to open when the MMC runs. This is, in fact, how the preconfigured tools and any other tools that you create are launched. For example, if you right-click Computer Management on the Administrative Tools menu, and then select Properties, you ll see that the target (the command that is run) for the menu item is as follows: %SystemRoot%System32Compmgmt.msc /s Chapter 11 311 Part 4: Managing Windows Server 2003 Systems
Please visit our professional web hosting services to find out about cheap and reliable webhost service that will surely answer all your demands.