I’m pretty sure that it has sunk in to the people of Microsoft by now that their deployment of Windows Vista has been an utter disaster. Vista has been out for over a year and a half now and it looks like there is only about a 14% adoption of the new OS.

This should serve as a warning for all other software developers out there and software companies. It is really easy to screw up your market and turn your clients against you.

This has prompted me to provide you with some lessons that we should all have learned from the Vista debacle.

Just because you decide you are going to lead does not mean that others will follow.

Microsoft figured they had it all figured out. Windows XP was arguably the most popular operating system on the market and the most successful version to date. Now was the time to lead the sheep clients to a bold, new OS.

Unfortunately, computer users like to think for themselves. They will not purchase something new just because they are told to do so.

Some of the more common alternatives that users went with other than buying Vista include:

  1. Doing nothing and sticking with Windows XP
  2. Buying a Mac
  3. Learning Linux
  4. Putting off purchases in the hopes that something better comes along

Lesson: Let your clients lead. Get to know what they want and put in the new options that they want, not what you think will make you money. Make the client happy and the money will find you.

Terms like “better”, “easier” and “improved” are subjective.

I will be the first person to admit that there are some definite improvements to the way that things are done in Vista. Yet, I often miss the way things were done in XP.

Microsoft has told us that Vista is better, easier and improved. Does this mean that XP was worse, harder and crappy? Of course not! So if many people feel that this is inaccurate, your credibility may just go out the window.

Lesson: Make certain that any claims you make about your new product does not reflect poorly on your old product and can be, more or less, agreed upon universally without leaving much room for opinion.

People will not change for the sake of change.

There is a certain geek element out there that want the latest and greatest in anything that you make. These are the types who stand in line for the new iPhone, even though they will not be able to get service for several months.

But, the majority of your clients do not fall into this category. Rather, they are cautious and are concerned about spending their money.

Lesson: You need to give your clients a reason to upgrade and change. Without that, they will not part with their money.

More options are not always better.

Have you ever stood in the cereal isle at he grocery store? Have you ever tried to decide which cereal to buy? It is insane how many different types and brands of cereal there are out there. Different manufacturers have knock off versions of other brands. Manufacturers try to create a new cereal by simply changing something small about one of their old cereals. It’s almost enough to make the buyer go cereal serial.

It appears that Microsoft hired all of their marketers from the cereal industry. They have split Vista into multiple editions and made the selection process so confusing people are not even sure how many editions there are. There could be four, five or six, depending on who you ask. And this does not even take into consideration OEM and open licensing. How is the average consumer suppoed to decide?

Lesson: Make your product models/editions/versions simple and easy to understand. Preferably, make one model and allow them to purchase additional options, much like the automotive inductry (but stay away from the upgrade bundle concept).

Trying to force users to upgrade will just make them find other ways of doing things.

Windows XP can no longer be purchased from Microsoft. This has been the case since June 30, 2008. They had announced that this was going to be the case back in April but they decided to postpone it. But, as it stands, you can not purchase a Windows XP from Microsoft.

Has this stopped people from selling it? No way! In fact, Dell is turning this into big business along with other companies.

Lesson: Do not try to force the hand of your clients. If they do not like your new product, they will find ways to stay with the old and send you less money in the process.

Don’t make people relearn something they already know.

With so many “improvement” in Vista, it is really difficult to know how to navigate around the system. While it may be more intuitive for a new user, the vast majority of people who will be using Vista will be those who have experience in other versions of the Windows operating system.

I know as someone who is technical, this really put me off because I’m not really interested in learning a whole new operating system, especially when I am finding it harder and harder to learn new things.

Lesson: Make your new product intuitive for both old and new users.

Make sure that those who are selling and supporting your software are on board with the upgrade.

I think that one of the biggest reason that Vista has done so poorly is that it failed to be adopted and promoted by the people who are in the trenches. I mean the techs, company computer guys, and sales personnel. Since these people were not behind Vista, they were not recommending it to friends, family and clients. This is where a new product is made or destroyed.

Lesson: Make sure that those who are speaking directly with the people who are parting with their money believe that your new product is the best version of the product ever made. Ensure that these people know as much about the product, they are excited about the product, and that they are using the product themselves every single day.

Don’t make people choose between functionality and aesthetics.

There are a very small number of people out there who will choose something useless that looks pretty over something that just gets the job done. Unfortunately, Vista, while it looks really nice, often does not get the job done.

