|
|
|
|
|
|
|
|
|
|
|
|
|
|
A quick guide to working with Windows 2000 Server (continued)
| Tool |
New Location |
Comments |
| Control Panel->Services applet |
Programs->Administrative Tools->Services OR Programs->Administrative Tools->Computer Management OR SERVICES.MSC |
The new applet provides more information than the old dialog boxes we've been used to. |
| Network Properties |
These have been split into a number of places: (a) to change computer name, domain, or workgroup: Settings->Control Panel->System, Network Identification tab OR My Computer->Properties, Network Identification tab (b) to work with network protocols and services, Settings->Network and Dial-Up Connections, then select the Local Area Connection icon, then Properties (c) to work with network protocol binding order, Settings->Network and Dial-Up Connections, then select the Advanced menu item and select Advanced Settings |
-- |
| Event Log Viewer |
Programs->Administrative Tools->Computer Management OR Programs->Administrative Tools->Event Viewer OR EVENTVWR.MSC |
The three basic log types (system, application and security) are still present, but you may find other logs from other services if running on the server such as AD, DNS or file replication. |
| Performance Monitor |
Programs->Administrative Tools->Computer Management OR Programs->Administrative Tools->Performance OR PERFMON.MSC |
This tool is now known as System Monitor. |
| Disk Management |
Programs->Administrative Tools->Computer Management or DISKMGMT.MSC |
-- |
Microsoft Management Console You are probably noticing that a number of these tools look very similar. That's because Microsoft now uses a standard approach for management tools called MMC (Microsoft Management Console). This defines both the technical architecture of these tools and the look and feel. These will take some time to get used to, but they can be very powerful.
Within the MMC, you can combine a number of component "snap-ins" which have a .MSC file extension and are the actual tools you run within the MMC. You can add them as they're needed and then save the console for later use. For example, you can build your own console to manage the resources you're interested in, such as the local Windows 2000 Server or any Windows 2000 Server you have access to manage.
In order to create your own consoles, start the MMC.EXE program. This gives you a basic console with no snap-ins, as seen in Figure A.
FIGURE A
 
Here you see the MMC with no snap-ins configured. Roll over picture for a larger image.
Then, from the Console menu, select the Add/Remove Snap-In option. You then select the Add button and are presented with a list of snap-ins, as seen in Figure B. Some of these tools allow you to select the machine that the tool will manage, whether it be the local computer or another specified computer.
FIGURE B
 
Choose from the list to add snap-ins to a custom MMC console. Roll over picture for a larger image.
Figure C shows a completed console that contains a number of snap-ins. This console is saved with a .MSC extension. You can then create a Windows shortcut to it on your desktop to start it when needed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-- Advertisement --
Sophisticated Meets Simple For Document Management
Share. Control. Manage.
Documents, emails, and content in the context of how work is done.
Native to Lotus Domino. The User Experience unseen for Lotus Domino.
Do more with less. Really.
See the possibilities Docova unleashes for Lotus Domino. |
-- Advertisement --
Teamstudio Edition 25 has shipped
It's finally here! Now that Teamstudio Edition 25 has shipped, listen to our latest Tool Time audio program to find out what's changed. Updates to all your favorite Teamstudio tools will be discussed.
Plus, you'll get an introduction to Teamstudio Undo (formerly known as Teamstudio Snapper).
Tap here to get started! |
|
|
|
|
|
|
|
|
|
|