Silicon Shecky

A few days ago I wrote about A problem with Add-Ons and Firefox 5, along with no support anymore for Firefox 4. Now Firefox is really trying to commit suicide.

Firefox was a great browser. Yes, I say was, because it won’t last that much longer. Not with the path they have chosen at least. Focusing on the consumer market isn’t a bad thing. You will get people who will use Firefox at home when their corporations don’t allow for its use internally. Actively saying, “We don’t care about corporations,” though is akin to committing suicide.

Mozilla might not care about the corporate environment, but they do need to be aware of it. With hosted apps, and work websites becoming more and more prevalent in the world, to survive on a consumer end, you need to be. Heck, most of the web sites that people visit are done by corporations. Now with the accelerated pace of releases, and no support for the prior release, web designers will need to check more and more versions of Firefox against their websites to make sure that they aren’t broken by the changes. The amount of manpower and time will drive up the cost of web development. Sites will shut down, or the other logical solution will happen.

Sites won’t try to be compatible with Firefox anymore. They just won’t care. Chrome is passing up Firefox in usage, and Internet Explorer still has the majority of market share. Google just needs to support prior versions for a corporate environment, just like Microsoft has already started to jump at companies reminding them they won’t run into a lack of security patches. Heck, IE8 and 9 are pretty good from a security standpoint as it is.

Firefox thinks that doesn’t matter. Consumers will continue to use Firefox. No, they won’t if it doesn’t render web sites properly. The lack of foresight on Mozilla’s part is pretty amazing. First thing taught in retail and marketing is that 1 complaint, 1 problem with a client, can hurt you in a huge way, as they spread the word to avoid such an item.

Six weeks between releases is ambitious, and hurts consumers who’s plug ins and add-ons might now work with the latest version. Can new versions of the plug ins be ready in under the time it takes for the next version to come out? This is the other side of the death spiral Mozilla is putting itself into. Consumers love the plug ins. If they don’t work, what good is Firefox to them anyway?

There is still time for Mozilla to save itself. They have to support a 3 month old browser they put out. They have to show the world that they care about more than their own egos. They have to stop being the poster child for what can be wrong with open source, and get back to showing what is right with it.

With all the hacks going on out on the net today, patching your machines is more critical than ever.

Microsoft is releasing 16 Patches, 9 of which Microsoft deems critical. Patches include Windows, Office, and .Net, and all attempt to address RCE attacks.

Oracle has also released a major patch for Java in the past few days which addresses a number of security vulnerabilities. Adobe has patches out recently for Flash, Apple is playing whack-a-mole with malware, and basically there is a lot of patching to do.

Don’t forget though, with all these patches, to test them before deploying them. It doesn’t happen very often, but some patches can break your software.

The Public folder issue with the Exchange 2010 migration has been solved. An old lesson was reconfirmed. Then the chewing out of myself commenced.

Many years ago, when I was first learning to fix and build PC’s, I would go to the local monthly computer show. Each month would mean some new part for upgrading or replacing. It was fun to learn about these things, see what I could do with them, even cause the parts to eventually die out because of my own stupidity. It was a glorious time.

Eventually though I ran into a problem that took forever to solve. I had replaced something in my computer, and straightened up the cables connecting the PC to everything. I fired up the machine, and… no sound. Checked the settings in windows, checked the driver, pulled the card out, tried a different card, all still with no sound. 6 months I kept dealing with this problem, checked everything I could, tried new cards and still no sound. Well I checked almost everything I could. In month 6 of this issue, I went to do another cable cleanup, and that is when I found that I, for 6 months, had the microphone plugged into the speaker jack and the speakers plugged into the microphone jack. This was before they color coded everything, and for 6 months I swore that they were plugged in right. I assumed they were is more like it.

For many years I have told this tale to friends, and colleagues to exercise the point of the KISS (Keep It Simple Stupid) method. Always check and double check the simplest things before moving on to the more complex reasons. Sometimes though, even I need a swift kick in the rear to remember this.

I had been struggling this week with the public folder migration from Exchange 2007 to 2010. The Mailbox migration had worked fine. The public folders though had been beating me up. The hierarchy was not propagating, let alone the folders communicating. I did some research, and found that the replication was done over email, basically emailing the folders between servers. So I started checking SMTP settings, telnetting between machines, even remembered that there was a problem with mailboxes on the 2007 server sending e-mail to the mailboxes on the 2010 server, but not vice versa.

All the symptoms were there, right in my face as to the main portion of the answer. I still didn’t see the simple thing though, instead looking up every way I could think of describing the issue in Google, with no fix. Then, on day 4 of this madness, while starting to look at yet another site’s solution, the answer hit me in the face. I logged into the Domain Controller, opened up DNS, and yep, there it was. Actually, there it wasn’t. When I set up DNS for the new server, I had forgotten to put in an MX record for the new server. All they years of dealing with DNS and MX records, I had forgotten the simplest thing, yet for 3 day had assumed I had put it in. I was elated and angry with myself all at the same time, especially when I saw the hierarchy start to show up on the Exchange 2010 server (the rest of the solution was cleaning up the old security certs on the exchange 2007 server, and getting a new self signed cert on it).

So once again, I get reminded of the 6 months of no sound from the speakers, and why one really does need to double check the simplest things even more thoroughly than the complicated thing.