2007

Shockey Monkey Live! Activations Saturday Night

I’ll be doing the second live activation evening for people that have been in the queue waiting to get activated on Shockey Monkey and for the people that signed up over the last week or so. The nice thing is that I’ve automated about 90% of the account provisioning process so it should go smoothly. I start at 8 PM EST Saturday, finish by midnight.

Just reviewing for the people that are seeing this for the first time:

  • Shockey Monkey is free.
  • You must be a legitimate incorporated entity with a live (that means not under construction) web site and a logo. (no hobbyists)
  • You need to sign up for it.

That’s all, add shockeymonkey@ownwebnow.com to your MSN IM and we’ll git ‘r done tomorrow night. 8 PM. Pass it on.

Update: What an evening.Thanks to all the people that showed up on a Saturday night to get hooked up. I also got a chance to work on a ton of other requests because things are so streamlined now. Hopefully the days of waiting for days or weeks for Shockey Monkey activation are long gone.

TechEd 2007 - Welcome to Orlando

It’s officially just a day away.. TechEd 2007 in Orlando!

Sub_hero

So, on behalf of my home town, I’d like to welcome the worldwide technical experts to Orlando. If you need anything while you’re here (short of a place to sleep) give me a ring.

If you’re attending make sure you stop by and say hello in the Messaging area (not the sponsor area, the Microsoft Technical Expert section with the big signs and stuff) – I’ll be there on hand Tuesday, Wednesday and Thursday answering any and all Exchange questions you may have. I might even have some special swag for the Vladville fans

Does today's arrest end or diminish the SPAM problem?

God I hope so. The SPAM levels have been steadily increasing over the last 8 months or so and we could use a break. But we’re not going to get one. First of all, tguardian was not one of the biggest spammers around, but you have to admire law enforcement for blowing it out of proportion. He was just a scamming little script-kiddy that banged SpamAssassin until he could get a score low enough. Doubt that? Take a look at the graph below:

Messages-go

That is the global message load over at ExchangeDefender, last 24 hours. You can clearly see the spikes as our customers in Europe, USA and Asia/Pacific open for business. You can also see that the trends for today are up when compared to yesterday. Why is this bad news for everyone involved?

Well, if this guy was as big as the law enforcement leads us on to believe that US mid-day spike in activity would be significantly lower. But it wasn’t. Here is what happens when the feds bust you for cybercrime activities (long live Razor 1911).

First, all of your computer equipment, electronic equipment, electronic media, etc gets confiscated and certainly cracked in minutes. From there they try to get into the botnets, try to do discovery, capture any contacts, communications, business dealings, etc. The feds try to get as many people red handed as possible.

And these scumbags know this! So how do you explain the “enormous bust, sign of a SPAM kingpin crackdown, the end of UCE” that the media and some bloggers are hoping for?

Easy, they are wrong. tguardian always was and always will be a little scriptkiddy, bulk of whats coming up is done through organized crime from abroad.

My friend the top 10 spammer of all time - Arrested

Always a good day when one of your friends ends up on the news for being one of the biggest criminals / scumbags around. Robert Soloway, aka tg, aka theguardian used to be one of the guys on #ice on IRC that picked on me about being able to get around every SpamAssassin recipe I could write.

Hey bud, cover your cornhole. I win.

/me waves

Palm Foleo - buy or eBay?

The days of “thumbing it” could be over if Palm can get a price point that makes sense. Yesterday Palm announced Foleo, a companion laptop-like device for your mobile phone. Basically, its a 10” screen laptop with a full keyboard, USB, bluetooth and more but without a hard drive. This allows it to run for about 5 hours and connect to the Internet using your PocketPC for network access.

Palm-foleo_64_jpg

Awesome? You bet! With more and more applications ending up on the road, getting a light device that can give you access to the Internet and ability to sync and connect easilly back to the workplace is essential.

There are, however, two things wrong with this device. First, the price $600 – I can get a laptop for half that much. Second, why isn’t Linux software pitched more prominently. Let’s face it, this is a paperweight with the apps they put on there. But throw in Citrix ICA or Remote Desktop Client, both available on Linux, and you’ve got yourself a secure remote office.

It’s a very good idea for a road warrior, but the price and promotion need a few touchups. Will you buy one, or will you buy one on eBay later this year after it’s discontinued?

Windows Server 2003 SP2 EEULA & CYA

Susan Bradley’s blog tagline ought to be “Protecting you from your own stupidity” because she fought for the SP2 EULA from the day it was prematurely made available as a High Priority update on Microsoft Update. We all have a tendancy to trust Microsoft, sometimes trust it too much. Such is the case with updates, particularly to the systems that we look at on part-time only basis. Today this hard fought evangelical EULA is up on Microsoft Update.

