If a Windows administrator looks in a crystal ball, he'll probably see a Linux server entering his data center;...
that is, if he's not sitting next to a Linux box already.
Windows admins can prepare for that inevitable future by perusing these Linux server migration tips. They were offered in a recent interview by Penguin Computing director of engineering Phil Pokorny.
Don't go into a Linux migration without doing some homework.
Fortunately, it will be easy to find relatively inexpensive study guides, Pokorny said. There's probably more online information about Linux than any other operating system, and there are many books, consultants and training companies available, too.
"Don't go into it blind," Pokorny said. "Take advantage of the resources that are out there. Get your staff trained."
Be open for a different look and feel.
In essence, Windows admins will have to act like they've moved to a foreign country, learning a new language and topography. For example, Pokorny said, in Windows when you want to turn on and off services, there's a little graphical user interface (GUI) that lists all sorts of services by name, and you can click the ones you want on and off. Linux has the identical system, but it has a different name and interface. The key thing in terms of migration is getting the Windows administrator to understand that many of the processes are the same; they just look and are named differently.
Take advantage of the built-in security tools in Linux.
The Linux kernel comes with a very capable firewall built in, and there are free security configuration utilities to help. "You don't have to pay extra to Symantec or Microsoft for firewalls and virus scanning tools," he said.
Use the command line in Linux.
"Linux has a strong heritage of a command-line interface," Pokorny said. For administrators, this has advantages in that those command-line interfaces are frequently very scriptable and easy to use to automate repetitive tasks, such as management and monitoring of the system.
"With Windows, which is focused on graphical interfaces, it can be much more difficult to script those things, so you're more likely to have to use multiple vendors' tools," Pokorny said.
With Linux, it's easy to use the command line and scripting languages to automate tasks. "Windows does have scripting tools, but they frequently get hung up in terms of implementing a completely automated task, because there's no command line or scripting line equivalent for some mouse click or menu click in the graphical application," Pokorny said.
Take advantage of some Linux distributions' GUIs, which can make it easier for first-time users to configure systems.
With Linux, you're not stuck with just the command line. "GUIs are a big strength of enterprise distributions, like Red Hat and SuSE," Pokorny noted.
"What's great about Linux is that you have the option of using the graphical tool, but you can also use the command line interface and the text config files that actually drive the application."
Pokorny advises Windows admins to start with the Linux GUI, and then start exploring command line options. "A Windows administrator might start poking around in the registry and then start to make changes there directly to tweak the system even more specifically for your application and your needs," he said.
Unlike the registry, which doesn't come with any comments, the config files that are referenced in Linux frequently come with descriptions of the parameters and comments on how to use a file.
Don't wipe out Windows and install Linux on a server without checking on hardware driver availability.
Before you wipe out Windows, take an inventory of the hardware on the system to make sure there are Linux drivers for all the pieces of hardware connected to the server.
Back in 2001, driver availability for Linux was a big issue, Pokorny said. For the most part, that gap has been filled today.
"If you have relatively new mainstream hardware, chances are good that there will be a well-tested Linux driver for it," he said. "If you have odd, old or not mainstream hardware, then there may not be a Linux driver for it." Then, you have to decide if you need that hardware or can easily replace it.
Do check out Samba, a free open source program, if you're adding Linux file servers to a Windows server environment for the first time.
"If you're introducing Linux servers into a Windows environment, you should focus on Samba software, which can allow your Linux server to participate directly in your Windows Active Directory domain or Windows NT4 domain," Pokorny said. With Samba, admins can allow users to have single sign-on, share accounts and access Linux servers the same way they access other Windows servers in the network.
"The Samba developers say that they understand Windows file systems protocols better than Microsoft does," Pokorny said. They've had to study how Windows servers work, respond to clients and so on, so they can duplicate that functionality in Samba.
"Going back to my first point, about doing your homework, I'd say that getting a book on Samba is a good place to start," Pokorny concluded.