Windows to Linux Migration in the Enterprise?
youngerpants asks: "There is a lot of talk at the moment about migrating applications from WIN32 to Linux. This certainly helps move the OSS movement along, however, the true test of Linux is in the enterprise. Whereas we can move applications, how can the enterprise itself (such as Active Directory to Open LDAP, Exchange Server to Sendmail and NTFS to Samba) be moved.
Have Slashdot readers used any applications or followed any strategies to migrate their enterprise? How would you tackle an obviously risky migration?"
1. Move from Windows to Linux. :)
2. ???
3. Profit!
Free your mind!
"Active Directory to Open LDAP, Exchange Server to Sendmail and NTFS to Samba"
I understand the gist of your question, although I don't think you understand it yourself. None of your examples actually discuss the one thing the enterprise is interested in: "Functional Parity"
AD to OpenLDAP doesn't go, because OpenLDAP is just a directory protocol -- I wish people would start to understand that. There is no directly usable management interface, no business logic, no nothing. It is just a protocol....
Comparing Exchange Server and Sendmail earns you a good thwapping over the head in my team -- maybe Exchange Server vs. Open-Exchange, but again you are comparing the wrong things. Finally, go stand in the corner for comparing NTFS with Samba.
I usually don't complain about Ask Slashdot type stuff, but this takes the cake. Go learn something about IT before you ask stupid questions.
People who think they know everything are a great annoyance to those of us who do.
Very small...
Individual Pockets -> Workgroup -> Departmental -> Enterprise
As much as I love open source and think it provides tremendous value to organizations, I have to realistically evaluate any large migration and observe two obvious points:
1) It's different. There will be people who will not want to see it succeed. You will need to PROVE that the functionality provided is SUPERIOR and that the cost of migrating is overcome by the reduced ongoing TCO.
2) Is your organization ready to provide the level of support it has become accustomed too? Are you a MS Enterprise or Select customer? You need to prepare for the fact that to some extent the warm fuzzy blanket of misleading comfort is being pulled away from the organization.
I would NOT begin by migrating something. I would begin by looking for a new unit, group, or area of the business. New is much easier to accomplish than migrate.
Finally, if you are a hardcore MS shop, the financial pitch to MGT can be the leverage that doing something small can provide in price / service negotiations.
Nowdays, with all this "Get the facts" FUD, the Free Software comunity reacts trying to show that it's not true that migration is a nightmare, and that it's not true that it costs money. The true is, Migration from ANY system to ANY other system, is a nightmare, and it does cost money.
The point we should make clear is: Migrating from Windows to Unix Is a good decition (I Say Unix to make clear that i'm not talking about Freedom or ethical or monetary issues, just about the technical stuff) and it will make things just easier and safer in the long run. Technically, there is no possible discussion.
About non-technicall stuff: Microsoft insists in their "get the facts" bullshit that if you use windows you can hire incompetent sysadmins, and with Unix, you can't. It's just not a good idea to hire incompetent people. Hire a good sysadmin, and pay him well, what do you prefere, to pay thousands to a big monopoly for the right to copy, or pay a worker for actual honest work??
ALMAFUERTE
WTF am I doing replying to an AC at 5 A.M on a Friday night?
Check out this link.
LDAP is so useful, that you might as well start here. Remember that LDAP is a multipurpose directory. If you want to replace AD authentication and a windows PDC, IDEALX has written some nice perl scripts and a tutorial on how to do this with OpenLDAP and Samba.
If you want to replace Exchange Server, use Openexchange. If you want to replace only your MTA, consider using postfix. On the server end, this isn't a ton of work. But you will likely have to change the way clients are connecting to your server & also what they can do with it. Sendmail/postfix will probably not be enough for you...
NTFS is a local file system. Samba is an open source SMB server/client. Big difference. See IDEALX for good Samba deployment.
The only places that can really migrate to Linux en-masse are places like call-centers where computers are used for specific and rigid purposes.
Larger enterprises look at and think about the "savings", but when you compare the training costs, hassle and resistance that most users will feel, you're not saving anything.
The places that have successfully transitioned to Linux (federal labs, Burlington Coat Factory, City of Largo, small companies) were either established Unix shops already or started with small or completely disorganized IT organizations.
Conformity is the jailer of freedom and enemy of growth. -JFK
If you want to do it all-in-one over-the-night type push, you're very likely to fail. Or at least your users will kill you.
Also, you may (or may not) hit many little annoying details that would make you belive m$ fud more and more.
I've been trough two migrations now and what i learned is this: go easy, keep the existing systems in place for their forseeable lifetime (dont fix if it's not broken approach), implement OSS stuff only for new services and gradually replace old systems with newer, running OSS. In a timeframe of 2-5 years or so.
I don't even think that Linux can save that show.... although it would look nice on those flat panel displays.
Sadly, Linux just isn't there yet when it comes to enterprise IT. Unless you're rolling your own core business applications, you're pretty much stuck with Windows. Want to run an integrated payroll/HRIS system from a shrinkwrapped package? No luck with Linux.
Further, IMO, while Suse's OpenExchange appears to be a compelling package (which I'd love to deploy in lieu of Exchange Server), I've had a very difficult time finding a local 3rd party vendor to support it.
The point of my post is not to denigrate Linux. I am generally a Linux advocate, and will still deploy it wherever it is practical (practical being the operant word here). The issue, however, is that much of these services are inside of niche markets where it doesn't make sense for the vendor to develop Linux support. Others are very bleeding edge and not commercially supported. If you don't have a very large IT department to support the services that you want to run, they're nearly useless -- that is, unless you've got gobs of free time on your hands.
OTOH; if you're rolling a custom app (and thus already have the staff you need), need a webserver, or a database backend, Linux may be an excellent choice. One way to look into it is to find out how Linux is most widely deployed and supported as a solution (ie web servers, database backends, etc). If you go the other way, choosing whatever solution you find that's "out there", you may find yourself in a heap of trouble -- looking for a new job. I supppose that this applies to all software, commercial or otherwise. Always ensure that you can support it...but it's something that one has to be especially cautious about when getting into a bleeding edge F/OSS package that is new enough where there is either no commercial support, or inadequate support for your needs...and unfortunately, there are currently quite a few of these out there.
-Turkey
Damn, the title of this article is just begging for someone to make a Star Trek joke, and no one's done so yet.
Ah, Slashdotters genuinely surprise me sometimes...
I support the Center for Consumer Freedom
I don't think you're old enough to wear pants yet. Please try again next year.
I've always been curious about this. I love Linux, but one of the areas where I think it is sorely lacking is in file system permissions flexibility. For example, if I had a folder and wanted the following in Linux, how could I do it?
MKTG group = rwx
DEV group = r
EXEC group = r
ADVERT group = rx
ADMINS group = rw
Is there a way to do this in Linux? I have no idea. It has always been my understanding that I'm stuck with UGO and sitcky bits for permissions. Is this entirely true or is there another way.
If you mod me down, I shall become less powerful than you could possibly imagine.
I'm hoping that one of the things that you love about Linux is its flexibility...most distributions can grow far beyond their packaging. :)
I believe that you're looking for ACL support (Access Control Lists). Check this out. Also, just do a google search for Linux ACL's. There are lots of projects in development, and considering how long these have been worked on, there are probably some implementations which are quite mature. YMMV.
-Turkey
Check out Access Control Lists (ACL). I mainly have experience with the Solaris implementation of ACL, but they have made their way to most Linux distros AFAIK.
Thanks clickster/ j-turkey, couldn't have explained the problem or the solution better myself (despite what passthecrackpipe may think)
Exaclty what I was referring to
You need to look into Access Control Lists. That will allow you do have much finer-grained file access controls.
I always see comments on these stories like, "zealots tell people to switch and can't back it up". Perhaps what the community needs to realize is, apart from companies who know what they are doing and can facilitate an effective transition, maybe it is best that companies do not do an abrupt shift from Windows to Linux. I am a vehement Linux supporter, but I realize that the transition may not be good for some people/companies. My parents both use Windows. I know that giving them a Linux box probably isn't the best idea until, say, Longhorn comes out and they have to learn a new system anyway. I think that the greatest growth of Linux on the desktop will not come from established companies, but instead the new companies that start with Linux so they don't have to worry about migrating this system and that system.
Thank j-turkey. That's the kind of thing that I'm looking for.
If you mod me down, I shall become less powerful than you could possibly imagine.
Scotty:
.... tricorder..... Get online and ..... see if you can find a .....patch .....for the warp core... containment driver!
She can'nah take much more'o this captain! Th' opensource drivers for the warp core containment controller card are only version 0.2.1 and the project hasn't seen an update for nearly a century! While the hardware is capable of running the engines at 110%, these incomplete kernel drivers can'nah hold her much longer than five minutes over 80%!
Kirk:
Bones! You've got..... Familiar Linux running on your
Bones:
Damnit Jim, I'm a doctor, not a kernel hacker.
http://www.novell.com/products/openenterpriseserve r/
Give it a year to mature and it will be a complete and viable solution to a Microshaft environment.
From end user (Ximian, FireFox, OO)
Backend: GroupWise, http://www.scalix.com/, Exchange 2K
Platform: Novell OES
Patch / update / version mngmt: RedCarpet
All fully supported by hand holding, management stroking suits.
Micrshit is doomed. ETofDeath: 2020(two more migration cycles). RIP.
If you have a lot of apps that simply can't be migrated, or there's no way to safely and gradually perform the migration, it may be best to hold off or look into a partial migration. The ultimate goal is to solve problems and/or save money.
Samba for me has been a very good file server, performing seemingly much faster than I've seen with Windows servers, with the flexibility to do some very interesting and unusual setups.
All will run on linux.
AD is hard to migrate because it is very proprietary. (Mind you SAMBA can authenticate users).
For free software I would use
1) Linux as a firewall
2) Linux as a file and print server
3) Linux as a database server (Oracle, UDB, Postgresql)
4) Linux as an Application Server (Oracle/SAP/Peoplesoft)
5) Linux as a web server - Apache/Tux
6) Linux as a J2EE server (Websphere/JBOSS/BEA)
7) Linux as workstation (limited use) OpenOffice/etc
Enterprise software means different things to different people. I for example am working with a bank that uses DOS (and some win95) for all its tellers. The DOS machines almost have never received an significant outage. And surely linux is more stable that DOS/Win95...
It can be done with UGO but it's not pretty. Basically you create permutations of every possible group/access combination. Requires a huge number of groups for any non-trivial case. UGO is not really workable in those situations.
If you're only worried about Linux then simply use POSIX ACLs. They've been standard in most Linux distros for many years.
...but you also need to point out that most of the labourers will be leaning on their shovels rather than working. At least, that's how the Minesweeper Consultant/Solitaire Expert crowd that I've seen in action behave.
The guy with the Komatsu (a WA1200, I'm sure, for the reach and flexibility) will be ripping around at full throttle, will top-dress your lawn in passing, fix the corporate toaster on his lunch break and be writing his own novel on the side as he works. And constantly thanking you for letting him play with this neat toy.
Got time? Spend some of it coding or testing
I loaned my spare Linux workstation to my sister-in-law, who at the time bemoaned the absence of PhotoShop.
Now she still misses the odd PS feature but also sorely misses GIMP features when on PS, the convenience of Konqueror and Firefox when stuck with MSIE and Windows Explorer, and really hates the constant crashing (I swapped her CD burner for a DVD burner yesterday and her machine had been up for 183 days since the last power failure - she never saves, with obvious consequences after five hours' typing up of a document on one of her kids' school's computers, I've seen an image left open on her machine for more than a week while she tries various stuff on it; her oldest son built a Klaymen figurine over the reset button out of plasticene, where it's been sitting for more than a month and she didn't notice). I'll update that machine soon so she can have GIMP 2.2, which is all-over much nicer than the 2.0 she's using.
Got time? Spend some of it coding or testing
closing your mind to an entire idea and calling customers idiots is not good practice in any walk of life.
The HOWTO that I linked to has a more detailed explanation of how to do it.
"Avoid employing unlucky people - throw half of the pile of CVs in the bin without reading them." -- David Brent
Go to http://www.resolvo.com/moveover/. They have automated migration tools called MoveOver for both server and desktop. Automatically transfer all user-defined files, emails, email config, desktop environment,etc. hope this helps.
To go along with the other posters, yes ACLs give you this control over permissions and I believe they are included by default in the 2.6 kernel. Certainly Fedora Core 3 and RHEL 4 include them.