Evangelicaleula

Why? Well, Service Pack of any sort is kind of a big deal. Despite Cousin Joel’s notion that it’s easier to consume it still introduces large scale changes to your operating system and the entire network environment. So whats the big deal with an EULA? Well, it’s just another reminder put up there to make sure you’re about to do something that you might want to think about.

Why? Because you don’t want to be this guy:

The blog notes and instructions from the SBS blog have all been heeded.  32
hours of talking with tech support on the phone, changing the nic card,
updating all the drivers, and still, the system is dogging to the point of
being painful
.  Here is the unexplainable issue:  I have 5 new machines, all
came from Dell with XP Pro installed.  They all had to be flattened and XP
Pro re-installed.  They worked great until SP2 was installed.  Now they take
5 minutes to open an 8MB spreadsheet they used to open in 20 seconds.  My 3
old machines were upgraded from W2K to XP Pro and they worked fine before SP2
was installed.  Afterward, they are slower, but work better than the new
machines.  The old machines can still run ACT 6.0.  The new machines fail
with a program error after opening the database.  Explain that!

All file access to the network is so slow now.  Don't suggest anything
previously mentioned in the blog.  4 MS engineers can verify that all the
tricks have been done as outlined in this blog.

There must have been some other deep layer of connectivity between the
server and workstations that does some kind of handshaking/security checking
that is slowing things down.  Excel seems to have been hit the hardest.  It
is a terrible thing to see a 2GB 4Ghz Dual Core processor take 60 seconds to
copy 10 files of 80K each from the network to the local drive.

I have 5 SBS 2003 servers and 3 of them are just fine.  This one is dying
and SP2 failed to install on the other one.  I am afraid to work the issue as
it might turn out like this one.

I really do need ideas and help short of flattening the server, as that may
not help anyway.  Ideas, anyone?

I feel bad for this guy, I really do.

However, a part of me wonders just how heavy the rock was. You know, the one that he was under since Microsoft started releasing service packs. As painful as the above is to read, and as painful as this process has been for him, this outlines the fundamental lack of respect for change management we have in the IT industry.

First, where is the full backup of the server that this was done on. At the very least this would have allowed him to take the server back to the last known good configuration.

Second, where is the test system on which he checked Act 6.0 for compatibility?

Third, never change more than one thing.  If you installed the Service Pack and it broke things, do not proceed to install drivers (that likely have not been tested with the said service pack) and do more exotic changes.

Fourth, test, test, test, test. Forget about the stuff you should have done before you patched, too late to setup a test vm, too late to do a full backup, too late to check the app vendor for advisories related to the patch, too late. You’re patched, there is a whole new world on your network. Isn’t the first thing to check all the workstations and rerun MBSA, performance testing, reset the performance counter on both server and workstations, build new baselines, etc? If not, why? 

Perparing for a Service Pack

There are a few simple things you can do to minimize your chances of a 35 hour support call:

1. Check the main application vendor for the customer and make sure their products are tested and supported on the new service pack. Service Packs are available months in advance and vendors can test/advise whether you should update or not.

2. Reboot the server.

3. Back up the server, full backup or image.

4. Download the service pack.

5. Disconnect the server from the network.

6. Apply service pack.

7. If all is well, connect one workstation to the server to test the performance, application compatibility, access policies, etc.*

8. If all is well, reconnect everything to the network.

9. Rebuild your performance baselines.

10. Create a new full backup.

* - The last thing you want is to start storing live data on the server that you may need to restore to the previous version due to major problems. By placing the server offline you don't have to deal with email that was delivered to the server that you will now lose, comitted data, etc, etc.

Now I realize that points #5 and #9 are in the same category as “Don’t eat pizza, it’s not good for you” and “Did you know that smoking causes cancer” but those are really the two things that will limit your exposure and tell you that there are problems before its far too late.

Got your own change management tip? Blog it or post a comment.

And I'm Back Update

I'm back, Vladville is back. You may exhale now, things are back to normal.

I am sorry that it took so long to get Vladville back together. It was a number of things. First, I made a committment to myself that Vladville will not be back online until I made sure I've integrated all the functions I needed for Vladville to be useful. Second, I had a ton of fun in New Orleans and I really did not feel like working on the blog code. But it's Wednesday and I'm caught up, the blog is where it needs to be and things are clicking along. There isn't anything new here (unless you look really carefully) but the code and the integration on the backend will finally allow me to do what I've been dreaming, promising and coming to terms with over the past year or so.

The Mistakes

As the Vladville popularity and audience grew I've felt a huge sense of obligation to keep certain things going, certain things I should have allowed to die long ago.

