The sentence above has become a motto of many discussions these days onQuote:> --
> Why Windows NT Server 4.0 continues to exist in the enterprise would
be a
> topic appropriate for an investigative report in the field of
psychology
> or marketing, not an article on information technology.
> - John Kirch, Microsoft Certified Professional (Windows NT)
a very
old topic - Windows NT versus UNIX.
The article http://www.kirch.net/unix-nt.html is definitely very
interesting one
- a complex study with many examples and technical proofs.
But I'll try to question author's technical knowledge of Windows NT.
First, there are some significant differences between NT version 3.51
(for which
the author has taken two exams and has the degree of Microsoft Certified
Professional) and NT version 4.0 (for which I've taken six exams and
have the
degree of Microsoft Certified Systems Engineer, as well as
MCP+Internet).
Good example is the argument for NT's "poor" shell scripting. MS
introduced very
powerful native command line (CMD.EXE) scripting with version 4.0
(missing in
version 3.51). I use this every day and there haven't been a task I
wasn't able
to execute using only the scripting language and the Resource Kit
utilities.
Let's mention some basic features of NT 4.0 shell scripting such as
string
tokens processing, numeric loops, arithmetical expressions.
Another example is the execution of applications on servers from remote
workstations (not the case of client/server apps)- Kirch claims this as
missing
for NT.
But in Windows NT 4.0 Resource Kit MS introduced "Remote Console". You
install
it as service on the "server" (actually you can install it on both NT
4.0
workstation and server). Using the client part, user can connect to the
server
and be on the server's shell. Then from the shell the user can any
program (even
GUI as far as it doesn't require remote user's intervention).
Simultaneous
connections from several workstations are possible as well.
Kirch's paper is updated on June 26 1998. But on June 17 MS announced
the
release of Terminal Server after almost a year in the last beta. It
provides
"X-window" type capability (not using X-window protocol) to the NT 4.0
server.
There is also third party tool like this that has been on the market for
long
time - Citrix's WinFrame.
Using one of these a user can connect even from UNIX workstation
(provided there
is a client for the specific UNIX flavor)
On the other hand, the question is not so simple as whether "Windows NT
Server
4.0 is no match for any UNIX operating system". There are many other
"matches"
in the real world one have to meet when choosing complex things, not
only
technical. It's a complex factor including the support, availability,
price,
training, performance. NT might be not the best in any of them, but when
you
calculate the "average" apparently it's one of the best for a specific
range of
tasks.
Definitely there are many features UNIX has NT server lacks, but stating
that NT
is not even close to UNIX is giving too much credit to some option
because you
don't know well enough the other.
At the end, I'd like just to add also that it's pretty strange to find
examples
with Novell in Kirch's paper. I don't think there is computer
professional who
would even consider Novell an "operating system" at all. Just one point
is
enough: it is this year Novell will release for first time protected
memory
kernel - something considered one of the most important "musts" of a
real
operating system. Something that has been implemented in Unix and NT (as
well as
all other OS-es) from the very beginning.
If there is something that does only file and print sharing, that's
Novell.
Kras Gadjokov,
MCSE, MCP+I (Windows NT 4.0)
M.Sc. in Computer Science
http://www.interlog.com/~kras