Staying up a bit late tonight and came upon some websites which might be of interest to some of you.
Unix Tutorials and Videos based on Ubuntu. They also have tutorials on other distros. Nice site.
http://www.unix-tutorials.com/tutorials.php?os=Ubuntu
Tutorials on Ubuntu, GIMP, etc - both HTML and video tutorials also has a bunch of free ebooks.
http://vntutor.blogspot.com/2007/06/free-online-ubuntu-linux-books.html
Near the bottom of this page, they have whitepapers, articles and how-tos regarding Ubuntu. Also some comparisons of Ubuntu vs MSoft, MAC, etc.
http://www.easy-ubuntu-linux.com/add-ubuntu-software.html
Friday, August 3, 2007
Thursday, August 2, 2007
Another Satisfied Customer
The last week or so I have been working on creating a custom version of LAVA for a client which would like to deploy a linux desktop to 320 users. After several technical meetings and several showcases we have finally built a live install cd image that takes into account all the hardware typically found at the various client's sites.
The administrative managers have all been generous and are genuinely excited about moving off of Windows XP. Most have had really bad experiences with XP. The network has been plagued with spyware, dropped connections, trojans, and the occasional window's update that went terribly wrong.
Walking around and speaking to the users I have found many are surprised at how mature LAVA, Ubuntu looks. Most shockingly is their expressions when I map their Window's 2003 fileserver shares and double click on an .XLS and .DOC file. You can tell in their expressions they are baffled at how easy Linux is. It is such a great feeling to see how well LAVA, Ubuntu has made moving users over to an alternative desktop.
I had some problems with some of the printers at the client side but after playing with compatible drivers, I was able to select a driver that met all the reporting and formatting requirements.
Also RDP via a scripted bash file was easy enuff to create. The client wanted redirected printers as well as drives so command line scripting was necessary. Once I mastered the settings, I built a BASH script and voila a desktop icon for the users to click on.
Internet Explorer - I cannot seem to get away from you.
Yep the client had some websites that not only need IE but also the Microsoft VM. Yuck. But with Wine installed, IE4Linux worked like a charm.
Having meet all the requirements on the field, it is time to actually hardcode those into a ISO and build a cd.
Alot of work still to go but if it wasn't Linux work, it wouldn't be fun.
The administrative managers have all been generous and are genuinely excited about moving off of Windows XP. Most have had really bad experiences with XP. The network has been plagued with spyware, dropped connections, trojans, and the occasional window's update that went terribly wrong.
Walking around and speaking to the users I have found many are surprised at how mature LAVA, Ubuntu looks. Most shockingly is their expressions when I map their Window's 2003 fileserver shares and double click on an .XLS and .DOC file. You can tell in their expressions they are baffled at how easy Linux is. It is such a great feeling to see how well LAVA, Ubuntu has made moving users over to an alternative desktop.
I had some problems with some of the printers at the client side but after playing with compatible drivers, I was able to select a driver that met all the reporting and formatting requirements.
Also RDP via a scripted bash file was easy enuff to create. The client wanted redirected printers as well as drives so command line scripting was necessary. Once I mastered the settings, I built a BASH script and voila a desktop icon for the users to click on.
Internet Explorer - I cannot seem to get away from you.
Yep the client had some websites that not only need IE but also the Microsoft VM. Yuck. But with Wine installed, IE4Linux worked like a charm.
Having meet all the requirements on the field, it is time to actually hardcode those into a ISO and build a cd.
Alot of work still to go but if it wasn't Linux work, it wouldn't be fun.
Friday, July 27, 2007
Back On The Saddle Again
So it's been a while since I have updated my blog. So what have I been up to lately? Well I have been working with several new clients and new Ubuntu installs.
I just recently oversaw the conversion of an Microsoft Exchange installation.
We replaced Windows 2003 Enterprise server running Exchange 2003 with Ubuntu running Citadel. Total users: 523.
After running the prototype email service over the course of 6 weeks with a small subset of the company's employees we moved onto production in mid June.
The total conversion of 523 users took approximately two weeks. Part of the quick conversion was the fact that the client did not have to replace Microsoft Office. Once the server was setup, our technical support team just had to change Outlook settings on all the user's profiles. Approximately 36 hours to backup all the users email data and transfer to new host and approximately 15 minutes per user. We also spent three days working out the Push technology in Citadel to connect it to their blackberrys and PDAS which required us to setup the SMS gateway.
The system has been online for four weeks now and the following statistically data was data-mined by the client.
20% less false positives when sending and receiving
38.5 % less spam
The client also reports that the email system seems faster. Moving in and out of their individual folders has become instant.
The only con was the generic webmail interface when compared to the OWL interface provided by Exchange. To combat this we install apache and setup RoundCube Webmail and designed a new CSS template with customized company logos, etc. Roundcube has alot of AJAX goodness to it. With some customization it looks and acts like Gmail or Yahoo.
Needless to say they are happy. They are planning on converting the now obsolete Exchange server into a fileserver sometime in the future.
We are finishing up with setting up an RSync server to pull the actual data folders containing each users email. This way we have a live daily backup of the user's personal email, contacts, etc. The Rsync server will also be Ubuntu.
It is important to also note that new server is actually running on slightly less hardware than the Exchange server was. In fact, each of these servers are virtual machines running on 4 separate pieces of hardware all replicating to backup vm servers. Any one of them can go down and load balancing changes points the clients to the backup server. Host VM server is also running Ubuntu and VMWARE server. Part of the initial requirements was redundancy. The client in the past relied on the one Exchange server for the entire domain with just a bounce back service provided by their ISP.
Over the next couple weeks I will drop off the email project and begin converting their firewalls from Microsoft ISA to a Linux firewall called Endian. I have had great success with it and it allows much more control over your incoming and outgoing protocols than Microsoft ISA. Part of the initial requirement is that several of the firewalls need to support VPN tunneling as well as multiple WAN and VLAN support. I showcased Endian to the client and highlighted not only the functional improvements switching to Endian but also relayed the fact that Endian allows protocol priority, packet shaping, automatic Proxy filtering, etc.
I just recently oversaw the conversion of an Microsoft Exchange installation.
We replaced Windows 2003 Enterprise server running Exchange 2003 with Ubuntu running Citadel. Total users: 523.
After running the prototype email service over the course of 6 weeks with a small subset of the company's employees we moved onto production in mid June.
The total conversion of 523 users took approximately two weeks. Part of the quick conversion was the fact that the client did not have to replace Microsoft Office. Once the server was setup, our technical support team just had to change Outlook settings on all the user's profiles. Approximately 36 hours to backup all the users email data and transfer to new host and approximately 15 minutes per user. We also spent three days working out the Push technology in Citadel to connect it to their blackberrys and PDAS which required us to setup the SMS gateway.
The system has been online for four weeks now and the following statistically data was data-mined by the client.
20% less false positives when sending and receiving
38.5 % less spam
The client also reports that the email system seems faster. Moving in and out of their individual folders has become instant.
The only con was the generic webmail interface when compared to the OWL interface provided by Exchange. To combat this we install apache and setup RoundCube Webmail and designed a new CSS template with customized company logos, etc. Roundcube has alot of AJAX goodness to it. With some customization it looks and acts like Gmail or Yahoo.
Needless to say they are happy. They are planning on converting the now obsolete Exchange server into a fileserver sometime in the future.
We are finishing up with setting up an RSync server to pull the actual data folders containing each users email. This way we have a live daily backup of the user's personal email, contacts, etc. The Rsync server will also be Ubuntu.
It is important to also note that new server is actually running on slightly less hardware than the Exchange server was. In fact, each of these servers are virtual machines running on 4 separate pieces of hardware all replicating to backup vm servers. Any one of them can go down and load balancing changes points the clients to the backup server. Host VM server is also running Ubuntu and VMWARE server. Part of the initial requirements was redundancy. The client in the past relied on the one Exchange server for the entire domain with just a bounce back service provided by their ISP.
Over the next couple weeks I will drop off the email project and begin converting their firewalls from Microsoft ISA to a Linux firewall called Endian. I have had great success with it and it allows much more control over your incoming and outgoing protocols than Microsoft ISA. Part of the initial requirement is that several of the firewalls need to support VPN tunneling as well as multiple WAN and VLAN support. I showcased Endian to the client and highlighted not only the functional improvements switching to Endian but also relayed the fact that Endian allows protocol priority, packet shaping, automatic Proxy filtering, etc.
Friday, June 1, 2007
WebPortal Structure
Schema for WebPortal 1.0
Finishing up the structure for the internals of the Web Portal.
The schema just outlines the fields I would need to store published application information. This assumes all other information such as user name , password, and group is stored inside either Open LDAP or Active Directory. In this first version of WebPortal, I have added rdp, vnc and web links as publishable items for end-users. The weblinks I think is handy; it lets you centralize things like webmail, and/or company approved sites. After I implement the site and have all the features, I plan to add, X sessions and some features to admin the users account in OpenLDAP and/or AD. Things like allowing the user to change their own password, etc.
Finishing up the structure for the internals of the Web Portal.
The schema just outlines the fields I would need to store published application information. This assumes all other information such as user name , password, and group is stored inside either Open LDAP or Active Directory. In this first version of WebPortal, I have added rdp, vnc and web links as publishable items for end-users. The weblinks I think is handy; it lets you centralize things like webmail, and/or company approved sites. After I implement the site and have all the features, I plan to add, X sessions and some features to admin the users account in OpenLDAP and/or AD. Things like allowing the user to change their own password, etc.
Thursday, May 31, 2007
Project News
Over the last month, I have been in heavy development with several projects, one of which is the LAVA project.
I wanted to update my blog and give an overview of some of the things I am doing with Ubuntu:
I am still open with the Terminal Server. So far I have been able to build a terminal server without LTSP (Linux Terminal Server Project) For my users and customers. I find the LTSP too limiting for serveral reasons. It assumes the client pcs are on the same network.
The client pcs I am servicing are not and therefore, I cannot give them an IP from dhcp or require that they run Linux on their PC.
The whole value of hosting apps or an environment to me, means giving them the app or desktop to any device, anywhere. This means running it without installing anything on their desktop and running it reliable across; Windows, Mac, and Linux.
Phase One:
User Desktop
Using UPX has made this possible by bunding all the required OS dlls, exes, and resources into a single binary that can run without installing. SO I am able to make a client exe that connects to the terminal server and runs the desktop or application. I have been able to build a client exe that rdps into a server, a client exe that ssh into server and runs either app or desktop, and a NX client that connects to freenx on server.
Phase Two:
Picking a Terminal server on Linux.
Solution One: TO X or Not
Linux has always had a terminal server built into it via X. The ability to have remote X served to clients has always been available for as long as X has been around. But making it easy to implement has not been. Using openssh on the backend server and connecting to it from Mac or Windows is easier now. Using opensource products such as JCraft or Xwin makes a connection to an X server easier. With UPX and alittle fine tuning and you can create a connection as well as shrink-wrap it into a single exe that you can distribute to your users without having to configure it and you have a solution that will work for even non-savy computer users.
Solution Two: XRDP
A recent entry into remote hosting is XRDP. Simply put, it makes Linux into a RDP terminal server so your window users do not even need a client. The normal Remote Desktop applet works fine.
MAC uses can use several RDP clients and they work rather well on my IMAC. Without running tests on performance and compression, this solution seems the best and easiest way to implement a terminal server from an IT standpoint as well as from a consumer standpoint. But because the technology is new and because it is based on RDP, I am leaning towards the normal X way of connecting.
Solution Three: FreeNX
FreeNX uses a custom protocol as well as custom client. There are several design problems I see with the current NX implementation.
1) It requires a custom port to be open on firewalls. Corporate America hates this and I hate it cause, my techs would have many calls just regarding connecting to the service. "DO you have XP firewall, Do you have MCAffee or Norton Firewalls installed? Do you know how to disable your firewall? What model Belkin do you have?" - Too much trouble just to make a connection. It needs to be painless.
2) In order to get printers to work the client has to 'SHARE' out their printer via SMB. I really, really hate this, most users do not know how to share out a printer let alone a folder. This also makes printing for MAC users very hard.
3) The custom client has multiple issues with VISTA.
Printing has always been an issue when it comes to remote hosting apps or desktops. Windows, Citrix, X, RDP, and even FreeNX all have somewhat broken ways of managing printing. I have bypassed this problem in two ways.
1) I have used a cups filter on the server to spool print jobs and attach to email which is forward to client. The client prints to the printer and a dialog box pops up asking for email address. They input it once and it remembers it by writing a txt file in the user's home directory. The filter than makes a PDF of the print output and uses sendmail to send to email address. This solution is simple and easy to implement.
Unfortunately it does not work if the user/client is hosting email with you via Evolution or such.
2) Solution two is in the works. It involves building a webservice on the server and serving print output as a pdf file via webdav to client exe which then opens the user's default pdf reader. This solves all the issues but requires some programming on my end for Windows and MAC binary clients. This is a longterm solution.
Selecting the terminal server: I am leaning towards X via SSH but will be testing each out over the next month.
Final Phase.
Building a web portal.
Ultimately I would like the client to download a single exe, possible 5mb. Which will have everything bundled in it, FREENX client or XWIN, SSH, etc. whichever i choose ultimately. It will have everything in the exe that it needs to connect to server farms without installing.
The exe will be a custom web browser using either IE, Mozilla or Safari - depending on the client platform to connect to a website I am designing that will allow the user to login, and serve them apps via txt xml files.
The site will have an admin section where we would create published apps which are stored in MYSQL.
When the client logs in the credentials are sent to OpenLDAP or ActiveDirectory. Their Username and Passwords as well as their group are stored in session variables. The site uses this information to pull the list of published apps the client has been given access to.
The published apps will be links to dynamicall created xml files that will have extensions such as .RDP or .X or .NX
When the client clicks on the links of the apps and the file is served back to the client via apache, the portal application will run either freenx client if it recieves a .NX file or a RDP client if it receives a .RDP file, etc. It then runs the appropriate client I bundled in the exe and makes the connection to the hosted app or desktop.
This way, the portal will really be a portal to apps and desktops both hosted by me or hosted by others.
I am currently writing a version in PHP with LDAP library and it works fine. So far I have the portal service .RDP, .VNC, and .X files. I wanted to do it in Ruby but I am not that efficient yet in the Ruby language. I do most of my web programming in .NET, PHP or Coldfusion. Since I am trying to make my datacenter all opensource, I choose PHP.
There is alot of work still to do, but because of Linux, because of Ubuntu, because of Open Source, it makes all this possible.
I wanted to update my blog and give an overview of some of the things I am doing with Ubuntu:
- LAVA editions: CD, Plus, and Development Editions are pretty much done.
- LAVA Terminal Server
- LAVA LAMP: Apache, PHP, Webmin, ProFTP
- LAVA Secure: Security toolkit CD
- LAVA Share: Fileserver
- LAVA Mailer: Email Platform: Picked Citadel as Exchange replacement.
I am still open with the Terminal Server. So far I have been able to build a terminal server without LTSP (Linux Terminal Server Project) For my users and customers. I find the LTSP too limiting for serveral reasons. It assumes the client pcs are on the same network.
The client pcs I am servicing are not and therefore, I cannot give them an IP from dhcp or require that they run Linux on their PC.
The whole value of hosting apps or an environment to me, means giving them the app or desktop to any device, anywhere. This means running it without installing anything on their desktop and running it reliable across; Windows, Mac, and Linux.
Phase One:
User Desktop
Using UPX has made this possible by bunding all the required OS dlls, exes, and resources into a single binary that can run without installing. SO I am able to make a client exe that connects to the terminal server and runs the desktop or application. I have been able to build a client exe that rdps into a server, a client exe that ssh into server and runs either app or desktop, and a NX client that connects to freenx on server.
Phase Two:
Picking a Terminal server on Linux.
Solution One: TO X or Not
Linux has always had a terminal server built into it via X. The ability to have remote X served to clients has always been available for as long as X has been around. But making it easy to implement has not been. Using openssh on the backend server and connecting to it from Mac or Windows is easier now. Using opensource products such as JCraft or Xwin makes a connection to an X server easier. With UPX and alittle fine tuning and you can create a connection as well as shrink-wrap it into a single exe that you can distribute to your users without having to configure it and you have a solution that will work for even non-savy computer users.
Solution Two: XRDP
A recent entry into remote hosting is XRDP. Simply put, it makes Linux into a RDP terminal server so your window users do not even need a client. The normal Remote Desktop applet works fine.
MAC uses can use several RDP clients and they work rather well on my IMAC. Without running tests on performance and compression, this solution seems the best and easiest way to implement a terminal server from an IT standpoint as well as from a consumer standpoint. But because the technology is new and because it is based on RDP, I am leaning towards the normal X way of connecting.
Solution Three: FreeNX
FreeNX uses a custom protocol as well as custom client. There are several design problems I see with the current NX implementation.
1) It requires a custom port to be open on firewalls. Corporate America hates this and I hate it cause, my techs would have many calls just regarding connecting to the service. "DO you have XP firewall, Do you have MCAffee or Norton Firewalls installed? Do you know how to disable your firewall? What model Belkin do you have?" - Too much trouble just to make a connection. It needs to be painless.
2) In order to get printers to work the client has to 'SHARE' out their printer via SMB. I really, really hate this, most users do not know how to share out a printer let alone a folder. This also makes printing for MAC users very hard.
3) The custom client has multiple issues with VISTA.
Printing has always been an issue when it comes to remote hosting apps or desktops. Windows, Citrix, X, RDP, and even FreeNX all have somewhat broken ways of managing printing. I have bypassed this problem in two ways.
1) I have used a cups filter on the server to spool print jobs and attach to email which is forward to client. The client prints to the printer and a dialog box pops up asking for email address. They input it once and it remembers it by writing a txt file in the user's home directory. The filter than makes a PDF of the print output and uses sendmail to send to email address. This solution is simple and easy to implement.
Unfortunately it does not work if the user/client is hosting email with you via Evolution or such.
2) Solution two is in the works. It involves building a webservice on the server and serving print output as a pdf file via webdav to client exe which then opens the user's default pdf reader. This solves all the issues but requires some programming on my end for Windows and MAC binary clients. This is a longterm solution.
Selecting the terminal server: I am leaning towards X via SSH but will be testing each out over the next month.
Final Phase.
Building a web portal.
Ultimately I would like the client to download a single exe, possible 5mb. Which will have everything bundled in it, FREENX client or XWIN, SSH, etc. whichever i choose ultimately. It will have everything in the exe that it needs to connect to server farms without installing.
The exe will be a custom web browser using either IE, Mozilla or Safari - depending on the client platform to connect to a website I am designing that will allow the user to login, and serve them apps via txt xml files.
The site will have an admin section where we would create published apps which are stored in MYSQL.
When the client logs in the credentials are sent to OpenLDAP or ActiveDirectory. Their Username and Passwords as well as their group are stored in session variables. The site uses this information to pull the list of published apps the client has been given access to.
The published apps will be links to dynamicall created xml files that will have extensions such as .RDP or .X or .NX
When the client clicks on the links of the apps and the file is served back to the client via apache, the portal application will run either freenx client if it recieves a .NX file or a RDP client if it receives a .RDP file, etc. It then runs the appropriate client I bundled in the exe and makes the connection to the hosted app or desktop.
This way, the portal will really be a portal to apps and desktops both hosted by me or hosted by others.
I am currently writing a version in PHP with LDAP library and it works fine. So far I have the portal service .RDP, .VNC, and .X files. I wanted to do it in Ruby but I am not that efficient yet in the Ruby language. I do most of my web programming in .NET, PHP or Coldfusion. Since I am trying to make my datacenter all opensource, I choose PHP.
There is alot of work still to do, but because of Linux, because of Ubuntu, because of Open Source, it makes all this possible.
Tuesday, May 1, 2007
Remote Applications
I received a question on whether my previous exe could be customized to run an application 'headless.'
Specifically if an app could be run without giving access to a whole desktop experience. The answer is yes.
I have uploaded an example single exe on my site.
http://www.ansotech.com/debs/portalnxa.exe
I hardcoded the exe to remote into my desktop and run firefox.
The user will see firefox launch as if on their desktop.
Please use
username: demo
password: demo123
Specifically if an app could be run without giving access to a whole desktop experience. The answer is yes.
I have uploaded an example single exe on my site.
http://www.ansotech.com/debs/portalnxa.exe
I hardcoded the exe to remote into my desktop and run firefox.
The user will see firefox launch as if on their desktop.
Please use
username: demo
password: demo123
NX your worries away
I wanted to thank Jim for sending me a post regarding NX.
For those who do not know what NX is, here is a summary. NX is a opensource alternative to Microsoft Terminal Services. It allows users on Windows and Linux to connect to a central server or workstation and run the applications that you centrally install for your enterprise. For IT administrators it saves time and money.
I have spent the last several months trying to make NX work correctly in Ubuntu and there is still work to be done. The ultimate goal is to replace the Windows 2003 servers I use as Terminal servers in my datacenter with Ubuntu running NX Server.
I wanted to give everyone a recap on my progress as well as allow you WINDOWEZ users a look into connecting the window clients to ubuntu or in my case LAVA Linux. Before I receive hate mail, LAVA is just a highly customized Ubuntu but it is still Ubuntu.
I have been able to UPX the windows based NX client as well as XMING and create a single exe that can be run without installing or configuring on windows. The user just saves the exe onto their desktop and double clicks. It automatically unloads all the dlls into memory that it needs as well as the configuration options that i have hard-coded for my environment. NOTE: It does not install anything on the Windows machine. Everything runs in memory. So removing it is as simple as deleting the exe. Upgrading is as simple as replacing exe.
The session connects to a default installation of LAVA PLUS I have running in my datacenter.
If anyone would like to try it out, please feel free to save the following exe onto your Windows 2000, XP or VISTA computer. That's right, I was able to compile and fix the client piece so that it runs on Vista.
Here is the link:
http://www.ansotech.com/debs/portalnx.exe
Username: demo
Password: demo123
Please let me know what you think. I am going to keep the access open until tomorrow afternoon.
For those who do not know what NX is, here is a summary. NX is a opensource alternative to Microsoft Terminal Services. It allows users on Windows and Linux to connect to a central server or workstation and run the applications that you centrally install for your enterprise. For IT administrators it saves time and money.
I have spent the last several months trying to make NX work correctly in Ubuntu and there is still work to be done. The ultimate goal is to replace the Windows 2003 servers I use as Terminal servers in my datacenter with Ubuntu running NX Server.
I wanted to give everyone a recap on my progress as well as allow you WINDOWEZ users a look into connecting the window clients to ubuntu or in my case LAVA Linux. Before I receive hate mail, LAVA is just a highly customized Ubuntu but it is still Ubuntu.
I have been able to UPX the windows based NX client as well as XMING and create a single exe that can be run without installing or configuring on windows. The user just saves the exe onto their desktop and double clicks. It automatically unloads all the dlls into memory that it needs as well as the configuration options that i have hard-coded for my environment. NOTE: It does not install anything on the Windows machine. Everything runs in memory. So removing it is as simple as deleting the exe. Upgrading is as simple as replacing exe.
The session connects to a default installation of LAVA PLUS I have running in my datacenter.
If anyone would like to try it out, please feel free to save the following exe onto your Windows 2000, XP or VISTA computer. That's right, I was able to compile and fix the client piece so that it runs on Vista.
Here is the link:
http://www.ansotech.com/debs/portalnx.exe
Username: demo
Password: demo123
Please let me know what you think. I am going to keep the access open until tomorrow afternoon.
Subscribe to:
Posts (Atom)

