File/print serving
You've gotta have it, but you'd rather not have to spend time dealing with it. What's the best way to keep file and print serving hassle free?
Geoff Halprin: NT provides a rich environment for file serving in a LAN environment.
Technically, the file permissions controls are superior on NT than on Unix, but in practice, people tend to ignore most of the advanced features, and just use the basics.
So most people would not recognise whether their files were on an NT server or a Samba (Unix) server.
Peter Menadue: Before the arrival of Windows 2000, many enterprises had positioned Windows as their OS of choice for file and print services and for departmental applications--scalability and reliability was definitely a perceived issue.
Since the release of Windows 2000 these issues are not being raised in the OS selection discussion. Increasingly, the selection of the OS is driven by the nature of the applications--Java or not.
Even though Java applications are available for Windows, from a pragmatic perspective, people tend to use Solaris for Java applications.
After working in the mini-computer market, I was involved in one of the largest rollouts of Windows NT 3.1 at the time.
We quickly realised that little provision had been made for automated management in the manner that most mainframe and mini-computer people expected. Windows has, with the addition of better management tools, interfaces, and scripting support become a substantially better platform to manage.
The no-client functionality of NetWare 6 is a welcome addition for NetWare shops, but Novell treads a fine line-in the longer run it may make it easier for organisations to migrate to other platforms where previously it required a client and server update.
This is a key moment for Novell--they must attract new customers and retain existing ones.
Dean Thompson: File and printer sharing have come a long way since the early days of Novell's NetWare product. Since Windows 95, file and printer sharing has been built into the basic operating system. This is a far cry from the days when Novell NetWare required that each machine load a number of drivers in order to connect to a NetWare resource.
Since then, both NetWare and other operating systems have evolved into more sophisticated entities capable of doing a lot of things. One item that has remained constant during this evolution process is the ability to share files and printers.
As most of the file transfers which are performed by users happen over the local network and that all the users on the network are most likely using some version of Windows, it makes sense to harness the file and print sharing services which come as part of the operating system.









I find the comments about Unix versions other than Solaris becoming considered "legacy" systems rather funny. I believe it was Solaris that recently announced they would no longer be developing a version for Intel...
Furthermore; the only reason there is an "OS War" is because Microsoft is more interested in making money and increasing their market share than meeting the needs of their customers. Linux is not the one with the "secret" protocols and undocumented "standards."