Must have / killer tool?

  • Thread starter Thread starter Chris Pratt
  • Start date Start date
C

Chris Pratt

Hi there,

I thought i'd pose a little discussion topic to find out what peoples best
and favourite must have / killer application or tool to help administer a
windows 2000 domain / server?

Chris
 
Apart from Herb and Lanwench suguested :-)))

There is no one tool, but a bunch of tools that make the whole. Some tools
from my list would be:
from MS:
- Network Monitor
- ADSIEdit
- Windows Resource Kit (all versions)
- ADModify
- DSLint
- dcdiag, netdiag
- .........
from www.sysinternals.com :
- RegMon, FileMon, TCPMon, ProcessExplorer, ObjMon
from GFI
- LanPortScanner

But the best thing of them all is scripting possibilities trough ADSI or
WMI.

--
Regards

Matjaz Ladava, MCSE (NT4 & 2000), MVP
(e-mail address removed)
http://ladava.com
 
Don't forget the /"and then a miracle occurs" switch.

Well it is magic....<grin>

I have trouble getting along without WhereIS, TList, and Kill for
more than about 10 minutes on a new machine.

(My whereis command has a "look" only in the path directories
switch which is great for "where did I put THAT OTHER tool"
questions.)

It's showing it's age as I wrote it last time for OS/2 (really) but
I have just about got it re-built (it works sort of) in C#.

It was my C# learning project. <grin>

Perl is hard to live without; Grep (I really don't like FindStr but
will use it if I must. -- I probably should just rename or copy
FindStr to MSGrep maybe that would fix it.)

As far as GUI and other stuff, I pretty much insist on SupportTools,
AdminPak.MSI, and ResKit being installed.

Oh, and the MOST IMPORTANT MS tool: TechNet.

Did I mention TechNet Information Library? Technet.
.....
Terminal services. <g>
Click to expand...
Yes, and "Cmd.exe: For %a in (...) Do [magic goes here] "
<grin>
Click to expand...
Click to expand...
 
I have tried this but it doesn't work on a Windows 2000 DC. It says it needs
2003 or XP.

Chris
 
Another tool we often take for granted:

A decent editor.

Even notepad or edline can qualify if you have
no other choice but consider...

The Recovery Console has NO EDITOR and
will not run external programs, i.e., those it doesn't
include through it's built in commands.

Recovery Console is great when you need it, but
is has no:
For/In/Do command
No editor
No redirection or piping ( < | >)
Few switches on common commands
(like Dir /S for subdirectories or /o for order by)

Adding the FULL cmd.exe processor to Recover Console
(minus anything that doesn't make sense in this context) would
be a GREAT improvement.

Adding external programs would likely be harder since the
APIs are likely missing for many things.
 
Back
Top