I've made far too many mistakes, ranging from talking about things and people I had no right to talk about all the way to being outright wrong about so many things I've lost count of. That is always a risk you take when you speak your mind.

I've stood up for things that were wrong, to protect the people that would have (or already have) thrown me under the bus at the first opportunity.

Most of all, I've been wrong about the people.

And...

... and while I can't and don't want to change who I am and what I stand for, it has been clear to me that I need to step up my game for those of you that are willing to learn, and a little more importantly, are willing to share. No, I won't tell you what I'm up to or what the big plan is but there are good times ahead, I hope you join me.

Deported to India

We have a little saying around the office, “If that patch isn’t committed to the cvs by noon we’re deporting you to India.”

Tonight I decided to get cute and implement some visual effects. I’m ashamed that the stuff below took 25 minutes to produce:

$style = ( $i % 2 ? 'altrow' : 'row'); $i++;
echo "<tr class=\"$style\"
onClick=\"window.location.href='
/view.asp?item=ticket&ticketid=$tickets[ticketid]'\"
onMouseOver=\"this.className='hrow';\"
onMouseOut=\"this.className='$style';\">";

I’ve posted it in its entirety so I can be ridiculed at a later date. What took so long? Stupidity as usual, but the longer you go in a stupid direction the longer it takes to figure out just what went wrong in the first place.

The top line just determines which style gets applied to the row in a listing. The idea is to alternate styles so that the table is easier to read. There are two styles here, row and altrow – pretty simple. As I list data I’m using the modulus (remainder after /2) to determine which style gets applied. There are two events that fire – namely when the mouse hovers over the row and when it leaves it. When it hovers, the style ought to be switched to hrow which is my highlighted row. After it leaves, reset the style back to what it was previously.

Then I decided to get cute. I wanted the row color to change as I scrolled up and down the list. I also wanted to be able to click on any inactive space in the row and still take the default action. Again, programming 101. Where I lost the ball game was on the this.style part – this.style takes on all sorts of things like color for example – all except stylesheet name. It took me good 20 minutes to figure out why/where/how before I finally went back to look it up. I suck.

Bugs and Mitigation

As mentioned on the Shockey Monkey conference call this week I’ve squashed all the bugs that have been reported throught the last week or so. I’m also addressing the current showstoppers as identifed by the folks on the conference call. Just to clarify the intent here – priority in development is given to people that have adopted the product for their business use and see it causing a lot of pain and issues for them. Those showstoppers are as follows:

  • Ability to create a ticket via email
  • Company update issues
  • Email parsing issues
  • Ability to change subjects
  • Ability to offer user autoregistration*

* = difficult to solve. Someone requested it be supported via email, which isn’t going to happen until email becomes an authentic form of communication (ie: never); With SPAM, spoofing, forging and so on there is no way to provide any level of authenticity to the accounts that are being created via email. However, a web-self-registration stuff is under development, will have it ready by the May 23 feature refresh along with all the rest of the stuff above.

I’ve gone through all the bugs and fixed them, with the exception of about 5 issues that I was unable to replicate on my own. If you could be so kind to login and update the bug report with the detailed actions you took to cause it I’ll gladly get it done, I can virtually promise I will have it update on May 23rd.

A little note on bugs and releases

I patch the security and critical bugs in realtime. Shockey Monkey has a development and release branches which as the name implies hold the currently active code and the code I am working on.

If a security issue is identified it is patched and automatically rolled out to all the users.

If its a feature fix it gets fixed in the development tree instead. There are a few reasons for this:

  • Security fixes are usually either 1 line or an extra loop check. I can quickly replicate them to the development branch of the code.
  • I intend to release bug fixes on weekends, during the weekly maintenance window for Own Web Now Corp which is 3–7AM EST Saturday.
  • The feature rollups/fixes are released periodically for two reasons: It’s easier to manage and its easier to solve a huge set of bugs and eliminate problems before new ones pop up.

Also keep in mind that as I fix these bugs I am also rolling in new features so the less branches and patches the better. Also remember that this is not a single web app running in an isolated space on a box that nobody ever touches – each code change, given enough stupidity on my part, can take down the entire farm. So every bug/fix I do has to be stress tested, etc.

This week was different from previous weeks in that the patch/update will be held off until Wednesday, May 23rd. Here is what’s at play. I am going to be out of town next Saturday. There is a big conference starting Friday where I will be meeting many of you that are using Shockey Monkey and breaking it down piece by piece. I am introducing two HUGE feature sets into the Monkey and just wanted to go through another few days of testing and checking before it went live.

Of note, Shockey Monkey changelog is now available at http://www.shockeymonkey.com/changelog.asp