Yet again a good number of days have gone by without a blog posting. Projects and upgrades have consumed most of my time in the last few weeks.
NX/NoMachine 4 Released & Tablets
NX 4 was released. I had installed and looked over various beta builds as it was being developed, and I put the released version on a VM copy of your primary GNOME desktop server. The install process is a piece of cake, and you just edit a few .cfg files to point to the right scripts to run at startup and away you go.
One notable feature is the ability to connect with a browser and get a full GNOME desktop and run all of your software without modification. As seen below, you enter a URL and up came the desktop. Speed on Firefox 24/Linux is very acceptable.
![]()
This browser solution has not proven itself to work well on tablets, even over local WiFi. But I was happy to see this on the download page:
![]()
Tablets have been interesting to me because one school of thought is that people would log in and get a GNOME desktop and work as they do from their desk. Another thought is that they would work more client/server and download documents and use local software and then upload. By far users have expressed more interest in the former. They don't seem to want to use different/local software and want to use what works here at the City. So the clients for iOS and Android will be greatly appreciated and used.
The biggest issue for us right now with NX 4 is that the clients are not yet ready for deployment in a multi-user environment with "regular users". NX3 clients allowed you to automate the login process and once they entered their account/password...GNOME came right up. NX 4 has a lot of prompts and questions which are better suited for power users. As it stands right now, we would be bombarded with questions and support and there would be a drop in productivity. If a user is attempting to connect, they have work that must be finished. If they fail, that work doesn't get done. There are plans on the roadmap from what I understand to add more of these entperprise features in the future, and we'll have to wait for them before we can deploy.
EDIT: Sarah from Nomachine posted information on this issue on the comments section. We were unaware and are going to test.
Support Portal Has More Features
Our in-house support portal is still helping us monitor all aspects of a thin client and centralized environment, and some modifications have been made. It's wonderful that when you have ideas, you can just throw in a few lines of code and it's done.
We're using the issue tracking module now for all calls received and the data is very interesting. In the shot below you can see that in the last 24 hours our primary support call center got around 20 calls. This is with many hundreds of users logging in and out of the workstations and using software. Our current regular concurrent load is right around 300 users. I have said it many times before, that using thin clients allows your staff to work on maintenance and future projects vs spending lots of resources keeping support intensive PCs running. I marked the general trends of problems
(RED) Linux/GNOME/Desktop problems Only 1 all day!
(GREEN) Phones
(PURPLE) Problems with hosted/cloud apps
(BLUE) Problems with MS Windows on various specialized computers
(BLACK) End user questions about working software or procedures.
![]()
I also hacked in a quick screen on the user detail area to show documents edited by the user. Very often people call and have "lost" their document...or sometimes they make edits to a document in /tmp accidentally and then it's lost when this area is purged. Now at a glance we can assist them without having to look on backup tapes and such. Very helpful.
![]()
LibreOffice 4.1 , Handling Rollbacks
This isn't unique to LibreOffice 4.1, because it's happened going back all the way back to OpenOffice 1.1. Whenever you get a patch or even more so, whenever you get a major release there are always issues where documents don't work correctly. I keep all of the old versions on the server and can always test and find the regression. Standard procedure then is to rollback a user until we get a patch and then upgrade them again to the latest release. This was done by me, with hard coded scripts. I put this into the support portal and now anyone in IT can either roll their own account back or rollback another user to solve these types of problems. All of this activity is logged, and we're nagged once a day of people on prior versions so that we continue to try and resolve their issue.
![]()
We have three bad issues with LO 4.1 right now, affecting about a dozen people. 1) There is a bug with building graphs from spreadsheet cells 2) There is a bug for selecting sections of spreadsheets for printing 3) There is a bug with drop down cells in Calc.
These users are on 4.0 and everyone is happy and working.
Firefox 24 Bug And Quick Response
Firefox 23 had an issue with saving files, the files were saved as 600 on Linux and no longer honored umask. When then happened was that work flow for many people was interrupted because as they shared files with others, they could not be opened. In general users do not understand how to use file permissions nor how to change them. The Firefox developers came through in a pinch and a patch is already landing in time for version 25. Thanks guys.
Alfresco Testing Continues.
We have three non IT people starting to test Alfresco 4.2 as a proof of concept. Deployment is not imminent at this point because we don't have the staffing; but it's gaining some steam and people are starting to see the power of working in this manner. The testers are putting PDF content into the Alfresco database and then seeing that it's immediately available on their tablets. We're meeting today again to discuss how to connect with LibreOffice, and will talk about the concept of using hybrid PDF as our official City file format. Right now LO is a bit clunky with this format, but we see possibilities I can start creating feature requests and possibly funding improvements.
Alfresco supports RSS feeds, so I have been building a proof of concept systray application which would alert users of changes to documents and work flow that need their attention. In the shot below, the icon is sitting in the tray and clicking on the icon shows the last document updates. At our meeting today we'll talk about this idea and whether we want to test notification popups too. The strength of open source: being able to rapidly build prototypes and then deploy solutions quickly with little to no cost.
![]()
SuseCon Orlando
It's only a few weeks away, and I'll be attending along with my coworker. Find us and say Hi!
NX/NoMachine 4 Released & Tablets
NX 4 was released. I had installed and looked over various beta builds as it was being developed, and I put the released version on a VM copy of your primary GNOME desktop server. The install process is a piece of cake, and you just edit a few .cfg files to point to the right scripts to run at startup and away you go.
One notable feature is the ability to connect with a browser and get a full GNOME desktop and run all of your software without modification. As seen below, you enter a URL and up came the desktop. Speed on Firefox 24/Linux is very acceptable.
This browser solution has not proven itself to work well on tablets, even over local WiFi. But I was happy to see this on the download page:
The biggest issue for us right now with NX 4 is that the clients are not yet ready for deployment in a multi-user environment with "regular users". NX3 clients allowed you to automate the login process and once they entered their account/password...GNOME came right up. NX 4 has a lot of prompts and questions which are better suited for power users. As it stands right now, we would be bombarded with questions and support and there would be a drop in productivity. If a user is attempting to connect, they have work that must be finished. If they fail, that work doesn't get done. There are plans on the roadmap from what I understand to add more of these entperprise features in the future, and we'll have to wait for them before we can deploy.
EDIT: Sarah from Nomachine posted information on this issue on the comments section. We were unaware and are going to test.
Support Portal Has More Features
Our in-house support portal is still helping us monitor all aspects of a thin client and centralized environment, and some modifications have been made. It's wonderful that when you have ideas, you can just throw in a few lines of code and it's done.
We're using the issue tracking module now for all calls received and the data is very interesting. In the shot below you can see that in the last 24 hours our primary support call center got around 20 calls. This is with many hundreds of users logging in and out of the workstations and using software. Our current regular concurrent load is right around 300 users. I have said it many times before, that using thin clients allows your staff to work on maintenance and future projects vs spending lots of resources keeping support intensive PCs running. I marked the general trends of problems
(RED) Linux/GNOME/Desktop problems Only 1 all day!
(GREEN) Phones
(PURPLE) Problems with hosted/cloud apps
(BLUE) Problems with MS Windows on various specialized computers
(BLACK) End user questions about working software or procedures.
I also hacked in a quick screen on the user detail area to show documents edited by the user. Very often people call and have "lost" their document...or sometimes they make edits to a document in /tmp accidentally and then it's lost when this area is purged. Now at a glance we can assist them without having to look on backup tapes and such. Very helpful.
LibreOffice 4.1 , Handling Rollbacks
This isn't unique to LibreOffice 4.1, because it's happened going back all the way back to OpenOffice 1.1. Whenever you get a patch or even more so, whenever you get a major release there are always issues where documents don't work correctly. I keep all of the old versions on the server and can always test and find the regression. Standard procedure then is to rollback a user until we get a patch and then upgrade them again to the latest release. This was done by me, with hard coded scripts. I put this into the support portal and now anyone in IT can either roll their own account back or rollback another user to solve these types of problems. All of this activity is logged, and we're nagged once a day of people on prior versions so that we continue to try and resolve their issue.
We have three bad issues with LO 4.1 right now, affecting about a dozen people. 1) There is a bug with building graphs from spreadsheet cells 2) There is a bug for selecting sections of spreadsheets for printing 3) There is a bug with drop down cells in Calc.
These users are on 4.0 and everyone is happy and working.
Firefox 24 Bug And Quick Response
Firefox 23 had an issue with saving files, the files were saved as 600 on Linux and no longer honored umask. When then happened was that work flow for many people was interrupted because as they shared files with others, they could not be opened. In general users do not understand how to use file permissions nor how to change them. The Firefox developers came through in a pinch and a patch is already landing in time for version 25. Thanks guys.
Alfresco Testing Continues.
We have three non IT people starting to test Alfresco 4.2 as a proof of concept. Deployment is not imminent at this point because we don't have the staffing; but it's gaining some steam and people are starting to see the power of working in this manner. The testers are putting PDF content into the Alfresco database and then seeing that it's immediately available on their tablets. We're meeting today again to discuss how to connect with LibreOffice, and will talk about the concept of using hybrid PDF as our official City file format. Right now LO is a bit clunky with this format, but we see possibilities I can start creating feature requests and possibly funding improvements.
Alfresco supports RSS feeds, so I have been building a proof of concept systray application which would alert users of changes to documents and work flow that need their attention. In the shot below, the icon is sitting in the tray and clicking on the icon shows the last document updates. At our meeting today we'll talk about this idea and whether we want to test notification popups too. The strength of open source: being able to rapidly build prototypes and then deploy solutions quickly with little to no cost.
SuseCon Orlando
It's only a few weeks away, and I'll be attending along with my coworker. Find us and say Hi!