🚀 go-pugleaf

In article <4d116u$p...@news.onramp.net>, we...@onramp.net says...
>
>I am currently running 100 user 3.12 LAN with heavy DataBase use. I have been 
confronted
>by the Director of IS about going to NT. Any thoughts?

I would ask your IS Director what he expects to get from going to NT.  We 
recently made the switch.  Before we switched I was given all of these 
wonderful reasons.  Here are some results.

Reason:
  It will perform better.

Result:
  We went from a 66 Mhz 486-DX2 with 64MB of RAM on an EISA buss, a Mylex EISA 
DAC960 disk array controller and a 3Com EISA FDDI nic; all running NetWare.

  We went to a 133 Mhz Pentium, also with 64 MB of RAM on a PCI buss, a Mylex 
PCI DAC960P disk array controller and a Network Peripherals PCI FDDI nic, 
running Windows NT.  It got visibly slower.

Reason:
  It is easier to manage.

Result:
  With NetWare, I used the following programs:  SYSCON, PCONSOLE and RCONSOLE; 
to manage the NetWare server.  I could log in and run these programs from any 
workstation.

  With NT, I use File Manager, Event Viewer, Server Manager, RAS Admin, Print 
Manager, User Manager and Performance Monitor.  Since all of these are NT 
programs, I have to come back to my workstation or the server to manage 
anything.

  I also have to remember to use Server Manager to resynchronize the Domain 
everytime I make a change to user settings.  I have to use File Manager to 
manually copy the login script files to all of Domain Controllers, because if I 
don't, I must wait 5 to 10 minutes for Directory Replication to work.

  When I want to set user's access to directories on the server, I have to set 
each directory ACL (Access Control List) individualy.  This is because NT ACL's 
are non-hierachial, and if you use File Manager to copy ACL's to 
sub-directories, it erases any other ACL's that may be in the directory.

Final Word:
  I could go on for hours.  My advice to you is to clearly define the 
objectives you want to achieve by using Windows NT.  Then learn enough about NT 
to know you are achieving the objects, and understand what you are giving up.
-- 
+--------------------------------------+--------------------------------------+
|  David Chamberlain (dav...@smms.com) |    Opinions expressed are soley my   |
|  Network Manager                     | own and do not neccessarily represent|
|  Successful Money Management Seminars| the opinions of anyone else at all.  |
+--------------------------------------+--------------------------------------+

David Chamberlain wrote:
> 
> I would ask your IS Director what he expects to get from going to NT.  We
> recently made the switch.  Before we switched I was given all of these
> wonderful reasons.  Here are some results. 
[...snip...] 

> Final Word:
>   I could go on for hours.  My advice to you is to clearly define the
> objectives you want to achieve by using Windows NT.  Then learn enough about NT
> to know you are achieving the objects, and understand what you are giving up.

Nice to hear that :-) I just can't stand everyone say that NT is better over and 
over again...I was almost concidering to migrate. But now I'm not. I my tip to 
weezy is that whether he starts a NT server or not, do NOT leave netware before 
you know that NT is exactly what you want. NT and Netware runs ok on same network.
-- 

                                                        ,,,
                                                       /'^'\
                                                      ( o o )
--------------------------------------------------oOOO--(_)--OOOo----
     doktorn of convulsion
     c...@algonet.se                                .oooO
     http://www.algonet.se/~cnv                    (   )   Oooo.
----------------------------------------------------\ (----(   )-----
                                                     \_)    ) /
                                                           (_/

dav...@smms.com (David Chamberlain) wrote:

>In article <4d116u$p...@news.onramp.net>, we...@onramp.net says...
>>
>>I am currently running 100 user 3.12 LAN with heavy DataBase use. I have been 
>confronted
>>by the Director of IS about going to NT. Any thoughts?

>I would ask your IS Director what he expects to get from going to NT.  We 
>recently made the switch.  Before we switched I was given all of these 
>wonderful reasons.  Here are some results.

>Reason:
>  It will perform better.

>Result:
>  We went from a 66 Mhz 486-DX2 with 64MB of RAM on an EISA buss, a Mylex EISA 
>DAC960 disk array controller and a 3Com EISA FDDI nic; all running NetWare.

Are you using any client/server based applications?  I believe that
with such apps it might be worth considering NT because of its SMP
capabilities.

>  We went to a 133 Mhz Pentium, also with 64 MB of RAM on a PCI buss, a Mylex 
>PCI DAC960P disk array controller and a Network Peripherals PCI FDDI nic, 
>running Windows NT.  It got visibly slower.




I am nopt responsible for: spellunk, grammer, and punctuazion

Ian M. Turek
imt...@compumedia.com

Network Administrator and Tech. Support Specialist
Pacific Northwest Bank
Seattle, WA
pn...@wolfenet.com

doktorn <c...@algonet.se> wrote:

>David Chamberlain wrote:
>> 
>> I would ask your IS Director what he expects to get from going to NT.  We
>> recently made the switch.  Before we switched I was given all of these
>> wonderful reasons.  Here are some results. 
>[...snip...] 

>> Final Word:
>>   I could go on for hours.  My advice to you is to clearly define the
>> objectives you want to achieve by using Windows NT.  Then learn enough about NT
>> to know you are achieving the objects, and understand what you are giving up.

>Nice to hear that :-) I just can't stand everyone say that NT is better over and 
>over again...I was almost concidering to migrate. But now I'm not.

I have just installed Netware 4.1 on my new HP NetServer LH, although
considered NT.  The deal is that not too many software vendors support
their software when running it on NT or through the NT file services.
Anyway, "everyone" versus one guy still does not appeal to me, at
least not until I see it myself.

As to NT workstation i think it's praetty slick, if my polish friends
now what I mean.


I am nopt responsible for: spellunk, grammer, and punctuazion

Ian M. Turek
imt...@compumedia.com

Network Administrator and Tech. Support Specialist
Pacific Northwest Bank
Seattle, WA
pn...@wolfenet.com

imt...@compumedia.com (Ian M. Turek) wrote:
>dav...@smms.com (David Chamberlain) wrote:
>
>>Reason:
>>  It will perform better.
>
>>Result:
>>  We went from a 66 Mhz 486-DX2 with 64MB of RAM on an EISA buss, a Mylex EISA 
>>DAC960 disk array controller and a 3Com EISA FDDI nic; all running NetWare.
>
>Are you using any client/server based applications?  I believe that
>with such apps it might be worth considering NT because of its SMP
>capabilities.
NW4.1 have SMP to!!!
And he shod'nt nead SMP any way if he upgraded his like he did.


>>  We went to a 133 Mhz Pentium, also with 64 MB of RAM on a PCI buss, a Mylex 
>>PCI DAC960P disk array controller and a Network Peripherals PCI FDDI nic, 
>>running Windows NT.  It got visibly slower.

-- 
Peter Holt

MiROi Utbildning i Karlstad KB    Tel   : +46 54 18 18 50
Bergendorffsgatan 5               Fax   : +46 54 18 05 86
652 24  Karlstad                  E-mail: pe...@kd.miroi.se
SWEDEN

we...@onramp.net (weezy) wrote:
>I am currently running 100 user 3.12 LAN with heavy DataBase use. I have >been confronted by the Director of IS about going to NT. Any thoughts?

Depends on which DataBase you're using. If it's BTRIEVE i'd go for Novell 
but if you rely on heavy use of windows applications and do have the 
resources for running a NT I wouldn't doubt a minute. Especially now when 
NT is soon to be updated (Q3 1996). Another but, if you know your Novell 
on your five fingertips then i'd go for the 4.1..

/mike