Discussion Locked

Upgrading of entire network

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Here is my dilemma:

I currently work in an environment that has a NetWare 4.11 and 4.2 backbone. We have 1 central location with 14 remote locations or subnets all with NetWare servers configured, and we have all NT 4.0 servers(no 2000 servers) in our server farm(mail, citrix etc.) at our central location. Other servers on the network: a Proxy server and an Intranet server which run Linux. So at the current time we have IPX/SPX and TCPIP running on our LAN and WAN. It looks like we will be a shop running only TCPIP in the not-so-distant future. So we have a choice of either going to NetWare 6 or 7, or just migrating to an all Microsoft network. We also have an AS400/iseries mainframe to add to the mix. How does the amount of bandwidth going to the remote sites play a part?

Question:
What are the advantages of going to a total Microsoft network? Are there any problems you foresee going from a NetWare to a Microsoft network? If you cannot answer this question do you know someone who I can ask? Do you know of any organizations or individuals I can turn to to further add to the brainstorming that I am going through?
I imagine our workstations will go to Win200 or XP, and our servers will go to Win2000 and Linux.I just wonder know what kind of expertise or training our data center will need to get in order to do a migration to Microsoft. Do you know of any good consultants I can take a look at for a migration of this magnitude? First I need a few individuals I can just talk to to get an idea of what I may be getting myself into.

5 replies

by erikdr

ADVANTAGES of a total MS Network? Well, only limitations in the number of server platforms if you'd need to bring in W2K for certain standard apps. But generally spoken, for pure quality W2K is inferior to Linux and NetWare.

As for the amount of bandwidth, NDS replication consumes a lot less than Microsoft ADS replication. This is because ADS would make separate sites of each location and then decide that the WHOLE DOMAIN needs to be replicated to each side. To get bandwidth effective than they recommend splitting your forest in multiple domains which is absolutely horrible - a major design weakness in the W2K ADS which is supposed to be improved in .Net Server 2003 ADS.

Migrating from and to different platforms requires skills, as does the NW4-to-NW6 migration on a smaller scale. Which consultants to choose will depend on your country/area - Cambridge TP (now a Novell subsidiary but still with quite a lot of W2K knowledge) might be a bet.

Hope this helps,

- The Netherlands

by diggerb

Disadvantages of wholely MS network:
constant security patching
slow replication to remote sites (down to the way AD has to be designed.)

I can not really see any reason for going aware from Netware. The NOvell NDS has been around alot longer than AD and is much more scaleable and better suited for the scenario you describe - it can be partitioned so the remote sites only have the parts they need.

This discussion is closed to new replies.