Many people, especially those who decide to upgrade to Vista, find that the cost of all the bells and whistles means that some of their old hardware and software does not work and their system is now slower than ever.

Lesson: Focus your attention on ensuring your product gets the job done. If you have time and it is warranted, make it look pretty.

Make sure your product is ready for the market.

Even Steve Ballmer admits that they messed up the release of Vista. There are too many incompatible software packages that were critical to business and many hardware manufacturers had not gotten around to finishing up releasing new drivers for existing hardware.

All this made Vista a show stopper before people even looked at it.

Lesson: Make sure your product is usable by the largest audience possible with as few barriers to upgrade or replacement as possible.

Don’t force a hardware upgrade unless you absolutely have to.

This has goe to be one of the biggest complains made by users. Vista rarely runs well on hardware that XP was more than happy to work on. So now, the cost of purchasing Vista has just gone up significantly. This can get very expensive, expecially if they are part of a large business that has hundreds or thousands of machines to replace.

Lesson: Try to keep the collateral cost of upgrading to a minimum. Do not make people buy new products or add-ons unless they absolutely have to.

Similar Posts:

If you found this post useful, why don't you buy me a cup of coffee to show your gratitude?

A few weeks ago, I ran across a couple of articles about a university in Holland that was having difficulty getting all of their Microsoft patches out to all of their systems. What did they decide to do?

Buy more servers? Nope!

Increase bandwidth? Nope!

Use a program that has been essentially outlawed in North American universities? Yep!

The university decided, on the advice of their IT consultant, that they would use bittorrent to deploy the patches.

This really got me thinking about how I would go about creating my own U.Holl server (as I like to call it). These are some of the thoughts that I have come up with.

The Server

Just to add a really strong sense of irony, I would probably build the U.Holl server on Linux, most likely Ubuntu with a typical LAMP installation. Then, for ease of management, I would install a tracker such as phpMyBittorrent or something similar.

In the tracker software, I would create several different categories based on the target systems that I would use. For example, there would be Windows XP, Windows Vista, Office 2007, etc. categories. Each category would have its own RSS feed.

The Clients

Each workstation or server that was to receive updates using bittorrent would have a copy of uTorrent running in the background. This would be critical. You would also need to tweak uTorrent so that it automatically ran an installation script r program each time it finished downloading a new patch. This script would also schedule a reboot at 3:00 AM (or whatever time you wanted) since it seems almost every hotfix from Microsoft needs to reboot the system.

A potential install script might look like this:

The trick to automatically downloading files is to subscribe each uTorrent client to the proper RSS feeds given out by the server. This way, each system only gets the patches it needs.

Potential

I think that this type of a delivery system has great potential. You could even use it across slow bandwidth links or to deploy other software, not just patches.

This is a project that I am hoping to spend some time on over the next while but I am looking for your input/suggestions now so that I can hopefully avoid some pitfalls later. Any input would be greatly appreciated!

Similar Posts:

If you found this post useful, why don't you buy me a cup of coffee to show your gratitude?

In response to my post “Windows Install - Simple, Easy and Quick“, Will has asked a good question:

Is there an option in Windows to save Documents and Settings to a different partition during install?

In Ubuntu Linux, I can have a separate /home partition. This lets me reinstall without losing *any* files or settings from a user point of view. (Also, it’s nice having all my wireless passwords work from install to install).

The answer, Will, is yes, there is a way to change the location of the Documents and Settings location in Windows. By default, a user’s configuration files are stored in C:\Documents and Settings\<username>. This location is created the first time the user logs into the system and their default settings are taken from C:\Documents and Settings\Default User.

But, it can be really useful to redirect the location of this folder. For example, I have redirected user’s My Documents from the default C:\Documents and Settings\<username>\My Documents to \\server\users$\<username>. This way, users were storing their My Documents on the network and not locally so that if a workstation blew up, then all of their documents would be safe on the network.

To allow this example to work, simply perform the following:

  1. Open Registry Editor (Regedit.exe) and navigate to: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders]
  2. In the right-pane, look for the entry “Common Documents” and double-click it.
  3. The value which present there by default is “%ALLUSERSPROFILE%\Documents”.
  4. Change the value to the redirected folder (e.g. “\server\users$\%USERNAME%”)

That should do it for you!

Similar Posts:

If you found this post useful, why don't you buy me a cup of coffee to show your gratitude?

