Replacing some of the more specialized apps with something that would work on Linux will be more challenging. I have yet to find anything in the Linux landscape that can compete with some of the project management applications available for Windows, though Planner 0.14.1 is looking promising in some of the testing I've recently been doing. The same is true for Visio (which I actually think is sub-par compared to something like SmartDraw which I use in my business). Even if these apps can't be replaced, it should be possible to move to a more mixed environment.

One of the big stumbling blocks for me though was what to do about that ERP application. It is Windows based and is accessed via a Remote Desktop Connection. I have had limited experience working with hosted Windows apps. With my own business network, I was always connecting Linux to Linux, which is very easy. But connecting to a Windows box from my desktop was a challenge as it always seemed I needed some .NET or aspx stuff to make the connection.

On top of that, I'm considering the idea of trying to get a Linux server deployed in the organization for some skunkworks projects (like setting up a wiki, maybe some other stuff) to help promote collaboration (there is way...way too much use of e-mail for sharing documents right now). That was another challenge though since I would only have a Windows desktop available to me (at least for the time being) and I would need a way to connect to the Linux server to set stuff up and maintain it (and yes, I'm aware I could use putty to ssh in to the command line - my kung fu is just too weak to do everything via command line though).

The combination of the above led me to want to get an answer to two problems - how to connect from a Linux desktop to a Windows server and how to connect from a Windows desktop to a Linux server.

Little did I realize it, but the Linux to Windows connection was fairly easy. In fact, I already had the software installed here on my desktop - rdesktop! So I did some testing using a Windows machine here on my network and lo and behold, making the connection was no problem. A nice side benefit of this will be the fact that I can now work in QuickBooks from my desktop! That seems to resolve the first issue. Still some other items to test like whether I would be able to print locally (which even with the Windows desktop requires some configuration work). And if Linux desktops were deployed, I'm not sure we have drivers for some of the bigger multi-function units like our Danka copier. Assuming those issues can be resolved, this testing has at least eliminated the issue of being able to connect to the ERP server from a Linux desktop from the equation.

The second question led me to an application called WinaXe. There are probably some others out there as well (I once tested NX Client but found it lacking). I tried installing the evaluation on my laptop and after some configuration, I was able to connect to my Linux server's desktop. Woohoo! The only problem is the WinaXe package has to be bought - $99 for a single user (seems kind of steep for what it does). Part of their advertising indicates their package is a simpler way to connect than say Citrix (which I've never been impressed with).

So at this point I've figured out how I should be able to get around at least the first big stumbling block - making a remote desktop connection from Linux to a Windows host. Obviously there is still a lot of work to be done to address other applications and the financial analysis has to be done. And the clock is ticking as Microsoft plans to stop making XP available in the summer of 2008 (it is a Dell shop I'm working at now). Lots of challenges, but I think it may be possible to transition them away from Microsoft, resulting in a much better network at lower cost.

At the very least though, I've now figured out how I can support some of my family members remotely and I can start using my desktop for even more of the work I do in my business!