Is the business model of free a wise business model?

I’m not sure this is a wise move…..

“Microsoft is another example of
smart use of the free model, says
Anderson. The company protested
quietly but took little legal action
while its Windows operating system
was widely pirated in China. Microsoft
executives were betting that each
pirated copy of the operating system
would help build a base of customers
who would pay for the convenience
of Windows support when they could
afford to. “Looking the other way,”
says Anderson, “Microsoft let pirates
be their best marketers, so that some
day that piracy would come back as
revenues.” Anderson says that the
Microsoft example perfectly illustrates
two major types of customers in
the world of free. One group is price
sensitive, and looks for the lowest
cost no matter what. The other is risk
sensitive, willing to pay—sometimes
a lot—for support, reliability, and

I would really not like it if some VP somewhere made a conscious decision to look the other way and then use WGA to get back revenues.

What I see is that some of those legal Microsoft customers feel that the risk of WGA is not worth the benefit.  If the business model of WGA i is to catch some of those pirates and yet to hopefully not annoy too many legal customers, I’m not sure that’s a wise strategy.

Don’t forget!! If you get the blue check or grey bar in WSUS — which is where something gets changed from the needed settings and turns off the SBS integration (it’s really not “broken” in my sense of the word broken since this is an easy fix), all you have to do as well as run the SBSBPA ( ) on your system and it will tell you what settings to change back to fix the integration.

I think it’s been reported that the bpa on 2k3 does say you are at RTM now… oh well 🙂

When you install WSUS 3 sp2 on your SBS 2003 r2 or SBS 2008 after you click finish the post install wizard will launch.  There are two ways to handle this.

Way one..

Hit cancel and the update will pick up the prior settings. 

Way two — double check the settings

From Karen Christian

I got an error on the console (‘The software update configuration has been modified and no longer meets the recommended configuration.’) after installing SP2 this morning and rebooting on this SBS2K8 server (TTSSERVER).  I fixed it by running MMC with Update Services, Options.  This server was a Jeff Swing Migration from SBS2K3.  Everything appears to be working OK now on this box. 

Here’s the process I went through to fix the problem (maybe it will help someone else):

Start, MMC, File, Add/Remove Snap-in, Update Services, Add, OK. Expand Update Services, expand ‘SERVER’, Options, WSUS Server Configuration Wizard, Next, Next, Next, Start Connecting, Next, Next (only English selected here), select All Products, verify selection of Critical Updates, Definition Updates, Security Updates, Service Packs, Update Rollups (all others are unselected), Next, Next, Next, Next, Finish. Close MMC. Open Windows SBS Console and Updates work once again (no error).

…doesn’t exist.  Anytime you make any sort of changes you introduce risk.  But the question you have to ask and decide is when the benefits of the patch outweigh the risks of the patch.

One person’s patch pain does not mean that you will see it too.  One server’s patch pain does not mean you will see it on all of your servers.

HAVE A GOOD BACKUP before you start ANY service pack. 

So far when installing WSUS 2003 sp2 I’ve seen (so far) two sorts of errors.  One is a 1602 permission error which I’ve only seen one of at this time.  The rest are 1603 errors.  1603 errors look to me to be installer issues and so far I’ve seen some being solved from using the office installer fix up tool.

The benefit of this patch is that it supports Win7s for patching purposes.

I’d recommend if you have issues with this service pack to post in the SBS 2008 partner forum and zip up and park in a skydrive the WSUS setup files from this location —

c:\users\name of your admin\appdata\local\temp look for the WSUS setup logs

You will need to set the ability to view hidden folders from the folder properties to see that location.

 If you have not signed up for the partner forums…  go to that location and sign up.

 To those that say that Microsoft needs to test better.. they did.  On all of my servers in testing I never had issues.  Installer issues are not unique to this patch, nor are they unique to Server 2008.  The cause of this issue is not the underlying way that WSUS is patched.  If you see people saying a patch blew up, there’s more than likely 20 other folks that it worked just fine on.  They just don’t run to the forums or newsgroups shouting “It worked”!