I am in the process of performing some analysis on the posts on Daily Cup of Tech. One of the things that I want to do is a word count and frequency analysis on the entire blog.Now, I could go with good ol’ pen and paper and start counting every single word on the blog. But, that would take me quite a mount of time, not to mention that I would not learn anything in the process.

So, I decided to export the contents of my mySQL database the runs behind the scenes at DCoT to a text file and then download a word and frequency counter. Do you think I could find a word counter that would count all of the words in the file and then count how many times each word appears? No luck.

But, my bad fortune is your lucky day. I decided that since I couldn’t find anything like this, I’d make it myself. So. today I present you with the Daily Cup of Tech Word Counter!

The application is a self contained program that is fully portable to USB devices. You can download the program and the source code if you are interested. The program is written in AutoIt.

Here is a screenshot of my new baby:

Most of the program is self explanatory. You can sort the output alphabetically or by how frequent each word appears. You can also sort in ascending or descending order. You can count the words that you type or paste into the edit box or use a text file.

The delete options may be the only confusion portion. When you are counting words, you need to clean up the rough text a bit. Delete some punctuation, get rid on non-printable letters, or scrub out the non-standard English words. Each of these options selects a different one of these options. Control characters are things like carriage returns and line spacing. Punctuation is your standard punctuation that you will find in most documents. Extended characters are characters that you usually do not see regularly and are often used in some non-English languages.

The Use Spaces option will replace all deleted characters with spaces rather than deleting them. This can modify your outcomes so feel free to experiment.

When you are done counting your words, a complete list of all the words and how often they appeared will be presented in the edit box.

Feel free to play around with this and let me know if you find it to be useful.

Similar Posts:

If you found this post useful, why don't you buy me a cup of coffee to show your gratitude?

I was doing some research the other day on getting your self out of a difficult situation when you don’t have access to some vital system resources because you are running as a normal user and you lost your local admin password.

I discovered that there is a way to reset your user interface and run interactively as the LOCAL SYSTEM account. This is important because the LOCAL SYSTEM account has a lot of privileges available to it. According to Microsoft:

The system account and the administrator account (Administrators group) have the same file privileges, but they have different functions. The system account is used by the operating system and by services that run under Windows. There are many services and processes within Windows that need the capability to log on internally (for example during a Windows installation). The system account was designed for that purpose; it is an internal account, does not show up in User Manager, cannot be added to any groups, and cannot have user rights assigned to it. On the other hand, the system account does show up on an NTFS volume in File Manager in the Permissions portion of the Security menu. By default, the system account is granted full control to all files on an NTFS volume. Here the system account has the same functional privileges as the administrator account.

A little while back, some enterprising individuals discovered a way to run the LOCAL SYSTEM account interactively. Here are the instructions according to one website:

  1. Start > Run > cmd.exe > type: at 12:03 /interactive “cmd.exe” (replace 12:03 with a time 2 mins from now). > close command prompt
  2. New command prompt will open, when it does > Hit CTRL+ALT+DEL > find explorer.exe and End Process.
  3. At command prompt type: cd.. > type: explorer.exe

This all words fine except that it is a bit confusing for someone who does not understand how all this works. So, I thought I would make it easier for those who do not have my background. I created a little program in AutoIt that completely automated the process. Simply run the program, wait for a couple of minutes, and you’re running as the LOCAL SYSTEM account.

You can download this program and play with it all you want.

WARNING: I have tested this program to the best of my abilities but this does not mean it is perfect. I did not have any problems with it but that does not mean you will not. If something goes wrong, don’t blame me! You’ve been warned.

For those of you who are interested, here is the source code for this little program I wrote. Feel free to hack around and make it do different things:

#include <Date.au3>
If $CmdLine[0] = 0 Then
;No command line options
;First run
$RunTime = _DateTimeFormat(_DateAdd(’n', 1, _NowCalc()),5)
$Command = @ComSpec & ” /c AT ” & $RunTime & ” /interactive “”" & @ScriptFullPath & “”" 2″
Run($Command)
Else
;Second run
$Command = @ComSpec & ” /c taskkill /IM explorer.exe /F & ” & @WindowsDir & “/explorer.exe”
Run($Command)
EndIf

Update: Someone asked in the comments how you get back to your normal account. Simply log out and then log back in as yourself. You should be back to normal.

Similar Posts:

If you found this post useful, why don't you buy me a cup of coffee to show your gratitude?

« Previous PageNext Page »