And the reality with our mutliple use boxes is that one cannot test for 100% no issues.  There may be during install.  That’s why we get paid the big bucks.  The key is to decide which patches are worth the possible risk and the best timing to do it.  But we have just too much software n the world to have 100% perfect installs and updates.  It’s just not a realistic attitude to take.  So plan on failure.  By that I mean ensure you have a backout plan.  A place to go to for help (newsgroups or forums).  Ways to restore the server.  Instructions on how to repair.  No service pack should be considered to be a trivial thing.  HAVE A BACKUP.

And to those that say that when I blog about patch pain that I’m showcasing why the cloud is superior are full of it.  Clouds have patch pain too, they just hide it.  Furthermore their maintenance windows/risk of patching/what gets updated and what doesn’t is on their schedule not yours.

Monday is the cut off for the early bird discount at SMBNation.  In full fairness, I get comped to go.  But I’m on the topic committee so if you don’t think it’s geeky enough for the Geekspeak track, please tell me so.

We have me, Dana Epp, Olliver Sommer on Windows 7 in the SMB space.  From getting crappy apps to run, to XPMode, to security, to the wows, you’ll hear it from us.

We have Mikael Nystrom on Win7 deployment using the deployment tools like the big guns do.

We have Kevin Royalty on Windows Home Server in the SMB world … and stay tuned ….some REAALLLLY exciting stuff coming from there.  You really do not want to miss that session… trust me…

We have Eriq Neale who’s going to be showcasing the latest from Apple (OSX server), IBM Lotus Foundations, Google docs, Jungle Drive and a bunch of other alternatives that are out there.

We have Karl Palachuk and Jeff Middleton on migration.  (yes the business of migration with the tech of migration in the SAME room)

We have Robert Crane on what you really need to know/do/extend with SharePoint

We have Dana Epp and Wayne Small on Virtualization for the SMB World

We have Charlie Russel on the wows and tweaks of Server 2008, from TS remote apps to Remote publishing, all sorts of hidden gems of the Server 2008 world.

But it’s not just about the sessions, it’s also about the ability to vent/rant/ask/talk/share/compare/talk to all the other folks that will be there.

Folks like Amy Babinchak.  Like Chad Gross.  Like Philip Elder.  Like Grey Lancaster.  And besides, you need to bet on when Wayne Small will be falling asleep this year…

“Your Community Confab – SMB Nation Fall 2009!”
Wednesday, September 2, 2009, 11:00 AM – 12:00 PM PDT

Join us HERE.

Registration link


(keep in mind this works for Exchange 2007/SBS 2008, apparently Exchange 2010 doesn’t do this)

To allow your RWW to have file access out OWA, go into the Exchange 2007 console…

Exchange Management Console

– Server Configuration

— Client Access

— Bottom pane, first TAB; Outlook Web Access

—- Listed should be owa(Default Web Site); Right-Click, select Properties on drop-down menu

—– In Properties dialog, select TAB Remote File Servers

—— Select Allow button

——– Add hostnames of servers you want owa clients to access. (whatever the host name is of the SBS box)

<honestly that is a nice wow to folks>



When you are manually installing Windows 2008 sp2 to your server and you want to MU it on (using Microsoft or Windows update), it will not show up until you have hidden or installed all other Important updates. 

The problem is, if there is an Exchange one you aren’t ready to deploy….. it won’t hide and thus will stop the offering of SP2.

If even ONE important patch is not installed, it will block the offering of Windows 2008 sp2 which (IMHO) is a key update you NEED on your SBS 2008 box

You remember that post?  Forget the idea that it was due to a dvd player or anything like that.   Saw it on another laptop tonight…

Someone told me to check a registry key to see if something was left behind in the pendingfilerename section…

 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager


That’s what nailed me.  Now to figure out what that offending creature is, remove it and see if this time the Win7 update will occur.