Rants (RSS)

Rants

Ray... you were doing so good until that last part....

If you are setting up a network of up to 75 users, one of the more
economical choices available is Windows Small Business Server (SBS)
2003.  The price of the operating system (say for 10 users) is around
$1,800.  While that does not sound significantly less than the
"full-blown" Windows Server 2003, the cost is significantly less if you
consider everything that ships with SBS at no additional cost.  The
basic version of SBS includes SharePoint, Exchange Server and Outlook,
while the Premium version includes SQL Server and ISA Server.  In
addition to this, if you purchase a good backup software solution like
Veritas Backup Exec, the Small Business Version of the backup software
includes an agent for Exchange Server and ends up costing you (if you
use Exchange Server) less than 1/2 the cost of Backup Exec for Windows
2003 Server since the Exchange Server license must be purchased
separately for that version and costs more than the basic backup
software itself.

 

In addition to cost, SBS is almost entirely installed via wizards and
this simplifies the installation process and prevents a lot of the
configuration errors that often occur during an integrated Windows
Server installation.  The various parts of the puzzle are far more
easily installed in SBS than in Windows Server.  Chances are, once the
installation is finished, all the parts will "talk well" to one another
and the conflicts should be relatively few and easy to resolve.
 

That's the good news.

 

The bad news is that SBS expects to be the SOLE master of your network.
The documentation explains that your SBS server must be the Domain
Controller and must be installed at the "root of the forest".  So, if
you decide a few years down the road (for whatever reason) that you wish
to transfer a part of you network load to another server, SBS is REALLY
reluctant to share the sandbox with another server.  In theory, of
course, anything is possible.  The reality is that the very simplicity
of your original install created a pretty "closed" system and migration
of DNS and Active Directory and other issues which is relatively simple
between two Windows Servers becomes a bit of a nightmare when one of the
servers is a SBS.

 

This is not necessarily a reason for avoiding Small Business Server.
If, however, you decide to expand your network down the road, you might
be looking at scrapping your investment in your Small Business Server.

 

Ray

'

So Les Connor was sharing with me this email from a Canadian listserve...and the first part of the post ...man it is warming my heart...but then we get to that "bad news" part.

 

Man oh man... how wrong can Ray be.

 

Ray... I have not ONE but two servers in my network and I have some file storage and live communication server on the second one.  And in fact in the R2 era we will be able to easily and cheaply add a Windows Server, an Exchange server or a SQL 2005 workgroup for the price of that server OS.. with no cal cost.  THEN comes the kicker.. Ray, Ray, Ray...once a SBS box hits that 75 user limit or whatever thing that you need to be big server land for ...like trusts and what not... you just go through the Transition pack.  You don't scrap anything.  You keep your investment.

 

The only thing unique about SBS is that it must hold all the FSMO roles and be the primary domain controller...that doesn't mean that it can't share the wealth and have addiitonal servers.  No you can't put Exchange on another box, or the parts that come with SBS but that doesn't mean you can't add additional servers. And honestly... get good hardware and I don't need additional servers. 

 

And for those folks that argue "well but you have all your eggs in one basket in SBS" to that I argue... yeah but it's one well looked after and monitored basket.  And honestly I find this ironic when everyone else in big server land are doing virtualization ...that they are sticking like 10 servers on one physical machine and folks think what we do in SBSland is crazy.

 

How can it be..how many years after SBS 2003 shipped that folks can get it so wrong?  What marketing information are they reading?  Where are they getting this stuff?  Why is the message not getting to the marketplace? 

 

It just amazes me how people get SBS so wrong. 

 

So let's recap class..... additional domain controllers.. CAN DO... additional servers... CAN DO.... grow into big server land parts if needed... CAN DO..... Remote Web workplace that NO ONE ELSE HAS..... HAVE THAT.

 

Come on marketing.... get that message out there of what SBS is...because people out here are not getting the message of what SBS truly and really is.. it does not limit me or my firm AT ALL.

Sometimes I feel like Nicole Kidman...

There are times when it comes to Software Assurance I feel like Nicole Kidman... no.. seriously... I'm Nicole... and Microsoft is Tom Cruise over there... got a new girlfriend/future wife... new baby ...and where does that leave me?  I'm the original one who believed in Software Assurance...bought into it... got the Koolaid from the initial day, got the two year, and then the three year... and now it looks like my SA reward for my three year period...the "upgrade" I'll get is the SBS 2003 R2 upgrade.  I mean yeah I'm a patchaholic and all that.... and the green check in the daily email is very cool....but ..uh... um....kinda a Nicole moment here 'eh?

 "SA is a hard sell"

It is isn't it?

True statement by a Var/Vap about Software assurance...that he had a hard time selling it...

In my industry I'm used to subscription models, but it's a guarantee that every year or month or quarter I'll get a new update (law changes and what not), as there were changes needed for that ..but not necessarily function changes.  And support under this model was built in.  But for other industries... where the upgrade story isn't as obvious, it's a tough sell...

But what if you are the "Katie" in this view of looking at Software Assurance... you know that if you buy OEM right now you get the R2 Technology upgrade program that guarantees you the green check.  You know that if you buy OEM you are stuck with that software on that box, it CANNOT be moved to new hardware....but ... you know if you buy software assurance to add to that OEM within 90 days you "can" move that operating system off that box and get the 64 bit SBS upgrades in the next Longhorn cycle..which... looks somewhat reasonable to hit within the three year period.... and if you do go three years you get the one support call, the media sent to you (which, I'll admit, as the "Nicole" here.. is nice to have as I don't have to go digging up the media it comes to me). And there are even some monthly installment payment plans you can do these days.  So from looking at Software assurance as a "Katie", it's something that looks reasonable.. ensures you WILL get on that 64 bit SBS platform.  And all my AD guru guys says that AD and Exchange just has to go on the 64 bit to get that good stuff.  32 bit was a total drag on our boxes... on all boxes.

But there's another thing the "Katie's" have... one of the var/vaps the other day said that they actually were better able to sell a solution the other day with the "managed service"/Software assurance.  The client really LIKED the proactive stance that the consultant gave because the SA gave them planned 'forward thinking'. This was a firm that "got IT" and knew it was a part of their strategic overall plans.  As a "Katie" they totally got Software assurance was part of their strategic overall plans and goals for that firm.  Interesting viewpoint isn't it.... especially as folks are moving to the "managed services" viewpoint.  "Katie" wanted software assurance because she was mapping out her technology future and wanted to ensure that it included an investment in technology.

The fact is for me, the "Nicole" here is that I did get a good SA deal in the SBS 2000 era.. I got Live Communication Server (which I still argue they need to code up a SBS lite version of LCS, but I digress), so my disappointment of being "Nicole" in the R2 era is tempered with my gains in the past. 

For those of you that have clients that are "Katie's", think about the forward looking view... that 64 bit coming down the road.... those that have managed services clients... something to think about isn't it ...to position that Software Assurance as an "investment"

But Microsoft... just make sure that in the future both the "Katie" and us "Nicole's" feel like we're treated well... you know what I mean?

So what about you?  You find that it's easy to sell software assurance... or it's a hard sell?

The body count

All returns out the door....

Many more returns efiled this year than last.....

One band-aided workstation that died on Friday....

One workstation that has a non functional mouse (ever try to drive a Windows workstation these days with no mouse?  It's not pretty... not sure what's up with that one.... the mouse just died or something)

Quite a few times where we needed to get tax information to a client who had no access to a fax machine.  So we took our copiers/scanner/printer and scanned in the tax info, went into Adobe Acrobat, secured/encrypted it, sent it via email, ensuring that we verbally gave the password to the client.

Earlier this year I was on a online committee that wanted to set baseline minimum standards for protecting data and one of the points that someone made was that a workstation that had identity information on it shouldnt' be attached to the Internet for surfing.  But look at all the ways that I needed the Internet today....

I needed the Internet to efile tax returns....

I needed the Internet to efile extensions....

I needed the Internet to email information... to receive information.....

I needed the Internet to research information.....

I needed the Internet to make online payments at www.offiicalpayments.com to pay tax due via credit card for clients.

We're a connected world.... so how do you help your clients stay connected? 

And by the way..just a heads up folks... maybe not tomorrow.. but the day after that... go call that CPA or that Accountant in the USA still running those 98 Peer to Peer networks and tell them to sign up for the www.microsoft.com/accountant program where he can sign up for the Action Pack.  There's no excuse for a CPA to be still on Windows 98.  There's no line of business application that you SHOULD still be on that can only run on 98.  I haven't met a DOS program yet that couldn't run on 98 ...but then again... I don't WANT to meet DOS programs anymore.  They have better alteratives.... change is good and we in the accounting industry need to realize that a DOS accounting application probably means that it was written with lousy security build in.

A Windows 98  machine in your network lowers the secure-ability of your entire network, forcing you to make adjustments to your network to get those 98s' to work.

June 30, 98, 98SEs and MEs are no longer going to get security updates.

After that date..they'll be your body counts...

OEM good versus OEM bad

There are times it's funny to look at the sales channels of Microsoft.  It's like they are competing with one another... on one hand you have (and rightfully so) Eric "Mr. Licensing" Ligman giving us the details of how limiting OEM is to our clients... the fact that the server OS is tied to the hardware, that if something happens to that system, or you want to move it to a new box, you are totally stuck and need to rebuy the software.  So it would seem that on one hand it would be wise to stay away from OEM when it comes to servers right?

OEM is bad.  Right?

Well ... not so fast... because over here in this corner is the Technology upgrade program that if you currently buy SBS 2003 SP from March 31 2006 forward, and you buy it from an OEM or System builder you will get the R2 upgrade.  Okay so now.. we WANT to drive people to buy the OEM version because it would mean that they'd automagically get R2 when it releases.

OEM is good.  Right?

Not so fast...with OEM we're also out of luck trying to get slipstream media for that system, and trying to even get a copy of Entourage is like searching for the Holy Grail.

Okay.. so lets say we buy retail ... which is better than OEM in that it can be moved from one hardware to another and thus is more flexible for that small business.  Do they get the ability to get the upgrade to R2 if they buy right now? 

Absolutely if within 90 days they add software assurance to their purchase!

Hang on class.. does anyone else see the problem here?  So the only way that someone going to Office Depot let's say and buying a copy of Small Business Server 2003 right now will be able to get the R2 technology upgrade is that if they pay 'more' money via software assurance?

But wait.. doesn't Microsoft also indicate that most small businesses 'don't' buy software assurance?  (Unless they are insane folks like I am, that is).

So if on one hand, we've been taught by Microsoft in our Partner channel that OEM is less flexible and forgiving for our clients so don't buy it, but on the other hand, at least until SBS 2003 R2 comes out anyway, I'd say to this beancounter, it looks like OEM "is" more flexible.  Granted you are still stuck with the lousy fact that if the server dies, so dies the software, but faced between the fact that you get a free OS going via OEM channels... and faced with rebuying the operating systems via the retail or Open License way.... it's rock and a hard place time for someone deciding the best way to license an operating system for their client.

...but then .. if most of the sales are going through the OEM channels... Microsoft answer this to me.. why is your documentation for these OEM machines lightweight?  Why is it that on the Dell support web site that SBS 2003 doesn't even have it's own support forum?  That all the SBS 2003 issues are mangled in with the Windows 2003 Server ones?  If the bulk of your sales is that OEM channel, why is it that for example Gateway OEM server folks that accidentially lose their software are stuck rebuying it if they don't order it in 90 days? 

So if OEM is such an important marketplace why not treat them better in more ways than just this upgrade program?  The number of times a SBS owner comes in and doesn't know what Remote Web Workplace is..well it's just insane.  And here it is the best thing about SBS 2003 (other than the daily email)

But what's a partner to do?  Buy an OEM operating system, tying that customer to that hardware so that if the hardware dies, there goes the server?  Unless of course you can somehow convince the customer to SA that server within 90 days to 'free up' the OS to be moved to another server.  Or right now buy retail or open value and attempt to talk them into a Software Assurance package?

...so what are you doing with your SBS sales right now?  Holding off?  Buying OEM for your client?  Even considered this right now?   

Man you could tell this was a Friday...

"Ntoskrnl.exe is missing or corrupt"

Ugh...

That's how my morning started and it went down hill from there...but it's partially my fault.  I'm not doing what I should be doing for my firm to monitor the event logs on the workstations as much as I do on my server.  I bet if I had gotten around to installing the monitoring software I'm thinking of installing I would have spotted that workstations harddrive starting to fail on me.  Instead I was faced with trying to take an extra workstation and make it "good enough" for a temporary workstation...and boy..when you are spoiled with two matching 19inch monitors...going back to one... is not easy.  So I tried first to just extract over ntoskrnl...but no go... so finally I had to practically lay down a new OS.  And THANK GOODNESS I have some rightful access to true XP sp2 real media, because otherwise I would not be able to try all these 'repair install techniques that I was attempting to do.

Man that is still the one thing in the OEM marketplace..and sorry folks...us here in small biz is just not going to see the value in buying Open Value or Software assurance for Desktops unless they are as wacko as I am and plan on using that bitlocker/drive encryption software that you can only get with the SA Vista (assuming that the Vista ships one of these years).

Take the time to think about the ..even minor disaster plan you have for your office...what's the Dell Tag code on that system so you don't have to crawl on the floor with the dustbunnies to tickle your nose...bottom line I cost my firm time... money... we didn't have today...because I wasn't pro-active 'enough' with my network.  I was still "break/fix" and this time, today ..that break/fix mentality of the workstations meant that I was doing something that shouldn't have been done in a manner in which I was doing it, without planning, without thought.  And all because I hadn't gotten around to including my workstations health in that pro-active stance I have in my network.

Come next week... guess what's first on my personal to-do list.

Yup.. get way more aware of what my workstations are doing so I can spot the 'coming storm' and deal with in on my timetable..not on a Friday when I didn't really have time for this today....

My firm cannot afford me to be in a break/fix mentality.  They need me to be proactive and one step ahead of the game. 

I wasn't today....

I plan... I hope.. to be next time....

..and yes, there will be a next time... I'm planning for it..and not just waiting for it to happen...

7 minutes and 42 seconds....

7 minutes and 42 seconds....

That's the exact time it took me to finally get through the maze of the voice mail system at the California Department of Insurance today just so I could be placed in a phone queue and hear annoying music....

14 minutes and 22 seconds later....

That's the exact time it took listening to the music to finally get to a human being to answer my question....

30 seconds later.....

That's the exact time it took to ask my question and get the answer I needed.....

http://gethuman.com/us/ Unfortunately the California Department of Insurance isn't on that listing...

There are times that voice mail systems are very effective...and there are times that they are just downright annoying.

We're losing the war

It's obviously big business.

Someone clicks.

The have a reason to do it.

...to do THIS... and as Donna points out it's getting worse and worse all the time.

But we have to do something out this...because it's they are truly winning the war...

 

When do you flatten a box, revisited

When a SBS box is set up by someone... well.. who hasn't a clue... is it better to keep that box and fight with whatever strange and weirdness the prior consultant did?  Or is it better to consider it almost like an "intrusion" event, where you nuke and pave and start over.

The other day when I blogged about how you should not flatten at the drop of a hat, the post was made with the assumption that you had history with that box.  You'd set it up.  It was under your wing.  The box I was working with the other day was obviously redeemable.

But what if you come into a disaster of a SBS network where not only did they not read any book or manual, but you can't even tell what the heck they did?

Do you nuke and pave everything? Keep the AD structure if it's reasonable?

Totally start over?  Jeff Middleton has some of these concepts in his www.sbsmigration.com kit .. especially the domain audit guide.

Personally I think we need to get a better diagnostic tool for when you come into a bad setup so you can figure out sooner versus later to cut your losses... but then again.. sometimes.. it's pretty obvious isn't it?

Flattening a box

If you are considering flatting a server and restarting because things "just aren't right" and you think that reinstalling will magically fix things.... guess again.  There's only two times you need to flatten a server and start over

  1. If you've installed the box and that initial install doesn't go right (we say install it three times anyway)
  2. If you've been stupid with that server, haven't protected it and gotten it nailed with a rootkit or something nasty

Then and only then should you flatten... otherwise just because someone else couldn't get a server working...and you think flattening and tearing out the active directory and Exchange in a network is somehow less disruptive than calling Customer Support and having an engineer look over that system, guess again.  Even when a system is seemingly a "sick server", it's better to get to the underlying issue causing the "sickness" than to reinstall the server, install everything back again, and possibly get yourself right back into the same position.

Just like in health care, get the proper diagnoses...and that means going to the "SBS Doctors" for your patient.  For those that are installing SBS boxes for customers, sign up at www.microsoft.com/partner for your access to support.

Dear Mr. Vendor:

When you install software on my system, please keep in mind that I just might decide your software doesn't work and thus may want to uninstall it.

Thus.. I should not have to load up regedit to dig into my servers innards and rip out one line item at a time... just to get out your software out so that we can get a server back in good working order.

If you are smart enough to install on my system.. I shouldn't have to go to through the registry to get you back out...

(Tonight's rant was brought to you by Panda Antivirus, we now return you to your regularly scheduled blog)

 

 

If the vendor supports Windows 2003 ..but not SBS...

If you come to a web site and the vendor states specifically that they do not support SBS 2003 ...but they do support Windows 2003.... don't just accept that these days.  Especially if the application just plugs into active directory, there is (should not be) any technical reason why the application cannot be installed and supported on SBS 2003.

What normally happens is that the vendor doesn't take the time to test it SBS as a platform and then hears conflicting information from customers that have attempted it.  What you need to do is to dig up an email address on their web site and email them.  In today's marketplace they just might want to take a second look at that statement and do their due diligence in the matter.

... oh and feel free to cc me at sbradcpa-at-pacbell.net when you write a vendor who says they don't support SBS.... I just LOVE those kind of emails....

The Partner problem

Karl was at SMBnation Amsterdam and posted some comments into the smallbizit yahoogroup and one of the posts was this:

 Q: How do you deal with a botched install by a lousy partner?
-- The conferee is only one year in the business and has come across a totally messed up install by a gold certified partner. How do you deal with the client?
-- Marina told the story of her first such incident. Major point: If you look at the logs, you can see EVERYTHING that was done.
-- Jeff: This is a common occurrence. Asked to see who had experienced this. Nearly 100%. Recommends having another technician (from your user group) go into the client and verify your conclusion.

And it saddens me that how many years later we still have "certified partners" that haven't a clue about SBS installs and SCREW THEM UP.

Shame on you.. I know that those of you reading this aren't in this category...but I truly want to go to each and everyone one of these partners that end up HURTING small businesses because they don't take the time to get the information they need.

These days these partners have NO excuse not to read, learn, listen.

I know I'm not yelling at the right people .. but shame on you Mr. Partner for not doing your job.  Small Businesses deserve at least a good job and not a screw up.

Issues that are not normal

Too many times in the newsgroup I see a poster come in and say "Our SBS has been crashing regularly since we set it up...."

Uh.. folks...that's not normal.  SBS doesn't crash....and allocated memory alerts.. while an annoyance.... shouldn't be the cause for such crashes, freeze ups, etc.

Typically I'd say that the issue is one of hardware not software.... and folks.. it's something that you shouldn't just live with, it needs to be investigated and dealt with.  Start with testing memory... and then watch those hardrives.. call PSS(*) for some perf mon help... but get to the bottom of it....

...because it's not normal at all...

(*)  PSS or CSS as it's called now is Product Support Services/Customer Support Services... phone numbers for it are here...

Little things that annoy....

  • Email messages from vendors that have brief subject lines and CRM:00490444 in them.... I mean does EVERYONE have to use CRM software these days?  Is everyone tracking everything?
  • Knowledge base articles that appear to be exactly on point but aren't on the web site when you click on the link to them "The KB article you requested does not appear...."  ...well it appeared at some point in time otherwise how could there be a title?
  • Certain help web sites that because you google and click on them STILL launch a popup window from a vendor even with XP sp2 popup blocker, google toolbar AND Windows Live toolbar
  • I still say the Small Business Specialist logo looks crooked....
  • News Reporters that go overboard ....."hijacking hundreds of thousands of PCs before Microsoft made a patch...."... more like hundreds of thousands of security experts that went overboard.....
  • My Pentel mechanical pencils (yes there are times I still use pencils) who's tips get bent from being in my purse so the lead gets stuck....
  • Folks who think SBS shouldn't be set up using the wizards......
  • People who've had SBS for a while and don't know about Remote Web Workplace......
  • People who knee jerk think that VPN is automagically more secure.....
  • Technology wars, including but not limited to..... one nic versus two, ISA versus (fill in the blank hardware firewall), .local versus .com, Windows versus Mac/and/or Linux, Big server mentality versus Small server agility

Okay that's enough annoyances for tonight.... what little things annoy you?

 

..and thank you Vlad... I needed that  



-------- Original Message --------
Subject: It's okay CRM:00020006
Date: Wed, 5 Apr 2006 23:26:20 -0400
From: Vlad Mazek <vlad ownwebnow.com>
To: Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] sbradcpa@ pacbell.net

I still love ya. See, tracking confirms it!

 

-Vlad

 

Vlad Mazek, MCSE 2003

CTO, Own Web Now Corp

Vlad Mazek's IT Blog: http://vladville.com

SBS Show Podcast: http://sbsshow.com

vlad  ownwebnow.com

http://www.ownwebnow.com

 

SBS Show #15 - Managed Services with Mobitech
http://www.vladville.com/sbsshow/sbsshow-episode15.mp3

 


ExchangeDefender Message Security: Check Authenticity

Is there a RWW equivalent in big server land?

Indy asks if there's a Remote Web Workplace equivalent in big server land....

<insert evil cackle here>

No, silly you, it's SBS's and only SBS's.

And I'll point you back to Tristan's post about RWW

Blog du Tristank : Ninja Feature: Remote Web Workplace in SBS2003:
http://blogs.technet.com/tristank/archive/2004/10/14/242211.aspx

He had posted up some instructions to hack up some web pages... but RWW is way more elegant.

..but yeah.. I think we SBSers should share out that feature with our big brother servers....but for now.. we gotta keep something they are jealous over, right?

 

Pop quiz - do you see a problem?

Pop quiz... do you see a problem with this image?

..come on... see it yet?

Not yet?

Look very carefully.....

It's about a "zone".....

Yup...this is another of my newer OEMs that do not pick up the proper time zone unless you untick and retick the "automatically adjust daylight savings time"..thus if the end user would be booking appointment s in standard time zone... the Secretary is on daylight savings time zone and thus is an hour off.

You might want to check and make sure your machines are picking up the zone properly.  It seems like every time I get a new machine.. I end up with a rogue time zone because it hasn't picked up the daylight savings factor.

Brand trust

CRN | IT Brands | Dell, Apple Lead In Brand Trust, Microsoft Dead Last:
http://www.crn.com/nl/crndailynews/showArticle.jhtml?articleId=184425736

...okay I can understand Apple leading in brand trust.. but Dell?

You have to be kidding?  I still think that the OEM channel is the one destroying that Brand Trust... or at least strongly pushing it in that direction....Do you trust Dell as a brand?

Let's not isolate ourselves too much....

Subtitled... okay MBSA 2.0 is closer...but I STILL cannot consistently scan my domain worth a darn.....

Okay so we already heard from a poster that he used a dll exclusion in the firewall...

So we went back into our Small business server firewall settings... and clicked on "define program exceptions"

And then on "Show" and added an exclusion exactly like this:  %WINDIR%\SYSTEM32\dllhost.exe:10.0.0.2:Enabled:WSUS Port so that it ended up looking like that:

 

(Remember I'm still on that old fashioned SBS IP addressing that we used to use in the 4.0 days)  And now... on those workstations that are checking into the MBSA console..they are properly scanning the patch status... but I still do not have a consistent scan-ability of the network.  Even when I added the extra RPC connectivity allowance like Level Platforms needs.

I'm still getting way too much of this error on some of the workstations...an  then I'll scan again and won't get it for those same workstations.... I am scanning by netbios domain name... so why isn't this still working?  Or I should say...consistently working?

Why am I seeing error "Could not resolve the computer name: name. Please specify computer name, domain\computer, or an IP address."?
A.

This error is common when scanning based on an IP address range. This is because MBSA will convert the range into a list of specific IP addresses for that range and attempt to resolve each IP address into the associated NetBIOS computer name. When that name resolution cannot be performed because the computer is switched off, or the IP address is not in use, this error will be returned.

The error can also happen when using a domain name of domain members are not accessible on the network, such as a laptop computer roaming outside the wireless network, or a desktop computer that has been shut down.

If you specify a DNS fully qualified domain name (FQDN) as the domain to be scanned, you will also see these errors. In that case, you need to use the NetBIOS compatible domain name.

But I'm not.. I DID put in the netbios based domain name.... and I kid you not.. many of the people I talk to say that they tried MBSA 2.0... couldn't get consistent scanning results... got frustrated and dropped using it.... because they too couldn't get it to scan through the firewall.

But this reminds me of an email thread I had today with a guy about keeping "some" network goo... as a balance between security and that managability that I need to have ....as while Dr. Jesper Johansson is talking about Server and Domain Isolation techniques... I'm sitting here poking holes in the firewall and knocking off the Strict RPC compliance in ISA server because I want.... no... I NEED to have managability of the network.  I NEED to have a foundational bit of 'goo' that runs throughout my entire network so that I can scan them and get assurances that they have protections in place... I mean yeah... scan my SBS box and it says I have "Severe risks" ...but right now.. the fact that I can't scan my entire network... I think ..means I have a bigger risk.  I mean I know I can't do the Server and Domain isolation stuff the big server guys have to do... but it sure would be nice if I could scan the network with MBSA....

Stay tuned.... we're getting closer.....

Okay big server land people.....

Okay big server land people.....why isn't there an 'edit' key in the Group Policy Object Editor?

In the group policy...you type these GUID thingys in by hand?

I mean ...really... you never make mistakes when setting up group policy settings or something?  So why no edit button? You guys think typing this stuff in by hand builds character or something?  I mean look at the gunk I need to type in there... and for the record... when giving us SBSers instructions on group policy..don't assume that all of us have been in there enough to know that when typing in a new key we will truncate the "HKEY_LOCAL part and just need "MACHINE" up there.....


HKEY_LOCAL_MACHINE\Software\Classes\AppID\
{B366DEBE-645B-43A5-B865-DDD82 C345492}
\Endpoints REG_MULTI_SZ "ncacn_ip_tcp,0,n"

Yuck .. I have to manually type in MACHINE..wack... Software.. wack... yadda yadda

2. Configure Windows Update Agent to use this static custom port by setting a registry key as follows: HKEY_LOCAL_MACHINE\Software\Classes\AppID\
{B366DEBE-645B-43A5-B865-DDD82 C345492}\
Endpoints REG_MULTI_SZ "ncacn_ip_tcp,0,n"
(where n is the port number you have decided to use.) You may also configure the endpoint using the Component Services application in Control Panel. The Windows Update Agent - Remote Access endpoint is located under the path Component Services\Computers\My Computer\DCOM Config. Right-click and select Properties, then use the Endpoints tab on the Properties page to configure the static port.

And why do instructions like this assume that once we get to Component Services section.... in the control panel...that we'll even have a clue of what to do when we get there? I mean like look at this:

Okay.. I see the static endpoint in the Dcom protocol ...but.. now what.. do I need a protocol sequence of connection-oriented TCP/IP?  I guess so but the instructions don't say to mess with that....but gang....don't assume that we've been under the hood before and when giving instructions.. be specific...because if there's anything else in there... we're going to ask and wonder if we need to select anything....

P.S... skip the GUI?  Edit the text file?  Import them from the command line?  Are you insane?  ...excuse me... what do you think I am.... a big server person?

 

 

Like DUH folks - MCE has rapid sales

Chris Lanier's Blog : Microsoft Sees Rapid Media Center Sales:
http://msmvps.com/blogs/chrisl/archive/2006/03/21/87204.aspx

Yes, there is rapid sales because of the two retail software that our Small Business folks can buy at a retail store, at LEAST Media Center can be hacked to join a domain is why.

This has got to be one of the stupidiest stats I've seen..... go into a retail store and see what is being offered in there.  Home and MCE...and MCE is even being placed on laptops.

Does Bill or Steve know how many times my fellow SBSers walk into a firm and they are stuck with XP home or MCE as the operating system that the owner bought because that was the ONLY thing at Best Buy they could get?

Small Business Server hardening guidance

On the Security 360 webcast that was on earlier today, the topic was on "browser hardening".  And the VERY first question was about Small Businesses and they were looking for guidance on hardening.. and the question included hardening of the SBS box.  I tell ya... us SBSers are EVERYWHERE aren't they? 

Here is the guidance I would highly recommend as guidance for locking down a SBS box.

  1. Walk to the server.
  2. Turn around.
  3. Yes, I said turn around.
  4. I really mean, you need to turn around.
  5. Walk to the nearest workstation that has a user working on it.
  6. Shove the user aside (nicely of course, but you want to be in front of that user's workstation using their session).
  7. Click on the date and time in the corner.

Got that?

So why is that a hardening step for locking down a SBS box?

Because I would strongly argue that your biggest threats on a SBS network is the end users.  End that have local administrator rights.  End users that can download and click.  And if you can click on that date and time and it comes up and allows you to modify it, that user most definitely has the right to introduce risks into your system.  So lets talk about how we can harden the workstations, shall we?

Want to harden a SBS server and network?  Start by hardening the user. 

  • You don't surf at the server
  • You don't use the server as a workstation
  • You educate your users that "download here for free" translates into "yes, you really do want malware on your box, don't you?"
  • You have an acceptable use policy that says "yes, this is okay to do" and "no, this isn't appropriate for our firm" - check with the sans.org policy site to set up an acceptable use policy.

So that that you have that education task out of the way... you harden the desktop.  Here's the hard part... you need to check with the applications that are poorly written and won't work under these conditions.  Some of these things are not for all..but it will take YOU some time to do, so play first on your own boxes before rolling this out to your clients.

  • Get more control using Group policy - Consider IE active X browser filtering using this KB by Nick "the naked MVP" Whittome -
    • Outlook Web Access and Small Business Server Remote Web Workplace do not function if XP Service Pack 2 Add-on Blocking is enabled via group policy:
      http://support.microsoft.com/kb/555235/en-us
    • I honestly do not think that we do enough in group policy in SBS.  We have the GPMC tool right under the hood and all it takes is us to get up to speed.  GRAB A BOOK.  And read this spreadsheet to see all the potential for things you can control.
  • Use ISA 2004 (only in premium) or your firewall software to block sites
    • We had this the other day... mysite.com is not for business and thus sites like those should not be used in the office.  Bad sites introduce risk. 
  • Get those workstations down to "normal" user mode.
    • Sit down with that client/customer and see what key line of business applications they have.  If they are "designed for XP" they will natively run under this 'normal' user mode or LUA.  If they are not logo'd, come out to the newsgroups, communitities and google on ways to get that app down to 'normal user' mode.  Yell at the vendor
    • So many of the latest security vulnerabilities will launch things in the 'context' of the user, so the lower rights you have, the better you are
    • Review Aaron's blog about these issues
  • Get patches on those boxes/Get on the latest software.
    • When SBS 2k3 R2 comes out, the "green check" of updates will be there to help keep that system up to date.  You don't have to wait until then or buy it if you don't want to.  Download WSUS now.
    • IF YOU DO NOTHING ELSE, FLIP YOUR SYSTEMS OVER TO MICROSOFT UPDATE.  Yes, I know I'm yelling, but we truly now, with Microsoft update, have the ability to patch our entire system (YES even ISA Server 2004 - which hasn't needed a patch yet), so all the way from the workstations to the server can now be done by MU.  If you have not, all you have to do is go to Windows Update and on the right hand side is the place to click to "flip the bits" over to Microsoft Update.
  • Install the same sort of security at home that you do at the office
    • We buy Trend pccillian for all home pcs (especially those that remotely connect back to the network)
    • We require that they have XP sp2, firewalls and all the normal stuff I have here at the office.
  • Follow some of the information and guidance on Dana's blog.  He had a webcast on Compliance at the SBsummit..

But even with all of this... what's the best way to harden a SBS server and a network?

You start by hardening ME.  Me the business owner.  Me the onsite admin.  You harden me, you get me to understand that you can't just harden the server, that "I" have to change.  I can't download things like I used to.  I can't surf like I used to. I have to be a little less trusting.  A little more aware.  A little more paranoid.  Accepting of the balance between security and business that I need.  We need to work on this together.  You need me to understand that there's no easy fix.  No one button that I can point you to.

You don't get it by downloading a guide.

You start by hardening ME.

Only then will you have a hardened Small Business Server network.

Real server hardware

See that ... that's a sign that I've got troubles... but you see... I shouldn't be freaking.  If this was a "REAL" server and not my OEM version, I'd be going...okay ...let's deal with this but don't freak because you have a RAID array, good quality hardware and a real server.

On my OEM, this is not real server hardware, and I have no RAID, so no fault tolerance of drives.  Heck I'm soooo non best practices on this OEM test box I don't even have a backup of this.

Do I do this at home where I do have a server that I somewhat care about?  Nope.  I back it up with a LACIE harddrive.  Do I have RAID at home, honestly not, but it is a slightly better server.  Do I do this here at the office where it really is important?  Heck no.  I have RAID, I have server quality hardware, I have backups.

But keep an eye on those daily logs... as just like this, they will give you a heads up that something needs to be done....

(running a chkdsk now as a matter of fact)

P.S. note to self.. when the box has to reboot to do a better checkdisk and the OEM server is headless...keep in mind that you can't see when it's asking for input... gotta go drag it next to a spare keyboard and monitor...

Dear people who code at Intuit:

If you can't get access to this link, let me know.  There is a document newly released on the web that is the "logo" requirements for Windows Vista.  You might need to take a look at this when coding your Quickbooks 2007 version... you remember..the one that was stated will run with normal user rights?  Since you are going to be changing your software ...since it can't do that now... you might as well make sure it fits the guidelines for Vista while you are under the hood fixing things.

Just holler if you can't download it... I'll make sure you get a copy.  Just send and email to sbradcpa -at- pacbell.net

Here.. lemme make it a little easier for you....just make sure you pay attention to this section:

1.1     Follow User Account Protection Guidelines

A user’s Windows experience is more secure when applications run with only the permissions they need.  Unless an application is designed to be run only by system administrators, it should run with least privilege.

 

Every application must have an embedded manifest to define its execution level:

 

<requestedExecutionLevel level="asInvoker|highestAvailable|requireAdministrator" uiAccess="true|false"/>

 

Most applications should have level=asInvoker (leastPrivilege in Beta 1).  Applications that are designed to be run by system administrators may define a higher execution level, and the justification must be documented.

 

Most applications should run with uiAccess=false.  Applications that need to drive input to the UI of another window may set uiAccess=true, and the justification must be documented.

 

How many have you installed? Revisited.

The other day I posted about how customers should ask the var/vap how many SBS boxes they've installed ...and I got a follow up question of how do you "jump" into the market when you've only installed them for yourself.

... well you just did didn't you?

That's one. 

Install it at home.  Set up a domain.  Dynamic IP resolution to DNS.  MX redirect and the whole thing.  Install it like you would for a client that didn't have a static IP but wanted everything else.

There ya go.  That's one.  And that's better than the guy that says "oh yeah, we do SBS in our office, it's just like Windows... and we don't use the wizards". 

We typically say it takes three times to install it correctly anyway.  Once to really screw it up, once while reading the manual, and finally when you 'get it'.

Just never be ashamed to reach out for help or call Support.  Calling support doesn't make you look stupid in front of a client.  More like a savvy user of resources.

Steven ..honey.. I know that was a demo..but MAN was that a sucky password

So in the very first webcast of the SBsummit (that is recorded and available for viewing now) Steven is demo'ing RWW at the Small Business Summit and he says one thing...and does another that raises the hair on the back of my neck....

http://www.sbsummit.com/home/

He first says "accessing the date remotely from a Kiosk computer" and then he used like a three character password to demo/log into Remote Web Workplace.  Dude... first off I don't use Kiosk computers...I hand folks a laptop.  I don't have control of that Kiosk computer, I don't 'vet' it for security issues.  But laptops are cheap folks.  Get a refurb'd one.  Then you know it's secure and doesn't introduce rootkits or keyloggers or anything like that.  It's MINE and thus goes though all the same security checks that all the other computers do.

And Steven.. passPHRASES... try something a little bit longer of a password next time... that's ONE SUCKY password.....

Looking professional

On the smallbizit listserve today, the discussion was about renting office space and if it helped getting clients because you looked more professional.

Let's take that one step back shall we?  Go to the Small Business site on the Microsoft.com page.  And now search for a Small Business Specialist in your zip code.  I want you to compare yourself to your competitors.  Forget about the "professionalism" of a shared office space versus a home office, look what your web site and email says about you. 

One of the advantages of a server with Exchange is that you can have a professional email address..and not @yahoo.com. 

Now I need to ask something of you... do you find when getting services that you like to get contact information specifically about a person, rather than a generic sales@firm.com?  Or is hiding the fact that you are a one person shop why you want to do this?  Just not sure if folks want to see a more personable contact address or they don't mind the blind contacts. 

Just keep in mind that while you can sign up for a shared "condo" office space and look more professional, you might want to start with how you look to you customers in other ways as well.

Paul on R2 and Best Buy

In today's Windows IT Pro newsletter, Paul Thurrot writes....

" The R2 version of SBS 2003 adds all the technology from the mainstream Windows Server 2003 R2 release, along with several unique additions. "

and

" In a bid to make it easier for small businesses to purchase SBS, Microsoft is for the first time opening up Microsoft Financing to smaller purchases. In the past, customers wanting to finance purchases through Microsoft had to buy at least $10,000 worth of merchandise. But this amount was prohibitively expensive for some small businesses, many of which are cash strapped and on month-to-month budgets. To help these businesses, Microsoft is lowering the minimum purchase amount to $3000. So even small business customers can spread payments out over time--
typically 36 months--and pay for the technology as they're using it. Microsoft Financing is currently offering a 12.5 percent interest rate, according to the company.
Finally, Microsoft is working with Best Buy to provide training for that company's Geek Squad, which was previously focused only on supporting client-side technologies. Now, Geek Squad members will be qualified to install, service, and support SBS 2003 R2 and other server products, allowing small businesses to use the local electronics superstore for technology purchases and support. "

First off, repeat after me, SBS 2003 R2, does not now, nor ever have "all the technology from mainstream Windows Server 2003 R2 release"... we don't get the second cdrom at all of the "mainstream Windows Server 2003 R2 release".  I don't know where you are getting your information Paul, but that part is dead wrong.  Now lets not go down the argument again of why we don't get "it" on our "IT", okay?  Let's not start that again as I'm pooped over that issue.

Now as to the Best Buy issue... this has been a bit of a concern for some in the small vap/var marketplace as they try to get their customer from break/fix to managed services.  Vlad posts about it here as well.

Is this a good thing?  Well for one it will get the Small business product out front and center of those small business customers.

Is it a bad thing?  Well.. as a customer of the SBS product.. I want to make sure my fellow customers get a Var/Vap/whatever geek squad person that knows SBS, that understands SBS.. and that Geek Squad person.... or even a var/vap should not be installing SBS for the first time for your business.

I would urge every small business customer to ask that consultant "how many SBS boxes have you installed"... if they hem and haw... or say "oh my firm does"... you say "no, how many have YOU installed".  If the answer is "uh..none..yet", then give them this link to the SBS trial software page and go ask for another consultant. 

As a small business you deserve someone dedicated to the small business marketplace.

But the good news indeed is that financing plan for small businesses.  I think that will indeed be a very good thing.

 

An open letter to the "Do it yourself-ers"

We were recording a bit for the mid week SBSShow (with Susanne back in the adding class to Vlad and Chris role) and I said something about "being a representative of the DIY crowd" because quite honestly, I still feel that way as that's my roots and I feel that is some small way that I try to give that voice to the conversation when needed.  Even though I've moved from that position, I can say that I feel like I can relate still to that DIYer who gets a server and sees the potential in a SBS box for their firm.

Well to all of my fellow current DIYers and potential DIYers... I have a message for you.. and please understand that I give it with a great deal of compassion for where you are at.  I understand what you are facing. You are probably the "geekiest" person at your office, and someone read all of the literature of how easy computers are and servers and someone shoved this box in your hands and said "you do the workstations around here, it can't be that hard!".  Or you are the Linux guy or the web developer or someone who's really good at technology and this fell into your lap. 

Now I'm not going to say that your journey from where you are now, to a comfort level with SBS which is where you want to be is not impossible... It definitely is indeed possible.  But you are sure not going to get there if you don't do some basics.  You are honestly not doing your firm any favors if you don't start this process with the understanding that you are setting up the security parameter of your firm, the fortress of your data, so you'd better approach this better than we normally approach technology.

And the first thing... above all other things.. is to put down the mouse and READ.

Start here.. RIGHT HERE and download each and every one of these documents (okay so you can skip the Small Business Accounting one if you don't have that) but you should spend some time on this page... in particular this document.

When I decided to move from geeky DIYer to "okay I'm seriously going to be the onsite network administrator for my firm" in the SBS 2000 era, I ordered a SBS trial kit and install it at home.  Three times.  And then I read.  Books from Harry Brelsford.  Books from Charlie Russel.  And these days I'd add books by Eriq Neale (with the disclosure that I wrote two chapters in that one, and one in Harry's book).  And then I found a hands on lab course that taught a person about SBS.  And these days you don't even have to leave your office.

...but

I did ALL OF THIS before I even considered installing it 'for real'.  And even then, I was ready to hire a specialist if need be.  If I didn't feel that I could do this, secure it, to do the right thing for my firm, I would not have done it.  And I even interviewed Microsoft Partners, but back then there wasn't the Small Business Specialist designation so I didn't find an SBSer that I trusted.  Heck I didn't even find an SBSer.  The consultants I talked to tried to talk me out of SBS...they said "I'd outgrow it"  Uh huh..yeah...right... that's exactly what all of the consultants I interviewed said to me.  That they didn't like to install SBS as they found it too "limiting",they said.   Look where I am now... with SBS 2003 and RWW being EXACTLY what my firm needs.  I think I outgrew them.

And by that time I feel ready and had the resources I needed.  I had done the homework and knew what I was facing.  I was indeed ready to do it myself.

But do you get the idea that this wasn't a decision I took lightly?  That at any point in time that if I didn't think that I had the necessary information, and experience that I was ready to bail and hire someone to do this?  That I realized that I wasn't doing my firm any favors by setting up a network that housed the lifeblood of my firm if I wasn't prepared to do this?

So to all those facing the same thing...looking at a project that they are installing the backbone of your firm.... stop reading that marketing stuff that makes it sounds like all you need to do is add water and stir.  It's a smidge more complicated than that.  And think about that it just might be cheaper for your firm if you get help.  Yeah there's a lot more resources out there to help small businesses these days, but just remember, maybe it's cheaper, maybe it's better, maybe it's more secure, maybe it's better in the long run to READ FIRST and get training... or maybe...just maybe a little help to get you where that SBS box is just chugging, and you are just "admin'ing .  And these days, folks are quite proud to say they install SBS and recommend it to small firms.

Do it Yourself.. .sometimes means doing it with a little help.....

Customer Support Questionnaire

Customer Support Questionnaire

 

1.  Describe your problem:

2.  Now, describe the problem accurately:

3.  Speculate wildly about the cause of the problem:

4.  Problem Severity:

        A.  Minor__

        B.  Minor__

        C.  Minor__

        D. Trivial__

5.  Nature of the problem:

        A.  Locked Up__

        B.  Frozen__

        C.  Hung__

        D.  Strange Smell__

 6.  Is your computer plugged in?  Yes__ No__

 7.  Is it turned on?  Yes__ No__

 8.  Have you tried to fix it yourself?  Yes__ No__

 9.  Have you made it worse?  Yes__

10. Have you had "a friend" who  "Knows all about computers" try to fix it

for you?  Yes__  No__

11.  Did they make it even worse?  Yes__

12.  Have you read the manual?  Yes__ No__

13.  Are you sure you've read the manual?  Maybe__ No__

14.  Are you absolutely certain you've read the manual?   No__

15.  If you read the manual, do you think you understood it?  Yes__ No__

16.  If 'Yes' then explain why you can't fix the problem yourself.

17.  What were you doing with your computer at the time the problem

occurred?

l8.  If you answered 'nothing' then explain why you were logged in?

l9.  Are you sure you aren't imagining the problem?  Yes__ No__

20.  Does the clock on your home VCR blink 12:00?  Yes__ What's a VCR?__

21.  Do you have a copy of 'PCs for Dummies'?  Yes__ No__

22.  Do you have any independent witnesses to the problem?  Yes__ No__

23.  Do you have any electronics products that DO work?  Yes__ No__

24.  Is there anyone else you could blame this problem on?  Yes__ No__

25.  Have you given the machine a good whack on the top?  Yes__ No__

26.  Is the machine on fire?  Yes__ Not Yet__

27.  Can you do something else instead of bothering me?  Yes__

 

Thanks to Cheryl Wise MVP Front Page for passing this along

B - E - T - A does not mean "in production" or "on a box you care about"

I am running a beta of Vista at home...not that I really meant to...but I kinda loaded it up in a dual boot and it's been on the Vista side ever since...but at the office..in the real world where it counts.... I rarely run betas....the exception being the Microsoft Antispyware product.

I don't install IE 7 on any machine...and I don't like the fact that seemingly it's not being quite warned about on blogs and other sources as that it truly is a beta...heck there's even a patch in the optional section that refers to IE 7

Then DO NOT install the ISA 2006 beta on a SBS 2003 box.  Remember that we are an integrated platform and we wait for our parts.  And I already saw a poster in the newsgroup do this. 

Repeat after me... you DO NOT install betas on computers that you care about.

The problem with translations

I hope he realizes......That I'll probably be running every post he does through a google translation tool...

One of the problems of being a world of languages is that we are a world of languages.... and the sad part is that things don't translate well sometimes... and especially not when it comes to technology trying to translate.

There are some things that have slang meanings, or just have a different meaning in different languages...or worse yet, with all the technology we have... just do not go through the machine translations well "at all".  I still remember someone asking for an example of a badly done machine translated KB article and the response was "pick any".  And the feedback was.."no can you give us examples..." and the person answered back "no, pick any of them, as they all have slight issues with translation".

I find myself in translation issues sometimes too.... Jeff Middleton and I were recently talking and we joked about how ....sometimes I'm just more blonde than I should be and I should have a "George Carlin"-like post of all the words that I just shouldn't use anymore in my posts...because quite frankly .. I thought of them as one thing...but in a different country ..even one that speaks English they didn't quite have the same meaning... or .. and this is more likely the case... the meaning "I" thought it was ... just wasn't what it was in reality when I went and looked it up in an urban dictionary ....

Okay I'll "out" myself on some.....one is "wack", another is "friggin" (hey, I didn't think it meant as bad as the word I was trying to avoid) and one lately.... uh... well.... lemme put it this way.... we're just not going to even post the word that I thought was another word for a smelly brown organic substance commonly seen in the farms near where I live...because on the urban dictionary... it didn't mean what I thought it meant AT ALL.... and we're just going to leave it at that....

Just put it down that sometimes.. some translations don't go well at all whether they are via machine....or via the blonde.

Would you live there?

I want you to think for a moment....

If your computer you use was a house would you live in it?

If your computer you use was a city, would you want to live there?

Just think about that for a moment... all of those items I asked you to think if you wanted to do with it... are all about trusting something.  Trusting the house to be safe and secure and liveable.  Trusting the city to be civil and a nice place to raise children and a good economy for jobs. 

Think of where your computer goes and what it does and what you do with it.  Do you trust it? 

Do you trust your network?  If your network was a city would you live there?  If your network was a State would you want to live in that State?

Now think of the Internet.  Think of what goes on in the Internet.  Do you trust it?  Do you feel that it's safe and secure? 

Think of it as a place to live.  A Country.  A city.  A house.  Where you would be, day in and day out.  It would be your home.  Would you want to live there unprotected?  Without a policeman?  Without a guarddog? Without the infrastructure of a 911 call system, and fireman, and doctors? 

So tell me... if you ...right now ... today... live in a house that you consider safe enough.  If you live in a city that you consider good enough to raise children and provide jobs.  If you live in a State or Country that you like to live in.  If you couldn't dream of living in a place that didn't have the basic infrasture of SECURITY as it's foundation.....you couldn't dream of living in a place where there isn't the assurances of fire protection, and emergency services, and protection, and medical attention that proactively ensures that you stay well and eat right and exercise and all of that.......

If that sounds like a really good way to live.....where you would want to be...

...then why do we do what we do to our computers?

...the very things that many of us depend on for our businesses?

...the very things that provide us with jobs?

....why do we not take care of them proactively... why do we instead spend money on the equivalent of the emergency room medical treatment....why do we not ensure we have adequate safety and protection so that we can minimize the risk....

...why do we with our computers and networks live in the equivalent of a crime infested neighborhood, not caring about cleaning up the crack houses and drug addicts, not caring about the drive by shootings and the muggings.  Not caring about our very lives.... why does it seem that if we "lived in our computers" it wouldn't be a good place to live at all....

so I want you to think about that....

If where your data lives.. is not where you'd like to live....

...why do you let your data live there and not protect it?

IT

You see I'm tired of the argument over "IT".  Yes I know we don't get "it" in '"IT", but sometimes, especially in a small business we don't always get exactly what we want.  And sometimes we have to come up with our own solutions.  These days business owners really don't care if the solution is from this vendor or that vendor.  It's your job to come up with a solution.

For the record if you want to know what of "it" you can do on "IT", you might want to check out this blog posting.

If you can't sell "IT" to your clients because it just because you already have a patch management in place and don't need SQL 2005 Workgroup?  More power to you.  Wonderful.  Fabulous.  You are ahead of 99% of the rest of the universe because most people I talk to don't have WSUS and a patch management/testing program/process in place.  And that's the gang that I'm beta testing "IT" for.  Because there are some firms that will want "IT", and as long as there are some customers out there that will be buying "IT", I'm beta testing for them.  I'm not walking away from "IT" just because it doesn't have "it", because there are still clients and customers that will be running "IT".

But gang... business owners don't care if "IT" has R2 bits or not.  They want you to listen to them and solve their needs with whatever tools are in your tool bag.  So if you need to use robocopy or Rsync... then do it.  And indeed post up the "how to" on a web site or wiki and share your solution with others.  Because the deed is done and every single time we argue about "IT" not having "it", it's not helping your client that doesn't care about "IT" or "it".  He just want you to handle your Information Technology needs.  You know.... the other IT in this argument. 

He or she hired you to propose a solution.  He or she doesn't really care where it comes from.  He or she just wants it to work.  And that's your job to pick based on his needs.  Just don't mess with his desktop or his Solitare game and just handle the server side and come up with something that works.  And if you stay on the "old" "IT" because your line of business apps won't upgrade to SQL 2005, that's do-able too.  Line of business apps do not upgrade to new databases quickly AT ALL and SQL 2005 is still a bit young for most LOB app developers.

So if you want to give feedback about what you think is wrong with "IT", a good spot might be steveb@microsoft.com, and can we all agree that "yes, it sucks, Microsoft, the Lawyer run Monopoly has got to be smokin' somethin' up there in Redmond with all of their SA/R2 stuff and man Longhorn better be good" and get back to solving real problems and not arguing over how dumb it is that we don't get "it" in "IT" and get on with providing real solutions to real clients?

One thing you have to remember about me.... at the end of the day I'm a business owner and look at things a little differently than most (besides the fact that I'm a Dew drinking female in a Tech/Geek world sort of adds to that wacko viewpoint too).  You see, I still see that there's still a lot of "drool" factor left in the Us Versus Them, even after I update it with the "it" versus "IT" stuff.

Because you see Remote Web Workplace and the 6 am email is still there.  And to me, the business owner, that's still the two killer apps of SBS along with the normal Email and sharing of calendars.  SBS isn't perfect.  And your job it to add to it to solve the needs for your clients.

You are the solution provider.

And if you noticed, I'm staying away from calling "IT" by it's real name.  For two reasons.. one I'm tired of the arguments over "IT", and for your clients, even calling "IT" as just plain SBS 2003 has some businesspeople (including my sister) asking "Isn't that out of date?  It's 2003?  Isn't there something newer?" 

So what would you like to call "IT"?  (We were calling it by something else but I found in the urban dictionary ...but what I thought it meant wasn't what the urban dictionary gave as the meaning....another blonde moment for Susan.... so I think I'm going to have to stop calling "IT" by what I was calling it.)

The trust factor

Define a "Managed network".

Got an idea?  Is it like Durf's ideal managed network?  http://smbmsp.wikispaces.com/Defining_Managed 

Yesterday someone was asking how do they get "into" the vertical market of Accountants and it reminded me that it's the same uphill battle the "managed" network folks face.

How do you become the "employee" they aren't paying with a W-2..  trusted..... part of the technology team?

Here are just some of my thoughts..... and first off with a caveat ....this is a very US centric post and these offers are not world wide.

  • Build the trust.  While we beancounters are probably still running (or fondly looking back anyway) to Windows 98, there was one thing that would (and still does) drive me crazy.  When a consultant comes into a firm, ensure me that you treat access to my network in a secure manner.  Don't ask me for the Administrator password and then build yourself a "backdoor" admin account and don't tell me you did that.  Inform me what you did.  Ensure that you change that password if employees change.  Consider discussing remote access windows and adjusting the access time so that you can only have access to the network at certain times.  Don't ask me to email or fax you a list of my network passwords either (I've had this with printer/copier vendors). 
  • Remind Accountants that they have client social security numbers on their systems and should take reasonable precautions in protecting that data.  Reasonable... quite frankly... doesn't include Windows 98.  Yes change is hard, but so is putting information back together again when your peer network that isn't properly backed up ...isn't being backed up.  They want and need shared calendars.  They need to send email (even though most of us are not encrypting it)
  • Be knowledgable about restoring a SBS box.  One of the issues that comes up in "selling" SBS is the "ol" single points of failure.  All on one box and all that.  But be prepared by explaining that a proactively managed system along with quality hardware is the way to do this.
  • Be prepared to deal with the "is it secure enough" discussions.  When even Vars/Vaps are not deploying Remote Web Workplace and instead use VPN, get a better understanding of the security of the technology and the real risk of that network.  Do a technology assessment with them.  Ask them about the last "incident" they had.
  • Sign them up for the Microsoft Accountant's Program (www.microsoft.com/accountant ) This is the US centric part of the post as SBA 2006 hasn't released to all shores.  As a result this MPAN isn't offered world wide.  If the person who works in the field of accounting (bookeepers, CPAs, etc) signs up, they are eligible for the Action Pack software offer.  Now think about that... that's the normal software the registered MS partners get that you can then take to your Accountant client and sign them up for and get all of their computers on a solid network.
  • And last but not least.... come up with a solution to get clients data from there....into here... now whether that solution is using a third party site or solution, or building something on that server (but quite honestly I'm scratching my head a bit about how you could do this with a SBS box with the user/device cals and the fact that you would always want that transmission to be over a SSL tunnel so they'd have to authenticate).  You may want to set them up with Logmein or I use Quickbooks Remote access which is a Webex 'invite' and 'approve' remote access solution.  Use the server for the data repository, but come up with a remote data transfer on approval solution for them.

Build the trust...fix the needs...

(just updated the post as I think they just redid their web site today on that RemoteAccounting link)

Buying software

Went to Office Depot tonight to buy Accounting software for a client who needed to update (old 2003 version ....yes... I bought Quickbooks... I think they will take my Security MVPdom away for that....) and I noticed that Small Business Accounting 2006 was no where to be found.  Oh sure, I could buy a SBS 2004 (three day shipment special order) but Microsoft SBA 2006? 

Nope. Not on the shelves.

Folks... Office Depot and Costco are where my small business clientele go to get software most of the time.

 

Be careful what you ask for - Part Two:

Subtitled.... "Does Susan blog too much?"

Earlier today I talked about the member of my SBS Partner group who said he was getting near information overload from all the various vendors and sources of Small Business Information.  My earlier post was asking us to brainstorm about the ways to make the various "official" web sites better. 

This post is about “What if you were in charge of the Universe” and could change anything you wanted to on the community listserves and newsgroups and blogs and web sites and podcasts and what not…..

It’s come up before that someone has asked us a few years ago that wouldn’t it be grand if we in the community could all come together and coordinate and work on the ultimate perfect SBS site/web/wiki/thingamabob in the world.  There’s one problem.  Because we all come from various places all over the world, and for most (if not all) of us, the things we work on are a labor of love and volunteerism so you’d better make it in a venue that we find “entertaining” while we volunteer on it, it’s hard to get coordination from a bunch of volunteers.  Add to that that most of us are control freaks, or that getting a collaborative site would probably mean that someone would have to sit down and understand licensing...and well.... this is why we sort of have all these places to go to for information.

So how do you harness this spirit to be able to make it easier for folks to find things with ensuring that the person in the community likes to do it and gets an “attaboy” for doing it?  Look at all the volunteer energy that folks give around here.

It’s not easy is it? 

I call SBSers “cockroaches”.  We’re little, small, indestructible… and we’re EVERYWHERE.  It seems like everytime I turn around there’s someone in some venue asking a question about SBS.  And sometimes I know it's hard to be aware of all of the venues and resources and web sites and links and.... just everything we've got around here. 

So let me ask this again…. So how do we as a community do better in helping you, the Var/Vap not get overloaded with information?  I was reading the book by Shel Israel and Robert Scoble and one of the things they said was to blog consistently.  Once a week, Once a month, Once a day.   But be consistent. 

The other day Jeff Middleton pointed out to me that I was about a three times a day blogger.  And I think he’s right.  A break at lunch.  And two at night before going to bed for relaxation.  But am I blogging too much?  Should this blog be more on just techy geeky stuff or do you mind the occasional introspective post… the every now and then (okay so it’s probably a bit more often than every  now and then) rant post?

What about our other communities?  Are the listserves getting too much into theory?  I think we’re not as patient in the listserves as we used to be….and I think we’re getting too much into theories and arguments and maybe a lot of folks are tuning out?  What do you think?

Grey Lancaster used to say "kill folks with kindness" and "be patient with newbies".  Now that "small business is big business" are we as patient with the newbies?  Should we be?  Or should we say "You know, if you are serious about small business, show it by buying a book, reading, and then come back."  Or should we follow Grey's leadership and welcome folks into SBSland and help them learn and grow in this profession?  Because all of us started just like that, with a kind word from Grey.  Including me.  When I was cleaning out my SBS 2000 notes and paperwork I found a bunch of newsgroup posts that Grey had done in the newsgroup that I had saved.

So how would you make the community listserves better?

How about the podcasts?  What topics aren't being covered that you'd like to see (not that I don't think Vlad and Chris and Suzanne and the SBSPodcast gang aren't picking fabulous topics...but since we're brainstorming...let's have some fun and see what we can come up with)

What about SBS Partner groups?  I know that SMBTN.org is doing mini conferences and emphasizing 'business' talks as well as tech ones.

Blogs?  Websites?

What other community resources could be made better and how?

Now I'm not promising that I can keep myself to one post a day...but let's just brainstorm on some ideas.  How can we make the community resources better than they are now?

So if you were in charge of the universe...what would you do?

Be careful what you ask for - Part One:

The other day in my SBS Partner group this topic came up…. Do we now have what we asked for …. And is it too much?

It was about how before in SBSland there was a veritable waste land of information.  We shared because we found that when we relied on each other we learned more, we shared the “been there and done that” information.  Even the Microsoft partner site was geared toward certified and bigger partners.  The comments I heard from folks that while it looked nice, it was hard to navigate around.

So here we are… about a year… year and half later and the comment was made that now, instead of the wasteland, we’re tripping over Small Business information all over the place.  To the point that we’re getting overloaded with stuff. 

I mean I was telling someone the other day about the resources and it was kinda silly… Podcasts over there….. webcasts here….. listserves… and web sites….. and are we getting too much information?  And are we getting the right kind of information that we need?  But at the same time are we not ensuring that once people have met a certain milestone that they have access to the right kind of information and someone or something is filtering out the noise so they can do a better job and they are rewarded for stepping up to the plate and being serious about Small Business.

Every now and then I like to do what I call “what if you were in charge of the Universe….what would you do?” and think about how we can do things better in SBSland.  It’s something that Jeff Middleton of SBSMigration.com once asked in the newsgroup.  I’m going to do a series of two posts… in this one I’m going to put you guys on the spot and ask how you think Microsoft could do a better job, and in the follow up one, I’ll ask you how you think the Community of SBS could do a better job (including me). 

Now I’m not promising that anything will happen because of these questions… but sometimes…just bringing stuff out in the open and hearing different ideas give us things to think about long term (and okay so I’m hoping folks in Redmond may just get an idea or two from the feedback posted, so it will be a fun experiment nonetheless).

So now I’ll turn it around to ask about the various community and partner sites in SBSland:

Right now there are three major landing places for SBSers and web site that are official from Microsoft…… the www.mssmallbiz.com site, the Microsoft.com/partners site and the new landing place inside of that that is unique for SBSCers.

If you were in charge of the perfect site(s) for SBS partners….both registered AND Small Business Specialist Certified.... what would you do to make it better?  Would you leave the www.mssmallbiz.com site just the way it is? Use it for a launching point to the Partner site?  Have all Microsoft information regarding SBS behind the Microsoft partner portal?

Here’s my two cents of why I like the www.mssmallbiz.com site just the way it is.  And this is just my opinion so I want you to think about your thoughts on these sites and post in the comments about what you think. It’s a little bit rough.  Unpolished.  Got some frayed edges on it.  It’s a Sharepoint site.  But it looks like something that a busy Small Business owner would put together.  It showcases the very technology that SBS has in it.  Sharepoint.  It sends me Alerts when there are new things.  It helps people join in the small business marketplace by putting out the welcome mat and letting people come in without having to register for anything right at first.  They can look around a bit before walking in the door.  A lot of stuff is in the window where you can take a look at it.  There are notifications and alerts. 

Now let’s look at the Small Business partner site behind the Microsoft portal and the SBSC partner portal.  You can only get there once you register.  It was funny but on a SBSC listserve someone asked if having that designation would “put your clients off” because they would perceive that you were not independent.  Let’s be honest with ourselves…..there is a definite lack of trust by both clients and Vars and Vaps of Microsoft.  But at the same time, for those folks that have stepped up to the plate and taken the certification and “paid the dues” you need to ensure that they have something special and unique that they get out of the certification.  But are there enough “push” technology from these sites?  RSS feeds?  What about the newsgroups?  One of the advantages of the Partner site is access to the managed newsgroups because you are guaranteed one on one Microsoft engineers.  But because I can’t search them as well as I can the public newsgroups via Google Groups, I’ll be honest and say that I tend to use the Public newsgroups as a resource, where as the Partner newsgroups are more for a one on one issue resolution venue.

Then there’s the issue of getting folks to sign up for the Partner site.  There’s many a time I have to urge a person installing SBS networks to sign up for the Microsoft partner site.  And then there’s the issue of “so can’t I look at what I get before I sign up for it?”

I’ve been involved in other organizations where a credential process has been underway and it seems like everyone struggles with this.  You have to have the bar for entry such that a ‘critical mass’ gets the credential.  But once this critical mass has been reached, you need to raise the bar so that the credential means something.  Then you need to ensure that there is information and value unique to that credential so that others will want to be part of the membership as well.

Coming from where we have been in SBSland, the historical place where we share everything to anyone…. to now where we honestly have to step back and say… you know …maybe we need to organize ourselves a bit more and start asking for things changed and let those who have ‘paid their dues’ have a little bit better space over there…but still keep a space over here as the Welcoming committee place.

So what do you think?  

If you were in charge of the Universe and could do anything you wanted to the Partner and SBSC sites, what would you do?  Do you use the www.mssmallbiz.com site?  What do you like?  What don’t you like?   How would you make the Microsoft Partner site for registered partners and SBSC ones better than it is now?

I think there should be more RSS feeds and push technology.  I know that I visit www.mssmallbiz.com a lot more than the SBSC site because stuff gets pushed to me.

So come on... let's brainstorm!  See what things we can come up with as ideas....and then we'll ask.  Hey, they can always say no, but you have to at least try to ask in the first place.

When dealing with technology, always leave yourself a backdoor

I was multi tasking a bit this weekend and the CTP build for Vista came out so I loaded that up last night as I went to bed in a dual boot manner.  So I've been flipping back and forth between Vista and XP when suddenly this evening the XP side of the world, dealing with the NIC card starts to freeze up the computer.  Then starts the fun stuff...the NIC loses connectivity. 

You know how hard it is to google up a resolution to a technology problem when your google can't google because of loss of tcp/ip connectivity?  And because of course I really didn't have a lot of time to be messing with fixing this...suddenly I became an Expert Vista user real fast. 

I still have to find the settings from Sandi that you can use in the registry to tell this blog that I'm not IE 7 but rather IE 6 so for now I'm on the wirelessly connected laptop typing up this warning about always leaving yourself a back door.

Whether that backdoor to the Internet is a wireless laptop...or... a Vista partition, make sure you have a way out to the Internet.  I can even get there via my Cingular Air Card these days.

Note to self... don't blog while under the influence of too much Dew...and well... um... sorta...in a mood...

I find it ironic..that my blog post ranting against marketing spin would be 'spun' in other locations and into different meanings.  It was a rant about marketing of both Linux and Microsoft and how marketing 'spun' things and didn't list facts especially to those that needed facts (like Vars/Vaps) and in fact Tony reminded me that I need to give facts about the new SBS 2003 R2 licensing that that platform includes.  I'll do that in a blog post after this one.

But there's a couple of things I like to bring back up about that post that some of the comments in there bring out.

  • Open criticism of a Company that holds me in high regard.  Okay where in the playbook does it say that because a company has held me in some esteem that I can't point out when I think their marketing is being stupid?  That it needs to be fixed.  Here's something to think about folks...it's because I CARE that I wrote that post.  If I didn't, I'd be walking away and saying nothing.  When I say things, it's because I think things can be brought out in the open, refined, discussed, possible changes made, or better understanding at least.  If I didn't care, I'd be giving up.  Calling it a day, folding my tent and going home. 
  • SBS shouldn't be used where there's a need for branch offices.  Okay where in the playbook does it say that you can't do Branch office stuff with SBS?  Where in the playbook does it say that small firms don't have branch offices?  Where in the playbook does is say that that branch office is in an office?  Sometimes these remote offices are home offices.  Some of these branch offices are Starbucks locations and on the road.  Who wouldn't want to do branch offices AND have the power of Remote Web Workplace (and if you are in the SBS marketspace and go Huh? when I say RWW or Remote Web Workplace SHAME ON YOU for not knowing about the TRULY killer app of SBS 2003!  Google it for heavens sake)

I think still the problem is there are two SBS marketplaces.....one is serviced by the Var/Vap.. and these are the firms that get technology and are mobile and agile....that are putting in more than one location, that are being agile....and then there are those that haven't yet gotten into SBS.  The ones that the Var/Vaps haven't touched yet.  The ones that still have to be convinced of a server...to move away from a Peer to Peer.

In the meantime, I'll still keep complaining when I think something is dumb and stupid.  Yeah, it's my opinion, and maybe I'll change my mind later (after all I am a woman and it comes with the territory) but if I yell, it's because I care.

Remember that. 

It's when I stop yelling at the gang up north of me is when Microsoft really should get concerned.

Anti Spin Cycle please?

When a washer is squeezing out the excess water, it runs a spin cycle.  There are some days I want an anti-spin cycle when it comes to marketing and white papers and what not to squeeze out the fluff and get down to the facts. 

My sister was talking about some software that was being demo'd to them...and it looked wonderful... it could do everything absolutely perfectly....there's only one catch.  Only the company demo'ing the software could afford all the modular parts that made the software do exactly what was being showcased.  No normal firm, especially these days, could afford all the parts that would make it all work.

There are times like today I get tired of the spin cycle.  Today I saw a Linux white paper that compares the TCO prices of Linux to Windows and in their comparison chart calls ISA 2004 a "web server" and includes it in the pricing comparisons.  Uh, nice guys, but ISA 2004 is a firewall and doesn't compare at all to an Apache/Jboss server.  Apache/Jboss normally goes 'behind' a firewall, which is what ISA Server 2004 Enterprise is.  Then on the SBS Faq site , today I noticed it said this in their faq about what's in SBS 2003 R2:  

"SBS 2003 R2 will only include one Windows Server 2003 R2 component and that component is Windows SharePoint Services Service Pack 2. "

Microsoft, come on, give me a break.  I get Windows Sharepoint Services Service Pack 2 on Microsoft Update for heavens sake.  When I can get it on a Sp1 box, and already have it there, call me wacko, but I don't consider that it's something special that's included from the Windows Server 2003 R2 parts.  Furthermore on this Windows 2003 R2 comparison page, it says that Windows 2003 sp1 gets it too.  You know why Linux is going to win the hearts, minds and pocketbooks of businesses?  Because we, John Q. Public are losing trust in you.  Truly, we are.  You are slowing eroding the trust.  And quite frankly stuff like this plays right into that. 

Want to have proof that the paranoia isn't just relegated to the Tinfoil folks?  This very statement was on a listserve the other day in regards to trusting Microsoft Defender Beta 2....

"If we relegate watching and protecting for malware, trojans, adware, spyware and the like to Microsoft, who will be watching them?"

Last summer I was in Chicago for Tech conference and the gentlemen giving the keynote (admittedly using a Mac to give his presentations) said that Microsoft was on the real verge of losing trust by it's customers.

Am I the only one that is getting tired of the spin that I see going on?  I mean there are marketing books on 'how to tell a story'.  Why can't facts sell?  Why don't companies see that facts can be just as powerful as fluff?

You know what John Q. Public really wants (or at least I think so anyway).  They really don't want to have to think about security, they really don't want to think about technology working at all.  They want a TV set or a toaster level of technology.  They don't want to be dependent on a family friend to get their printer working over a two weekend timeframe or be dependent on their 10 year old to take care of their computers.  But they still want to download that music and what not. 

So will a Linux distro or Microsoft be the maker of that TV set or toaster of the future?  The maker of that technology that just works? 

I really don't know.

Right now I'm not sure John Q. Public can trust either one.  Right now the Maytag spin cycle is working overtime in both camps.

...and then there are those times that technology works....

So...we revisted our problem computer with the printer error....and so we lifted up the XP Home to XP Pro and in the process it refreshed the bits so that when we added the printer 'this' time, the HP loaded up like a champ. 

We shared it out and now Son and Daughter can both print via secure wireless network to the printer attached to Mom and Dad's computer.

I felt like Zelda Rubeinstein in Poltergeist (the second time) pushing hair behind my ears and saying "this printer now works".

Who knew that the sound of an inkjet working could sound sooooo good.

Let's hope the technology poltergeists are really and truly cleaned out of that system.

Take that HP!

Okay Charlie Russel (of SBS admin companion book fame) has pointed me in the direction of a HP tool to "scrub" the machine of it's malfunctioning printer driver.

I'll keep you posted...so far the computer is winning the battle...

This computer safety announcement courtesy of Seagate

This public service computer safety announcement courtesy of Seagate, makers of fine (and heavy) harddrives.

 

It's recommended to not accidentially drop a harddrive on on your foot.

 

We now return you to your regularly scheduled blog reading....

"ouch!"... "Dang that hurts"

 

Can I get that without fries and google please?

Dear Mr.  Dell.....can you guys offer a "bundle free" version for us folks that don't want this stuff?

 

You guys in the big server world flatten these guys and reimage them to your specs.

 

We down here in SBSland do not.  We walk into a client and because of Dell and other OEM bundling and potentially deceptive advertising of computers labelled in the "Small Business" flyer as "small business computers" we have to deal with XP homes that can't join a domain, and these days Windows Media Center computers that we have to hack up and void the warranty to join a domain.

 

Mr. Dell you are affecting the security of every small business with your "bundles" and "advertisements" out there.  You do understand this?  How come you can't take some of this bundling revenue you are getting and preparing a small manual on how to keep all this stuff up to date and patched that you are bundling on my systems?

 

When I go to Taco Bell I want a lunch "bundle".  I don't want one with my computers. 

 

 

http://www.windowsitpro.com/Article/ArticleID/49338/49338.html

 

 

Dell Testing Google Software Package Install on New PCs

            

   by Paul Thurrott, thurrott@windowsitpro.com

 

"Yesterday, PC giant Dell admitted that it was testing a package of

Google software on its new PCs, setting the stage for a second round of

desktop competition for Microsoft. The first round came 2 years ago,

when the world's largest PC maker started offering Corel WordPerfect

products on its PCs. Since then, Corel has reported millions of new

users each year, thanks to PC bundles."

Exactly how many licenses do I have?

I have access to an MSDN license that gives me testing rights to an operating system

I have access to an Action pack license that gives me rights to run the IT side of my business

My firm has a Open Business/Value (whatever the 3 year software assurance is called) because at the time I signed up for it, there was not the MPAN program and since the majority of the firm's income is from consulting other than IT, I didn't feel that it was kosher to be running the firm on my "action pack" license.

I think I'm about as legal as you can get, as least I hope so.  A fellow CPA said to me that what they didn't like the most about Microsoft licensing was the 'wink wink' that seemingly occurs.  That he felt that Microsoft purposely turns a blind eye to the issue of illegal software sales. That oh sure... Bill Gates and make a big deal about it, say that it's going to take 10 years, annoy the heck out of us with Windows Genuine Advantage and Activation, but when push came to shove they needed to put their money where their mouth was and truly make and effort to show they were really and truly serious about piracy.

Two of Vlad's posts showcase this better than anything... first a vendor still selling NFRs and then a Doctor buys the Action pack.

Microsoft... if you want to walk the walk and talk the talk on piracy.... this is where the cliches' come to pass and you put your money where your mouth is.

You spend the Lawyers fees to shut down that vendor.

You train your staff to understand the difference between a Doctor of Medicine and a Implementer of Technology.

Patches protect you from viruses?

"Notice: To protect your system from viruses, Dell recommends that you download any recommended patches and hotfixes by visiting the Microsoft Support website at support.microsoft.com or by selecting Tools -- Windows Update in your Internet Explorer browser"

I have some issues with that statement... for one... viruses can be unleashed on fully patched systems and do damage, so the statement that patching alone protects you isn't good enough.  Secondly that statement is from page 7 of the "Setup and Installation Guide" of a Dell OEM SBS server.

  • Where's the discussion of configuration of automatic patching and flipping to Microsoft Update (should you want to do that)?
  • Where's the discussion of obtaining a desktop/server/email antivirus to protect all the methods of potential infection?
  • Where's a discussion that patches come out once a month and therefore expect a possible reboot of the machine if you set up automatic patching?
  • Where's a link or discussion of what Service packs are appropriate for a SBS box.
  • Where's a discussion how you shouldn't even be using the Internet Explorer browser on your server

Yeah yeah... probably way over the head and in the next part of the server install set up from Dell..but I just though it funny that they define "viruses" as being preventable by patching.

Remember the 123 protect my PC:

  • Firewall
  • Antivirus
  • Patching

So?

Okay so why does this page http://blogs.technet.com/ link to this page.... http://blogs.msdn.com but that page http://blogs.msdn.com doesn't have a link back to that page http://blogs.technet.com/?

Just wonderin.....

Dear Live Communication Server people:

Dear LCS people....just saw this blog on the demise of Netmeeting in Vista and just wanted to remind you folks that I do love your Live Meeting server that allows me to have internal only messaging in my firm, allows me to track who's in the office and who's not and allows me to integrate it with Sharepoint.  But I gotta level with you guys that I'm one of the wacko ones that got Software Assurance and caught the product somewhat reasonably priced ...and I even re-SA'd it to hang on to it. 

Harold talks about the Exchange and LCS being under the same business group...but I just want to put in my two cents once again for a lightweight, no VOIP, no hosting of streaming media...just plain old 'chat' inside the office for quick messages. 

Most of us in small business are using our own duct taped together solutions for an internal IM...but if you guys just happen to want to have another product to roll out...and yes, sorry, it's got to be cheap... a nice low feature internal only IM would be nice if you have some time.

Feedback worth listening to

I was reading a post on the coding horror blog and the post about "good bugs versus bad bugs" reminded me of a company that seemingly takes feedback and does nothing with it.  No, I'm not talking about Microsoft here...but rather one of my LOB apps CCH. 

They do something in their tax program that just is inconceivable to me.  You see there are times that we need to fill in a form called a "Power of Attorney" where we can talk to the IRS (taxing agency) directly.  And there are specific identification numbers that we use.  Unique to each partner in the firm.  So when we migrated from Lacerte to CCH you can imagine our surprise that the "supposedly" less robust Lacerte, who all along has this master firm database ability to quickly and easily pop in a partner listing of unique info that was global to the program has been able to do this all along, but when we got to the CCH program, it cannot do this. 

It's a database program mind you.... in reality...and a basic database function....the ability for the program to remember unique data for each partner without having to individually place it in each taxpayer... it's now a "feature request" that we've put in for three years.

Now I cannot imagine that larger firms don't see this as a feature request.  I cannot imagine that larger firms don't have umpteen times in a day that they need to fill out a power of attorney form.  And the fact that this process is so manual, and that I have to keep a document separately to keep track of this information absolutely boggles my mind.

Why does it take a number of customers to wake up to a fact that they are missing out on something only because they haven't compared the features of a competing vendor to realize that neither vendor seemingly designing the software in a manner that optimizes what is the basic function of the program.  A database... a gathering of data.  Not a word document that has to be opened each time to enter in a data, database.  But an all encompassing program that keeps track of everything that the user of the program might need to do their job?

There are times I really wonder if any of the app developers are listening to the right people. 

Are they listening too much to the bleeding edgers?  Are they listening too much to the folks that have been using the same tax software since 1913 and they haven't changes their technology ways one iota?  (Okay so I'm exaggerating, but I kid you not, people do not change and migrate to new ways of techology well at all).  But truly, are they listening to the users of this software?  Sometimes I wonder.

My guess is that many of you reading this blog are not "users" of SBS but Var/Vaps.  And you are not the "users" of the software.  Oh sure you use the admin consoles and what not, and you still have to from various third party apps like Level Platforms or MOM and what not cobble together the "Var/Vap" console that you'd love to have (and that I swear I was at a AICPA Technology conference a few years ago and Bcentral was supposed to do something similar in the accounting space, but I digress) but in reality, you aren't the users of SBS.  

There are times that I don't think the vendors out there listen to you guys the "Admins" of SBS.  But the problem is and will always be the marketplace of SBS.  We're cheap down here, let's face it.

A blog should not have email

The RSA Security Conference is coming up and if you remember last year's conference Bill Gates made two announcments.... one was that IE 7 was going to be released for Windows XP and the second was that Antispyware was to be free to individuals.  It will be interesting to see what keynotes there are this year.  Last year the major ones were webcast.  So I'm out on the site and they have a new "Security Exchange" that includes Blogs....well..let's just say it has "one" blog.  And here's the kicker that made me laugh.  When you go to the page where the blog content is, there isn't ...that I can see anyway... a RSS subscribe icon.  Instead there's a place to click to..... "Subscribe to receive emailed updates of new blog entries from Ira Winkler"

Uh... gang... there's this thing called RSS? You know it's where you have a RSS reader like Newsgator or RSS bandit and all your RSS feeds come to you...and they aren't jumbled in all with all that junk mail I already get?

It's bad enough that the Orange XML tag is "RSS" on some pages and "XML" on another...but can we have another standard?  A blog standard?  That it comes with a XML feed that can be sucked in?

Not emailed, thank you very much.

https://www.rsaconference.com/exchange/blog_view.aspx?id=3

Apparently paper competes?

I was in Office Depot and it's like every paper stock sold there is now whiter or brigher...but whiter doesn't mean brighter... so make sure you have your terms right.  Apparently there is guildelines...or competitive grades of paper... and North American papers are different than European.  I mean I always knew that the American 8.5 x 11 wasn't quite the European A4 grade.

I guess, though technically the A4 size is the true international size and we're the ones who need to change our paper in the United States.  But then again, I distintly remember learning the metric system in school and they said we'd be driving kilometers by now....

...last I checked... we're still measuring stuff in miles....

Changing things is hard.  Just ask my office were we have to make sure that all our "old" white paper is saved and used for non important projects so we don't mess it up with the "new" white paper.

Who knew white doesn't match white any more?

How do you get the Industry journalists to care?

Earlier today I was called by a journalist for my industry to ask some follow up questions about some statements I had made to an author... and it showcased to me just how far we need to go to get people to care about Computer Security.

---------------------------

Thanks for the follow up call regarding the article that was written for _my industry journal_.  I am concerned a bit that you stated that your reviewer of the article did not understand that running with administrator rights on our systems is a key factor of why we get malware and spyware on our machines.  By all means forward this email and my email address to him or her and I'd love to discuss this in greater detail.

In my own office I had a Secretary that was getting malware and spyware on her system and the antivirus and spyware tools would not stop them.  Remember that such software is always 'reactionary' and not proactive in defense.  Since I took the time to adjust her system to run without administrative rights, she can no longer surf to sites and download icons and emoticons that I have not authorized, she can no longer merely 'surf' to web sites that may infect her system.

Two actions can get malware on a system typically in my office.

1.  Clicking and downloading from web sites that are designed to 'trick' the user into installing spyware.
2.  Surfing to a site that injects the spyware into the system because it piggy backs on unpatched web browsers, Sun Java or other 'infection' means.

Now given that I keep my web browsers fully patched, the second risk is lessened, but unless we stop the end users from downloading and installing software that they are truly not authorized to install, we will always be one step behind the bad guys.

Moving to another web browser is not the answer in the fight against malware and spyware.

Let me point you to a couple of articles on this topic:

http://www.thechannelinsider.com/print_article2/0,1217,a=166172,00.asp

http://blogs.technet.com/jesper_johansson/archive/2005/11/30/415328.aspx

"Barring users from gaining administrative access—and thus restricting their ability to install such unwanted or malicious software—will automatically tighten security and will garner other benefits as well."

Spyware and Malware was voted number 10 of the Top Tech issues by the CITP and ISACA members in an AICPA poll recently.  Spyware and Malware is big business that includes Russian mobs and other criminal elements.  By not doing all we can to protect our weak links in our firms…the desktops… we are playing right into their hands.  Firewalls do not stop this activity.  Antivirus and Antispyware are always one step behind.  As long as we do not control our desktops and instead rely on the ability for our end users not be be 'tricked' and 'scammed' we cannot adequately protect our systems.  The average user doesn't want or need to be a geek, but we in business need to protect their systems accordingly.

http://www.crt.net.au/etopics/migmaf.htm

Vendors like Quickbooks that consistently require "Administrator" rights also impact our security decisions.  I built a web site to highlight these vendors www.threatcode.com They don't have to care about coding securely because we… the buying marketplace does not care.  We do not care because we do not know why running with administrator rights is dangerous.  It's a vicious cycle.  Because the marketplace doesn't care, the vendor won't change.

To give credit to Intuit, the maker of Quickbooks, they have stated that they will change the way the 2007 version of the software is built to be more secure.  But this was only after the SANS.org organization made them their first "Hall of Shame" vendor for coding in this manner:

http://www.sans.org/newsletters/newsbites/newsbites.php?vol=7&issue=59

Application Vendor Demands Unnecessary Administrative Privileges Violates Policy of Least Privilege

This new section allows the user community to share intelligence on applications that require users to lower their barriers to cyber attacks. Now that the US Air Force has established a minimum standard of due care, soon to be adopted by other government agencies, there is a standard against which to measure the application designers' security decisions.

The first inductee into the Application Security Hall of Shame is QuickBooks.

The latest release of Intuit's QuickBooks, widely used by accountants and businesses, negates the security attributes of the underlying operating system (e.g., Windows) on a computer using this Intuit product. Installation and operation of QuickBooks requires granting operating system "Administrative privileges" to the user, giving users complete control over the security features of the computer on which it is installed. In an enterprise setting, this hinders the organization's ability to ensure security policies are implemented appropriately for password control, user privileges, and other security disciplines for a computer with QuickBooks installed. This is an unfortunately perfect example of an application software product demolishing the security capabilities of the underlying operating system. Computers with unprotected operating systems are easy pickings for would-be intruders looking for personal identity and financial information in QuickBooks files.

In response to Newsbites' recognition, Brad Smith, senior vice president of QuickBooks, confirmed on December 2, 2005 that this problem will be fixed in the next major release (QuickBooks 2007), scheduled for delivery within 12 months.

--------------

Bottom line... as long as we don't know...don't understand.... we won't care.  We won't ask for vendors to make the software help us be more secure.  We and vendors both have to understand that that least privilege is an absolute minimun in this day and age of security issues.

So what's the ratio of Lawyers to Software Engineers these days?

An email was sent to some folks saying that they needed to ensure they were on a certain Office service pack.... and it looks like it's another case of Lawyers and Patents going overboard again....

Thanks to Mr. Amado, you can't link Access and Excel one way, you have to go back to Excel and change things.

From the PatchManagement.org listserve.... 

I believe this might stem from the Carlos Amado vs. Microsoft patent case
(http://www.siliconvalley.com/mld/siliconvalley/11829604.htm).  It's US
patent # 5,293,615 for those so inclined to read the volumes of legalese
abut it on uspto.gov.

Microsoft has KB article 904953 (http://support.microsoft.com/kb/904953/)
which is titled:

"You cannot change, add, or delete data in tables that are linked to an
Excel workbook in Office Access 2003 or in Access 2002"

This is the "More Information" section of that article:

"Because of legal issues, Microsoft has disabled the functionality in Access
2003 and in Access 2002 that let users change the data in linked tables that
point to a range in an Excel workbook. However, when you make changes
directly in the Excel workbook, the changes appear in the linked table in
Access."

So what do you want?

I want a SBS best practices tool.
I want a automatic GUI domain migration.
I want a ISA log that doesn't track the first 'unauthenticated and then authenticated' log in the log file.  Pick one,  I don't need both.
I want a tool that goes into a Spyware infested XP and can lift out all the good data and clear off the bad.
I want OEM systems to stop shipping with all the crud they do.
I want to have filtered audit logs that will warn me when only the bad stuff is occuring.

I want all error logs to be written in plain readable English and not require me to go first to www.eventid.net and then to google and then dig up something else.

I want all wizards to tell me proactively when I'm about to screw something up and didn't mean to do that....

I also want world peace and and end to world hunger and everyone getting along and virtual hugs to everyone and know that there's not enough money in the world to get ever everything I want out of either Microsoft or SBS or the rest of that list.

At the end of the day someone says "okay we can do this, we can't afford to do this".  It's called a budget.  It's something that we in Small Business tend not to do like our Big Server counterparts.  This is budget season where my sister works and the manuverings and stuff that goes on as they snip a bit from here... do a bit over there... and in the end no one gets everything they want.  It's a compromise.

In small business, our budget is typcially the checkbook or the credit card.  The ones I've seen never sit down with a plan at the beginning of the year and forecast revenues and expenses.  They don't set an 'expense goal' as it will for departments.  There isn't this end of the year, let's spend our budget because if we don't we won't get it allocated to us next year ridiculousness that large companies have. 

I'm also going to generalize and say that many small businesses are cheap.  Dirt cheap.  And what they don't realize that their manner of 'break/fix' computers is not only costing that firm more in the long run, it's placing them at much greater risk.  But that's the problem isn't it with small businesses.  They aren't used to the budget and plan method are they?  Rather then break it and panic and fix it.

So what do you want?  Because you can't get it all.  It's about choices and trade offs isn't it?

Just call it "Sam the SBS Server"

It's funny.... there are times I don't get marketing.....and there are times I don't get customers....

...take this for example... a guy complaining about the mailing about the "New" Small Business Server 2003.  It struck me funny for two reasons... for one there is a bit of a point to it that the consumer focuses on the 2003 and doesn't realize that there has been changes to the SBS platform since October of 2003 when it shipped.

Let's see what's different shall we?

For one... if you have Premium.. in the year 2006 you have the latest version of ISA Server 2004 that you didn't have in 2003.  We now have Exchange 2003 sp2 supported on SBS 2003 and thus can go up to 75 gigs of Exchange storage that we didn't have before. 

For two... since October of 2003, we've installed Windows 2003 sp1, Exchange 2003 sp1 and 2, Sharepoint sp1 and 2, MSDE and SQL Server sp4, Outlook sp2.. and every month I install new bits on my machine.  For that matter...every month I have a "New" SBS box as the bits I had the month before are not the same bits I have now.

You know what I would do if I were in charge of marketing?  Stop calling it by the year.  Instead just call it the "Latest SBS".

And when it comes down to it.... that business owner really doesn't care what you call it.  He's buying a solution, not a year. How about we stop worrying about the names of products and instead understand that what we're really selling here is a business process solution.  We're not just selling technology, we're here to help find a solution to a business need, fix a business pain, make something work, enable someone to do something.  The name of the technology solution is, quite frankly, irrelevant to the person writing the check.

They just want it to do when you said it would do.

 

 

So where's your media?

I sure hope Merv is wrong...but it sounds like he's not.

JRittley is stuck.. he can't find cdrom1 of his SBS 2003 media set that he got with the OEM Gateway server that he got. And what's the only way that he can get a replacement?

Buy an entire new Server OS.

Yes, you read that right, unless you order replacement cdroms within 90 days, Gateway says he has to rebuy the Server OS all over again in order to replace the missing cdrom.

You know.. I sure hope Microsoft realizes that all these stupid policies by the OEMs... no media and only the OS on a hidden partition replacement method, a 90 day replacement media policy... are affecting John Q. Public's view of Microsoft.

And me as a shareholder of Microsoft in my 401K is concerned about that...Dell or Gateway shouldn't have that much ability to impact the view of a software company in my book....

So ... you made a duplicate copy of your media and stuck it in a lockbox or something paranoid like that?  Me on Open License... I can get replacement media all the time for a nominal shipping charge.  I sure don't have to rebuy the server OS if I accidentally lose the disks.

Wow.

So?

Where's your media?  Got it in a safe place?  Got all your disks?

Ensure tinfoil is in place please?

Quick you may need this protection..... especially if you go and listen to the latest Steve Gibson podcast about the 'rogue developers of Microsoft' who placed 'an intentional back door' into the operating system.  In the meantime you may wish to also read the MSRC blog and their take on the same issue.

Now Steve says 'he's leaning toward Open Source because you can review what's in there'.  Oh.. really ...just like this vulnerability in Novell's SuSe Linux that just came out today and appears to already be under attack.  The vendor was notified on 11/15 and the fix out 1/13/2006.  "Remote exploitation of a heap overflow vulnerability in Novell Inc.'s Open Enterprise Server Remote Manager allows attackers to execute arbitrary code."  Why isn't that a 'back door built by rogue developers like the WMF exploit?

Tim says he's waiting for next week in his blog about this...and that's exactly what Steve wants.  Look at the 'buzz' this one podcast has gotten.  Talk about a very VERY unprofessional way to handle this.  First off... Mr. Gibson, I email secure@microsoft.com ALL THE TIME and seemingly even with the spam filters that tend to mark my pacbell.net as spam, I get responses from them.  Secondly, whether he cares or not, on the backchannels of security listserves, his podcast is being ...well quite frankly...laughed at.  Next...for him to say that he is the 'first' in this charge.....he was not the first to charge that WMF issue was a 'backdoor', on January 2nd to be exact, other bloggers and companies did.

If you are going to charge something like this, Mr. Gibson... first off don't charge something of this magnitude without contacting the company first, secondly .... to podcast something when you aren't even sure of all the facts?  That's just irresponsible in my book.

Enough with the tinfoil folk... get real....flaw yes.  Intentional backdoor by rogue developers?  Get reasonable Mr. Gibson.

Dear Tip Top Equities

If you think for one moment that I will even think of buying anything from you after you've spamming my Pacbell account for the last few hours.... guess again folks.  And why in the world would I want to buy a penny stock called HLV Capital anyway?

It amazes me that spam works.  Obviously it does enough otherwise it wouldn't be effective. Today I was asked if I could get rid of junk mail completely and I said "No."  Just like how junk snail mail pays for the rest of us to use regular postal mail, so much of what annoys us and bothers us, has a value to someone, a market. 

If there was only a way to get rid of the profit motive, this stuff would dry up.

So Mr. "Under the Radar Equity", "GrandSlam Stock", "Stock Radar", guess what....I'm not buying!

So I was on the MS Partner site...

And I was looking for SMB partners... so I started with the site how your clients would see you.... and I gotta say... now maybe this is Fresno or something... but have you truly looked at how professional you look to a client from that MS partner portal?

Some of you list no web sites, no email addresses, or your web sites are dead.... or better yet... the bio of your firm is .... well... if your only experience in computers came from after you yourself surfed to p_rn sites and you ended up having to clean up malware...that's not exactly professional in my book.

And folks?  Frontpage makes some better [admittedly boring] websites better than you guys do. 

Come on guys... look at what you look like to your customers and clients.  And quite frankly....some of you need to take a second look.

You'd think I'd learn by now

HA!

See that?

That's a Dell OEM with a Nvidia driver up in the "High Priority" patches.

I do not do video drivers via Microsoft update just because I've had bad personal luck with them... but I never get a video driver up there in high priority on a box that I've flattened...yeah yeah... I know... I should just flatten these guys and start again...you'd think I'd learn...

So I get the TechNet Magazine today...

....free subscription to US only [sorry about that check out www.technetmagsubs.com/zout] and on the cover is the ad for an article inside that says "Security Alert:  Disable your admin account" and I first thought...okay.... who's come up with that idea.... as do that on a SBS box and you'll find that when you apply Service Pack 1 the SBS part of the install won't work....

...so I flip to page 75 and .... oh...it's him.

Giving that he's now an honorary SBSer guess I'll cut him some slack now. 

:-)

When is free wifi not always a good thing...

Matt talks about an experience I've noticed as well... you get to an airport and you say "Hey, free wifi, that's so cool!" and then you realize that some ports are blocking and you can't do all the things you wanted to do in that time your plane is held over.  It gets back to that net neutrality again, where the pipe you log on to is able to allow you to do what you want it to do. 

I always carry my Cingular Wireless card for the PC so that no matter where I'm at, if it can get cell phone connection, I can get online...and if I'm at a place without cell phone coverage...man that is roughing it way too much for my level of comfort.

Mr. Murphy at work again

So I'm loading up a new Dell computer at the office and I connect it to the network via http://servername/connectcomputer as I've done so many times and I go to change the home page from being not http:\\companyweb [as it's a little slow to pop up and folks like msn.com anyway.... and wouldn't you know it.... I've been beating my head on this one screen for hours now.

DNS/DHCP is coming off the server, everyone else can log into companyweb just fine throughout the entire office, I can log into companyweb just fine using another profile on that one workstation..... it works just fine on the existing computer.......but not with THAT user account on THAT new workstation.

I've reset the permissions on that user account

Logon attempt by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0

Logon account: user

Source Workstation: Annoying_computer_that_I'm_about_to_throw_through_the_window

Error Code: 0x0

And nothin...... it acts like the three login/permission on the entire web site issue...but the perms on the web site look good.

There are times that Mr. Murphy loves to play head games with us, doesn't he?  It would be the boss' new computer too wouldn't it?

...off to google... I'll let you know what the resolution was..if ...the computer survives that is....

Sometimes it's embarrassing to be an Accountant

Truly there are times that when I'm at geek events I drop the "CPA" credential because second only to Attorneys, my profession has a reputation of being behind on technology.

These days I'm embarrassed as well by the Accounting applications... between ones that won't support patches past a Security patch in 2004, to my favorite poster child of Quickbooks that to this day requires local adminiatrator access, for a profession that prides itself on Accountability and SOX and all that control stuff....we sure don't know how to code up an application worth beans.

So in addition to the information here on how to get Quickbooks to share data on a server, and here, Stefan reports on the smallbizit listserve that to get the program to share out properly, he had to give the Quickbooks service account full control of the directory where the data is residing.  Also he had to exclude the service account from the password policy and set it to 'password never expires'.  Then you had to stop and restart the service.

Okay so I don't know about you but the fact that with a $39.95 password cracker program from www.elcomsoft.com I can hack the passwords of Quickbooks in mere seconds, the fact that they still require local admin rights in the 2006 version, that they won't even address the local admin issue until 2007, doesn't give me all warm fuzzys that that application is sitting on my domain controller.

When is the backbone of business, the accounting application, going to step up to the 'secure coding' initiative here?

Guys, this is embarrassing when it's the accounting applications leading the pack here.

So I called and shut down two credit cards today

So as a result of my SB1386 notification, I called and shut down those two credit cards to ensure that they could not be used in any fraudulent transactions.  While there I was checking out some of their fraud protection stuff....

.... I can just see it now... 'Ms. Bradley... we're seeing expenses to Frys, NewEgg, CDW, Amazon, CompUSA and Sephora all one one day... and we think the Sephora has just got to be the fraudulent transaction as all the other vendors are pretty typical transactions.....'

 

Is McAfee [and other preloaded software] a virus?

So it's that time of the year that we look around and ensure our systems are up to date before busy season and get new computers if needed.  So I go and I buy the Dell Optiplex line, this time making sure that I bought the extra PS2 port option which isn't really 'extra' per se at all as it doesn't come standard with the box.

So I boot up, get it up to a workstation mode [before joining the domain] and there's my first lovely Red Mcafee window that hits me in the face.... well...says I.... let's get rid of that since I have the firm antivirus.....and I realize that there's no "x" in the corner to shut down this annoying configuration wizard.  You have to go through about four screens before you can finally get to a place to cancel.  Then to rip it off the box, you have to remove about three McAfee programs that are on the system....and I don't want McAfee in the first place!

The major insult to injury is the fact that in being installed on the Optiplex, it has with it's McAfee Security Center, taken over the duties of the XP sp2 Security Center.  Even though the a/v is out of date, there is no little red icon of Windows down in the system tray telling me "I'm screwed", instead there's the 'normal' McAfee red icon that tells me nothing.  So I uninstall that... reboot the machine...and the XP sp2 security center does not restart... I ended up having to restart the box 'again' to get the Red shield down there like I wanted it to be, being the indicator of the patches and the antivirus.  I still don't have my fully functioning antivirus that I want... and everyone that I tell this rant to said "oh just flatten the box, those preinstalled things are like a virus".  But how's the Mom and Pop non geek person going to handle this?  They don't need a McAfee security center... how are they going to follow Microsoft guidance for how Microsoft update and patching works when there's no shield in the corner?  No icon? 

Mr. Dell?  I bought this computer.. I didn't give you the right to shove the antivirus that you made a corporate deal with down my throat.  It's getting to the point that I'd pay more for a plain computer, because quite frankly I've had enough of this.

 

Solving all the needs

If you haven't seen it before a while back I did a "Us versus Them" page that compared SBS to 'normal' Server.  The other day another person posted in the newsgroup that they couldn't understand why the Server OS was the price it was and SBS...with all those other things on it... was so much cheaper.

Seeing a comment on the SBS blog talking about the SBS 2003 R2 choice of SQL 2005 Workgroup reminds me that the marketplace of SBS serves many people.  For me, and my industry, the very first time I've ever used SQL server was for Sharepoint in the SBS 2003 platform.  Prior to that I didn't even install it. 

The other day a consultant had a problem with a server and it majorly affected active directory.  When he came up for air long enough to reflect on his weekend, lack of sleep and pain to that customer, he asked for one thing...

"I have some concerns about Small Business Server", he said.  "Make it simplier"

So here on the one side of the marketplace is a Consultant who want less of the complexity, less of the glue, less 'stuff' to make it easy to recover, easy to backup, easy to ensure it's up and running.  And then on the other side is the Consultant that wants all the complexity, all the features, all of the functionality of the big database of the huge platform. 

Can't have it all, can we?  And you know what... I think the marketplace will understand the pricing of the platforms that small business can handle and they will choose what platforms they code on accordingly.

I am a small business.  And for now I am very happy to be on the SBS platform and you know what.... there are times that I won't get everything that I ever read about in a glossy brochure.  But you know what?  I know I can't afford a Rolls Royce.  I drive a Acura [it's like a Honda] and that's just fine for my needs. It's a comfortable mode of transportation and I'm quite comfortable in it.

So maybe I'll have to balance a bit of complexity of SBS with not getting a SQL that does an Oracle replication.  Because after all it's my applications that normally tell me what database they want, not me telling them what platform they need to code for.  I think they'll know that in my sized industry to pick the right database. 

But that's just what I think anyway....

Trend needed hotfix to send Perf reports out after V3

Wayne in the newsgroup reports that .....

FYI..There is a patch for Trend Micro V3 which corrects issues with SBS2003 Reports and other not being sent to external domains.

For more information read the thread Trend Micro V3 Issues 12/04/05

 

For  others who may have this issue you need; Client Server Messaging Security 3.0 - Messaging Security Agent Hot Fix - Build 1157

The zip file is; Smex_7.2_11571.zip

 

Which includes; csm_30_smex_72_win_en_hfb1157.exe

 

Which fixes:

"This hot fix corrects an issue that some MIME formats could cause    Message Module(TMMSG) to convert the original SMTP message into a wrong format. Converting the SMTP message into the wrong format  might cause Outlook Express to time out when retrieving email messages using the POP3 protocol."

 

Applies to SMTP too. Once the hotfix was applied SBS2003 Performance reports go straight out and Meeting Requests arrive intact.

 

Wayne

 

Okay I gotta rant... come on Trend "Request the smex70_win_en_hfb1157.exe file from TREND MICRO Technical Support.

Premium Support Program (PSP) clients can contact their Technical Account Manager (TAM) directly

No, Trend, you put a patch like that in a place that those of us who live in a 24/7 world work and live in can get to it.

 

[btw that wasn't Wayne ranting...that was me, Susan as usual!]

 

Sam the SBS Server is very upset today

I was going to interview Sam the SBS server for this ...but right now he's yelling and is so upset I can't calm him down enough for the Interview.  He's very upset that a year after he was deeply embarrassed by what he did that it happened again.  That people still have the original code on their systems and have not patched.

Server bug cripples Dublin law firms | The Register:
http://www.theregister.co.uk/2005/12/10/server_bug_cripples_dublin_law_firms/

He said that when this first happen it was Microsoft's fault.... now this is yours.

We now have this patch on the Microsoft update site.

You now have no excuse whatsoever to not have this patch on SBS 2003 boxes.  All you have to do is flip that server from Windows Update to Micrsoft update...which ... if you've ever WU'd that box it now recommend that you do so.

If these servers were installed by an IT Pro?  This is your job.  Both Sam and I cannot understand how the IT pros of the world not at LEAST know about Microsoft update, not trying to be learning WSUS, not be proactively helping your client to patch.  Want to know one of the ten ways to get your server hacked as per Johansson and Riley's book “Protecting your Windows Network“?

Don't patch it.

If this is a DIY setup, okay I'll cut you a little slack ...but even still... you don't even have to install WSUS... all you have to do is visit Microsoft Update as those SBS patches are now offered up.  I cannot believe that just as we reach the milestone of patches now being offered up on our boxes, that someone cannot find their way to Microsoft update... I cannot believe that they went this long without updating...that's RTM code of October of 2003 that hasn't been updated.

Let's review class of exactly how easy it is to visit Microsoft update.... start, click on Windows Update.

There?

Now on the right hand side, see that Microsoft Update box?  Click there and go through the process of installing it.  Download what it tells you to.

Heck, turn on autoupdates, because I'd rather you have unmanaged patches being installed on your box than none at all.

I'm sorry but I'm in a mood.... if you buy a computer READ THE INSTRUCTIONS.  It's our duty these days to patch.  It's our responsibility to learn the power of the technology we have.

Learn to patch.

Go to Microsoft Update.

Sam the SBS Server was ashamed of what he did the last time... today he's ashamed of us.   That we can't take the time to understand enough on how to keep him running.

If you don't have Microsoft Update 'flipped' to being the update mechanism on the server[s] you have and control, do it today. Make Sam the SBS Server proud of you and not embarrassed that you couldn't even keep him up to date.

We suck at communication

For the last couple of days I've had a project where I've had to read emails.  Emails that were not my own.  And I must say that email is damaging our business communcation.....

FOR SOME OF US WE CONSIDER THAT SHORT EMAILS IN ALL CAPS IS APPROPRIATE LEVELS OF COMMUNICATION

for others they consider that all lower case is the way to do email

4 sum its uzing shrt wrds

The sad thing is, much of what I'm looking at is business correspondence, and yet emails are treated like instant messages, with short comments that if you attempt to go back later on and review the conversations, much of the meaning is lost.  We don't need to put a Gettysburg address in email, or a Federalist paper dissertation, but I think we need to be a lot more professional in our business email correspondence.

What happened to the rules of letter writing?  And why has the “Instant Message“ method of email become the standard communication means?

It's made me look at my correspondence in a new light and make sure I'm not “IMing“ when I should be giving good business communication.

Dear Microsoft Licensing People

Dear Microsoft Licensing People...

When giving information to SBSers... make sure you are not giving them “Big Server Land” information.

It's Friday and I'm in the mood for a rant....

In the newsgroup today someone was trying to download a copy of a trial version as overseas they couldn't get the software through customs worth a darn, and so someone told them to buy SBS under Volume licensing and they said “oh yes that if you had Open value that they could get downloadable media..... they said... and I quote from the post...

'I have a confirmation from Microsoft that though it was not possible to download the media through eOpen, it is in fact possible to download licensed media through Open Value at the MVLS site. This is confirmed for US only.'

 

Well I AM an Open Value customer and I can confirm WITHOUT A SHRED OF DOUBT that it's not available for download.  Folks, this is why the media gets sent to me automagically because we need a product key.

See this download screen?

Do you see the fact that there is NO SBS 2003 on that listing? 

Folks when you talk to Microsoft in any way shape or form, especially when it comes to licensing, can you say to them “can you check and make sure your information that you are giving me pertains as well to SBS?”  And if they say there is no difference, don't believe them, because when it comes to Software Assurance and other small business licensing information, I can assure you that we are unique, we don't get all the benefits and for many folks that you call on Microsoft licensing, they really don't have a clue about the small business licensing.  Hands down the best resource for Smallbiz licensing is Eric Ligman and company on the Mssmallbiz site and the official Microsoft Mssmallbiz yahoogroup.

So ...want to know the real scoop of what I get with software assurance?  Check out this grid.

Okay let's review...since I have 2 servers and less than 50 desktops....

  • For the Open Value that I have that doesn't go through the Eopen site but instead through MVLS site, I do get version upgrade rights.  So I'll be getting SBS 2003 Release 2 [WSUS, SQL server 2005 workgroup and Exchange 2003 sp2].
  • I do get media for the server sent to me automatically [mainly because I can't download it]
  • I will get Windows Vista uprade rights and a copy of Virtual PC Express edition for every Windows software assurance license I have.
  • I don't have 50 Office licenses so I won't get training.
  • I do get a cdrom called the Information Worker eLearning cdrom 
  • I get a Windows eLearning cdrom
  • I get a Server eLearning cdrom [it's not SBS specific though]
  • Office gets home use rights
  • Desktop - for every $200,000 of SA for Office and Windows I get one phone incident [translation... I get barely get one phone call at that conversion rate]
  • Server for every $20,000 of SA I get one phone incident for servers.
  • I get “cold server rights“.
  • I get one user ID for Technet Managed newsgroups [I think I have enough newsgroup access :-) so I might pass on that one]

Someone said that Microsoft themselves internally should not necessarily pay for licenses but be required to track their compliance. 

Bottom line folks...whomever told that SBSer that we can 'download' a copy of SBS... is ...well... flat out wrong.

Upgrades to SBS 2003 R2?

Adam says he just talked to the MS Concierge and they said the only way to get R2 was to buy the 'whole' product again, as there were no upgrade options.

Adam?  Tell that Concierge-y person to go listen to the SBS weekly show where Guy Haycock 'aka the buck stops here' SBS Product Manager says there will be. 

Guy's post and that podcast should clear up any confusion.

One correction to Guy's post though.. he says that if you have SA for a nominal fee you'll get the media... for those of us on the three year SA plan it gets automagically sent to us.

And Adam?  The web site you were pointed to was Windows 2003 R2 pricing, not SBS pricing.  We don't have SBS pricing yet.

When standardization isn't a good thing

Sometimes standardization is good, and sometimes it's not....

Ed Foster's Gripelog || Dell Won't Recall Defective Motherboards:
http://www.gripe2ed.com/scoop/story/2005/8/30/0141/79530

Between the motherboard issue from the past, to a more recent issue we are tracking with fans going out on the Dell GX 280 CPUs.  When you start seeing a batch of hardware start acting flaky... ask around... you might not be alone and thus you might need to start looking a little closer at that system.

Declaration of Administrators and End Users for installation of software and patch standardization

Sun Microsystems:
http://www.sun.com/2005-1004/feature/
read that link regarding the Google toolbar being now included in runtime updates

I hereby put forth a Declaration of Administrators and End Users for installation of software and patch standardization.

If software companies can do End User License Agreements, I can have my own agreement and declaration of rights.

Dear Software Vendors.

When updating me, you will not bundle in technologies that I didn't realize you were partnering with.  You will not make it confusing to my Mom and Dad when keeping their computers safe. 
This has got to stop.  You say that this is being done to support free and open source software and all it is doing is adding tool bars I don't want, software I don't need.

I refuse to install any Sun Java Runtime as long as you bundle software with it.

I don't want to have the Yahoo toolbar with Adobe reader either.  I don't want MSN desktop search with my MSN IM.  I don't want to have to constantly monitor every single application for options, uncheck boxes or any other ways I have to constantly monitor for unknown applications entering into my networks, my parent's computers.

As an administrator, as an end user, I demand that you do not make me have to ensure I read every screen, click every click to only get the software that I thought I was getting.

I agreed to install one application from one vendor.  I did not give you the right to insert a tool bar that gathers information from me.  I did not give you the right to precheck "yes" to installing additional software.

I want all of my vendors to start agreeing on a patch installation standard.  I want them to publish in a database their supported versions, where one can easily go to see in the registry what version one has, and other such standard procedures to audit the application of patches.  I want to be notified via email or rss feed when you are releasing patches for my applications.

You want my trust?  So that I'll buy products from you?  Use your software?  Then you be way more transparent and accountable to me.

I'm the user of your software only as long as I want to be.

Remember that.

Susan Bradley
Admin

Yeah I know... it's Friday... I'm in a mood.....so....anyone know the email address for Scott McNeally?

Knowing what you need

What if you heard a story about a person who had a laptop so infected that it needed to be flattened but they couldn't find the original cdroms to rebuild the machine?

What if you heard a story about a person who moved a file frome one machine to the office machine and ended up infecting the office network.

What if you heard a story about a computer guy who was supposed to write a database program, asked the business owner to buy a server from Dell, a Business server...and it sat around for like 60 days and when the programmer finally came in he said “you got the one with SQL right?” and the business owner said “I don't know?”

What if I told you that when they called in another person [a college student] to work on the server when the first guy walked off, no one knew the password so they had to use a cracking program to reset the admin password?

What if you heard a story about a person who was considering setting up only one machine in the network as the Internet machine because he didn't want to risk infecting all the rest of the machines?

What if I told you all these people..... are the same business owner?

The stuff I take for granted...most business owners don't know about.  They don't know that original cdroms should be kept for just this reason, but better yet they don't know the way to KEEP their systems from getting into this mess in the first place.  I make sure all email get scanned at a gateway before it comes into my office.  I buy antivirus for our employees at home to keep their machines clean.  And above all else, I would have hired the right person.  You get someone who has installed networks for small businesses.  Not someone who does this on the side.  Not someone who's a college student majoring in computer science [unless of course they have indeed installed SBS boxes before], you get someone that knows SBS boxes.

You don't need someone who has worked in large enterprises, you need to have someone who has handled the issues of a small firm before.

Mr. Business owner?  You go to an appropriate professional when you get services done, right?  A doctor for medical needs.  A mechanic for car needs.  Why do you feel that 'anyone' can work on computers?

Don't change the way you set up your computers, change the way you hire your computer specialists.  You set up your network to be your defender not your infector.  You get someone who understands the needs of a small business.

You get a professional.

I got my backup wizard back

If you remember from the other day my backup wizard wasn't working ... well got it all fixed up.  Now I'm not going to tell you what was done to fix it for two reasons....

one... the chances that a real nicely maintained and well cared for SBS box is ever going to see what I did to my box is very very slim to none....this issue was on my old, beat up, beta bugged, so many betas that it permanently has “build number“ in the corner box.

for two... this isn't a fix that was found lightly.  A debugger had to be set up on my system to figure out what had gone wrong on it... needless to say it was a registry key that ..once gone.... kinda screwed a few things up.

The moral for this story is?

No amount of googling, newsgroup posting, searching would have solved this.  I could not have solved this.  This took someone to set up a debugger on this box to determine the underlying cause.  I needed Microsoft product support services on this.

Furthermore, this was an issue that was worth every penny of a support call.  If this had been a real box, this was one sick little puppy on our hands.  As it was I opened up the case because it was a stumper of a case.  Folks that say “I can't afford to call product support“ ... I'm sorry but if you business is like mine and it depends on technology, you can afford a reasonable amount of maintenance.  People will put gas, change the oil, get their car tuned at the mechanic but consider calling support something they don't do.

Well it's time you made sure you include Product support in your toolbag.  Notice as messed up as this little guy is we didn't reinstall it, we didn't flatten it.  Even as messed up as it was, it was not bad enough to force a reinstall.  Those who say “I come into installations not knowing the issues so I just reinstall“, take the issues one at a time.  Look in the event logs,  Google up the obvious errors, go to www.eventid.net for the harder ones, ask in the newsgroup.  But when you can tell from your googling that you are hitting a brick wall, you call.

 

Only 6

I was at yesterday's TS2 presentation and only 6 people in attendance were using WSUS.  Remember SBS 2003 in the R2 era will have WSUS inside the box.

Now I will still honestly tell you I vastly prefer Shavlik's push, patch, done versus WSUS's setup, tinker, approve, review reports....but gang... you need to download WSUS on your own systems and start playing with it now. 

To me WSUS isn't just a patching program, this is risk management for that firm.  And if you are not helping that firm deploy patches, service packs...why not?\

Want to stay safe and secure?  You patch.  To me it's just a natural part of the computing process.  And as long as I've built in the processes to ensure I have a easy way to recover on the rare remote chance something might occur, patching is not an issue.

Today in the newsgroup someone said “I have an old backup”...I'm sorry but with USB harddrives as cheap as they are, given that you can hang one off a shared drive off a workstation, you have NO excuse not to have a backup.  As easy as the SBS wizard is.....shame on you for not doing what you can to protect your business.  You have a responsibility to yourself, your family, your employees families this Christmas time to keep your business operational.

Patching and Backups.  Two EASY ways to keep yourself in business.

Man if you aren't a partner after this....

So I met Stephen today... Stephen Cracknell at the local TS2 presentation.  And at the end of the four hours, after all the offers, links, invitations to email him, to cc' him, to ensure we gave him feedback, I think the about the only thing he didn't do was invite us over to his house for Christmas Dinner.

You know you get out of things what you put into it.  And there's a lot of offerings out there [yes, many of these have US only or are US centric but yo... I live in the USA so cut me a little slack, but do check with your local Microsoft office and community]

So what did the TS2 presentation go over?

But do you get it that all of this stuff starts with YOU becoming a Microsoft partner and better yet YOU becoming a Small Business Specialist?

Ready to Learn

Okay if you are reading this you aren't the person I'm going to be ranting about.

You are here because you've gotten plugged in.  You've stepped up to the plate.  You are a person I would not mind sending a Small Business client to. 

And I apologize in advance to those of you this rant is intended for ...the ones that won't even been reading this.....but I think your technology customer deserves better.  You aren't listening enough.  You aren't taking the time to learn.  You aren't open for new ideas.

Have you noticed lately that many of you have been competing with a person that I'm not sure I would call an “IT Pro”?  A person that this is a side job, that it's not a career or a profession?  A person who idea it is that computers and servers are 'throwaway items'?  That in all the spin of “technology is easy” we've not realized that the only way for technology to get easier for the end user is to make it harder under the hood.  Yet there are folks I've seen posting in the newsgroup that I have to remember Grey's words to be more patient and kind to.  They come in with a “I know it all attitude” or they come in with a “I don't need to crack a book” attitude.

I don't mind the person entering the Small Business Marketplace that grabs a book, sets up a test network, reads a KB article...heck.. can attempt to Google up an answer.  I do mind the consultant who's not listening to their customer, who's not taking the time to practice a solution, or learn something new.  The one who sets up a box incorrectly and then complains that 'hasn't anyone ensured this works?“ when it's a misconfiguration that they've done to screw up the system.

I do mind the person who blindly says “Oh my customer doesn't need Exchange, will never use it“   Why do you say that?  Shared calendars?  They don't need that?

I do mind the person who blindly says “Oh my customer doesn't need Remote Web Workplace“.  Why do you say that?  Have you truly evaluated their needs?  Remote connectivity?  Heck we're leaving more and more of our workstations on 24/7 to remote back in.

I do mind the person who blindly says “Oh my customer doesnt' need...... fill in the blank....“ Why do you say that?  Aren't you making decisions based on what you think their needs are?  Are you thinking ahead enough?

I do mind the person doesn't set up a SBS box with the wizards and thinks they are smart enough to know better to set them up without the wizards.  Sure, understand what they are doing, but you'd have a hard time convincing me that installing all the parts of SBS, manually configuring everything, that you can set it up as dependably as the wizards.

As a customer, I would rather you not learn 100% on the job on your client.  Do your homework for some of these things, you know?  These days as cheap as Virtual Server is {$99), there's no reason that things like your first install of a SBS box should be in your client's office.  There's no reason that your first Swing migration should be a clients.... practice on your own network with a copy of Microsoft's new Virtual Server.

In fact, I'd strongly recommend that you grab a copy of Virtual Server.  You can practice all you want on a variety of things in a virtual setting and keep copies so that you don't screw up a real server.    How about virtual hands on labs?

The point is ... go into your client with confidence.  Yeah you don't need to know everything.... but have the attitude that you are open for learning, open for new ideas ....

...but then again... the people reading this post already are open for learning and new ideas aren't they? 

The Toy Server

The “toy server”. 

SBS has been called this by even some of my fellow MVPs as the “Toy Server”.  Yet under the hood is the same active directory, the same bits and code, the same parts as our big brother servers..... and as such we have the same abilities to do stuff as our big brothers.

Using Ntdsutil.exe to transfer or seize FSMO roles to a domain controller:
http://support.microsoft.com/kb/255504

See that KB?  It doesn't matter if you are SBS or Windows Server... that command works.  The only thing we cannot do on a SBS server is take any one of those roles off our SBS box.  All 5 roles must permanently stay on a SBS box.

  • Schema master - we only have one forest...heck barely a tree.. so no surprise there
  • Domain naming master - role in a forest [again, we're a tree] and this role is required to add or remove domains to or from a forest
  • RID master - and our SBS box is the one that needs  to hold the tools and updates to user accounts and computer passwords
  • PDC emulator - one for each domain [hello we only HAVE one domain]
  • Infrastructure master - again since we're the ones that do the forestprep/adprep in our wizard, we keep it on our box

Because our wizards/our SBS box does the dcpromo stuff, we don't see, don't understand what is going on under the hood.  Active directory in SBSland just works because it's been standardized for us.  Smarter folks than us have figured out how to set it up and standardize it. 

But here's the thing...because these roles must stay on the SBS box, because even as a “toy server“, we have all the glue, all the gunk, all the same things as our big brother servers we can easily replicate this information to another server in a process that big server land does all the time.

The funny thing about going through about 1/2 of a SwingMigration this weekend is that all my hanging around and unsuccessfully lurking in the Active Directory listserve is that other than that we don't have to WORRY about configuration or planning of active directory, it's the same gunk.

So far I've replicated the active directory to a temporary domain controller, disconnected the temp dc [important step as the edits and seizing you do next you want to make sure you are not replicating back to your still good and still running main server] and then seized the roles because the NTDSUTIL command first attempts to gracefully transfer and since you don't WANT to be taking the roles from the still running production network, this the utility says “Okay, whatever I'll just grab what I need“,

So those of you who know me, who know that I bought a kit and am doing this to move to a new server at home because it's so wheezy are probably wondering why in the world am I going through all of this for a home, 4 computer network?

Because of my sister's customized Disney desktop.  If I screw up her desktop one more time, or her Outlook settings, or her...anything on her machine, I'll probably be sleeping out in the garage.  It's that important that the burden in migration is on ME not on the end user [aka her].

So comparing a migration that I purposely did last year with a clean install to one using the FSMO copy roles aka the Swing Migration method?

I still would argue that migrations suck in general.

But as far as the attitude that some folks have that we're a “Toy Server”?  Not under the hood. Not where it counts.  It's the same active directory....and as such we can use the same tools as our big brothers to help us in migration, in disaster recovery, in all sorts of things.

If you are reading this blog from a Server

Like Happyfunboy says...

SHAME ON YOU!

Now I'm going to assume that you have a laptop running Windows 2003 and it's not your production, domain controller.....but if it is STOP DOING THAT!

You are introducing risks in your firm and you more than likely removed the Enhanced IE security that makes Windows 2003 server immune to the latest security advisory.

Dear Active Directory Migration people of Microsoft

So I just went through part of Jeff Middleton's process designed to move the domain roles from one server to another...something that big server land does a lot of but we don't down here.

I'm just putting you guys in AD on notice .... in a very public way....via this blog..... you gotta blonde this down before we're forced to upgrade to 64 bit.

I understand the process going on with the transfering of the FSMO roles and the process of moving the server to where the desktops don't even sense that a change has been made, but let's get real.  Not all of us SBS 2003 owners are going to want to migrate...what they have will be 'just fine'.  I'm sure it's like the consultant crowds are seeing a bit now.... those networks/owners where things are “just fine” are still on SBS 2000.  But for those of us that do... and for even folks that use a consultant..... many of the IT Pros out there have never done this before.  Heck even Brian Desmond ensures that people go through apprenticeship before letting folks loose. 

Let's review our current options for migration

  • Inplace - oooh yuck - leftover permissions and junk and running on possibly underpowered hardware  [and remember this one we can't do in 64 bit era]
  • ADMT - Microsoft mothership approved...but you rename the domain and rip everything out and your Exchange mailboxes size may grow [not quite the issue these days...but still]
  • Clean install - another rip out the domain glue
  • FSMO transfer role with drop in of Exchange store- [aka Swing] Joe may like command line ...but if this is going to go from only being done by IT Pros to being done by reasonably intelligent DIYers....sorry Joe but I think this could be made a lot easier with a good gloss of GUI on top.  And I'm not sure at all we'll be able to do that 'trick' of 'drop in the Exchange store' reconnect and we're done.

Get the idea that migration sucks in general?

I like nice pretty gui screens that ...yeah...while I might not read them .... are designed to keep me from being stupid [or hopefully try to be].  Server "kikibitzfinal" knows about 5 roles

Schema - CN=NTDS Settings,CN=KIKIBITZFINAL,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Kikibitzrtm,DC=local

Domain - CN=NTDS Settings,CN=KIKIBITZFINAL,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Kikibitzrtm,DC=local

PDC - CN=NTDS Settings,CN=KIKIBITZFINAL,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Kikibitzrtm,DC=local

RID - CN=NTDS Settings,CN=KIKIBITZFINAL,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Kikibitzrtm,DC=local

Infrastructure - CN=NTDS Settings,CN=KIKIBITZFINAL,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Kikibitzrtm,DC=local

 

And yeah I can drill into the Active Directory Users and Computers and check the status of the FSMO roles, and I can use ntdsutil to view them... but Mr. AD people?  Gotta get it easier than this....that's for sure.

So if I just bought it... why does it need updating?

So I bought Trend's PCCillian Internet Security 2006 ..and I downloaded it on DSL here at home so I wouldn't have to 'watch paint dry' also known as using dial up to download it.  So I burned it on a cdrom, took it over to Dad's computer, installed it, registered it, and sent it off to update it so as to make the XP sp2 security center to say it was up to date.

And it needed both an engine update and a dat file update that took an hour on dial up.

Uh... I just bought you from a web site.

The application is called 2006 version.

And the point of this was to make it easier for me to secure his system and yet it needed a major update before he was truly up to date.  I do have one more download, Office 2003 sp2 as that would take about 2 to 3 hours on his connection and 10 minutes on mine.  I just might have to violate the 'buy nothing day' to order DSL/Cable modem for him.  I mean it's not like don't mind being there for that long....but dial up .... is so ... well painful.

A little too much security

Eve of Thanksgiving.....everyone else has left for home or away for the 4 day weekend.....

I go to remove the backup device to take an offsite copy......

Use my keys to unlock the safe, swap out the drive, leaving the keys dangling in the safe....

I turn around...ensure the door to the server room will lock.......

.....  “click“  .....

..... and .....

....uh.....

where did I just leave the keys to unlock the office door, drive my car......

...... uh....

oh dear......hmmm.....

good thing the phone still works....

the blonde strikes again, doesn't she?

Dear postoffice of host.hawk.igs.net

Right now your admin did a stupid thing... they put a “please notify infected parties when I receive virus laden emails from someone that they need to have someone look at their mailserver” setting. 

But here's the thing.

It's a totally STUPID setting.

With all the spoofed emails today it's totally meaningless.  Man if you were not blocking zip files I'd be doing it right now because this Sober variant is changing so fast that trusting your antivirus will keep up with it is stupid.

So Mr. host.hawk.igs.net? 

Shut off the virus notifications ...they are meaningless.....they only add to the Sober variant problem.

Want to talk to a human?

This ... you gotta listen to....

NPR : Phone Guide Is a Real Customer Service:
http://www.npr.org/templates/story/story.php?storyId=5024153

Morning Edition, November 23, 2005 · Entrepreneur Paul English has produced a "must have" for the modern consumer. It's a guide to the customer service phone systems of major corporations. The big payoff? The guide tells you the quickest way to reach a human.

Paul's site... THIS is going on our firm's website/sharepoint -- http://www.paulenglish.com/ivr/

...so Microsoft called my Boss today....

And invited him to a morning presentation on Mobility, MOM, Security solutions and other ways to deploy end to end secure solutions for clients to make scalable and dependable infrastructure....blah blah blah blablah...... at about which time he turned the phone call over to me....and pretended to the lady on the phone that he didn't do anything with Computers and didn't even know how to turn them on just so he could get back to work.  He figured I might be interested so he turned her over to me... even still... as geeky as I am I said “uh can I get back to you on this invite?  So I went to go dig up what they were inviting him to ....and they had to have been reading from the wrong script is all I gotta say.....

'Join us at Microsoft Connections for a look at the tips and tricks you'll need to get the most out of your investment in Office 2003 and Windows XP.  We’ll highlight the ways you can use applications like Powerpoint, Publisher and Outlook more effectively to get your work done faster.  You’ll also learn how your PC running genuine Windows XP can make your environment a secure and productive one.  If you’re looking for a smarter way to communicate with your customers and grow those relationships, we’ll take an in-depth look at Outlook 2003 with Business Contact Manager.  You'll want to stick around to see how the brand new Small Business Accounting 2006 can make managing your business finances easier than ever.'  

 

That sounds a smidge more reasonable than scalable and dependable infrastructure.... but even still... the buzz words that were coming out of the description of the event.... I don't think even Steve Ballmer himself would have been enticed to attend that event.  I just sounded so plastic and not real world at all.  I reminded me of.... well let me put it this way there are some words I'd like banned at Microsoft presentations.....

 

  • Rich as in ...rich client experience.... rich user experience.....
  • Actionable ... action item....
  • Competency ....now in fairness this is a word that is annoying to me because of other baggage it has...not just Microsoft's
  • Deliverables.... is that even a real word? 
  • Leverage..... this one annoys me too...
  • and more here ....

Bottom line... even for your geeks....the buzz words get a bit much....

Yes the sky is falling

Incidents.org reports a “0-day” for Internet Explorer and while one should always use caution these days when surfing I think we're not fixing the real problem here.  This issue along with many others can be mitigated against if we run any software program more securely.

The issues is javascripting that can leave the attacker in the “rights of the user”.  Don't run as admin or tighten up your browser ...which everyone should do...

Run IE in high security or if you are surfing on unknown places use 'drop by rights', but let's stop yelling the sky is falling and instead, lets fix the real problem.  We're trusting all of our browsers too much and our workstations that run as admin are not protected enough.  Firewalls are not enough here.

Update:  Read Dana's blog and reports are on Mozilla browsers it's a Denial of Service.  I'm going back to waxed string and paper cups.

The competitive analysis

Something happened at a SBS partner group meeting .... let's just say one vendor who obviously helps host the event, helps to provide infrastructure to the event blew it.  They had a chance to step up to the plate of where we are in business today.  But ... actually let's put it straight on the table here... one person who was still living under the misguided view that their best way to compete was to exclude.  So they saw a topic about another operating system being presented at a Group meeting and asked for the advert to be pulled.

And you know what happened?  That one person represented all that is the dark side of marketing.  Remember when I said the other day “And the truth shall set you free?”... well marketing folks?  Salespeople?  Listen up.  You don't control the message anymore.  Oh you can try.  And you can use new technologies and channels to try and get my attention, but I have a lot more ways to get my information than from you these days.  So instead of opening up and having a meeting about how a server product can interoperate beautifully with many products, how in a small business you probably have Open source right under your nose [Opened up a Linksys?  Guess what OS is running it?  It's not windows]  

So instead of an honest, here's the facts and ways that every small firm has both of these in your firm and making the customer happy you end up causing a bit of ... well I wouldn't say upset...but let's just say you played right into the stereotype for sure.

Now, if I had been that Sales person/manager/whatever position it was that saw this meeting announcement, rather than calling someone and asking somone to ask to take it down, I would have instead turned the meeting around....

I would have pointed out the Interoperability between other platforms and SBS.  I would have pointed out that Mac's work quite nicely.  I would have pointed out that in public comparisons of SBS to alternative products they totally blow the stats.  [I'll do a call out on one of my personal favorite studies... shall I point out how they screwed up? ...

First..  they say Nitix is self configuring..that when new users are added that directory, email etc are set up.  That SBS has no comparison.  Dang... you mean I've been running that user wizard that sets up the email, user, etc and then I run the //servername/connectcomputer all this time and they don't do anything.  [obviously I'm not sure what they are comparing are apples and oranges but there are comparisons]

Next... they say Nitix is self protecting..that it sets up firewalls automatically and have the ability to evade attacks.  Dang..once again I guess that setting in Windows 2003 sp1 where the firewall is enabled until you run the connect to Internet wizard and only open up what you need doesn't work 'eh?  And that Data execution protection that blocks potential buffer overflows has no merit?

Then... they say it is self managing..that if you change the configuration of a service the affected subsystems are affected, again ... I'm just going from words...but the Connect to Internet wizard, the Change IP wizard has many of these features.

Then...self healing...built into the services of Windows are a lot of 'on fail take this action'.  So again lets compare honestly.

My favorite has to be the chart on page 11 where it states there is no firewall and no database in Small Business Server 2003 Standard.  Hello?  What exactly do you think the RRAS firewall and the MSDE is in that system?  I have both a firewall and a database at home.  No spam blocking?  Exchange IMF version 1 and now Verson 2.  Cost?  Free.  Redundant internet connectivity is only effective with an external router so as to not change out the DNS on that external connection.

And then last but not least...the major advantage Windows/SBS has over alternative platforms in the Small Biz community is the “Bus“ effect.  You know... the “Bus effect“ don't you?

The “if my IT pro person gets hit by a Bus I know that I can call up a Small Business Specialist and find a person that can help me out.  I don't want to be tied to one IT pro ... I want to ensure I have support.

That's the kind of comparison that “I“ would have done in this meeting.  Rock solid comparison that showed how Sharepoint has no competition.  That Sharepoint can be used by Macs. 

So Sales people?  This is how you compete.  You compete on the facts.  You invite your competition to the table.  And then to use a Happyfunboyism  .... you then KickAth!....  well you kick some you know what around anyway and you show that SBS and Linux and Mac and Windows Mobile and ...whatever you want can all work together.  It's all about picking the right solution for your small client...and if you build a better mousetrap .. you have nothing to worry about.

Off topic a bit...but have you noticed....

That sometimes words end up in your vocabulary that have meanings you didn't quite expect?

To me “the blog is horked“ means....well it's broken...not working...

Well ... reading the urban dictionary version...

Oh man.....

Yuck.

I mean we already have a problem with grammar and spelling already due to computers.  Who knew that a messed up blog description could be so.... well... gross? 

 

SBS Podcast Show - Intense about Disaster Recovery

Vladville - SBS Show:
http://www.vladville.com/sbsshow/2005/11/sbs-show-episode-4-recovering-sbs-in.html

The second part of the geek out podcast is now here.  The SBS Show this week is now online.

As HappyFunBoy said on IM...this one was pretty serious stuff because the two gentlemen being interviewed LIVED through disasters.  You want “been there, done that”, these guys are “been there, been through that”.

Blog is horking big time today

Many apologies, like most technology, the minute you threaten/plan new stuff the existing stuff starts failing... big time.  We apparently have major issues with the rss.aspx feed so we're getting 'server busy' about every hour on the hour.

In the process of moving to our own server rather than the co-hosted version so hang tight.

Isn't migrations fun?

Dell Optiplexes and the "cheesy" keyboard

Got one of those new Optiplexes from Dell ...the ones with the SATA drive and was surprised that they keyboard and mouse could only be USB.  I don't remember that the spec's saying that they were not going to be shipped with PS2 ports.  Yeah it's not a biggie...but it is. 

For one inform me that you are doing this, for two, why do you have to ship the cheesiest feeling USB keyboards as a result.  I'm probably going to buy a Wireless keyboard or something a bit beefier.  Yeah we got plenty of USB plugs but the point is.... the Optiplex's ....or at least this model just dropped a peg in my book.

Did I miss November?

Went to Target tonight... that's pronounced...Tar...shay you know.

Okay...can someone tell me what happened to the month of November?  Since when is Christmas right around the corner?  Did I miss Thanksgiving?  Is this December?

The Religious wars ....the technology wars

You know what gets tiring on some listserves that have a security focus?  The religious wars.  The “my software is better than your software” stuff.  The the whole “I don't want to pay for software” or the “we use open source software because it's free”.

Nothing in life is free, or so my Mother told me. 

Maybe I”m the weird one, I don't know...but the idea that I'm going to trust my business to “software by a volunteer committee” or something somone downloaded for free it just slightly freaks me out.  I have to stop and make a business risk decision regarding my choices.  I guess it's because I've been on volunteer committees and ...well.... I know how they work.  There are times I've been on committees that it is really excellent people and really the people that should be at the table are indeed at the table.  And then I've been on other less structured committees and ...well...the people that end up at the meeting table are just the people that showed up.  In my own City where I live where the people that show up day in and day out at the Council meetings, that give feedback regularly, that give input to the Council meeting...well that's their life.  That's all they do.  And they don't live in the real world enough to bring that view to the table.  They are just 'there'.  They just show up. 

The reality for today's business world is that we need a blend of tools.

Many argue that the active directory structure of Microsoft [especially in Windows 2003] hands down is better than other platforms to give a firm control.

Many argue that the desktop permission structure in other platforms, both Mac and Linux is more superior. [Well at least they are better at forcing their vendors to code appropriately anyway]

Arguably the platform with more forensic tools and distributions [KnoppixSTD and the like] is Linux.

As a business owner if I were picking an operating system based on “free“, you'd still see me at the checkout stand buying Novell's SuSe distribution.  Why?  Because I want an organization behind what I deploy.  I want support.  Don't get me wrong ...the community support of SBS is fabulous...but at the end of the day if there something amiss with my system, I want someone at the other end of a phone line that I can talk to.  I want someone who's made it their career and not a hobby to support the platform.  I want an operating system...no matter what the brand.....built by a person who has a vested interest in that platform from a career standpoint. 

Sometimes the decisions that come out of committees don't end up always the greatest decisions.  Look at our Congress for evidence of that [need I say more?].  The manuvering and deal making to get some of these decisions out the door is just crazy.  Yeah, big businesses can have just as much politics as Congress going on some times, but I still just have a lot warmer, fuzzier feeling about buying the things my business depends on. 

The funny thing I find when the “religious wars“ start up is NEITHER side knows enough about the other one to make reasonable arguments regarding their position worth a darn.  Windows NT is dead.  If you are still having to support NT, 98, 95 or ME I'm real sorry for you but stop using it as a benchmark. 

The next problem we admins have is not knowing.  It's getting to the point these days in the Server platform that we're getting like the Office platform.  “I want the OS to do this“..... “uh...it does that.“ 

I think some of this comes down to not taking the time to learn.  You know the guy who found that Sony Rootkit?  He wrote a book.  Windows Internals.  And what's the stereotype for the average IT person?  We don't read.  

I'll bet many of this blog have not read or know and I'll bet little of us out here use some of the following:

  • Software restriction policies - want to restrict what software users load up?
  • IPSec - want to ensure that only computers you want talk/connect/link up with the computers you want?
  • Group Policy - control desktops, what the user gets to use, lock down IE, control the firewall...
  • Windows 2003 Security guide - and if you are looking for a “click here and secure me“ ..this is a learn more about your system..the point is to this guide is that YOU have to understand your system to make the choices

Someone in a listserve today said they liked a certain vendors setup because it didn't rely on agents but rather forced you into better understanding the foundations of what you were setting up... ISA 2004, IIS, Windows 2003 server and XP sp2.  He said he prefered that over 'agent based' because it masked and made you not understand the foundations of the network you were setting up. 

It's funny isn't it?  Technology wars have parallels with human ones.  I think if all of us took a bit more time to learn, to understand, to find out more about the other guy, the other platform, the other technology, we'd stop these silly arguments and start fighting the real enemy

So my challenge for you this weekend is as follows.....Don't just read Mark Russinovich's blog about the Rootkit issue, download one of the free tools from the Sysinternals site.  Learn what it does.  Peek under the hood of the operating system.  Go read a book or two.  Listen to a podcast or two.  But lay down the weapons shall we?  Because as a small business owner, we don't necessarily care what you recommend, we just want you to listen to us, pick the solution that will best fit our needs and then we want you to know it.

Setting up and trusting

Gordo talks about how a misconfiguration of a Desktop search caused issues in a network.  Are you aware of the other issue that it may have?  On your Exchange?  The SBSPodcast guys talked about it last week and they pointed to the KB article

Exchange 2000 Server and Exchange Server 2003 performance may be affected when desktop search engine software is running on Outlook or other MAPI client computers:

I'm getting a bit annoyed about all these defaults that some of these programs are doing and when I ... okay..so I.ranted about how Thunderbird had automatically set itself up to update, I forgot about my MOST hated silent installers.

Adobe.

Tsee reminded me of the sneaky way when you download the Reader that if you don't uncheck the boxes you end up with the Yahoo toolbar.

Yup, I agree... hands down ...probably right behind Sony's DRM issue are installers like this.

You know what Robert, if Microsoft OR ANY of these software/webware vendors expect to earn my trust, how about in addition to a privacy policy that I can read ahead of time, how about a “my rights as a end user“ doctrine.  That you only install want I give you the right to install, you only do it in the manner in which I agree to, and above all else you stop taking me for granted.  If you think my small business clients are going to trust you or any software vendor these days the way you guys are treating us?  I'm sorry but the lack of respect that the online world gives to us out here..... Bill and Steve may be saying it's 'turn turn turn' time to go to the web, but until we “trust, trust, trust” the web, we ain't buying out here. 

Quite frankly .... we don't trust you.

You guys are going to have to earn it first.

Doesn't everyone get goosebumps when http://domain/connectcomputer works on a MCE?

So I used the “Banana hack” to get the domain bits back enabled under the hood on my Media Center Edition and just for grins I didn't manually install/join the domain.  I wanted to see if all of SBS's wizards would work.

There's nothing like a slight goosebump feeling when you realize that the SBS wizards all work like a champ.  http wack wack put your domain name in wack connectcomputer and [making sure you put that into your trusted zones in IE just to make it easier] and we got a domain joined MCE that ...the first thing it does is load up automagically the Outlook and Trend Antivirus. 

That folks [are you listening MCE people?] that's why I love a domain.  I want the server to be the handeroutter of this junk and I don't want to use the Trend PcCillian peer to peer stuff, I want to set this stuff up at the server and never worry about it again.  I want it to have the blue dot in the corner and be controlled by my server.  I don't do games, but I want the TV stuff.  And I want it joined to my active directory.  Next up to test out Remote Web Workplace [wonder how TV streams over that RWW connection, eh?]

So to all those folks who didn't want to buy a MCE edition for your firms to be the WOW factor because it wouldn't join a domain...

DO IT.

Join that domain.  Hang it off your SBS Server.  You don't need X box extenders in your conference rooms.  But hang it off your SBS.  Heck even WSUS has the MCE patches these days.

Kick that WOW factor in your office ten fold, get one of those plasma screens that look really cool and get a Media Center computer.

 

Inplace upgrades are just not my thing

Marcus posts about his inplace upgrade of SBS 2000 to 2003.

First off, I'd never recommend an inplace upgrade.  For one, it leaves behind permissions of both the 2000 and 2003 permissions.  Ick.  Messy.  Then there's a couple of problems I see here... he's been listening to marketing... he says SBS is for the less than 100 employee firm [try 75] that doesn't have a IT person on staff and wouldn't call PSS.

Well for one.. small firms outsource their IT to consultants.. ones that are SBS experts... and two.. heck I've called PSS and paid the fee for support.  Gladly. 

Since when do small firms not spend money for good solid support?  Not here.  We see value where it's needed and will pay for support. 

No Marcus what this really points out is not a problem with the SBS product per se [I hope you used the wizards?] but rather the fact that migration and upgrading platforms in Microsoft operating systems... well..it still sucks.  Why do you think there are folks still on the NT platforms.  Because migration isn't easy.  And I would not recommend that any firm who has an existing domain try to do it without someone who's done it before.  Active directory migrations are not easy.  And it's only going to get worse the next go round.  We're building up a lot of glue and not really giving any sized firm a really good migration...or for that matter... a disaster recovery story.

Sounds like Marcus missed that SBS does it's own self signed certs for Outlook over HTTP and inside the remote connection help file of Remote web workplace it has an exact how to, step by step instructions on how to set that up. 

Marcus, the best thing I can say is don't let this one off set your view of SBS.  You did a messy upgrade that even the pros don't like to do.

But I'm with you.... we need to get the story right for the future.

Try a clean installed SBS 2003 next time.  And all the wizards.  I think you'll come away with a different view.

Dear CAL people

To whom it may concern in the SKU and CAL department.  Yes, I know that we've asked before for less SKUs.  We've asked before for easier licensing, for Dell computers to be forced to stop saying XP Home operating systems are 'suitable for small businesses'.

There's one more thing I'd like.

I'd like another SKU.

Yes you heard me.  I want to have one more SKU for a SBS add on.

I want a Terminal Server bundle for SBS.  I want one SKU number to give to a small business owner or partner that would represent a Windows Server OS and 5 TS cals [and then add on more in increments of course].

Have you ever tried to explain to a normal human being that all they need is one Windows Server license, that the Server cals they say you don't need because you are a SBS server owner has nothing to do with the TS cals?

Even after reading this whitepaper, the normal human being still goes “huh“?

I talked to a normal human being today and it was obvious that he was confused by this document and just wanted a product SKU number that he could go to his vendor and say “I want that“.

So Microsoft CAL people?  Can I have one more SKU?  Please?

Taking action

91 percent of Canadian small businesses see Software piracy as unethical, says the headline.

Unfortunately around the world, there aren't enough Canadians, I guess.  Because there are enough firms, enough folks that are going to screw it up for the rest of us.

What am I talking about?  The Microsoft “Action Pack”.  It's a software kit for Microsoft partners to use and install and LEARN the software.  And it's reasonably priced.  Very reasonably priced.  To the point where there are some folks willing to nit pick their way through the verbage to justify it's use in their business.

Recently on a list serve I'm on, one of these 'oh yes, I deserve it' situations came out.  The firm argued that becaue they devised and deployed Microsoft solutions for their own employees and independent contractors that they qualified.  That's like saying “Gee, because I write Excel Macros in my firm I qualify for Action pack because I deploy solutions”.

Give me a break.  The intent, the goal of the Action pack is to get consultants, resellers, Vars, Vaps more confortable with the product to in turn, drive more sales.  It's not to provide cheap software for some customer who's willing to bend the rules.  In my book, unless you are in the new MPAN program for Accountants, if you are a firm and you have to HAND the box to someone to install it, then you don't comply with the rules of this offer.

So if you are one of those folks that are bending the rules to get Action pack?

Don't.

Stop it.

You'll screw it up for those of us who are legal.

So how long is that going to stay connected?

You know there's one thing that concern me about those new SATA drives that I am now getting in my office in our new computers..... those cables.  It just seems to me that they seem a heck of a lot flimsier than the old fashioned ones.  In fact on my home PC ....yeah, yeah .... the one I'm STILL building.... I've knocked off the data cable putting in cards a couple of times now.

And I think I need to start carrying spare SATA parts and certainly need to get a SATA ready USB enclosure.  One of the gang on the malware lists said that she was delayed a bit tracking down cables and hardware so she could work on an infested drive.

My normal trick of moving data from one computer to the other and then hanging the old drive off the new system isn't going to work this time without additional cables and connections.  It has no IDE cables inside the Dell Optiplex we just got. 

So how many spare parts do you have lying around?

 

How much of a control freak are you?

Dan [name changed to protect the innocent and the fact that I'm going to rag on his boss in this blog post] in the mailbag today asked a question about 'hosted' Exchange.  He said that his boss wanted him to look into hosted Exchange [asp] as an alternative to moving their MX records to their SBS box.  The problem is that the boss did not want to leave the server on 24/7.  Dan said that he only agreed because he didn't have the environment to run a high availability server.

Dan?  Boss of Dan? Come over here... see my network? Do you see my older 'member' server?  It used to be my main SBS box but now it's the TS/member server box.  That server is 5, maybe 6 years old... now I personally think the sweet spot of server hardware is about 3 to 4. You know what happened to me today?  Another drive on the RAID 5 array on that old server dropped off.  You know how much down time that affected me?  About 45 minutes.  During my lunch hour no less.  And about 15 of that 45 minutes was on hold with Adaptec [delay due to the Hurricane because all calls are going through Millpitas and not shared between California and Florida] because the drive had to be zapped off again [it did this the last time I lost a drive on that older server about a year ago and I couldn't remember the commands] and then brought back into the array as a hot spare and then it slid into the location where it's supposed to be and drive 0,1 in the three drive array.  And other than the screaming like a banshee sound that it makes while one of the three drives has dropped off the face of the earth, the server is still running, still serving, still doing it's thing.  In fact, many folks say that you want to leave your servers up and running, that it's the spinning up and spinning down that does more wear and tear on them.

I keep a spare harddrive [in fact now need to order a new one] just so I can slide a new one in with no issues.  High availability to a firm doesn't mean a datacenter.  It means just reasonably nice hardware.  Server hardware.  It's certainly not the overgrown desktop hardware that is running the DELL OEM I bought for testing purposes. [It is literally the absolute CHEAPEST model I could get and it's basically an overgrown desktop with one drive].

It means ...that even if you DO go the route of some of your parts being 'hosted', I would argue that you STILL want true Server class hardware.  Now these days, I'm not convinced it's SCSI all the way... I think it can be SATA as well.  But there's a RAID in there so you could drop a thing or two along the way like I did during lunch and it would not matter one bit.

Next reason why you want your SBS box on 24/7.... remote connectivity.  There's many a time I go off to a conference and go 'oh shoot I forgot that' and can remote back into the office 24 hours a day, 7 days a week. Remote Web Workplace 'is' the killer app of SBS. 

Next reason why you want your SBS box on 24/7.... patch management.  I have and do scan and patch my network in my jammies from home.  Now then, if you turn your system off...how can you do that?

So ...okay... next... about that Boss not wanting to point the MX records to the SBS box... okay so the Gang at the SBS podcast will hate me for this but here comes....come closer.... you know about that POP connector that is supposed to be a transition tool?  The one that you are only supposed to use temporarily?  Well like they said in one of their podcasts... folks have been transitioning on that sucker since SBS 4.0.  I use the pop connector at home all the time. 

And what about the MX records and all that.... you know that with a service like TZO.com you can have a backup MX record so that if 'IF” your SBS box goes down the email will stay in your backup MX holder and then forward it again when it's back up.

Okay ..so like WHEN would you want hosted Exchange?  I think you'd want hosted Exchange ...and hosted SBS for that matter.... if you are

  • Not a control freak like I am
  • Live in an area that you need to be nimble and move out of harm's way

I think [hint hint] Vlad in his blog need to post about advantages/disadvantages of hosted Exchange and ways to connect [VPN, RPC over HTTPS [I vote that one even with real SBS]. and whether you should stop Exchange to free up resources [remembering of course that again, if you have a real server, it can handle this stuff just fine].  For me I'm just waaaaayyyy too much of a control freak to handing Exchange not being in my office under my control.

This nimbleness I know came in handy for one of Jeff Middleton's tech support clients.  He helped them backup their data and they sent it off to the software vendor that in addition to having a PC based application also had an ASP version.  This allowed them to quickly get back online.

So Dan's boss?  Leave that server turned on please?  You don't need to turn it off and night and reboot in the morning.  This is a server, not a workstation.  Heck we're even leaving workstations on 24/7.  And bad guys can break into you via the Internet just as effectively if you are stupid on setting that box up during the day as well as during the night.  While turning a machine off and encasing it in cement, dropping it to the bottom of the ocean probably does increase security of your system greatly, it kinda doesn't help much to boost productivity.

Leave it on, Mr. Boss.

Okay who searches while they IM people?

I'm just taking an unofficial survey of how many folks have

  • Accidentally typed in an Adminstrative password in an IM window [after it grabs the screen] and sent it off to a friend [hopefully friend anyway]?
  • Accidentally hit the search button instead of send in MSN 7?
  • Accidentally invited half of your entire IM listing to a chat?  [and in my case that's a BIG list]
  • Accidentally typed in the conversation of one chat into the window of another causing the person in conversation A to wonder where you went and the person in conversation B to wonder what the heck you are talking about?

...and other follys of IM?

...and exactly WHO searches and IMs with someone at the same time anyway?

.... uh... I don't know about you... but...uh... googling... it's kinda a private solitary thing... ya know?  I search alone.  I don't get this 'buddy search thing'. I mean I'm into sharing things with the community ...but searching?

Why doesn't Microsoft say that?

“....why doesn't Microsoft say that?“

It was a question I was asked earlier this week in response to an email I sent to a journalist. 

...and you know what... I really don't know why someone from Microsoft in their PR department didn't just say what happened.  The truth.  But for some reason the truth, the facts didn't get out to the public.

And the sad thing is, the truth would have made the public more secure, would get rid of the fears, the doubts.  But because that message didn't get said, because the words weren't said, I think Security was affected.

Security is defined as Freedom from doubt, anxiety, or fear; confidence.  .

And in the WindowsUpdate newsgroups, some people had a lot of questions about a 'buggy” patch.  Even on non affected Windows XP machines.  Even one of my fellow MVPs emailed and asked if anyone had any links to information about a “buggy” patch.

But here's the thing that is amazing.... you see the patch wasn't buggy at all.  The bad effects of this patch that the press talked about was mostly as a result of Administrators who had made security settings, tightening to registry keys, called 'hardening'.  But here's the thing.... these settings are actually not recommended by Microsoft at all.  They really are not supported.  So anyone following these guidelines, knew, they understood that they had responsibility for their network. They knew they would need to test. 

So I can't understand why, when the press starting writing their stories about the effects of this patch why someone from Microsoft didn't just say the truth.  That it was the people chosing to set up their network this way that got the most affected.  Now I'm not saying that people that were not running Windows 2000 and did not adjust permissions didn't have patch issues, but I think all of their specifc issues got passed over by the headlines regarding this so-called 'buggy patch'. We lost the real story of what was happening with this patch because of the overwhelming press that got stuck on the issues with the patch that were inflicted by the Administrators themselves.

And all of this confusion could be done away with if the Public Relations of a company just said the truth of what happened.  Truth didn't get said.  People got confusion instead.

Sometimes I don't understand the world of marketing and Public relations.  In fact, sometimes when I'm faced with a hard slick sell, it turns me off.  Big time.  In fact, give me truth.  Tell me the warts of something, because if you don't I'll find them in the product.  And believe me, if you didn't tell me about the truth of a product, and I find out about it after I've bought that product, I'll feel like you didn't tell me the truth and never forget that.

I was talking today with another guy about a software product I have at my office.  Bread and butter, line of business application.  One that I moved from one to another a few years ago, a competing product.  When I was talking about the issues I had with it, and comparing to a competitive product, the gentlemen and I that were discussing these products were commenting that we couldn't beleive that both products hadn't done better things for the customer.  That they had been in the marketplace this long and neither one was perfect.  Both had software 'warts'. And if I had known about the software warts of each platform, rather than just getting the salesman 'speel', I think I would make the same decision I made, but I wouldn't feel ... well... slightly abused by the 'speel' I got from the Salesman assuring me the software was perfect.  But because no customer was in the role I was, truly comparing the two, no one had recently made the migration, I didn't get the real facts.  I got the slick ads. 

So here I am, in a software program that works, but isn't perfect.  And if the salesman had been more honest with me I wouldn't feel the way I do now.  “Sold“ to.  Owner of a product that doesn't quite work like it was advertised.

Trust is defined as Firm reliance on the integrity, ability, or character of a person or thing.

I don't understand why firms don't understand that the best way to build trust with me and my business is to be honest. If you want me to be a long term customer, don't sell to me, be honest with me.  I moved from that other Line of Business application because they kept promising and not delivering.  And jumped from one that kept under deliverying to another software that kept pushing back a release date to the point where the ship date missed an entire tax season.  We were told one thing, when the truth was another.  And while the salemen were on the phone lines assuring me that the product was shipping, when I called tech support on this product, they said “oh it won't ship until May“.

Why do we accept what we do from Salesmen?  Why do we accept the slick ads?  I've chatted with many a folk who buy a software product only to find that once they peel back the onion layers and the software doesn't work as advertised they feel like a bit abused.   Why is it that the human folly is that we need Madison Avenue to convince us to buy things we don't need?  Isn't the obvious example of this perfume?  It's fragrant, colored water that more is spent to package it, advertise it, than it does for the ingredients for the product itself.

Sorry if I'm rambling a bit tonight.  But several conversations this week have led to this rambling blog post.  Today at lunch with a good friend, the two of us were chatting that we're not sure the press or the public relations of a firm control the message anymore.  We agreed that in this day and age of blogs, newsgroups, communities and word of mouth, even the three major networks didn't control the message anymore.  All it takes is someone who will never forget a bad experience and will tell this in a public online forum such as this and there goes a dent in all that good public relations you've built up. 

I don't know, maybe I“m being naive here, but I think being honest and truthful goes a long way.  I thnk it builds the trust.  I'm not convinced we need all the slick packaging that we end up getting.  I think being honest to the business owner... building that trust... I think that's a stronger, more long term sale.  You might not see the immediate “Madison Avenue” benefit, but I think that honesty will reap a longer term relationship. 

A funny thing happened the other day to showcase how a bit of honesty changed a conversation. I was hanging out in Andy Goodman's MCP chat the other day and was using my usual online alias and at one point in time started chatting with a poster arguing strongly about the advantages of SBS 2003 over SBS 2000.  I said that it was obvious in the recent patches where Windows 2003 was not a readily vulnerable as Windows 2000 proved that it was time to get off that platform.  And at one point in time when the poster was challenging me, he said “what have you drunk too much Microsoft Koolaid or something?“ and it took me aback a bit.  There are times people think I choose Security too much.  But here's the funny thing, once I had 'outted' myself and told the chatter exactly who I was, he recognized me from the blog and his attitude changed.  He was listening to me, not as a “koolaid seller“ but as someone who had earned ...well hopefully anyway... a little respect.   I had changed the relationship by being honest with him of who I was. 

And speaking of chosing Security over Business is that I don't think we choose Security enough over business needs.  Because at the end of the day John Q. Business Owner doesn't want things blocking him from doing his job, his business.  He will find ways to go around that barrier if it stops him from doing his job.  So security better just work.  And it better be honest.  And the technology salesman shouldn't 'spin' the product promising that the product will do things it won't do.  And we'd better not have to buy more 'things' to get the products to work the way they are advertised in the slick magazine ads. 

Because if you aren't truthful with him, he'll remember.   

If you aren't truthful with me, I'll find out and not forget either.

...so coming back ...hopefully full circle.... to this rambling post of mind tonight that you've indulged me in tonight [well not that you had any choice in the matter... I was in a mood],

Say Micosoft?  How about just being honest and saying that you had a bunch of “Buggy Admins“ who forgot that at the end of the day the responsibility for their network is theirs, not yours.  And if they chose to move away from a supported position, then it was their job to test that patch.

At the end of the day, I'm the one who's in charge of my network...not Microsoft.

The buck stops here.

A post for The "~'s" and the "V's" and all the rest.

There's a person I'm going to refer to as The “~”.  Now while I'm going to speak specifically about this one person... in reality he represents a type of a person. 

His job is to fix things.  Find things.  Get things to break.  Figure things out.  Analyze things.  Thus, he's the type of guy that would be installing Exchange 2003 Service pack 2 today.  Now.  In fact, I'm surprised he wasn't up at midnight installing it on some box somewhere.  And in fact if things go smoothly ... he might be a bit disappointed.  He and those like him actually like breaking things.   Because then they learn more about the thing they are breaking.

There's another type of person I'm going to blog about.  This person is the IT Pro.  The Consultant.  I'm going to call him The “V's“.  Now he's a bit like The “~”, but a smidge different.  You see he wants to figure things out, but he wants to ensure once he's installed something, understands it, it's reproducable in a solid manner to his clientele.  So he'll install Exchange 2003 sp2.  Document it.  And quite quickly in fact, but he's probably going to go through the dry run steps of a 'best practice for deploying Service Packs” checklist.

He'll make sure he's read the documentation, he'll make sure he's backed up the Exchange Store.  He'll understand that for his clients that depend on email, Service packs deployments on Exchange are upgrading a Jet database.  Thus he'll make sure he builds in a rollback strategy.  But he's going to to a dry run on a test machine and recreate as best as he can the steps and checklists he'll use for deploying this Service Pack.  He's then probably going to watch that box for a few days and monitor the log files and just make sure everything is as it should be.  And then he'll start rolling it out.  Mainly because his clientele are near the max of those 16 gig limits right now and they are busting at the seams.  And he'll read the documentation on how the default store goes up to 18 gigs but above that needs a manual registry adjustment.

He's also probably going to “triage“ this service pack and only deploy it to those clients who are near that 16 gig database limit.  The ones that need that registry edit.  You see he's probably already in the process of deploying SBS sp1 and he'll want to give is clients a bit of a breather on that for a bit before fully rolling this one out.

Then there's me.  And it's this personal view from my Patch Deployment Central.  It's this view that I post to this blog.  My role in my office is to not introduce risk.  My role is risk mitigator.  So I'm not going to be the one downloading the patch at midnight installing this on my box.  I'm waiting.  I'm going to first install it on my home server, again following the guidance of The “V's”, and I'm going to watch the log files.  I'm going to then pick a date in my office that it's a good time for me to deploy this.  In my office my traditional time for deployment is Friday night, after the office closes at 5 p.m.  I'm going to ensure I have a rollback plan.

And what if you don't have a home server to test this on?  What if you are a DIY admin and you only have your one SBS box?  Well, you can be rest assured of the following....

  • The “~'s“ have done it and are running just fine [well it will be as soon as he installs SBS]
  • The “V's“ have done it and are running just fine
  • The patch has been certified for SBS boxes by Mothership Redmond and Los Colinas [there is no need to wait for a SBS only service pack]
  • and soon I'll be doing it here

In my earlier post I talked about how one shouldn't patch at lunchtime.  There's a running joke that we are so confident in patching that we'll just blindly install patches before testing.  If you don't have a test machine, but only a real production one, just keep this in mind... follow the recommendations.  Have a backup.  Remember you have to have SBS sp1 on the box “before” applying this Service pack.  And honestly you really should consider a Service Pack like a near new operating system.  You don't have to be first.  You can wait for all those “~'s” and “V's”.      

Need some guidelines and ideas for Patch [and a bit of Service pack] testing?  Here's some things I've gathered up along the way...

  • Identify the operating system subject to testing.
  • Identify the service pack level.
  • Identify the hotfixes installed on your systems (if in addition to security fixes).
  • Identify critical third party applications.
  • Identify third party applications that have had patching historically.
  • Identify those files used in patches that may have causes issues in the past. Are the included in this current patch? Assign testing resources appropriately.
  • Study the bulletin to determine if you can uninstall the patch. If not, determine if additional resources for testing or imaging need to be in place before approving the patch.
  • Test the installation of the patch both manually and via your automated patch technology. Can you uninstall the patch using add/remove program or your patch tool?
  • Review the processes of your line of business applications. Are they performing as expected? Attempt to replicate a production environment using imaged data. Having an exact image provides the best testing bed.
  • Set up performance and monitoring tools to review your testing machines43 such as PerfMon, tools from Sysinternals and review all log files.
  • Confirm the installation of the patches via registry review or other means.
  • (OPTIONAL) Confirm the effectiveness of the patch using testing code.
  • Follow any additional procedures your situation requires.
  • Approve the patch for release.
  • PREPARE BACKUPS. [Oh yeah did I say prepare backups?]

The Infraguard Technology Risk checklist also includes the following:

  • When applying a patch to any system vulnerability, verify the integrity of, and test for the proper functioning of the patch
  • Verify that the patch will not negatively affect or alter other system configurations
  • Test patches on test beds before being released into the network
  • Backup your system before applying patches
  • Conduct another vulnerability test after you apply a patch
  • Keep a log file of any system changes and updates
  • Prioritize patches prioritized
  • Disseminate patch update information among the organization's local systems administrators Add timetables to patch potential vulnerabilities
  • Require that external partners deploy all non-critical patches within 30 days
  • Require that external partners deploy critical patches to servers and clients within 48 hours

So if you are one of “The “~'s“, go ahead, deploy it.  The rest of us mere mortals will type up a checklist and at least make sure we have a backup in place.

 

Exchange Service Pack Destroys Reading Ability

Yes, the thing I was ranting about earlier this week..the sensationalist headline I'm using here for a reason.

Got ya to read this blog post didn't I?  Didn't I?

It's apparently obvious to me that the sight of a new software patch destroys all ability for folks to plan and read documentation.  Marina and Mariette have said time and time again [even to me when I forget] that we need to SLOW DOWN and READ.

Already getting folks pinging the blog after... AFTER... apply the patch and folks, I don't know about you but I cannot imagine that you have

  • Read the release notes
  • Read Vlad's blog
  • Backed up your Exchange store SEPARATELY from the normal backup [In fact stick it someplace special on a harddrive somwhere just for this purpose]
  • Anticipate that once again, the Exchange patch, since it's coming out from the “normal“ Exchange folks would once again flip our OWA login from just plain user to domain\user [or so one poster to the blog says happens... you mileage may vary ... I haven't tried it so you early adopters will have to see, word is from the gang that the User name only stays and works -- it's just the OWA page that 'says' Domain\user name.  It will still work fine with just “User“.  Nick says the SBS gang fixed the underlying SBSized plumbing so Exchange won't stomp on us anymore after you apply SBS 2003 sp1]

IMHO, either ... give up fixing that stupid domain/user thingy... train your users to go through RWW and never use straight OWA..... or try applying the previous fix/up patch that did the trick with Exchange 2003 sp1 when it did that to us.  Honestly I think we need to just give up our SBS customizations if Exchange or any other patch is going to stomp on them all the time.  When I picked my domain name, I picked it nice and small.  To me, I'd rather stay with a 'standardization' of patching.  So if Exchange is going to constantly reset that .. I say... fine .. let's stop fighting it.  Flip it to domain\user and we won't have to worry about fixing it anymore.  It's honestly an end user education issue anyway.  I'm starting to be a big fan of patch standardization.

So, can we read first please? 

Sometimes it 'is' the last thing you try

So I have the big hunking HP Pavillion Harmon Kardon has the built in 10 key on the keyboard that we beancounters drool about, weighs about 9 pounds dripping wet, monster in for a checkup, installing an update to the Trend antivirus [and just realized this doesn't have Microsoft antispyware, shame on me] and what not and for the last two days I've been off and on trying to troubleshoot a problem with it.

You see about every 30 seconds on both the wired and the wireless connections I was trying it would fall 'off' the connection.  I always enable the network connection icon down in the system tray and I would see it drop the connection and then reenable the connection. 

I'm thinking viruses?  Spyware?  Nic drivers?  and trying to troubleshoot a device when it's falling off the Internet every 30 seconds isn't fun, you have to google msnsearch on another machine, find the drivers or software patches you need and then copy them over.  Needless to say I was just about stumped and about to call in the hardware gurus.  And flat out honestly, I'm a software gal.

So one last ditch effort I boot into safe mode to see if I can see if the nic drivers are acting up under safe mode and realize you can't enable the network icons in the system tray in safe mode.  So I reboot into normal windows and ...for whatever reason that escapes me now.... I hover over the far right icon which is the 2Wire network connection monitor for the Home DSL modem that this monster laptop normally connects to.  And again, maybe it was annoyance with icons or something...but I made the monitoring software temporarily exit the program.

Two days.  I've been scratching my head off and on for two days trying to figure out why this has been dropping off the wireless and the wired network at the office and it was the fact that the 2Wire wasn't able to phone home to it's DSL modem was why this laptop kept dropping off the Internet.

It is always the last thing you try isn't it?

Now given that we're about to insert in a Linksys or equivalent at home [where this monster normally parks itself] so that the DSL can be shared out with the Granddaughter on another computer [and not this one that I'm typing this blog post on to confirm with myself that the connection is solid], so that she doesn't mess with this clean, pristine laptop, I'll probably have to permanently disable that monitoring software of dubious reliability.

I'll also have to figure out the best way to protect Granddaughter.  I'll see what I can do with restricted user mode and the fact that when she visits...she wants to play games. And unfortunately game writers have yet to fully embrace the “Secure by Design, Secure by Default, Secure by Deployment” mantra.

Yup, sure enough... rock solid connection.  So exactly again ...why do I need a network connection monitoring program that 'causes' network connectivity issues when it's not connected to what it's wanting to be connected to?

Yeah, there's probably a group policy setting that I should go find for this - the temp file issue

Annoyance 101 - Temp files.

When you receive an email and there's a file attached... why is it that the default location for the files is some buried obscure location on your hardrive?

I mean it's an attachment, right?  Why can't I have a “My Attachments” folder rather than some Temp file location?  I mean Temp file to me means that it's temporary.  Yeah you are supposed to do a 'save as' and get it out of there, and from a security standpoint it probably would be wise if you clean that out you know...but in reality... how many times in a small firm does stuff get stuck in the temp folder and we never realize where it is?

Yeah we can do Desktop search and all that to find it, but wouldn't it be better if something popped up when we went ot save and said “you do realize where this is being saved, right?”

So?  How many times have you found stuff of clients in temp folders?  Is it an education problem?  Or should we be adjusting where our email programs dump those temp files? 

I say ..fix the program.  What about you?

Clean Slate

So when do you give a vendor or a person a clean slate to start over.

A new page?  Start from square one.

I was thinking about this tonight in regards to a couple of conversations and sometimes I wonder if sometimes...just sometimes...we let the word of mouth... the Church of the Customer not let us make up our own minds.  Now don't get me wrong.  Word of mouth ...the been there and done that can be the greatest piece of information and knowledge sharing you can get, but isn't there sometimes when evaluating something it might be better coming into it with an open mind from the beginning and then letting the facts let you come to your own conclusion?

A fresh start; another chance after wiping out old offenses or debts. This idiom often appears as wipe the slate clean. For example, Henry's boss assured him that the matter was finished and he could start with a clean slate, or He wished he could wipe the slate clean, but it was too late to salvage the relationship. This expression alludes to the slate boards on which school work or tavern bills were recorded in easily wiped-off chalk. Since 1850 or so the term has been used figuratively, and it has long outlived the practice of writing on slate.

I still remember going to a movie that the critics loved.  Their 'word of mouth' regarding that movie meant that I had certain expectations in mind.  I sat in the movie theater ...waiting for the movie to get to that part that the critics said was wonderful.  And I sat.  And sat.   And sat.  And soon the end credits rolled.  And their word of mouth, set my expectations so badly that ...to this day... I can tell you exactly the movie that I sat through thinking.... did I see the same movie they did?  Did I wander into the wrong theater? 

Don't get me wrong... I think the “been there and done that” and “word of mouth” is valuable, but sometimes...just sometimes... you might want to do something I call the “To kill a mockingbird” effect.  Walk across the street.  Turn around.  Now look at the view from the other angle.  That word of mouth you are getting is just that... a view.  And maybe...just maybe..... making up your own mind ...without expectations might also be of use.  Maybe the view is just what happened to them.  A one-off.  Maybe the view is that from a long time ago [like me and that movie]

I will never forget a movie that horribly set my expectations. 

So tomorrow in my part of the world in the end of the week and Sunday to me, is the beginning of the new week.  It's the day we get to 'start over'.  Now I'm not saying I'll be watching that movie next week.... but just maybe I'll start Sunday morning with a clean slate and pick a new movie to watch and decide what I think about it.

How about you?  How about you pick something or someone and start off next week with a clean slate?  A new view.  Another chance. 

And this time... make up your own mind from what you expect...not from what others have set for you.

Why I ask for "the exact error message"

Coworker - my computer at home isn't working? Got any ideas?  It won't boot?

Me - what's the error message?

Coworker - it's a long one.

Me - yes, but what is it?

Coworker - I have to write it down?

Me - yes, is it a BSOD - a blue screen of death?

Coworker - no.

Me - okay so when it happens, can you write down 'enough' of the message you are seeing...otherwise I can't search for an answer.

So he brings in the handwritten note of the message.  The primary part of it being the “UNMOUNTABLE_BOOT_VOLUME”  and of course, within seconds we have our answer.  Yeah, it's not a blue screen...uh huh... yeah.

I see so many times folks will say “my computer just bugchecked” what does this mean?  What's this error code?  And yeah, I can google msnsearch and point you to the Debugger Tools with the help file and all that ... and I might be able to give you a hint or a clue ....but you know what?  There's an easier way.  Support.  It's called support.  An for you guys in the partner program you have even more options for support.  And all it takes is one trained person to review that file and more often than not they can tell you exactly why that machine errored out and where to look for a fix [if it's hardware driver based] or give you a hotfix.

Now I'm not saying that you are guaranteed a free call or anything ...but honestly... isn't your firm worth the $245 call?  And depending on the issues, there have been times that I've ended up being 'comp'd' that call.

Getting the right help gets you back in business quickly.

Why aren't you taking advantage of the resources you have access to?

Getting there

“Tech for Non Profits” blogs talks about getting to SBS 2003 and I agree with blog post one.... that moving from a domain to another domain in a pain... I guess he didn't know about our swing solution at sbsmigration.com...but there's a couple of things I think need a little clarity in post number 2.

First off... DON”T give up on centralized virus management... excuse me.... you want the dat file coming into the server and autodeployed.  Get the corp editions of that for that purpose...not the yellow box standalones.

Next, the firewall can be adjusted by you at the server...or you can edit the policy to let the workstations manage the firewall [see here for the policy to be adjusted]

Next...get off of pop email...please?  You do realize that you can't use Exchange IMF or any of the cool server spam tools.  And just because you are small doesn't mean you can't do full smtp email with tzo.com forwarding your email [I've blogged about this before...I'm not going to bore the regular readers with the details...but they've probably heard this rant before anyway]

Next you don't have to have local admins on the workstations... once the install of the programs are deployed...shut those workstations back to standard user.  Easy.  I mean, I don't know about you but I don't redeploy Outlook 2003 sp1 every day.

Larry... migration from a domain to another domain isn't easy.  From peer to peer is the easiest method and the /connectcomputer will migrate the settings of the profiles. 

Yes, DNS is sweeter when you let SBS do it's thing...but that's AD.  I love the AD glue and so will you.

Part of the problem is there are many ways to set up networks.

...and Larry?  What updates?  as the SQL one normally doesn't like to install unless you've run the monitoring wizard. 

I'm tired of following best practices

This all started on the WSUS patch management listserve where someone said “Oh you MUST install SQL on it's own box” and started us talking about how one firm, one person's 'best practice' didn't always fit for another firm.

I'm tired of big server land 'best practices' to be used to compare to my small network.  I mean...show me a big firm and I don't think they are any better than I am. 

But one thing that I think is for sure is that you can't use big server world's best practices to set “MY” best practices.  They don't compare.

Let's see some of the myths of best practices and see if they fly in my network....

  • Best practice number one - Never put IIS inside your network.  Okay if we follow this lovely one, we can't run WSUS or other such tools that actually help me to be more secure.  Folks that say this one are back in the IIS 4.0 days.  IIS 6.0 has proven to be solid. 
  • Best practice number two - always put SQL on it's own server.  Well in SBSland, the first thing we will do is violate our EULA.  Does it freak out the gurus to have all our services on one box?  Oh sure.  But excuse me?  Look around at what is happening in the virtual server world.  They just announced some changes to Virtual licensing going forward.  Does anyone else but me see that 4 servers on one physical server sounds kinda like what we do in SBSland?  We just don't have the fences between the children on the playground is all.
  • Best practice number three - Always put a firewall on an external device.  The problem with this one is that invariably the issues with firewalls is how they are set up and not necessarily where they are positioned in our space of SBAland.  Have you left the default password on it?  I also find that I patch the ISA one a heck of a lot more regularly and the monitoring report [even though I'm not 100% fond of it], makes me view it more.  A Linksys on the edge just doesn't give me the 'in your face' information I need.

so ...what other best practices do you think ...well....just aren't necessarily best?

Man ...where do I get all this junk on my workstation?

I upgraded my computer yesterday...well...not exactly... I did a Drive image of my existing disk [120 gigs] over to a 300 gigs [which doesn't say 300 on the “My computer” by the way, because I was nearly out of room and the poor drive was file swapping like crazy to keep up with me.  So I imaged the old one to the new one and then moved the new one [putting the necessary jumper block in place] to be able to boot off the new disk flawlessly.

Hands down this is the easiest way to migrate...but at some point in time, I'll want to migrate cleanly and it's still a pain....Which reminds me I need to grab a TV tuner card for my workstation at home [the new one I havent' migrated to yet] so I can throw MCE on it.

Dell just called about the workstation I ordered....for FREE they can upgrade that 80 gig harddrive to 160 gigs.... okay...whatever... 160 gigs of stuff that will have to be moved in the future... fine.....

 

 

The vendor issue

Earlier today, David Litchfield wrote an open letter to Oracle users recommending that they get on the phone, send an email and demand better security response and an improvement in quality of their security patches.  Cesar on the SecureFocus list echo'd Mr. Litchfield's comments as well [you can read David's comments below Cesar's in the post].  Now most of us SBSers don't run Oracle, but as Mr. Litchfield points out.... our data is probably on such a database somewhere.

Dr. Jesper Johansson posts about a similar issue... vendor support of patches.  When a vendor puts us at risk like this .... it's unacceptable. 

And of course my favorite software that forces me to make insecure choices... Quickbooks which demands local admin rights.

Vendors know that they have us in a bind...upgrading and migrating to a new software is a pain in the rear.  But at the same time we HAVE to start waking up to the insecurities these vendors are placing at our doorsteps.  The decisions they are making on our behalf.  The risks they are forcing us to accept.

Mr. CEO... how about you lose $1 of your salary for every time you put my personal data at risk?  Maybe if it hurt you personally in the pocket book more you'd care and force your employees to read Secure Coding and the Deadly sins of Software

I have.

...and I don't even code anything....

Dell ... if I'm a corporation ...I'm not buying XP HOMES!!!

If Dell Optiplex “Means Business” as the headline reads...why then as I am spec'ing out a new desktop for the office does it DEFAULT... DEFAULT mind you to XP Home.  Dell WHY are you shoving XP HOME machines down my fellow small business owners when the Optiplex line is supposedly for business?  Do I now have to go to the Precision line of desktops which appear to be all XP Pro based machines?

Then on the Precision lines... they are putting 160 gig to 250 gig harddrives on those local drives.  In a business setting...where the desktops are not getting as backed up as they should... why do we need a 250 gig harddrive?  Shouldn't we instead be making sure that we're backing up all critical data on the server?

Then, the default is to not give me a resource cdrom for drivers.  Again, for disaster recovery purposes ...why would I not want such a cdrom?

Then what drives me crazy as an admin is the size of the minimum harddrives.  I don't want a workstation to have 80 gigs of storage.  Why do my workers need that much?  For the mp3 files they are not supposed to be downloading?  The Precisions are even worse with a minimum of 160 gigs of storage as default.

Now granted one could take advantage of the new Small Business SKU and buy XP Home on those boxes and then add Windows XP Pro with software assurance...but that just seems a bit cumbersome as well.

Yes you can add a SBS 2003 to an existing domain

Roy says in the comments... “Yes, you can add SBS to an existing domain but not forever. In the KB article you mention is this comment: "This retirement process must occur within 14 days of adding the new SBS 2003 computer to the domain or the new SBS 2003 computer may display warnings and shut down periodically."

Uh Roy... that's only for migrating from one SBS to another or for moving the FSMO roles.  You “CAN” add a SBS 2003 to an existing AD domain and as long as you ensure that the SBS is the Primary domain controller and all the FSMO roles are on that SBS box you 'CAN' add a SBS 2003 to an existing AD domain.  The gang out here has done it before.  Check out the info on sbsmigration.com as it's basically doing a similar process.

Yes Roy, you can add a SBS 2003 to an existing domain...forever.  You just have to get rid of the 'normal' AD domain stuff off the prior DC and make sure all of it is on the SBS box.

It can be done.

Remember what that KB article says..... it's not meeting these conditions that make it shut down...

The following conditions must be true after you install the new SBS 2003 computer in an existing domain or the new SBS 2003 computer may display warnings and shut down periodically:

  • The new SBS 2003 computer must be a domain controller that is installed on the root of the domain.
  • The new SBS 2003 computer must hold all the Flexible Single Master Operation (FSMO) roles.
  • The new SBS 2003 computer must be a global catalog server and must be the licensing server.
  • There must not be any existing domain trusts or child domains.
  • Only one SBS server can exist on the domain. If SBS 2003 is installed, no other SBS 2003 or SBS 2000 server can be installed on the same domain.

Failure to meet these conditions may cause the SBS 2003 server to shut down.

I love my Lunch time menu internal communication system

Steve has a problem.  He has a small network and because he wasn't wacko like me, didn't catch Live Communication Server.  So now he's looking for INTERNAL ONLY nothing going out the firewall thank you very much [no MSN hotmail need apply] for an internal IM system. 

In fact I need to load up LCS 2005 with it's new communicator thingy...but I've not got around to it because I don't really need all those VOIP, forward to cell phone, internal routing of calls do-dads-thingy-whatchamacallits-wingdings here.  We like plain phones that just work, thank you.  And IM is really just for the 'ping' for “what do you want for lunch” and “hey, there's a call on line 2, you want to cut that one you are on short?”

Sometimes..like with the Audiovox 5600 phone geek toys are WAY cool.  But sometimes simple is just better and all we need.

Vlad blogged about his same problem earlier.

Keep in simple, that's all we really need.

Got any other ideas for Steve?

Mr. Minasi we can do that too!

Met up with Markoh SBS is evil because it can't have a secondary domain controllerMinasi at the MVP summit and it reminded me that we recently got a clarfication on how we CAN have a secondary domain controller and all you need to have to cover the licenses of that secondary DC is plain ol' SBS cals.  You don't need Windows server cals.  The SBS license specifically allows us to have our member servers and even our additional domain controllers covered by a SBS cal.  So all you need to have in order to set up and be legal for an additional DC is the server CAL that came with the Server OS [and yes if you buy Open License version of Windows 2003 server you can buy it with one and only one CAL] and then your SBS CALs.

So to review....

  • SBS CAN have a secondary/additional DC
  • The CALs for it are merely ONE Windows server OS CAL [you know the one you get with the OS itself]
  • and then it's covered by the SBS CALs.

The Enterprise IT pro white paper even talks about this.  “You can add a computer running Windows 2000 Server or Windows Server 2003 as a replica domain controller to a local or remote office for redundancy in the event that the server running Windows SBS is unavailable. Replication with the server running Windows SBS keeps Active Directory up-to-date on the additional domain controller even in the remote-office scenario, provided there is a link between the offices. Users can then log on to the network normally until the server running Windows SBS is brought back online.”  Personally I've found that what's more important is the DHCP than the Domain controller per se...as workstations that can't find a domain will merely log in via cached credentials. 

Bottom line.. buy good hardware and normally is a non issue in a small office.

Yes, you can do that Mr. Enterprise IT Pro.

In a white paper on the download site about “Introduction to Windows SBS 2003 for Enterprise IT Pros“ it says

 

I feel the need to repeat this, so here it is: there can be only one machine running Windows SBS in a domain! In sum, that means that the only kind of domain that a Windows SBS computer can be part of is its own. You can’t add it to an existing Windows Server domain, and you can’t add another Windows Server machine to a Windows SBS network as the primary domain controller. (You can add extra machines running Windows Server to a Windows SBS domain as replica domain controllers, line-of-business (LOB) application servers, or servers that have Windows Server 2003 Terminal Server enabled, but we’ll cover that later in the "Common Scenarios" section of this paper.)”

 

And I'd like to point out that one sentence “You can't add it to an existing Windows Server domain”... which is... well...it's just plain wrong.  You see you can add a SBS box to an existing domain.  You see there's a KB article out there .... 884453 in fact that is titled up as "How to install Small Business Server 2003 in an existing Active Directory Domain" that is right on point telling you how you can do that.

 

“You should use the steps that are described in this article as an outline for how to install a new SBS 2003 computer in an existing domain to maintain the existing Active Directory directory service infrastructure.“

 

Needless to say I'll be finding a way to give feedback on that document because that one part in particular is a bit wrong.

 

<psssst.... whitepaper already updated on the web....dang you guys work fast...>

The lowercase "c"

I'm sitting in Portland with a couple of hour layover before I go home after a couple of days in Seattle.  And in my slightly sleep deprived state as I wait for the time to get the next leg of my flight, it’s always a bit of a reflective time as those of us in this “community” all scatter back to the corners of the globe...there's a couple of thoughts I need to express.  This summit feels a bit transitional for me as I’m part of the “old guard” these days.  No longer the newbie, I’m the one who now gets the pride of seeing that newbie ‘oh wow’ glow of a new MVP coming to Seattle for the first time.  THe one who beams when a fellow MVP makes the connection with a product group to help grow the connection between customers and a large company.  This is also a good time to self reflect on what exactly is this thing called community.

 

To me, I think there are two “communities” out there.  One with a capital “C”, one with a lowercase “c”.  The “C” one is the one seen by the business side of folks.  This is the one that the “buzz” words are thrown out around… you know… we’re going to “leverage this and that” as the business side of “C”ommunity is apt to say.  To me this one is the one that has the logos and the swag handouts.  The “C” is the one that is seen in the business world as a conduit for viral marketing and word of mouth.  The one that Madison Avenue tries to harness.

 

But there’s another Community out there.  The lowercase “c”.  The voices that I think large companies need to make sure they are listening to.    The lowercase “c” one is the one that folks like Paul Thurrott, I think, missed seeing.  Since he posted about the MVP summit, I'm going to publically comment about some of the issues he brought up....He said that I'm a bit freaked out by the sense of entitlement I get from many MVPs. Many of these people are fantastic and are true experts in their respective categories. But as in any large group, there is a minority that kind of ruins it for anyone.”  I think he saw the “C” part of the community, not the “c” part.  He saw the minority that do it for personal reasons and not the “c” ones that look at this insane thing we do as ‘paying it forward’ kind of thing, or a calling to keep Microsoft honest.

 

Another journalist that was at the event didn't want me to introduce them to Microsoft employees.  He said that he didn't want to get too “close“ because of his journalism role.  I guess I see it differently than he does.  Because in my view there are times that I feel I can yell louder when I am known by people behind the wall.  You know how you can argue more passionately and strongly with family members than you can with strangers?  I think there's a bit of that going on.

 

When meeting with Folks this week, many of the things we asked for were things that the gang has asked for for three summits now.  And the funny thing is, in many cases, the items we’re asking for,...the really obvious stuff like tools to help transition the break/fix businesses into managed care plans are already in the marketplace.  Level platforms comes to mind as one such tool that’s already there making an impact.  It’s often been said that a large percentage of features requested in office are already in the product but people don’t know they are buried under the hood. 

 

I think Paul was right in that he should be freaked out by the “entitlement” view he saw.  I get freaked out by it too.   In fact embarrassed a bit by it sometimes.  I also strongly feel that the “MVP” view is only one of many data points that Microsoft as a company should look at.  We’re just one datapoint, one set of voices and I would hope that Microsoft is not just listening to MVPs or journalists like Paul.  In fact, there are times, we're not the right “voice” to listen to. 

 

In all honesty there's been a bit of a concern about Paul Thurrott being an MVP as he says.  He is after all a journalist.  And as a journalist, how can he sign NDAs on the one hand in the MVP program and write about the latest and greatest stuff at Microsoft.  Does Paul Thurrott need to have access to Microsoft in the role that he has.  Definitely yes.  Does he need to be one datapoint as a feeder of information that has impact.  Absolutely.  But is it even fair to him to put him and others in this catch22 of a situation where it's his job to report on the latest and greatest and even not yet released Microsoft technologies and then bind him by a NDA? 

 

Can a member of the press who's role it is to report, is it fair to him or her to put limitations that might have to be investigated as a potential “leak“.

 

But I'll be the first to admit when I signed up to the Blackhat brieflings under a Press Pass [that I later on had to back out on going to].... I'll be the first to say that saying I was a member of the “Press“ due ot my Patch management articles I write felt weird.  Interestingly enough I didn't feel independent 'enough'. 

 

Is the Press a member of the “C“ommunity or a member of the “c“ommunity?

 

I tend to find that the lowercase 'c' of community are not silos of information and I'm not sure we're pushing enough to get the parts of a large company to better communicate. We had a presentation on Exchange and our SBS group considers Outlook just an extension of Exchange...it's just that platform's communication conduit.  Thus having Exchange be even more aware of Outlook and Outlook of Exchange is key.  Sometimes all of us work in silos of information and don't look at the bigger picture.

 

I'd argue to Paul that the MVP program is indeed important.  We give a voice to a group. But honestly,the lowercase “c” of community is obviously just fine without us MVPs.  Questions are still being answered, topics are still being discussed even though we were pretty much offline.  Because while the uppercase “C” of Community might have a finite size, a budget, swag and all that... but the lowercase “c” is bigger than that.  

 

But at the end of the day it is just one voice...one datapoint.  Sometimes I get embarrassed by folks saying that this is “THE“ Susan Bradley.  But what they miss is that I wouldn't be “THE“ Susan Bradley if they rest of you weren't doing what you do.  

 

And then we get asked “If Microsoft is the richest company in the world, why do guys do this?”  Bottom line it's the 'pay it forward' for many of us.  The 'attaboys'. We'd still be doing what we do even if Microsoft didn't invite us up every now and then. 

 

A person who has this 'pay in forward' attitude isn't taught this....it's part of the fabric of their personality, twisted that it may bel....

 

You, the lowercase “c” of community makes me into the Uppercase “C” of Community.

 

For that I thank each and everyone of you that read the blog, send me questions every now and then so I don't run out of blog topics.  Yeah one could argue always that the MVP program is awarded for past community work, but I think Microsoft gets the most out of me when I'm representing their current customers.I wouldn't be a MVP... a person who represents voices in the community without having people to listen to in the first place.

 

It's my hope that when I'm in various places as a representative of you, I don't embarrass you so that Paul can't be talking about any SBSer including myself when he says “some MVPs”  have a sense of entitlement.

 

I still say when you stop worrying about “what's in it for me”, you get rewards ten fold...not to mention an online relationship that is unique and special.

 

For everyone of you that make the lowercase “c” into the community that it is,....

 

Thank you.

You have mail!

To all those in meetings where you bring in your laptop....can you shut off the sound?  One of the Vista features is a presentation mode that shuts off the sound and IM and changes the desktop to being “more PC”.  [Politically correct that is....]  But I'd argue that there should be a meeting mode..... because there's nothing more annoying to be in a meeting and somone logs in to their computer and you hear the music.

Next to me in the Portland airport is a guy who just got is email.  I can tell because the voice just said “You have mail”.

So folks... can we turn off the audio please when you are in meetings and traveling?  It's just a smidge annoying...

I want an RSS feed and I don't think I'm the only one

On a couple of listserves, WSUS, and Focus on MS, I've seen some folks talk about how their first indication that Office 2003 sp2 was when their workstations popped up with a “you have patches to install” icon.

Hands down the Security folks have the SDcubed +C nailed.. Secure by Design, Secure by Default, Secure by deployment and Communication.... the Security patches are communicated to us ahead of time, we know what code is installing on our box.

But if you want us admins to 'trust' enabling autoupdate on our workstations, you HAVE to inform us that you are going to be releasing Serivce Packs that will be coming down on Microsoft. Update.  Yes,  I know it's not a security bulletin and thus not your communication responsibility, but go wack the team upside the head in Service Packs that should be communicating better.

If you want me to enable auto updates, then let me know what's coming down on my box.  I should not use the “updates are being downloaded icon” to be my communication vehicle for such things. 

Gentlemen, I want an RSS feed of any bits that hit my machines.  As an admin, I've been asking for a email notification for Security patches for many years now.  I've upgraded my request... these days I want an RSS feed.  But the bottom line is, I'm not the only one who was blindsided by that SP coming out.  And as I'm the controller of my network at the office, I don't want to have to use my Laptop where the AU is enabled to be my “what new code is going to be offered to me indicator”.

Feedback

I got a ping today and in the email this was included....

“My biggest concern is that the last 3 calls to Microsoft's Business Down Critical Support have yielded no help whatsoever and the communication issues have been a huge issue as well.  Our techs don't even want to call support any more as a result, and I want to pass this concern on to someone who can make sure it is heard”

Ouch... that hurts...and something that is a real shame to hear.... if you don't like what you are seeing give feedback... it's the only way things will change and get better.

The 'other store'

We walked into the “other' store in San Francisco.  The Apple store.  And while one could argue that the tack that Microsoft has taken with it's 'open' platform that allows anyone to upgrade and build on the Windows platform, man could Microsoft take a page or two or three or four out of Apple's marketing playbook.

Young, hip.  With a presentation section that had a young woman talking about 'using' the Mac to the “Genius bar” that allowed you to book expertise to help you migrate data from one Mac to another Mac or... uh... migrate from a PC to a Mac. 

And with displays that are pleasing, uncluttered....not like the glaring, noisy, jarring Best Buy with the absolute information overload of varieties of Personal computers and laptops.  

Designs of systems that just are clean and stylish.  Don't tell Steve Foster this, but even challenges his Acer Ferrari laptop up for a coolness award.

Training ...education...not just shoving stuff and warranties at you with blaring rock music in the background.

Mac, I have to give you guys hands down credit.... in the marketing and buzz department you kick.... you majorly kick.

The checklist

Geek clothes....

...more geek clothes....

... Blogging T Shirt.....

Power cords......

Cell phone power.... [and btw you would think that a cigarette lighter that's supposed to be a mini usb would fit my Audiovox but it didn't and Steve and I were in Yosemite today with my dead cell phone... cut off... no email...no IM... no...oh yeah we were taking the day off weren't we?

Check the weather report ......

Get maps to San Francisco and Frys....

Print out PDF with full detailed info on where we 'think' we will be.

I know I'm going to forget something....

oh..yeah....

Don't forget the train tickets.....

You may receive a stop error if you are running PcAnywhere with A/V

You may receive a "Stop 0x00000020" error message on a computer that is running Windows Small Business Server 2003 or Windows Server 2003:
http://support.microsoft.com/?kbid=905539

This problem is known to occur on servers that are running Symantec pcAnywhere 11.5 with Symantec AntiVirus 8.x or with Symantec AntiVirus 9.0. An updated version of the Symantec Event Handler driver (Symevent.sys) causes this problem. The Symevent.sys driver is installed with pcAnywhere 11.5. The Symevent.sys driver causes the Symantec real-time protection drivers to generate the "Stop 0x00000020" error.

To resolve this problem, download and install the latest Symevent.sys driver.

My comment... what the heck are you doing running PCAnywhere on SBS when you have practically forty trilllion ways to connect to that box without using a third party program.  If your vendor demands that they have to have PCAnywhere... get a new vendor!

P.S.  Okay so forty trillion is an overstatement...but still...

I don't salute you one bit....

 James Coates says....

"I salute you for keeping a Windows 98 computer running in the face of enormous pressures to upgrade to XP,"

And he gets PAID to write this?

And he's a technology writer?

Do we really value ourselves properly?

How many hours will you bang on an issue before you call for help?

An hour?  Two?  A day?

I mean do they assign a value to your time spent dealing with an issue?

What about you?  The IT Pro?  I've had this rant before, but sometimes it spills into buying products or services as well.  The idea that a consultant will not call for support and pay the fee, or will not buy a product that will make his or her life easier.

Don't you value your time?  Don't you value your expertise?  Why will you not look at the cost of a product and thing of the time savings you will have?

Think about that the next time you hesitate before spending money on something to make your life easier.

Installing a new A/V

So while I'm making sure I'm not getting ragged on at the summit, I realize my Trend a/v is getting close to renewal...so I re-up. 

Now here's the annoyance...because I'm going up to the 2005 version, I have to uninstall the old one.  And of course...when does it tell me this?  AFTER I've attempted to install the 2005 version... and of course that means I have to write down the Product Key code and all that....Oh wait ..never mind.. it kept the product key code ...now I'm doing the full install even though I use the XP sp2 firewall and the XP sp2 security center.

You know one thing that is amazing... how can the normal non geek understand what these anti spyware prompts are telling you?  Heck I don't even know what some of this stuff is doing!

If you are an app developer... have I got a forum for you....

If any dev type folk happen to be down in Los Angeles at the Professional Developers Conference... and if by any chance anyone from the Intuitive Accounting application program is down there... can you really do me a favor?

Can ya

And then join the Vista Technical forum on “Security for Applications in Windows Vista“.

Please notice that “I“ as a buyer of software posted the first post, so obviously you Devs from any Intuitive accounting software probably are still paryting down in Los Angeles for the next couple of days at the PDC.  I'll let you slack off for now, but I'll be watching to see if you start posting in there.

Security for Applications in Windows Vista - Microsoft Technical Forums:
http://forums.microsoft.com/msdn/ShowForum.aspx?ForumID=116

I'm working on getting your software buyers to care... can you work on caring as well?

But Steve, you don't understand, I'm not small business... I'm just a Little Enterprise

You know... I really shouldn't draw any conclusions when Vista is still in beta, certainly not even to the point of shrinkwrap or anything, but sometimes, Steve [Mr. Ballmer] you make it such an easy target because of the rumors and leaks and messages that don't get communicated well.

Again, referring to article, it says “the Enterprise Edition“ - “Optimized for the enterprise, this version will be a true superset of Windows Vista Pro Edition. It will also include unique features such as Virtual PC, the multi-language user interface (MUI), and the Secure Startup/full volume encryption security technologies ("Cornerstone"). There is no analogous XP version for this product. This version is aimed at business decision makers, IT managers and decision makers, and information workers/general business users. Enterprise Edition will be offered exclusively through Software Assurance.

The marketing message: Enterprise Edition provides an advanced application compatibility solution that will be crucial to many large business users, can be deployed to multiple language locales using a single image, and provides Secure Startup functionality for the ultimate in security on the go. It is the client OS that is optimized for the enterprise. Enterprise Edition reduces IT cost and complexity by providing tools that protect company data, reduce the number of required disk images, and ensure the compatibility of legacy applications.”

You know... why can't Vendors get it that even small businesses need to be run like Enterprises.. and why can't folks like Steve get it that it's a heck of a lot easier to get small businesses on the security bandwagon sometimes.  I'm not saying that all small businesses are like me, but in my firm, you don't have to go through forty million committees to get an Executive buy off.  You just convince me.  Just me.  Once you convince me, the rest of my firm comes along for the ride.

I mean ... I may be little...but that just means I'm a “Little Enterprise”.  Don't I have company data to protect just like big firms?  Don't I have just as many legacy applications that I have to ensure are compatible [which reminds me I gotta go see if Vista Beta and Quickbooks play nice...]  I mean you haven't seen legacy apps until you come into some of the farming communities that are using customized Grain programs. 

Sir, I don't need games but I do need application compatibility and security. 

But I'm little.

Just don't forget me, okay?

I mean I guess they have to have something that makes Software Assurance valuable and since I already have SA on SBS, I 'think' when I'd be getting new software I can add SA on the individual units that I purchase within 90 days of buying OEM software [at least I think I could?].   So I think I might still be able to get this for those machines I might want this version on..... but I think it's going to take another aspirin for sure.

Dear Mr. Ballmer - make the message clear

I'm not a marketing major or anything, but in reading the page about the upcoming versions of Microsoft Vista, can I just ask a favor of you?

Apparenly you have taken a page out of the US Government's House Ways and Means Committee and their never ending quest for Tax Simplification.  Those of us in the beancounter industry refer to these actions to 'simplify' as “Full Employment Acts for Accountants”.

We have in the umpteen versions of Vista - the “Small Business Edition”. Oh gawd, says I.  Includes the following unique features “Backup and Shadow copy support”.  Uh our server does that.  Castle and Server Join networking. Okay Castle is peer... if “Server Join” isn't the same thing as fully supported domain active directory full glue.... ala Small Business Server..... so help me ...

Okay so I probably shouldn't rant before having all the facts but I'm come on Mr. Ballmer...you are making it harder for us in the marketplace of Small Businesses called Small Business Server with XP Homes, this version BETTER glue and glue good to SBS boxes otherwise it should not use the name “Small Business edition”.

Don't ship anything... not Microsoft Small Business Accounting 2006, not anything that isn't fully supported without issues on a SBS box if you use the words “Small Business” in the name.

Just once I'd love it if your computer wasn't set up by Ron Markezich but instead you walked into Best Buy with a hat on your head or something so folks wouldn't recognize you and you go try to buy a computer and set it up yourself.

We already get headaches now with licensing.... don't add more.  Please.

Do you?

I was talking with a fellow SBSer about how he runs their business and he said that every morning he checks a console for the uptime of all the servers that he monitors in his company.  And I asked him, “Are you charging for that?” and he said... no.

Well why not?

Everyone of you that does any kind of making sure your clients are still okay, still making sure everything is working.... it's a service that you should be charging to your clients.

When USBs work they work...when they don't....

One of my tasks is to get data from 'there' to 'here' inside of our network.  So on a regular basis I'm copying cdroms, usbthumb drives, to the point where the other day when I was handed data on a floppy disk I sort of sat there for a moment as my brain wrapped itself around the idea of data small enough to fit on a floppy disk.  Wow.  They can fit that on one disk?

So now I'm fighting with a Maxtor OneTouchII that someone brought in that when I first stuck it in the USB connector of my workstation it found it and 'woke up' and assigned a drive letter.  But then it reported that the drive wasn't formatted so I stuck in the Maxtor software driver cdrom.  Well that was a mistake as now I have an 'unknown device', and it won't wake back up and assign it a drive letter.

And, of course, I uninstalled the Maxtor software but OF COURSE it's still all over the stupid registry. 

Why is it that USB's either work the first time... or they screw up and drive you to drink?

So ...Maxtor.... and all you other softwares out there...when I say “uninstall” can you PLEASE uninstall?

Who can protect us from clicking?

I was earlier arguing with fellow MVP [aka the Naked one] Nick about what responsibility we have for end users.  He had a situation where folks were surfing for music lyrics and surfing and clicking and Aurora gunk was downloading right behind it.  He wanted it stopped [and rightly so].  But here's the problem I see.

Spyware is big business today.

Worms and viruses are mere conduits for getting spyware on the box.  When vulnerabilities go for $20,000 a pop, when virus/spyware writers are making six figures in a year, that's the reality of the world we live in.

Yet I still get beancounters that don't care that Quickbooks demands that they run their systems insecurely. 

It's we...the marketplace out here that has to care.  All of these software vendors are in business and they will only push security to the point at which the marketplace cares.

Right now my beancounter crowd as NO CLUE of what local admin rights are even about. 

We have to get 'us' the marketplace to care.  To push.  To say to everyone, I'm sorry you cannot code like that anymore.  I cannot run my machine like that.  You have to protect me better.

XP sp2 cannot do it.  Not by default.  They will not put resources into it.  Vista is the name of the game, Nick.

But it's us, now, that need to get our vendors on board.  They are the ones that are going to drag us down, not Microsoft.

Remember you cannot build on security afterwards, it has to be designed into the product.  We have to think about it ourselves first.

SCW, Exchange Best practices,  the XP shared computer toolkitl.   All of these are tools we have to help us.  In the home space the best tools are still Dropmyrights and not running as Admin.

“But I can't!“ We say, “my vendors won't let me!“.  So complain.  Get them to take action.  To stop setting your risk analysis. 

I mean when you get in a car, you buckle your seatbelt right?  You take precautions.  You got trained.  Where do we do ANY training whatsoever on our computers?  Even in my own office, I cannot depend on the end user understanding enough.  But maybe they should?  Maybe, just like with a car, there should be more training so that they can operate it safely?

Blowing through the myths

September 8th there will be a webcast to blow through the cobwebs.

Attend this session to learn why Small Business Server is perfect for any large business under 75 users.  This session will debunk some of the common myths regarding the reliability and scalability of Small Business Server environments.  We will also discuss scenarios on how to use Small Business Server 2003 for the most complex server workloads such as multi-server environments, line of business applications, and Terminal Services.

Haven't we been saying that for YEARS?

How to sell to a Beancounter

There is one way to a Beancounter's heart. 

Free CPE.

So for all you SBSers out there that realize there is a potential to upgrade the Accounting industry and possibly get them off of Win9x and Word Perfect, here's the game plan for you:

In many areas of the Country there are local CPA chapters that are regional divisions of the larger State CPA Society.  These CPA Societies are the ones that can certify your presentation as CPE.  Do NOT make it 'sales-ishy', you must make it a learning experience.  Put a hook of Security in there.  Talk about how Gramm-Leach Bliley Act requires Financial Privacy.  Thus this weekend when I was watching the Hurricane coverage and they were showing ads for “Gotomypc” and the announcer was talking about how it was not problem getting the Firm's Financial Statement off of the Home PC without having to go home, boy was that a fun thought in my mind that if an employee would think nothing of leaving confidential client info on their home PC.

Contact that larger CPA society, and find the location of the local chapter.  See if they have a Technology committee that meets. Offer to do a presenation.  You do realize that for 4 years I ran the local Technology Committee here where I live before I became the State Technology Chair.  It was a fun gig because all these vendors would call and offer to present a program.  Write up an Outline, do 'death by Powerpoint' and plant the seed.  Remember how “I“ first got turned on to SBS?  In a CPE class.

Here are some ideas to help the Beancounter see the Advantage of a network

  • Centralized Storage - ensuring that all the data is in one spot ensures that it's fully backed up and properly secured.  Charlie Anthe showcased an upgrade that he did where every workstation was mapping drives to each other's local drives and that totally blasts the rule of only set up those rights and privileges you minimally need.  All that mapping means that there is data everywhere and it's not getting backed up.
  • Data never leaves the server - I purposely make the choice to NOT set up Outlook over Http.  Because I 'don't' want any offline data file storage on a laptop that may be stolen.  The fact that I can remote back in and never pull data off that server is wonderful in my book.
  • Security - Compare and contrast the security of Remote Web Workplace to PCAnywhere.  Because, yes, that is the app you are competing with.  Point out that PCAnywhere uses two static ports and that if that router gets reset, there goes your access.  Whenever a software program starts off with “We use a proprietary encryption algorithm“ run in the opposite direction as fast as you can.  Notice that by version 11.5, they finally junked that and are using AES 256 encryption.  Now class what does RDP include?  Oh just these standard RSA RC4 encryption thingys.  So your first question should be ...what version of PCAnywhere are your running because it looks to me like those older versions need to be junked and fast.
  • Multi-user means a network.  Now I'll be the first to admit that Microsoft has this problem too.  They build a package for 'multiuser' and we have to hack the package to get it on the server.  Come on gang.... a Network is just a workgroup with more toys.  All those mapping of drives from one system to another means that you've got major major goo and a major major eggshell network setup.  We can't set up this stuff like this anymore.  Especially not in a network for an industry that needs to realize that we have responsibiltiies to our clients to protect data.  SBS 2003 with XP sp2 puts firewalls on each computer only opening up those ports that are needed for operation and blocking all others.  It's called defense in depth.
  • Sign them up for the MPAN program [which btw offers free CPA and an alternative to Quickbooks in the new Small Business Accounting]
  • Oh and KILL OFF THOSE WINDOWS 98 WHILE YOU ARE AT IT

...do that and I'll stop yelling at them in the CPA listserves I'm in.

So it looks like they haven't changed in 5 years.

Let's see class how many wrong statements are in this list that was posted by “HappyFunBoy's“ blog post?

  • sbs sucks...and is stupid - Hardly ... I think that partner is for having a closed mind
  • sbs is slow, which is stupid  - Slow? What are you installing it on?  The minimum specs?  You know how they lie.
  • running exchange on a dc is stupid  - If you only know how many firms I find running Exchange on a DC... you'd be amazed.  This is 2003 era anyway.
  • putting everything on one server is stupid - Actually I prefer it all on the same box... I monitor it better than if it were strung out
  • not being able to add other servers is stupid  - uh... did you miss the part where we can add additional servers in SBSland?
  • sbs is a good idea for companies that will never ever grow, but stupid for anybody else - You do know about the transition pack?
  • ms is stupid for not putting all this [cool] stuff in their "real" products - That's probably the ONLY good statement in this list.... except we ARE real.

You know... it really makes me question if I want to send customers over to “Microsoft Partners” if 5 years later they are still so stupidly closed minded to how SBS can absolutely ROCK for a dynamic small company.

But like HFB says... if you want to pass these customers by.... more work for him.

[BTW to make it clear... HappyFunBoy heard these comments by the TS2 attendees, partners that just don't get SBS even still.  He'll be the one reaping the rewards of SBS sales, not them.  I'm just surprised he didn't get up and slug some of these partners for saying this stuff.]

Dear Mike Healey

Dear Mike:

First off I have to apologize.  I'm picking on you because your name was in a CRN article about SBS.  You see you were labelled as a partner who “dislikes” SBS and that will instead push the midmarket bundle.  “Discounted software” you said and “let the actual customer needs dictate the number of servers”.  Yes Mike, let the customer needs dictate the solution, but don't close your eyes on SBS.

In 1998 I went to a class on networks and computers and in that CPE class I was first told about SBS 4.0.  I knew that it would be a perfection solution for my firm.  So I found a consultant who knew NT, but not SBS.  We muddled through, didn't screw it up too much.

So along comes SBS 2000 era and I went searching again for a SBSized partner.  And this time I was told “we don't recommend SBS”, “we find firms outgrow it”.

Yeah, right.  So here I am how many years later and still, there are Microsoft partners who turn a blind eye at their customers needs.  Oh they say they are listening, but I see the same pattern that I as a customer encountered.

You see, Mike, unless that mid market bundle, which right now is just a pricing bundle and has no 'specialness of SBS', has anything like SBS's killer apps of a monitoring email and Remote Web Workplace, all you are doing is hurting your Small Business customer.

Remember we 'can' add additional servers, member servers, additional domain controllers.  But if I'm a business owner that is in the target size for SBS, you'd really better show me a business value for 'not' being on SBS.  And it better be a good reason too. 

Rick Richardson at the Illinois Business and Technology show asked the audience “when's the last time you saw a killer app” to a room full of Accountants.  He said Visi-calc.

I said Remote Web Workplace.

I think I'm right.

Dear IT Pro Community:

HOW TO FACE OFF AGAINST MICROSOFT

Intuit has repelled the Redmond six times. Now it's defending its

largest business -- small-business accounting software

http://newsletters.businessweek.com/c.asp?id=583044&c=0a3482e76a3aa5ed&l=2

 

INTUIT'S BENNETT: READY FOR MR. GATES

Facing another onslaught from Redmond, the finance-software maker's

CEO says, "I love our position." Score so far: Intuit 6, Microsoft 0

http://newsletters.businessweek.com/c.asp?id=583044&c=0a3482e76a3aa5ed&l=3

 

-----------------------

 

I am a CPA in Californa.  On a pretty regular basis I deal with small business customers.  Some that have standalone computers, some with networks.  I have a trusted relationship with all of these small businesses. 

 

Just like how you install software better when 'you' know it.. just like how you have impact with what I call the 'wow' factor and word of mouth, so do I.  As a result Microsoft has just introduced the Microsoft Accountants Network to introduce my world to Microsoft's Small Business accounting 2006.  As part of this network my community is now eligible for free CPE and the Action pack [for $299 a year]. 

 

Now before you start yelling "Hey Microsoft, you are now allowing CPAs to use Action pack? You are taking software sales away from us",  Correct me if I'm wrong, but I don't think you make your income from software sales.. you make it on the labor and installation of the network. 

 

Microsoft is offering to my world because they realize too how much I influence software purchases when I am plugged in.

 

Now in these same beancounter communities are the "just good enough' folks.  The same people that when they raised their hands in a presentation on Wednesday and said if you ARE running Windows 98, you are sending a message to all of your clients that you don't CARE about the security of their data.  These are exactly the cheap, 'it's good enough people' that you can now go to and say, "here's a way to get software, to get secure, to get free CPE and all you have to do is sign up and check out this software bundle"

 

Also for this plan it gives them "business critical down" that includes things like printers failing on April 14.  To a beancounter ..that IS a critical down issue.

 

This week I was in Illinois and Cindy Bates of Microsoft indicated that the firm that "gets IT" has higher growth that one that doesn't.  Here's your chance as a consultant to go to that CPA in your area and show them the MPAN program and say ...it's time you killed off that Windows 98 machine.  It's not good enough ANY MORE.  Show them THIS link and tell them this is one time “too good to be true“ isn't.   

 

Now then my IT community out here... all you IT consultants... you talk to that CPA and tell them about how they can share calendars.  How with Audiovox Windows Mobile phones, the partners can check their calendars from anywhere.  That having their client data on a system hooked up to the Internet IS safe, and in fact with high speed access I would argue allows you to be more secure and up to date.

 

I told a room of 100 or so Accountants that if they thought the SBS 2003 product I talked about and used at my firm and actually demo'd was cool, that they needed to go and find an SBSer.  To go to YOU and ask you how many SBS installs you had done.  Be honest.  Don't say you have and you've never even seen the product before.   

 

Just remember if you don't treat my CPA community right, I just might hear about it.

A bit of customer service

I'm going to relay a story and see if it has any echos in the consulting world. I had an experience last night where I was expecting a level of service, but because the person in charge of 'my' experience was busy trying to help and support another person, I didn't get the service level that I was expecting.  Now I don't think the person who got the superior level of service is going to recognize how good of service she got.  But I'll never forget my experience with poor service.

We all have that kind of issue in the customer support world.  The “A” clients, the “B” clients and worse yet the “C” level clients.  You know what I'm talking about don't you?  You take the exercise of looking at your client list and grading them.  Giving them a grade.  Hopefully you don't have any “F” or “D” clients ...and if you do... you should fire them.  But if one of those “C” clients is taking time away from one of your “B” or worse yet, one of your “A” clients, you need to stop yourself and ask...why am I letting that client do this to me.

Be careful that your “C” clients aren't taking away from your other ones.

Now in my case ... I felt so strongly about it... felt that it truly was taking way too many resources from other consumers of the service to send off an email and complain.  Now keep in mind for all my throwing about of the 2x4, I'm a pretty laid back, tolerant person.  Okay so maybe I should put the 'caveat' of laid back and tolerant doing certain things or something, but all in all, I don't think I'm as intense in person as I am via email... you know how that goes.  So for me to ensure that I gave customer feedback in this instance, means that it made a lasting impression.

Consulting is a service industry... just make sure you service customers and clients correctly.

...not the success they thought it was going to be...

So I'm talking with Bob Scott of Accounting Technology and he says about SBS 2003 something along the lines of “it's pretty solid...but it's not the runaway success they predicted...”

...oh and that was a red flag in front of me....

...and it's funny...because here I am with one foot in the IT world and one foot in the Accounting world and SBS's success IS over 'there', but here in the Accounting world...where let's face it...we're CHEAP.... I have a hard time convincing folks that the technology that they think is 'good enough'...isn't.

Sorry Bob, but walk over here to the IT side of the world where it IS the success.  We just have to get the folks in my beancounter world to realize that they have to get 'it' and IT.

Sign up for that Microsoft Accounting network folks... you should have been here when Cynthia Bates of Microsoft was showing during her powerpoint presentation an video about a small business who realized their existing technology was a THREAT and not a resource.

Who's responsible for the goo anyway?

Donna points to a recent survey that blame Microsoft for the worm....

But here's what I don't get... there was a workaround in there... Null session... and excuse me but I've read/heard about null sessions being a bad thing for HOW LONG now? 

Let's analyze this... YOU Mr. network person, YOU Mr. Businessowner let file and printer sharing goo traffic INSIDE your protected network and you allowed annoymous connections. Remember the workaround from the advisory? 

“If an administrator has disabled anonymous connections by changing the default setting of the RestrictAnonymous registry key to a value of 2, Windows 2000 systems would not be vulnerable remotely from anonymous users.” 

WE KNOW we cannot 'trust' our networks and yet we are doing NOTHING to secure than any better than if you had an entire fleet full of Win9x machines.  I mean you are pretty gooey and creamy in the middle there.

As far as not rolling out patches as soon as you can, I'm sorry I'm getting to the point where truly..when's the last time patching desktops broke something so badly you had to roll it back?  I'm not talking servers here.. I'm talking desktops.  Honestly when's the last time anything happened?  Maybe we need to zone ourselves... speed up those desktops that are obviously pretty gooey...and protect those servers better.

Isn't it better to have a small % chance of breaking something on the desktop ....than Disneyland not being able to sell tickets?

If you think your OS is good enough 'as is' ... and not willing to update to a platform of XP and 2k3 that were NOT hit by this ONE BIT, well then you have to make your network less gooey on the inside.

I mean don't we roll out antivirus signatures every hour on the hour?  How is that different?
------------------------------------
A web poll of more than 1,000 business PC users1, conducted by Sophos, has revealed that 35% of respondents blame Microsoft for the recent worm attacks against businesses across the globe, which exploit a newly discovered vulnerability in the software giant's code.

Systems administrators are also feeling the wrath, with 20% of respondents blaming them for not patching systems quickly enough. 45% hold the virus writers responsible for the 19 worms, which all take advantage of the same flaw.

"The majority of users believe that the virus writer has to take the ultimate blame for deliberately creating and unleashing this worm to wreak havoc on poorly protected businesses," said Graham Cluley, senior technology consultant at Sophos. "But what is most surprising is that so many people blame Microsoft for having the software flaw in the first place. Users' anger is perhaps understandable as Microsoft's security problems and their consequences are felt by businesses the world over. Many respondents appear to be incredibly frustrated by the constant need to roll-out emergency patches across their organizations."

http://www.sophos.com/virusinfo/articles/zotobpoll.html

How to join a MCE to a domain

I almost called this post “the Banana” as you will see when you read the post on the google link.

Now I'm not one to advocate a 'non supported' solution..but.. well.. I just think it's totally DUMB that a MCE 2005 cannot be optionally joined to a domain.  I can't tell you how many people have said they wanted the 'coolness' of a MCE 2005 sitting in their conference rooms and once they found out it couldn't hang off the domain so that they could control it like any other box they backed off of it.

So ..here's the “Banana hack

And Microsoft?  Realize that some of us are flexible out here and want these suckers in businesses? 

You probably also have no idea how much more sense a SBS makes in a Mac network over and above an OSX do you?  Guess I'd better blog about that one next....

Really we're not all like that....

Charlie has a blog post about a visit to his Accountant.. one that is still working on a 1980 vintage network. You know the type... one step up from a sneakernet.  What I love is already the “oh it ain't broke” posts at the bottom... “why doesn't he get a consultant to come in and fix the problems like a database instead of Excel and an email server setup

Apparently they missed the memo about what SBS is... you... folks.. business owner?  CPA?  Attorney? Blog comment people at the bottom?  Folks?  Come over here... that's what SBS is all about.  It IS providing a database.  It IS providing an email server..and here's the thing... it puts in in a package that gives you the business owner way more control than you ever thought possible even if you aren't geeky. 

Oh and business owner?  Are you still using a AOL.com email address?  If so ...do you realize how lame that makes you look?  It's not professional AT ALL.  There is such a better way to be more effiicient in email, in saving files, in backing up, in securing your network it ain't funny.

In my own office .. I think back of how much more automated I am.  I used to have to manually install a/v signature files.  I used to have to sneaker net.  Now I can remote in FROM HOME.  Last Friday night in fact, I security patched the entire network sitting in my jammies. 

So many times in small businesses we don't know any better.  We just make do with 'good enough'.  Well sorry folks.... this is one sign of a network that was so broken it's not funny.

  • No antivirus
  • No patch management at all
  • No monitoring of that server for security purposes
  • No email
  • No easy storage solution

Sorry folks...but that's not the sign of needing 'parts' thrown at it, that's the sign of a need of a solution in a box.

...oh and Charlie...we're not 'all' like that... some of us are using dual monitors [in face one of our guys in the office has four flat screens].

P.S.  ... that Accountant should.. if they are recommending and installing accounting software..to sign up for the Microsoft Accountant's network

Please note..while I know that the folks reading this blog are probably not small business owners still on dial up and Win9x, and I truly know I'm preaching to the choir and you already know how hard it is sometimes to convince them to change... remember two things... this beancounter embraces technology [yes there are some of us out here who do] and secondly there are times that the blog is cheaper than therapy.  Notice the category of “Rants” to the side?  This is a Rant.  Preaching to the choir of why SBS fits so well with a small firm, I know...but that's all it is... just a rant...

About that RSS branding Robert...

Scoble talks about how those Orange XML tags are confusing for newbies looking for RSS feeds and told to look for RSS feeds... you know that is even MORE annoying?  Those RSS tags that DON'T go to feeds, but rather link off to another page that has the feeds.

People BE consistent.

There are pages on the Microsoft web site [not sure if I should quite point them out though. they are a bit MVP related and I'm not sure if you can get to them without popping through passport ] that have an RSS icon and all they do is link to another page that has the XML real feed links.

Okay Robert... how confusing is THAT?  How about making sure that any page that has good info that gets regularly updated has an RSS feed.

Like this one.  See this page here?

Where's the RSS?  Heck where's the XML?  I don't see either one? 

Content should be read.  Good content should be RSS-d. 

'nuff said.

 

You could have 74 additional servers if you really wanted to....

Once again, let's get the misconceptions about the SBS platform blown away tonight shall we?

No... SBS 2003 does not have to be the ONLY server on the Subnet.  It DOES have to be the PRIMARY domain controller and hold the FSMO roles.. however if you really wanted to have 74 additional servers and no clients....

Go knock yourself out..it will support it.

I don't need a trust in a small business dude... I have two servers here just fine.

...next... dude.. that's Windows 2003 server that forces that documentation of why the server shut down... if you don't want it google and shut it off.. most consultants LIKE it because it documents when the owners have mucked with the server... and lethargic?  Lemme guess... you beleived the 'minimum standard specs“ of RAM didn't you?

1 gig of RAM and nothing less is what I recommend for a real production box...you can get away with 512....with a small one or two client network...but mine isn't lethargic one bit. 

Bored to tears waiting for me to ask it to do something yes... lethargic...no.

Yes I know... you aren't human...but you really are...

Yeah yeah I know...the Captcha thingy down there really sucks...but it was the best I could do at the time to get people from stop spamming the blogs... it was so bad that Christian was about to stop blogging...and as much as he blogs... you know it's bad.

So bear with me a smidge longer... we've been in this really long process of getting up to the new Community Server platform and somehow the summer is just racing by. 

I think I'm a bit like ~Eric's Brett.... he doesn't want to blog... I'm too chicken to upgrade.

Stay tuned and put up with the Captcha thingy just a smidge longer...okay?

Ever notice how you end up with screws leftover?

From the mailbag comes the request that I fess up what I have in hardware based on my talking about how I haven't migrated yet to my new computer....now you'll know I'm not a 'real geek' in that I have to slide over and see what the Intel [yes....I know... I couldn't break the habit and buy an AMD] chip is and all that... I can tell you it was a fun exercise in that I put it together.

Yes, you read that right... this is a NewEgg, Frys and CompUSA built machine...built by a GUI gal. 

The important parts about it is that the case is black.  Now the choice of black is very key here because it goes with the Mickey Mouse themed room that the upstairs office is decorated in.  A hovering Space Mickey is over my head along with the beginning of the trail of the pixie dust that Tinkerbell leaves on the ceiling as she flies out of the TV sitting on the TV mount on the wall over to the window behind me [yes, there's a Tinkerbell doll hanging from the celing.]  So since the monitor is black and all, I had to make the new computer a black case and all as well.  Regardless of the rest of the pieces...the outer case looks cool.

But since I'm sure the emailer wasn't wanting to know about the Black computer case....it's an Intel 3.2 GHz chip, 2 gig of RAM, a 250 Sata drive, one DVD/CDRW drive, one DVD/RW drive, Nvidia GeForce 6200 turbo cache [and I'm seriously thinking of putting in a second video card here at home for the second monitor as I have one at the office and there are time here at home that I'd really like to have a second one around], one floppy [yes even though I'll doubt I'll need it].  I'll have to ask my friend down in LA what the Motherboard is as he's the one that recommended it.  Tells you how hardware-ish I am doesn't it?

The lessons I learned?  Even though I READ the instructions...really Marina... I did!.... it wasn't clear that I was supposed to put in the two power connectors.  I thought it needed only one.  So that slowed me down a bit in the building of the computer until I figured that one out.  Next, make sure you get that goopy stuff called Artic Silver and you don't have to put as much as I put on there...but it works as when I first put the thing together the machine was pretty quickly shutting down and when it did work ...if you went into the bios it was reading that the temperature of the chip was too hot.  So it needed that silicon gunk as the wafer of protection it came with wasn't enough.  Took the fan assembly off the chip, put the gunk on there, stuck the fan back into place...and voila.. machine runs just as it should.

You do end up with stuff however that I'd like to complain about...

Screws.

..no not as in 'she's got a screw loose' even though I'm sure some might say that... I mean I always end up with leftover, weird sized, what screwdriver do you use with that... screws left over.  I have them all over the place.  Along with cables that I can't remember where they came from.  Somewhere there's a bunch of computers that are missing a ton of screws and cables. 

Call me.  I think I have them here.

Why doing a clean install of Windows XP is a good thing..

You cannot find options under "Use Extensible Authentication Protocol (EAP)" on a computer that you upgraded from Windows 2000 Service Pack 4 to Windows XP with Service Pack 1 or Service Pack 2:
http://support.microsoft.com/default.aspx?scid=kb;en-us;902934

It's Knowledge base articles like that that make us recommend clean installs on Windows XP.

That said... I have to admit that I'm sitting here typing this up on my clunker machine of XP sp2 while my new spiffy super dooper SATA harddrive machine is sitting over there with it's side off waiting for me to hang one of these harddrives on this machine inside that machine to make it easier to migrate the 'profile' data.  Once upon a time we could just copy the 'wack' folder from one system to another and everything would just magically work.  But then someone invented...the registry.

Yes the same registry that the Scriptomatic guys joke that you are always reminded in KB articles that oh if you muck with this sucker you could blow up New Orleans in the process if you aren't careful.  I think the problem that we all have with people not wanting to migrate up to Windows XP sp2 from what they have because what they have is 'good enough'...I think it's also a problem of migration is still ...even with the file and transfer wizard...isn't good enough.  I know in my own office, if Word has a funky macro in the old machine and the new one isn't IDENTICAL, I'll end up with a messy normal.dot or a macro template that I muck around for hours trying to get back out of the newly built system.

..one of these days I'll be on my new super dooper computer....just probably.... well most definitely...not today....

APC's understatement of the year

On the APC web site is this tech note

“In order for PowerChute Business Edition to remain functional, users must upgrade to any version of 7.x. Due to expiration of the Sun Java Runtime Environment certificate, versions 6.x of PowerChute Business Edition will cease to operate normally as of July 27, 2005. Failure to upgrade will result in PowerChute Business Edition no longer providing monitoring and graceful shutdown of your system.“

What it really should say:

In order for PowerChute Business Edition your Server that your business relies on to remain functional and boot worth a darn and not sit there for eons stuck on Applying Computer settings, users must upgrade to any version of 7.x. Due to expiration of the Sun Java Runtime Environment certificate, versions 6.x of PowerChute Business Edition will cease to operate normally as of July 27, 2005. Failure to upgrade will result in PowerChute Business Edition no longer providing monitoring and graceful shutdown of your system.  Failure to upgrade will result in you spending hours debugging the problem thinking it's viruses, corruptions, harddrive issues, and possibly cause network consultants to rebuild entire networks and spend unnecessary hours and weekends stuck fixing this.

APC?  Be a bit more honest about this... I'm not looking forward to next Tuesday when we'll have that possible forced reboot for a patch day coming up.  Remember this only nails you after you've been forced to reboot.

Asking the hard questions...do you Mr. Vendor, allow me to patch?

When someone emailed me about an accounting application that would not certify installing patches on servers past Security bulletin 04-012, a patch released last April, I felt it was time to open up a new section in the "Vendor Hall of Shame" for those vendors that will not go on record as supporting security patches in a reasonable time frame.

PATCHING:
http://www.threatcode.com/patching.htm

If you would like to make submissions, the nomination form is here:

NOMINATIONS:
http://www.threatcode.com/nominations.htm

...who's feels that it's time we start getting a list of those vendors that we need to be more aware of so we can make smarter software decisions.  If they won't support us patching..and we're small enough that we can't test appropriately.....then we need to know these constraints ahead of time so we can protect and defend and mitigate appropriately.

Maybe we need to look into IPsec for domain isolation?  Maybe that's one way around this issue?  The point is though that we need to know ahead of time what vendors patch support policy is so we can decide to patch without support, use other means to protect and not patch, stick that server on an isolated segment and just in general plan ahead.  Knowing this stuff ahead of time before we sign on the dotted line.... maybe it's something that even we in the small firms need to start asking about when we buy software on subscription.. something a bit more long term line of business like than a box from Office Depot.

We've taken it for granted that we can just patch and not have to worry about non supportability.. I think we need to start asking the tough questions....

  • Do you support restricted user?
  • Do you support security patches if done in a reasonable time?
  • Do you use a minimum of firewall ports?
  • Do you use the industry's latest and greatest accepted standards for secure coding when dealing with highly sensitive data? SSL in transmission, Encrypt in storage?

Just some questions to think about...

The vendors who set your security policy

I got an email today from a friend who was VERY rightfully concerned that a Vendor was setting patch policies for his network.  How can that be you ask?  Well it's called “support”.... you see they would not certify and support that customer on a server who patched 'past' Security bulletin 04-012 on Windows 2003 server...they hadn't even certified Service Pack 1 for Windows 2003. 

Yet they went on to say that they really recommended [and oh really so does Microsoft you know, that you wait for Service packs as they are more tested you know I mean we'll point to their article called “Why Serivce Packs are Better than Patches” to prove our point ].  In the mean time they are giving no guidance for exposure, mitigation...alternative ways to set up a network that you were blocked from patching. 

After I picked myself up off the floor on that one..let's see exactly what that server is exposed to shall we?

So let's see what we are exposing ourselves to shall we [and this won't include next Tuesday's critical patches...]

  • 05-037 - Jview Internet Explorer - Moderate [okay don't surf at server..but still]
  • 05-036 - Color module - critical
  • 05-033 - Telnet - Moderate
  • 05-032 - Agent - Low
  • 05-031 - Step by step training - Important
  • 05-030 - Outlook Express - Important
  • 05-028 - WebClient - Important
  • 05-027 - SMB - Critical
  • 05-026 - HTML help - Critical
  • 05-025 - Cumulative IE - Critical
  • 05-019 - TCP IE - Critical
  • 05-018 - Windows Kernel - Important
  • 05-016 - Windows Shell - Important
  • 05-015 - Hyperlink - Critical
  • 05-013 - DHTML - Critical
  • 05-012 - OLE and COM - Critical
  • 05-011 - SMB - Critical
  • 05-010 - License logging - Moderate
  • 05-009 - PNG - Critical
  • 05-008 - Windows Shell - Important
  • 05-004 - ASP.NET - Important
  • 05-003 - Indexing service - Important
  • 05-002 - Cursor and Icon - Critical
  • 05-001 - HTML help - Critcal
  • 04-045 - WINS - Important
  • 04-044 - Windows Kernel - Important
  • 04-043 - Hyperterminal - Important
  • 04-041 - Wordpad - Important
  • 04-037 - Windows Shell - Critical
  • 04-036 - NNTP - Critical
  • 04-035 - SMTP - Critical
  • 04-034 - Compressed folders - Critical

...okay.. I'm tired of keypunching...do you get the idea that there are just more than a few patches that accounting vendor are recommending that you not install on a server running that critical business application?

They point to this article as to why the program is regression tested and certified only with the generally available releases of service pack, and that if the customer is in urgent need to install these updates that they set up a test system to try it.  Oh for the record ....that article recommends service packs and then applying 'selected patches' based on your network based on your needs....it doesn't say ...oh only patch so far and then wait until your vendor says they've finally gotten around to certifying patches.  Which is the way we really should do it...only apply just enough 'code' to our systems as we need.  But certainly not 'oh stop at 04-012 and call it a day...

So here's the consultant/admin/you name it stuck between a rock and a hard place.  He or she either takes on the burden of software patch testing on their own...setting up a test network on their own, or they wait until the vendor certifies them. 

I'm sorry but the words “we won't support you if you patch the underlying system that our accounting application is installed on” is unforgivable.  Honestly I'd hate to see the patch level they run their machines at... I mean really if they take such a cavalier attitude about patching YOUR most critical business asset ...how seriously do they patch their network and their systems?

Look...according to that vendor..they shouldn't even be patching for 04-045 discussed in Robert Hensing's WINS hack.

So I guess the only advice we can do is to totally separate our accounting data from the rest of our networks..isolate it... segregate it...ensure that it's on it's own subnet, acl'd to smithereens and IPsec'd and sandboxed or something?  Certainly don't be as blase' about installing it as we have been me thinks.  Maybe that's what we should do is start going back to these vendors that won't support patching and demand that they give guidance for alternative ways to set up our networks such that the accounting software is totally isolated and thus protected and mitigated against?

You would think that the Accounting vendors would be embracing of security and all things surrounding it...

I guess not...

It's pretty sad when I look around and can point to a number of Accounting vendors that just absolutely don't get it ....

Pave and Nuke

I have a workstation... it has malware on it... it got it from a clicking end user when they were a local administrator to that box.... because the annoying popups were so bad and the combo of XP sp2, Google toolbar, Trend antivirus, and Microsoft antispyware were not enough ..we took the box to where they only had restricted user rights...meaning they could no longer click and install.

So the last few days when it would boot up a file would freak out upon boot.. usually a dll...usually in the system32 directory.  So I knew I probably still had he critters left behind.  So I started looking at the machine.

First rule is to look for unusual services... didn't see any of those...so lets go to the next step where we look at the files causing the error.  ssayerxp.dll.  Hmmm...wonder what that is...and interesting...not on other machines in the office...nor Googlable.  Okay let's look at it's properties.

Now this is interesting... Digitally code signed with a Thwate Code certificate for NicTech Networks.  Remember how Peter Torr asked how could he trust Firefox since it wasn't digitally code signed?  So this IS code signed... so what does that prove other than I can now trust my malware?

So I called Microsoft Product Support Services and asked for a WOLF analysis done to ensure that the damage was limited to this box.  The good news it was [I'll be typing up a full article about that later] and this sucker is slated for nuking and paving.

That's right I said nuking and paving ...because even with all my tools, it wasn't until I put the workstation to Restricted Rights that the malware showed up enough for me to find it.

I don't trust the machine anymore.  Data is on my network anyway.  Backups are in place.

It's nuke time for that workstation.

A little bad advice

Like my prior post, sometimes there's an instance where someone gets bad advice.  And right now I'm seeing one issue with getting bad advice in the past.  Remember class, my history.... I was once told that SBS was too limiting for me....that I would outgrow it...that it wasn't for me.

Look around folks...now tell me that SBS is limiting?  Let's see...oh yes... Remote web workplace where a co-worker is logging into from overseas...oh yeah..that's limiting... or Cell phones that sync up with the mail server... ah yes... see how limited I am?

So when that firm has indeed listened to a partner.. a Microsoft Partner in fact... I'm sorry...but I don't think it's right that they should now suffer and not be able to get any kind of version upgrade rights into SBSland from 'normal' server.  Alas the migration from Windows 2000 [plain] to SBSland is not seen as an upgrade/version upgrade or anything that qualifies the customer who got bad advice to a slightly better deal. 

Now... you know me.. I certainly call a conversion from plain Windows 2000 to SBS..ANYTHING above a 2000 version an upgrade.  I mean ... we have so much more to offer than plain server it's not funny.

Call me silly, but I think it's even more silly that the customer who thought they were getting a good recommendation...didn't.  Especially now.. some would argue that there were major drawbacks on the SBS 4.0/4.5 platform, less drawbacks on the SBS 2000 platform... for a firm in the 'sweet' spot, it's just a shame that they have to now pay for the bad advice they got.  Even in the SBS 2000 era... SBS was seen as a bit of a 'runt' box and cut down... 'oh you have a limited version of SQL don't you?' ...uh...no you are thinking of SBS 4.5... so it took a long time for Microsoft partners [remember MY story about how I had to insist on SBS?] to deploy SBS 2000 and you pretty much had to get someone wacko enough to beleive in the platform.

So I would argue that it's now a bit hard to say ...gee you should have gotten a better Partner recommendation...when it was 'buyer beware' and the customer had to insist on SBS in many cases.

Other examples of bad advice... don't buy Full retail/packaged product of SBS 2003...buy it via open license.  It gets you into the Open license model where EULAs and CAL codes and what not are kept track of for you.  As a customer of SBS, make sure your consultant talks about the options you have in licensing... if all he or she does is bash Microsoft... go get a new Microsoft partner...a Small Business Specialist in fact [just got the welcome box today as a matter of fact]

Oh...and one more bit of advice?  If you ARE selling/installing SBS and you aren't a Microsoft partner...arent' considering going for the Small Business Specialist designation...if you are not a hard core SBSer and planning your trip to Seattle and SMBnation, the SBS lovefest? 

Why not?

How many employees can a SBS server handle?

And no the answer I'm not looking for is 75 users or 75 devices which could mean hundreds of potential users....how many Accountants can use a network built around a SBS server as a foundation?

Well according to engineers at Dell, not 35 beancounters.  It drives me crazy when Dell or any dealer blows past the 'sweet spot' of SBS... the range of about 20 to 40 users and tells folks that SBS cannot handle multi server environments.

Let's review what is the killer apps of SBS and why... if you are in that 'sweet spot' of head count... you really and truly need to question your sanity as to why you are passing this up.

  • Monitoring email - the daily in your face to the admin email that keeps me aware of what's going on in your network.  Don't get it anywhere else but SBS.
  • Remote Web Workplace - just enough connectivity but not enough connectivity.  Get those boxes on XP inside the office [which I would argue you SHOULD anyway - and dude... the benefits of remote access are just too good to pass up
  • The wizards... someone the other day was asking about changing the IP and I said we had a wizard for that among other things... at the end of the conversation... he was joking..what DON'T you have a wizard for?  The point is they make our lives easier...don't fight them ...they are the 'tao' of SBSland.

Now then... let's review what we can add to a SBS server to make it fully workable ..and I would argue the one to choose in a firm that is in that sweet spot ...but still need the multi-server setup.

  • Can we add member servers?  Yes.
  • Can we add servers to be a Terminal server? Yes.
  • Can we add servers to be a dedicated LOB SQL server?  Yes.
  • Do we need server CALs for these?  Nope.  Covered by the SBS server EULA.

Right now the biggest drawback to SBS 2003 is honestly the size of our Exchange...16 measly gigs of space...BUT the fabulistic news is that in Exchange 2003 sp2 [due out later this year] this goes up to 75 gigs.

As a general rule of thumb... I would argue about 1-25 people need one server ...yes you read that right ... I said one person....as someone installed a SBS 2003 server for just one person as he wanted OMA/Smart phone sync ability [which ... I must admit...is really cool].  25 to 40 you probably want a second server...or... your line of business application forces you to a second server.  Regardless... I am proof positive that making the SBS as your 'base' and adding servers makes sense.

P.S... need to migrate 'into' SBS? We can do that one too.

..and 100% of Quickbooks users...

 http://blogs.technet.com/tonyso/archive/2005/08/01/408487.aspx


This article says that Microsoft's research indicates that 85% of corporate users and 97% of consumers are running their machines as administrators, according to Neil Charney, a director of product management at the software vendor. Charney said the company is hoping those percentages will decline as a result of the User Account Protection feature.
Read up on UAP here.


And I would argue 100% of Quickbooks users.....

www.threatcode.com  Get your vendors on the LUA/UAP wagon...and get them on it NOW...


..okay make that 99.99999% of Quickbooks users because I know a few that have indeed taken the time to wack the hives and gotten it to run a bit more in restricted user.

I hate ClassesRoot

Steve Riley in an ITShowtime says that most programs that can't run restricted user write gunk to local machine or user or whatever he said ... [it's a great series...I'd strongly urge you to watch/listen]...so here I am fighting with a workstation ...not with Quickbooks restricted user..but our Time and Billing program.

Practice Solution  3027Cannot Update.  Database or object is read-only.

Grrr... and when I go through the registry looking for places where this writes.. man almightly is this sucker all over the ClassesRoot hive just like Quickbooks is.

3027 is an Access error message and yes, this is running on an Access 2000 runtime program... so I'm off to hack the hive some more and let you know what it turned out to be...

Well no wonder this sucker is all over classesroot.... “It is primarily intended for compatibility with the registry in 16-bit Windows.”  I love that we get updates on a yearly basis for these line of business applications and they are coded like I'm running Windows 9X.  I hope someone tells them there's a new operating system in beta and do plan to code for it in the next century or so....


Update:  I had to open up permissions to C:\WinCSI.NET folder on the local drive and to get rid of all the Windows\System32 funky dll errors that would pop up after booting, I had to remove each item from the startup menu with the exception of the ISA 2004 firewall client. 

Someone, I'm not sure who, said this process takes ten minutes to figure out what programs need to run in restricted user.... I guess my clock is slow or something as I've yet to figure these suckers out in less than an hour....

One more restricted user/LUAized workstation... more to come...

Dear Steve:

Dear Steve: 

I used to call you Mr. Ballmer, but we've swapped emails a rare time or two [yes he does email back] and I've used this blog venue a time or two as well so I think I can call you Steve now.  I just read where you announced in front of a bunch of beancounters that you'll be selling a “new” higher priced version of Windows and Office that will be high end desktop editions. 

We have plans in the Vista generation to introduce an Enterprise edition”

Oh please don't.  It's bad enough that we have to deal with convincing folks that Windows XP Home is ...well..for HOME and not for an office, it's bad enough that the Dell Small business sales catalogs feature XP Home, it's bad enough to wade through the versions of Office [and no ..the Student and Teacher edition should not be a valid version for a small business].  But when you say you'll have an “Enterprise version” that will have high end features...watch it, Sir.  You know us small businesses can [and many times do] have more of your new technology than older firms.  I'm 110% Borg now [the added 10% is due to the Smart Phone we just got].

Don't say “Enterprise” and only think Big Business.  Show me a large firm and I'll show you a lot of older stuff.  Show me a small firm and I'll show you a firm that's a lot more agile.

Be careful in your targeting of this product, Steve.  “Enterprise” is a state of mind, not the size of a firm.

We're looking to start a support group for former Enterprise Admins who are now SBSers

<with special thanks to the fabulous, beautiful, charming and brilliant Lanwench who graciously allowed me to steal this from something she wrote about her thoughts about SBS.  In this post she lists all the things about SBS that may [will?] drive Enterprise Admins to drink about SBS>

Some things that people will need to watch out for – especially after they do it the “old fashioned” way the first time and then realize that some features don’t work right:

 

  • When setting up workstations themselves, don’t name them what you want to end up with – you have to add the computer accounts using the wizard and then pick the name you wish for that PC during /connectcomputer
  • Don’t change OU names, or move computers out of the SBSComputers OU – if you don’t create the computer accounts with the wizard, or if you rename OUs or move a lot of things like group policy won’t work right, annoyingly!
  • Don’t move users out of the default OU either
  • I believe that the template account one uses when creating new users with the wizard doesn’t set up roaming profile paths (not sure) [Susan – no it doesn’t, this is another wizard]
  • During the SBS Setup, presuming one has configured one’s hardware RAID already & created the system partition, one can simply cancel out of the wizard when it’s time to select the paths for various things like the users’ home directories, data folders, profile folders, etc – can create the additional partitions/assign drive letters as needed, and then click the ResumeSetup shortcut on the desktop. The doc/wizard doesn’t make this obvious. Or, one can alt+tab to computer management/disk management & create the Exchange/data partitions then, and then go back to the setup wizard
  • User quotas are enabled by default (I think) – if one is like me, and hates these, turn it off manually [Susan – by default and yes I turn them off as well]
  • Circular logging is enabled by default in Exchange – if one chooses to use NTBackup instead of SBS Backup, this will not be changed, and must be deselected manually in ESM
  • (I don’t remember whether the mailbox quotas are set up by default on the store, or, if they are, whether the dangerous “third trigger” is set – I don’t like or use that one) [Susan  - on by default, I also turn them off]
  • The CEICW needs to be run as it is entirely possible to do everything it does manually, but it takes a lot of steps – in IIS, access to OWA and RWW, etc., will by default be set up to deny connections from anything other than localhost & the LAN IP range
  • The POP connector may sound like a great thing, but don’t use it – get your client to register a domain name & host his own mail. POP is for clients to talk to servers, not for servers to talk to servers…and you shouldn’t turn your server into a client anymore than you should turn your server into a router (the latter is the opinion of this writer and does not reflect the editorial stance of this station)

 

Note: SBS is a great bargain, but you have to do a tradeoff of sorts. You can get an SBS network functioning pretty well without using the wizards for some stuff, but not all of it (until MS decides to release a painfully detailed doc outlining *exactly* what, and where, the wizards do stuff). IT Pros may not like “black boxes” (I don’t!) but for the price point on SBS it’s worth it to most small businesses – so one has to cede a degree of granular control if one wants things to run properly. It is *always* good to know what is happening under the hood of any system – wizards should not be a substitute for knowledge, but just give up & run the wizards and it will work out all right. There is probably a therapy support group for enterprise-product admins who have gone through this. I’m looking for one.

You know you are a geek when...

You are standing in the bank and you recognize the exact make and model of the Dell small terminals they are using as teller workstations.

You stand in such a way to see the screensaver so you can see what OS they are running [Windows 2000]

And when the teller is unable to do a search and brings over another teller and says “This is giving me an error message saying I have an ODC error and it's not giving me any results

...... and you stand there as they are discussing the issue for a bit before piping up and asking “Is that an ODBC error?” 

Oh yes

“uh if it's an ODBC error that's indications of an underlying problem connecting to the database and you won't get any results back”

And now two bank tellers are a little more knowledgable about their computer systems and the standard errors that indicate ...just take the money of the person who drove to an ATM to get it and send her on her way and deal with it tomorrow.

I argued with a computer today

So I'm at a bank and in order to complete the transaction with involved ordering historical items, I needed to pay for the copies of the items.  Problem was, I wasn't a customer of the bank.

Do you take checks?

No, cashiers check, cash or money order.

Okay.

So off I go to find the nearest ATM...

So I call the cell phone 411 and instead of just talking to a human at that point I talk to the ATM finder computer system for a Bank ....a Bank that's located ...in America.

Would you like to find an ATM or Branch by zip code, street or phone number?

hmmm how about City as I don't know the street..that's why I'm calling... okay let's try street.

Street.

Please state the City and State.

Clovis, California.

That was Delano, California, if this is right say yes, otherwise say go back.

Go back.

Please state the City and State.

Clovis, California.

That was Kerman, California, if this is right say yes, otherwise say go back.

Go back. [grrrr I'm thinking]

Please state the City and State.

Clovis, California.

That was Calwa, California, if this is right say yes, otherwise say go back.

Go back. [No, I'm thinking.. CLOVIS...geeze, I mean I am on a speaker phone and sometimes I don't pronouce words as clearly as I should but geeze]

Please state the City and State.

Clovis, California.

That was Colma, California, if this is right say yes, otherwise say go back.

Go back.  [really grrrrr now, how can they not hear CLOVIS, I'm really pronoucing the word as clear as I can now]

Please state the City and State.

SEE - ELL -  OH -  VEE -  EYE -  ESS .....Clovis, California

That was Kerman, California, if this is right say yes, otherwise say go back.

Go back. [in a very loud argumentative voice this time]

If you'd like more information, please visit our web site at www.bank that is in america.com.

I'm in a CAR for heavens sake obviously not paying the attention that I should ...how can I get to your web site?  I haven't fixed the Audiovox yet for one!

I called the Cellular operator. I told him it was so nice to talk to a human. 

"I haven't got the slightest friggen clue what you just said."

Sometimes you get the funniest things said to you.  It all started when someone asked how to stop spyware and even with Firefox and a firewall they were still being infected and overwhelmed.  And I told them in addition to the Microsoft Antispyware tool that they really needed to pushing to stop using local administrator and instead try to move to restricted user mode to better protect that computer.  That antispyware software wasn't enough, that we truly needed to stop running our computers with local administrator rights. 

I knew though that they will have line of business applications and thus won't easily be able to do this.  So I explained that they needed to urge their software vendors to better support 'restricted user'.  And as a result of my email .... the response that came back was.....

"I haven't got the slightest friggen clue what you just said."

Steve Riley says tonight that he and Dr. Jesper Johansson have an idea for a second book for home users [you do know about their first book don't you?  You should!], and there's a section in the outline that talks about “Running with least privilege”.   But already I can hear the poster that said that to me, read that outline and go ...... “I haven't got the slightest friggen clue what you just said."

And there's the rub.  Here it is a basic foundational rule in security... only give those rights that you absolutely must, and most of us haven't got a slightest friggen clue about what it's all about.  Aaron says “The security principle of “least privilege” is well understood:  Software should run with the smallest set of privileges needed to perform its tasks. “

Understood by whom?  Certainly not with the folks I hang around with.  Certainly not home users.  Certainly not buyers of software that haven't a clue that that Accounting application you just bought, that is a pain to make run as restricted user, is actually causing you, forcing you to run your system in a very insecure way.

Even in the Ebook/College notes for the Teen's guide to safe computing “Always use Protection”, I don't see where Dan talks about restricted user at all.

So here's to the day that I don't say the word “restricted user” and someone doesn't say ....."I haven't got the slightest friggen clue what you just said." 

In my view it can't be soon enough.

I had a local admin on a desktop...I don't anymore

One more down... a few more to go.  Slowly and surely I'm taking back the use of local admin from the workstations.  Yesterday one of my computer users got one more pop up on her IE and it was driving her crazy.  So I sat down and tweaked up the registry so she could run as restricted user.  Now you can say that if I had her use an alternative browser that would be the solution, but that's not the issue here.  It was clear that she had been tricked into downloading things.  So the important part wasn't to change browsers, but to protect her from getting tricked into clicking and installing.

More importantly too is that any application that requires...that demands local administrator should be put on notice that Microsoft “Vista” [the new name for Longhorn] has got a name and is that much closer to doing more on LUA.

It's time to take back our rights and throw out those local administrators.

P.S. One of the reasons that her desktop was relatively easy to LUA ize....no Quickbooks on hers.

The perfect solution for a small business

If you read this article you would think that the answers to your prayers is Open Source software because of course..it's free.

There's one problem with this article.

There's only about 1%...maybe 5% of the world's small businesses can take a 'free' software and customize it, and do what they need to it without an IT pro that knows what they are doing.  The rest of the civilized world when faced with software problems on EITHER 'free software' or Microsoft software spend THEIR TIME AND ENERGY making that software work.

Newsflash for you folks -- your time is VALUABLE.  Put a rate on it.  And the next time you are banging your head on an issue, add up your cost.  Take for example the issues we've had with Service Pack 1 on SBS.  You do realize that when there are issues with security patches and service pack installation issues on SBS it's a free call?  You do realize that while I would say the newsgroup rocks, there is a team of Motherships out there to support SBS?

Nothing is life if for free.  It takes time and energy to implement.

What you really need is good advice, someone to tell you what works, what they've implemented before for your sized firm.  Going to anything 'free' does not mean your budget for IT will be less.  I've migrated too many times to know there is a loss in productivity.  That learning curve is NOT easy.

So maybe learning new 'free' stuff works for some...doesn't work here.  And certainly not something that most small business owners care to do or take the time to figure out.

They need to do their job, not learn how to compile or roll their own patches [as the Open source community are apt to tell me is one of the benefits].  Pick the right software, but above all else, get the software that is supported for YOUR sized organization.

That is truly what is important.

 

MCE on a SBS domain

Media Center Edition.  Think it's just for the home?  I think there's another untapped marketplace out there.

At the SMB Technology Network several of those in attendance mentioned that they were getting asked about installing MCE in the businesses' conference rooms.

There's just one problem... they can't join a domain.  So unless you use a googlable info on having them join a domain, use “pass through authentication”, you really can't have them in your SBS network [you know me on wanting to make sure all workstations are controllable].

I still say everything should be domain-able....but that's just me....

p.s. when I say domainable -- I mean out of the box and supported by the vendor...not upgraded from 2004, not only available on a clean install, not there if you hack it... I want it there all the time in a supported condition.

The incident

Longhorn following Unix on security? | The Register:
http://www.theregister.co.uk/2005/07/11/longhorn_security/

"In October 2003 someone asked: 'How come, when I go to a Windows machine, everyone has to be an administrator?'," Nash told conference delegates, referring to an incident at Microsoft's partner conference two years ago.

Jeff Middleton SBS MVP asked that...and yes we SBS MVPs are very proud of that fact.

Don't forget...it's up to us to now push our other vendors.

The shades of color between black and white

Someone posted something...and me in my stupid reactionaly opinionated way, emailed the poster back and argued that the point he made was missing the bigger picture.  I argued that with XP, the use of blank passwords wasn't the threat it used to be and that in a home setting, may not be as bad as you think.  For example, the default setting in XP is that you cannot connect remotely to the Administrator account over the network if the local Admin account is blank.  I've tried it... once when I forgot to set the local Admin password and I was trying to do something remotely and it failed.  I applied domain administrator credentials and remoted to that machine just fine, applied what I 'though' was the local admin and no go.  Well I finally realized that I had a blank local admin password.

Bottom line in the emails that went back and forth...and before he finally blocked me from emailing him, I couldn't get him to see any different color than what he wanted to see.  I tried to tell him that Dell Optiplex's don't do this.  That a blank local administrator password [assuming you had physical security] was in some cases actually more secure, and that if you had physical access [which is part of his post] ...you could just reset any password set up anyway.  I've done that several times myself.  And here at home with my not yet domain-ed new workstation, it hides the true local administrator in the User account view.

Remember law number 3?  If I have physical access to a computer the game is over.  That the fact that a password is or is not there is irrelevant now?

It gets back to users [and I would argue home users] don't want to be bothered by all this information.  We already have information overload, too much spam and my hairdresser still says she hates computers.  They want security handled for them.  Managed.  Made easy.

So many times, myself included, get stuck in this black and white view.  That there's only one way to do things, one way to secure things.  Heck... you tell me that you don't like ISA server, that you are setting your SBS up with one NIC and I'm practially hyperventilating.  And really I shouldn't.  Because there are indeed may ways to secure things.

So Michael?  I know you won't read my emails anymore, nor will you probably read this, but the fact is we've got bigger security problems to worry about in my view than this one.  I'm still ranting about applications that require administrator access, or ones that don't secure data properly.  I'm complaining about the bloatware on Dell OEM machines.

I'm not an idiot.

I just have a different opinion than you.

And that's okay...because you see there are indeed shades of color between black and white.

The human impact of Sasser

You know...too many times we live in a fast world and don't think about the impact that technology has ...good...and bad....

In Stepto's blog [Stepto works for the Microsoft Security Resource Center] he talks about the personal impact Sasser had on him.  Makes my impact in Vegas last year ...pretty trivial.

You know.. behind 'big bad Microsoft' there are people.  People that care.  People that do work hard.  I'm mean yeah I'm sure they also hire jerks a time or two, but all in all behind every cold company is a bunch of just plain old people like you and me.  Wanna know what wacko thing I did?  Just to say thanks for being there and monitoring security 24/7... on New years eve I sent an email of thanks to Secure@microsoft.com right at [or right near anyway] midnight my time.  I mean yeah it's their job...but that's still someone giving up time away from their family on a major worldwide holiday after all.

I got an answer.

I've emailed Steve Ballmer...and every time SteveB@microsoft.com emails back. 

P.S.  Can't say the same thing for Michael Dell.  Never got an email back....

Perhaps he needs to hang around the Security newsgroups a bit?

CNN.com - Sasser author gets suspended term - Jul 8, 2005:
http://www.cnn.com/2005/LAW/07/08/sasser.suspended/index.html

Okay let me get this straight....because he 'created' the virus when he was 17, but only released it on his 18th birthday and thus not an adult.....he's on probation for 21 months and only 30 hours of community work?

Honey... sit him down in the Microsoft Security Newsgroups and make him answer newsgroup questions at 1 hour a day for those 21 months.  Now THAT would be proper treatment of this guy.

I was in Las Vegas and Tech 2004 when Sasser hit and I'm sorry...but 30 hours of community work for the impact of that worm is a total joke.  We had entire vendor booths that were put out of commission and thus looked a bit foolish at a technology conference.

Folks, until we get judges and laws that realize that this is a crime, that it has major impact... I'm sorry but this is a bit of an insult for all in the Security community who fight so hard against the bad guys, worms and viruses and what not.

Yeah give him a second chance...but make that community work have a bit more impact than this...

....oh yeah..and one more thing.....he now has a job.

The Motherships

If you are a reader of the blog you'll have heard me talk about the “Motherships”.  Basically it's those folks around the world that are tasked to keep an eye on us. 

Sometimes those folks need our help.  On Charlie's blog is a reminder of the power of 'us' reporting into the “Motherships”.

Right now they are seeing rare BSOD's in applying Service pack 1 on SBS machines.  Now it could be related to the Dell Open Manage [you know where you have to be on 4.4 and not on 4.3] but maybe not.

IF YOU GET A BLUE SCREEN... don't hesitate one single second...don't walk but run and call Product support services and ensure you say you are a SBSer [uh...but....don't ask for the SBS Mothership because they probably won't have a clue of what you are asking about]

Then work with that PSS Engineer to get a dump up to them for analysis.  A blue screen on a computer these days is normally driver related and most of the time I don't see it affect data...your sanity yes....but not data.

So bottom line if you are seeing this... CALL.  And don't let that US $245 stop you either.  When it's an issue like this..due to a service pack installation they will not charge you.

To my hero[s]

To the consultants that see SBS as a solution to a business needs.

To the consultants that refuse to install Terminal Services in application mode on any domain controller.

To the consultants who refuse set things up insecurely.

To the ones who will lose a job rather than reduce the amount of security they recommend.

To the consultants who push clients to lock down desktops, install XP sp2, lock down Exchange, install SP1 and WSUS

Thank you for that.

Keep up the fight.  We need you doing the right thing.  Setting the bar.  Thank you for that.

An interesting comment tonight... “one thing we say to a lot of our enterprise customers is you should be more like our SBS guys..... they generally don't have spyware and malware problems....but the big guys do... Why?  Because it's actually quite easy to lock down a small business network you just have to convince the owner...and it can be deployed very quickly....“

Oh can I kiss the man that said that?

 

Dell, OEM, WSUS and Ed

Reading Charlie's blog  on an issue with Dell Open Manage 4.3 and below and SBS 2003 sp1, reminded me that I've not seen any resolution for you guys on the issue with getting WSUS installed on Dell OEMs. 

For one, because I don't have a Dell OEM, I can't get a support ticket opened up to ask about it and there is nothing on their Service web page that I can tell that confirms or denies the issue we are seeing where we can't get WSUS on a Dell OEM machine.   It's getting stuck on the Dell supplied IWAM account ...and while it 'shouldn't matter' ...apparently it does.  I don't like to be too alarmist if I don't personally see an issue, but all I know is that I've had too many folks report this issue to not take it as gospel.

Ed complains that Bloggers shouldn't get preferential treatment when we publically complain ...and Ed... I quite agree with you.  In that respect my blog is no different than the 'full disclosure folks' I rant about.  One shouldn't have to have a vocal hissy fit about something that is broken to get it fixed, the vendor should just do something about it. 

For me, I'd personally like it if Dell would have some sort of designated liason with the SBS community.  I'm sure we sell enough Dell boxes around here.  But when we're just hitting a brick wall ...sometimes it just makes you feel better to hiss...well, just a little anyway.

So for any of you folks that ARE seeing this issue and DO have a Dell support contact?  Can you do me a favor and see what the status is of this?  Feel free to ping me or contact via the blog.

 

Hotfix? Got yur' hotfix?

Microsoft Hotfix.  I need a hotfix.  

Need one.  And normally at like 12:30 a.m. on Saturday night... I don't know what's up with that.  Call the 800 number for Microsoft.  Press '3' [at least I think it's 3?].  Rattle off, “yes I need hotpatch blah blah”.  Talking to a very aware and awake person at 12: 30 a.m. in the morning even.  Okay.  Email address is “blah“.  Got it.  Yes I know it's not regression tested.  Yes I'll put it in a test network first [yeah... I'm testing it in my production network..]  Done.  Sent.  Received.  Got it.

End of transaction.

Antivirus vendor hotfix [for a firm that will remain nameless]

Call for a hotfix.  It's an 800 number but only Monday through Friday until 5:00 p.m. Pacific time [uh..okay] So I call... I say I need a hotfix.  The guy asks 'have you tried to change the registry to '1' and see if that works'.  “uh, well since you close at 5 and I have to do the computers after 5 in some cases I want to have it just in case”.  “ok”.  After a bit of back and forth he indicates I need to be called back by a next level engineer. Which of course means....tomorrow.

By the way this is the fix for the 'roaming clients' i.e. laptops that won't connect back to the mothership to get their dat file update.

But why is it so hard to get hotfixes?  I mean we complain about Microsoft's procedure [and admittedly in the USA I'm spoiled as I CAN get them 24/7, some of my fellow SBSers are not as lucky as I].  So why can't you stick them on a web site, let me click through something to register for them so you can follow up, and just let me download.  You don't have hours that match up with SBSland's need for technical hotfixes, so why make it difficult like this?

Just seems like this could be streamlined is all.

What time is it?

What time is it?  No, really, what time is it?  If I wanted to meet up with you at 8:00 a.m. tomorrow morning and you were in a different time zone, what's the best way to make sure that I arrange to meet you at the right time? 

It's a little thing that I take for granted but has been nailed on a couple of times and in fact found this very Tablet PC didn't have the little check box checked to ensure that daylight savings time would be automagically converted at the right time.

So here I am doing my rant about the issue that I have about OEM machines not “keeping' that check box even though as you load up the computer you check the box.  So much so you should have heard me and John Levy at the AICPA Tech Conf.  He argues that outlook should not be hooked to the computer time and in fact should be relative, whereas I beleive it has to be based on GMT.

Well imagine my surprise when I've heard of a worse issue than mine.  Because we are a world wide world and global community, we need to worry about what time it is around the world.

Fellow MVP Steven Teiger brings up his headache about time greater than any headache I have.  In his time, the government sets the time zone when they decide and not by standards. 

Can you imagine not having your time automagically taken care of, but rather, on the decision of politicians and thus you have to scramble to make the time change consistently?

If you've never had to unscrew up a Group calendar when the calendars aren't in sync, well you just haven't had fun.

So next time you complain about that annoying check box that doesn't keep track of the time, there's someone else who has to deal with something way more complicated than you do.

Standardization is indeed a good thing.

The Advice

Was watching a show on Showtime about “Life Coaches” and the statement was made that we don't take advice seriously until we pay for it.  It's funny I was just talking about this the other day to a fellow MVP about how it amazes me that people will not pay the Server price call of $245US to Support, but instead will bang their head on an issue.

When something happens in my network, I have various tolerances for 'action plans'.  If it only affects me, I'll put up with the issue and google.  If it affects the entire office, I've got the credit card out and calling.  We're not making 'wigits' if the network is down and thus the more people that are affected by issues, the faster I'm calling.

While my SBS doesn't go down much at all, when I do have issues, calling in the proper amount of help and not spending hours on an issue just is not a reasonable plan.

Ask yourself.. how much is this network affected? What are they losing?  Can you work around the issue?  You know XP workstations can use cached credentials and they will log into the local profile.

Just think about that the next time you spend hours on an issue.... how much ... what's the real cost of that call?

It might be less than you think.

Duct tape, plastic and cardboard

I hope you forgive me... normally this is a technical blog. But tonight I've been watching Apollo 13, a movie I've seen before, a movie I know exactly how it ends, but no matter how many times I watch it, I end up during those last four minutes grabbing a kleenix and just getting inspired about the power of man [or of woman for that matter] to make a difference.  With impossible odds, with plastic, duct tape and cardboard, a group of minds overcame hardship, overcame technological odds and brought three men back home.

It reminds me of the power we have as humans.  Don't think we do? Listen to the reading of this American document that is always empowering to me.  I'd rather not think of it as a document of war, but that's what it is, isn't it?  But I don't consider just an American document, I consider it a worldwide document of the power of an idea, the power of humankind, the power of change.

I think I was about 11 or 12 years old when I visited the East Coast and saw where this document was born.  I still remember putting my shoes on the worn doorstep and walking into the room where this was written and thinking that I just stepped in the exact place where over 200 years ago, people gathered to decide to take a stand.  I stepped where those men stepped.  I stood where they stood and thought of the declaration they made for change.

Listen to the words.

Remember these words were written by humans, normal folk like you and I. 

It always reminds me, inspires me that we can make a difference.

We've come a long way as mankind since then.  We've gone to the moon and back.  Heck, we're doing a bit of space stuff this weekend even.

My wish is that we do more to realize that we're all in this world together and get along.  That we've got a small planet.  Really just a dot.

Call me silly, but to me the daily war you and I wage out here in keeping your clients safe and secure is more important than any national issue.  It is a war.  One that I have every confidence that we can win.

...and don't forget... duct tape, plastic, cardboard and and some smart thinking got three guys in a broken space ship back home.  Just think what we can do with the technology and brain power from around the world that we have now.

News at 11

 Crazed woman arrested in Fresno after she disrupted a United flight from Las Vegas to Fresno.  Passengers say that the woman unbuckled her seat belt during take off and crawled over the seats and began strangling a passenger two rows behind her.  When questioning the surrounding passengers they said "I really don't know what happened."  "One minute the guy was just discussing to the passenger next to him, how he downloads stuff through Morpheus and how it loads up pop ups and gunk on is machine and every so many weeks he uninstalls Morpheas and then uses Microsoft Anti Spyware to clean up his PC and then reloads Morpheous and starts over again".  "He said that he didn't want to pay for Morpheous so he just put up with the pop ups and ads until it got really bad and then used the free Microsoft Anti spyware"  Passengers said "the next thing we know she's screaming at the top of her lungs and got her hands around his throat".  They said that the female passenger calmed down a bit when the gentlemen praised the Microsoft product for being so good [and free] in cleaning up his machine on a regular basis. and the fact that he was urging a fellow passenger to search on the Microsoft site to download it and  install it on his machine.

The woman was carted away muttering..... "risk... he's actually ACCEPTING spyware as a reasonable computing experience because he's so cheap and sees this as perfectly fine"

Family members and a group of folks called MVPs were not available for comment....


........................

Okay ...so I didn't climb over the seats, strangle him, nor get hosipitalized...but everything else is the truth.

So we're a bit high maintainance females

You would think Anne and I would fight over the TV station or where to eat or which sink which one of us is going to use in the hotel room..but no..we fight over the high speed access.  Thus this time in my geek travels I brought with me a tiny [and I do mean tiny] Dlink Wireless AP that broadcasts the room's connection.

So for those folks on the 17th floor of the Spa Tower at the Bellagio...no the hotel doesn't exactly offer wireless connectivity... you just have two geeky gals that hate sharing one wired connection so we made it easier to connect both of our laptops.

 

And yes, it's reallllyyyyy tiny.

Piracy in Software

What do you get when you purchase software?  Think about it... it's instructions, it's a cdrom..but what really 'is' it?  Is it a manufactured item?  Not exactly is it?  It's someone's brain cells in a silver cdrom isn't it?  Think about it.  It's someone's ideas, thoughts, goals, brain power, it's all of that isn't it.  And all we do is “license” it.  We don't own it.

So I just don't get it sometimes when people ask about buying software from somewhere and the price of that software is just way way way too underpriced to be legit.  A couple of instances occurred recently when someone asked about software being sold on Ebay [red flag number one] and the Ebay seller said that the transaction involved “evaluation software” and you would then get a registry program to tweak it to be a full software.  

Say...whaaaattt?

The only way you can get full software from an eval is BUY full retail versions and install it over the top of the eval.  You don't lose anything other than the time bomb.  There is no such thing as a tweak program.  Next is the bogus issue of selling OEM software with something as stupid as a mouse.  I'm sorry...but OEM Server software means you HAVE a server..not just a mouse... to go with it.  And then there are sites that offer 'downloadable“ SBS software.  Excuse me?  We don't even download the Premium version of SBS service packs and have to order those by cdrom.

Software licenses have a price tag...this isn't the normal marketplace...this is the price that has been set for this software.  So that if you see someone selling a SBS Standard at a beginning Ebay auction price of US $40...that isn't a value that has been set by marketplace factors ..... not unless you call selling not for resale product, or selling pirated versions marketplace factors.

As a result of all this bootleg stuff...we all pay.

Just keep that in mind will you...the next time someone asks if a cheap software is a good deal, remind them that they are stealing from all of us.

Just remember.... we all pay for piracy in the long run.

Still having issues with backup and monitoring after SP1 and the KB doesn't work?

Lrob pings that he's still having issues with backup and monitoring..... However, that particular fix does not work for me. And I am about to take a gun to this unit. This did happen after a service pack update and also broke the MSDE icon that sits in the system tray. Before the service pack it had the green arrow and would list the server and associated database. Now, no arrow, no database listing. It has been this way for a while and does not seem to be affecting the server operation except the backup and monitoring pages. I have looked everywhere and have tried different things. Is there anything else related to this that you know of?

If you've tried that KB, that's all I have... if it worked before the service pack...then call product support services and get help on this.  Don't let the threat of the price tag scare you.... once the issue is identified as being caused by a security patch or service pack, the issue is normally a free call.

Also the icon can be removed and it's merely a leftover from a SQL patch.

The best advice I can give is to call.  For those that are supporting customers on SBS... sign up for the Microsoft partner program as they have Business down support offerings.

If you are supporting customers on SBS and are not a Microsoft partner...can you come a little bit closer to the monitor?

Closer?

<wack upside the head>

Why aren't you?

This is your business and why aren't you getting all the tools and resources you can to best support your customers?

 

When things screw up...reinstalling is not the answer

Today I had an issue with a SQL application...one that I was banging my head on for hours.  And I called in support in the form of a very talented MVP who fixed me up in less than 2 minutes.  2 minutes.

Today in the newsgroup I see, once again, folks that get into a bit of a bind and then think that the way to get them back in business is to do a clean install of the server.

Folks ... a server is not a workstation that you blindly flatten and start over again.  Those workstations hanging off of that server will totally freak that you've changed the 'glue' they once used to stick themselves in the network. 

If you get stuck or in a bind.. don't flatten, don't bang your head, don't reintall... CALL.  It's worth every penny to call Product support services to get their help.

Don't forget...call when you get stuck.

You know you are a geek when....

You reach in your purse to show off your 1 gig usb thumb drive and compare it to the CompUSA salesman's drive [his was smaller but still a gig]

You tell him about the USB pen drive that is a Writing pen and he didn't know about it.

You can remember when 1 gig was a large harddrive in a brand new computer [and these days they have 400 gigs in CompUSA]

You remember when the operating system and Lotus 123 would fit on the same bootable floppy disk.

When you travel, you seemingly end up in cities that contain Frys electronic stores [what's up with that?]

You buy things at Frys Electronics stores and ship things back home when you buy too much.

You were extremely pleased when Instant Messenger raised the limit of IM buddies from a maximum of 150 because you were starting to have to look at folks and wonder if they were IM address worthy.

Your Amazon.com book purchasing list is populated with [as Brian put it] books by Security Freaks.

You just went to a clients today, and while there when they got DSL installed, you immediately jumped them over to Microsoft Update and explained how the little icon would show up next Tuesday.

You strike up conversations with fellow plane passengers about “Patch Tuesday”.

You don't listen to music on your MVP MP3 player, but rather Security presentations.

Yeah... I think I got it pretty bad....

Proud owner of several Porsches

I HATE TAPE DRIVES.

Now that I have that out of my system.... let me tell you why I hate them.

For one my Sony Quad tape drive decided to stop working over the last couple of days and the more days that went by that I was only able to backup to a physical hardrive on my network and not remove a copy of the data offsite [especially after the BBQ incident the other day] the more nervous Nellie I got.

You see for the last couple of days the tape drive would suck in the first tape in the quad but never fully load it up and get it ready to go.  I tried making sure the SCSI cable was tight, that the backup software was updated [it's ultrabac], that the scsi card software had the latest driver.  And then the annoying part of the Ultrabac is that it doesn't use a signed driver for the Ultrabac quad loader and can't use the Sony digitally signed driver ...and well.... I'd finally just HAD it with tape drives.

I'm still going to send it in to get it fixed as I think it's the heads or alignment or something, but during lunchtime I stopped by CompUSA [we don't have a Frys here] and bought a bunch of large LACIE harddrives.  At first I was not going to hang the USB2 off my domain controller and bought a USB2 card for the member server where my Terminal Server and Live Communication Server is loaded, but every time I went to install the USB2 card, the video on the member server wouldn't work.  I don't know about you, but while a headless server is okay, it's not my favorite way to start out a server install.  Now with the video being on board, and no switches on the USB2 card, it was a sign to try the LACIE on the server.

So with much trepidation, I plugged it in the back of my SBS 2003, crawling on my hands and knees with a flashlight to find the USB slots, getting my formerly dark outfit that I am wearing progressively grey with dust bunnies in the process.  I found the USB slot, shoved it in, closed my eyes, crossed my fingers and crawled back out to see what it was doing on the server.

It found the drive.  It gave it the letter G.

Sigh of relief.

So off we go to backup the server.

I think I might get used to this.  For one I can literally browse to that G: drive and see the ultrabac backup files there on the drive... tape drives you have to run the header report.  For two it's faster.  For three... well for three it was a heck of a lot cheaper to buy a bunch of LACIE drives than to buy a new tape backup unit that's for sure.

Apparently I'm now being backed up by a Porsche

P.S.  backup finished in 2 hours exactly... I think I might like this....

Are you an Admin? Should you be?

From the Administrator Accounts Security Planning Guide

 

If you regularly log on to your computer as an administrator to perform common application-based tasks, you make the computer vulnerable to malicious software and other security risks because malicious software will run with the same privileges you used to log on. If you visit an Internet site or open an e-mail attachment, you can damage the computer because malicious code could be deployed that will download and execute on your computer.

 

 

If you log on as an administrator of a local computer, malicious code can, among other things, reformat your hard disk drive, delete your files, and create a new user account that has administrative privileges. If you log on as a member of the Domain Admins group, Enterprise Admins group, or Schema Admins group in the

Active Directory® directory service, malicious code can create a new domain user account that has administrative access or put schema, configuration, or domain data at risk.

 

--------------------------------------------------------------------------------

 

Oh ..go ahead...say it... “But SBS loads up the workstations in administrator by default“. Yes it does.  And why does it do that?  Because 99.99% of my line of business applications will not work unless you either

 

     a.  run as local admin

     b.  Hack the registry to death

 

 

I made this point to the CPA meeting we had up at Microsoft, that to demand using restricted user rights wasn't Microsoft's problem, it's OURS.  It's our vendors that we need to push to do this right, especially for Longhorn coming.

 

As much as I love to rant about non-admin, I wasn't about to drag myself out of bed at 5:30 in the morning to watch the web cast by Aaron... I'll get the recording   In the meantime the TechEd Bloggers look like a few are finally 'getting it'

 

Now... go talk to your vendors... they are the ones who need to get it.

You would think a phone company could call or email or something? Having issues with PacBell DSL?

DSL went out at home and my sister did all the things she thought to do... unplug the DSL modem, unplug the Linksys router, but no go.

So I get home, log into the router and it says PPOE authentication failure.  Hmm... so I try resetting it and no go.  So I check to see if it's just a network issue and fortunately have a dial up backdoor account to Pacbell and get the tech support phone number.  And as I answer the voice activated menu, I get to the point where the nice lady says “There's a network tech note, please press pound if you'd like to bypass this message

Ah ha.. must be network connectivity issues.

“As of June 2nd, if you are a Pacbell customer you now need to include @pacbell.net in your authentication information”

WHAT?  You have GOT to be kidding.

Went to the linksys... added the @pacbell.net to the PPoE log in screen.

Sure 'nuff.  That was it.

Okay Pacbell...exactly HOW would I know this?  Did you send me an email 4 days ago?  Call me?  Send me a note?  Smoke Signals?  Anything?  Where did you tell me this?  And thank goodness I have a modem still in my desktop as a backup to get the phone number to call you and find out this was it.

Bottom line if you have residential DSL from Pacbell, and assuming you can still read my blog, go fix your PPoE authentication and add “@pacbell.net“ to get your residential Pacbell DSL working.

Like Eriq has said before with his issue on Verizon... for telecommunications companies, they sure suck on communication.

Professional Identity Theft

I got a call today from a mortgage company to confirm that I did the bookkeeping and tax return for a client.  Slight problem.  I didn't recognize the client.  Next problem, the woman from the mortgage company said the letterhead that was typed up had my full name on it.  You know...with my middle name that is only on legal documents and Board of Accountancy web sites.  Next, while it had the firm address, the letter was typed with merely my name on it, and did not have the firm I worked for.  Any letters that I write have my firm letterhead on it, and would not merely have my name, and definitely not my middle name up there like that.

Now after I've slightly stopped freaking out over this... I'm contacting the State Board as there is indeed enough info on that site and my firm's site for someone to pretend to be me.

Hmm.... think Al Gore ever envisioned the Internet to be used like this?

Putting you guys on notice

If you are a blog reader you'll know that WSUS is finally out and for us SBSers, you should understand that this is step one, a big baby step on the way to perfect patch management system.  For us premium folks, it won't patch ISA Server, so we'll still need to watch for that [but honestly ISA hasn't needed too many specific patches]. 

What does this specifically mean to us? 

For one, when you come into the newsgroup saying “I've patched my server” I'll now ask you if you are using WSUS and “really” patched your server.

For two, I'd really like you to think about controlling when you patch and do an approval process and think about zoning your systems so that not everyone just automatically updates.  For example, I truly think it's not a good idea for servers, your critical business tool, to be downloading a patch and rebooting on Tuesday night. 

Samanatha Bee may joke about Patch Tuesday, but I call it Dead Body Wednesday as invariably there's one person who automatically updated their server and due to a misconfiguration, didn't go through the trip well.  WSUS is another tool in taking back the desktops and protecting them.  A huge tool for patching your servers smarter. 

On page 521 of the Dr.J/Riley book, there's a page called “How to get your Network Hacked in 10 easy steps” and number 1 is “Don't Patch Anything”.

Well guys, while I would still say this isn't my 'perfect' patch tool since it doesn't have the SBS specific patches like Shavlik does, nor does it appear to be able to install and download our SBS 2003 sp1 [mainly due to Exchange, as it's my understanding that patch can't be silently installed] it's a vast, vast, improvement over merely using Windows update.  I don't think it will help us to get to Service Pack 1 [nor would I want it to as our Service Pack is too big], but it will help us to patch after that.  It can be installed with or without the service pack installed and is not dependent on that being on your box if you are worried about that.

Gentlemen, start your downloading.

Samantha is right, the lines to the ladies room is very short

In the beginning of the Tech Ed keynote, Samantha Bee from the Daily Show talks about what we call the “bathroom line effect

Us geek gals have no lines for the bathroom.  In fact, I've been in Tech Conferences before and I can attest that you could practically roll a bowling ball in the ladies room and you'd probably not hit too many gals in there.  Yet I know several Tech gals, that are the glue of their communities.

But to summarize, TechEd so far has announced:

Now at this time WSUS and MU doesn't patch ISA server 2004...but then again... ISA Server hasn't needed too many patches  :-)

Notice that all those things that are talked about in that customer experience video is what we SBSers already have under the box?  Exchange 2003, Sharepoint, ISA 2004, in fact with the new Active Sync, it's easier than ever to set that up.  I think Wayne is going to blog about that soon.

Sorry Amazon.com, it wasn't you after all

I'll be surfing out on Amazon.com and after I've stuck something in the shopping cart...like...oh .... Dr J's and Riley's new book..... I'll click the back button and I get a page not displayed.

Rats.  Stupid Amazon.com.  Does this to me all the time.  Really annoying.

Well I was out checking knowledge base articles and found this:

FIX: You receive a "Page cannot be displayed" error message in Internet Explorer when you browse back to a Web page that contains data that you previously submitted after you install Windows XP SP2:
http://support.microsoft.com/?kbid=890178

No WONDER I keep getting that issue.  It's NOT Amazon.com at all.  Remember this is a call for a hotfix, now why this isn't more available, I have no idea, but at least I can call for the free hotfix.


Update ...okay I'm confused.... if I get the hotfix it says I need to enable it by entering a reg key, but if I have cumulative update the steps do not have to be followed.  Have you seen these hotfixes that are like this that have 'reg key enablers'?  Outlook Express has a bunch of them too.

hmmm... I think I'll do the workaround.....

Being agile

Being involved in events and traveling always reminds me of making sure that you keep a view of agility.  I'm once again cross legged sitting on the floor because the seats are full in the waiting area at the airport and I'm going standby on an earlier flight.

Being somewhat a bit involved in making sure the last two days went smoothly as my last official role as Chairman of the California Society of CPAs, technology committee meant that having a cellular access was key to keeping in touch with those who were helping to organize the event.  At the Microsoft campus, while there is wireless, in the area that I was in, it's tied to authentication.

Afterwards when we were chatting with my SBS pals, it was clear that everyone of them were hesitent in rolling out wireless because they wanted the infrastructure that Microsoft had deployed... but there's one problem...many of the vendors that supply that two factor authentication just don't sell in the SBS space.  Either they don't offer token cards in a small enough quantity or they think adding a $5,000 piece of equipment is the way to go.

We want security, but we want simplicity...oh an can you make it cheap?

 

Software change management

When I'm using my standalone laptop that has the standalone Trend PcCillian is when I truly realize that on a daily basis I have a massive amount of 'software change management' on my PC that I do nothing to 'vet, test, or approve'.  Every month I test software patches in my office, I ensure that the software that I use is compatible with the patches and then approve them for deployment.  I manage their application.  Yet at the same time, I do nothing to test anything about software that has the ability to be automatically downloaded many times during the day to my system.  But it too is massive 'change' in my system.

Think about it...that 'stable' pc of yours gets software changed ...all....the....time.....and we think nothing of it.

Today, watch out for ..what truly is a stupid virus infection.  And what does it rely on?  Stupidity of us.  Hmmm.. gotta work on those service packs for humans again, don't we?

 

Knowing more, making it easier

Back in the hotel room before dinner, I was demonstrating the SBS I have at the office as well as my SBS at home.  ...Yes... I have two SBS boxes that I live with....and it was interesting that two comments came up that I've heard of before.

Exchange needs to be easier.

I want to know more of what I can do with what I have.

I still would argue with my fellow SBS MVPs that the process of calling the ISP, getting the MX records set up, even the wizard to set up email... the confusion over what do I call the box, local versus com, loses a lot of folks.  A couple of folks that have SBS admitted that they aren't fully utilizing it because they couldn't figure it out, nor could the non SBSized consultant they called in could figure it out.  Any Exchange 12 folks... or SBS folks out there?  Blonde that sucker down folks, because you are still losing folks on Exchange.

I then showed the folks that link inside remote web workplace for 'more help' that goes through the parts of SBS for the user view.  That has to be the best kept secret of SBS... is that internal help button.  I don't remember if they ever extracted that out and stuck it on a web site.. hey... maybe that's something I need to start blogging about as a reoccuring post topic.  I'll cut and paste parts of that help file and stick it on the blog and “Susanize” it.

Looks like I have a bit of cleaning when I get back home

So I'm remoting into the server at home and looking at the ISA 2004 firewall reports and build a daily report.  {Keep in mind you Premium folks need to do likewise} and the first think I need to investigate why, even with the ISA firewall client loaded, it looks like all my workstations are securenat clients.  Oh well, deal with that one later after I find an interesting item...well two actually... In the top browsers used  to access web sites it tells me in an office full of Windows XP sp2, I have Gator [uh oh... I bet I know the workstation that has that...I've got a troublesome workstation....hmmm .... probably need to lock that sucker down better, I have problems there] and then MSIE 5

1 MSIE 6.0 20 27019 80.60 %
2 Gator 2 5159 15.40 %
3 Unknown 27 1053 3.10 %
4 Windows Update 13 156 0.50 %
5 MSIE 5.0 1 60 0.20 %
All Others 61 0.20 %
Total 32 33508 100.00 %

MSIE 5?  5?  Is that like Win9x?  What the heck is what looks like a 9x box on my system.  Either some device... and what the heck device is that?... is reporting a wacko 9X box signature or something?

Looks like I have some investigation to do when I get back home.  I don't have any 9x system on my network... I beat them to a pulp a long time ago.  hmmmmm....I'll keep you posted.

Amazon...you are not coming through for me

Okay I'm bummed.  You see I have the opportunity to go to Redmond as part of my last official act as Chairman of the Technology Committee of Caliornia Society of CPAs and I just might have the opportunity to get the book “Protect Your Windows Network:  From Perimeter to Data” signed by the authors.... except for one teensy weensy problem.  Even though Amazon says it's released [heck they even say they have used versions of a new book for sale], the book looks like it's not going to make it in time for me to have it for an autograph. 

Rats.

Oh well, remember if you can't be at TechEd to hear them in person, you can listen to them via a live webcast:

Steve Riley on Security policies, and Dr. Jesper Johansson on the Security Configuration Wizard.

Okay who wants to place a bet that someone is going to ask him during the presentation if you can run the SCW on SBS?

Remember that while it truly won't 'kill' us, it really doesn't do much [other than if you hit the settings to kill off Windows 98 machines, then you truly will indeed have an security impact], so don't use this tool to harden the SBS box.  It's pretty well tweaked for now.

But that will fix it right?

When something is broken, it's wise to fix 'that' before doing a work around.  I had two examples come across my desktop today.  The first was a poster on the PatchManagement.org listserve who was having issues with Mapped drives being messed up after a security patch and the way he was fixing it was to reboot the server....at first weekly...now more like daily.

....that's not exactly the greatest fix for a issue with a patch in my book, I'd be calling Microsoft Product Support Services [remember issues with a security patch are a free call] and properly diagnosing that issue with some netmon tracing and what not.

The second was a blog poster who asked me to blog about the manual way to set up the ntbackup because if he used the wizard the server would spontaneously reboot in the middle of the night.  If they ran it by hand, it wouldn't.

Uh... that's not exactly a topic that I plan to blog about and I'll tell you why.... the wizard...and all wizards on a SBS box ...should world.  Remember Yoda?  Do or do not, there is no try?  Well the same holds true with the wizards.  They work.  If they don't work, fix the fact that they aren't working...but they should be working.

Applying a service pack on top of a broken connect to internet wizard isn't going to fix the broken wizard.  It might reregister a dll or two, but if there is some foundational setup part wrong, applying a service pack over something that is broken isn't going to help too much.

If something doesn't work...google the exact error or call Microsoft Product Support Services [it's called CSS these days...but I'll probably always call it PSS].  Get it resolved 'before' the service pack install...not afterwards.

Setting expectations and better communication

If there's one thing we newsgroupers don't do sometimes is properly communicate.  One of the misunderstandings around the SBS 2003 sp1 install is that we in the newsgroup went out and said “oh you don't need Windows 2003 sp1” and then now we are saying you do as step one of the SBS 2003 install.  Also the next expectation that was set was that a service pack for SBS would just as easy as adding water and stirring. 

So let's take the miscommunication... first off what we should have said was that “Don't install the Windows 2003 sp1 service pack 'just yet'.  I knew we needed it as part of our SBS installation and just said “don't install it“ but we should have been clearer that we meant that you didn't need to do it just yet.

As far as applying service packs, I've been patching SBS servers since SBS 4.0 days and because we have a lot of components, the service pack part is always done in a modular setup.  For those that haven't worked with the SBS platform before, I'd strongly recommend that you order the cdrom media as the fabulous M&M's have put together an exact how to with the cdrom install.  The cdrom install in my opinion is way easier.

I've said this before, I'll say it again, I don't like service packs in SBSland.  Give me a security patch, give me a non regression tested hotfix, but security patches have always been icky in SBSland.  I still remember how I found the newsgroups in the first place, I was running SBS 4.0 and doing either the patch to 4.0a or 4.5 and discovered the newsgroups around that time that let me know that there was a window you had to close to find the box you had to click to  say “Yes continue” or something like that.  So I guess I”m a bit jaded in that I think Service packs are just plain icky, period.

I have connectivity ...but now I need juice

At the Dallas Fort Worth Airport getting ready to fly back home after a quick trip to Texas and while there is Tmobile hotspot available hear... finding a power plug in is near impossible.  What is up with these airports that think we are just going to watch CNN while waiting for the plane rather than blogging and reading emails?  I mean really.....

Remind me that I need to buy a spare battery for my tablet pc so I can have juice to entertain myself in the airport and then juice to entertain myself in the plane.  My Acer Tablet is a perfect size for traveling but the lack of airport plug ins usually means if you see someone sitting cross-legged on the floor next to a plugin in an airport... introduce yourself.... it just might be me.

Dear ZDnet:

Dear ZDnet ..when posting a headline could you include the

words "known PATCHED flaw"... just a FYI. 

You make the headline sound like this flaw is NEW

and it's something that's not been patched, but

it's been fixed since like LAST JULY.

 

Hello people ... you know that most of these computer

issues we're still seeing these days are due to NOT PATCHING?

 

Online extortionists exploit a known flaw in Microsoft's Internet Explorer

Web browser to download and run a malicious program.

http://ct.zdnet.com.com/clicks?c=191786-2072731&brand=zdnet&ds=5

The business process of your client

I'll probably insult every SBS consultant around...but here goes.... I don't think you are doing enough for your client. 

Hear me out..... every day I walk into businesses.... I walk into my OWN business and the processes we use for our daily business processes are so inefficient it's not funny.  And yet, if you want to take your client to the SBS "and" stage of the business relationship..... SBS and CRM... or SBS and Great Plains or SBS and Small Business Accounting...., you don't need to understand technology and tcp/ip stuff.... you need to understand how their business processes 'stuff'. 

How does the document flow work?  Why do you handle documents like that?  Why are you typically using some Excel spreadsheet to kludge information from your existing programs?  And why is it that the people hired to handle the paperwork tend to do things "just because we've done it this way' and no one stops to ask....'gee is there a way to make it better?'

You come in ...you sell SBS to a customer and neither they, nor you, honestly take the time to fully inform the client of all that they can do with their SBS box.  Since the box works so well, it's just back there chugging away and for most bosses... SBS isn't the server in the other room... it's the Internet ...or it's Outlook. 

But start to look at SBS "and" and the piicture changes..... you have to do lots more investigation and analysis of business flow... and efficiencies.  It's about 'where is the best place to capture data' to get it into the pipeline efficiently, effectively, and does the data you've collected... is it of relevance?  If you aren't going to use data...why capture it?

I was listening to a Gartner Group audio and they made the point to not jump on technology just for technologies sake... it needed to solve a business need.  Take RFID... it fits the best they said when the items tracked were scattered and random.  If the items you needed to tracked was more organized... bar codes actually were a better solution. 

The moral of this story is...don't just throw technology at a problem if you haven't taken the time to understand what the problem is in the first place?  Are you listening to your client's pain?  Are you identifiying definicies in business processes that need fixing.  If you are just throwing technology at your client, it may not be the right thing for them.

 

Typed on a bus  on my way to LA for the Star Wars movie with friends on my tablet pc using the Cingular air card so if there are typos......

The worst thing about blogs are

The worst thing about blogs are they are a diary so postings I make on one day are updated later

IF YOU ARE LOOKING FOR THE TREND PATCH TO FIX THE SCAN MAIL, I CAN'T SEND IT TO YOU BUT IT'S RIGHT HERE:

http://kb.trendmicro.com/solutions/search/main/search/SolutionDetail.asp?SolutionID=23065

I've send an email directly to Kevin to let him know it's available...but the easiest thing to do would be to come into the newsgroups or yahoogroups and ask the question live.  The blog is like a diary.

Hope that helps Kevin!

P.S. the worst thing about Trend's tech support is they are closed after 5 and on the weekends.  Really annoying.  I don't understand why patches like that can't be more easily available to partners that need it.

You know you do a little too much beta testing when.....

You know you are one wacko beta tester when...

  1. Every computer and server you have at home practically permanently has “For Testing purposes only. Build blah blah” burned into the screen in the bottom corner
  2. You keep old beta cdroms marked “confidential only” as souvenirs.....ah... beta 2...now that was a fun event... remember patching SQL server after slammer?  They had to give us step by step instructions on that one..you remember?  What memories that was
  3. RTM is a let down to you... what?  We don't get to have more changes?  You guys have to release it?  Dang!
  4. You know exactly where you were when products launched....in San Francisco with Grey for Windows Server 2003 and stuck at the office when SBS 2003 launched... and I'm still a bit miffed at the guys in New Orleans....the only time the guys would hit me on instant messaging was for about 2 seconds either on their way to the bathroom..don't know what was up with that..... or on their way between events.  I did however get a phone message on my cell phone.... there's nothing like Duran Duran's 'Hungry Like the Wolf' via voice mail.
  5. The Betaplace web site is practically your home page.
  6. You are getting real good at 'standing up boxes' as it's called 'in the biz'.
  7. You can tell when people at Microsoft have migrated domains from their email headers .... this one I have to admit really showcases I really need a life.

To all of those at Microsoft who 'dogfood' this stuff and 'shake it out' before we get it ...thanks.

Words that a network admin would like to see banned

Most of the time I'm a patient person, and then there are those days when a few words sprinkled here and there just kinda annoy me.....

“It always takes ten minutes to open my Outlook.“

I'll get a stop watch.. I'll bet you

  • It's not ten minutes
  • It's not always

“My machine always does that“

Again, let me get a program that watches every keystroke and I'll bet you

  • It's not always

“My machine is extremely slow“

Why is it that the people with the fastest machines in the office, always think there's is the slowest?  What's up with that?

  • No, it's not always

There are times when issues are caused by computers and technology and tcp/ip packets and ...well whatever... and then there are those times when... let's just say it's not always caused by computers, shall we?

  • No, it is indeed not always caused by computers

The "paranoid" backup

One thing I should make crystal clear about my last blog post is that “SystemState” backups as well as data and Exchange backups are automagically done with the SBS backup wizard.  I only do that extra system state and burn it to a cdrom right before I do something like a service pack.

As a normal part of the SBSbackup routine, that system state backup is automagical.  The only reason why I do a special system state backup is because I'm paranoid, worry wart, throw salt over my shoulder, part Jewish Mother [even though I'm not Jewish, nor a mother], wacko who just feels better knowing that I've made extra sure that I have everything I need 'just in case'.

For the rest of you mere mortals, the SBSbackup routine will be just fine on a regular basis.  Just remember, at any time, you too can be just as paranoid wacko as I am and just manually run that system state...just in case.

Excuse me... I gotta go find a salt shaker.... I need to throw some more salt over my shoulder.....I'll be right back....

README really means Read this...and SQL SP hits the streets

Marina [one of the Magical M&M's from Smallbizserver.net has a favorite saying “READ!” and it's really true that we don't spend the time to READ.  The ReadMe file that's on every install cd [and especially service packs] is meant to be just that... a file that you should ...well..... you know.....READ.

This is extremely true as we get ready for the SBS 2003 service pack.  Just saw on the Download page that SQL server 2000 sp4 just got released today and even though it says it is supported on SBS 2003 [which it is] you still want to wait for OUR service pack. 

Download details: Microsoft SQL Server 2000 Service Pack 4:
http://www.microsoft.com/downloads/details.aspx?familyid=8e2dfc8d-c20e-4446-99a9-b7f0213f8bc5&displaylang=en

While it can be run, it is supported, it's not blonde and “automagical“.  So wait for our own SBS service pack where it will be way way way more automagical.

But don't forget ...when we do get our SBS 2003 service pack...don't forget to READ...don't just stick the cdrom in and start installing... take it to your workstations where a printer is attached, print out the readme, click to check for an updated version, and...well.... READ IT.

Thwunk!

THWUNK! 

Geeze I hate that sound.  It's the sound that the subwolfer makes when the power goes back on in the house.  Everytime the power goes back on in the house I practically jump three feet.

I came home tonight and tried to open up the garage door and nothing happened.  Then I realized it was because we had no power.  While at the office I have UPS's on each workstation and servers, I don't at home [and wouldn't to power such things would I?].  I had earlier attempted to remote from the office to the home system to get a couple of files and was surprised that the Remote Web Workplace wasn't working.  While I have a dynamic IP address, I have tzo.com which has an automatic 'bit' in my Linksys router to broadcast the tzo.com domain name out so I can remotely log in.

Well obviously with no power... it was a bit hard to remote into the server.  No wonder I couldn't remote in.

Today I was at a client's and they lost the power and they lost the spreadsheet they were working on.  One battery backup would have saved that project.  Think about it.  They aren't that expensive and yet when you are in the middle of something and haven't saved it, it will pay for itself in one power outage.

Think about it before you get THWUNK'd!

Sometimes just a reboot at the right time is what you need

So I'm installing another server at home [rebuilding the blue glowing baby server that went to smbnation and back and I had installed 'Standard' this weekend and was kicking it up to Premium tonight to get ready to move over to this one from the poor beta-ed, WSUS'd, overgrown desktop “server' that I have here at home and I had checked to make sure the cdroms I had with the standard were post Sharepoint cdroms and the Companyweb worked with Standard.  When I upgraded to Premium I upgraded to Sharepoint and when to launch Companyweb and got

Cannot connect to the configuration database.
 
Huh?  It worked before?  So I googled and found a KB but then went.... uh... you know... I don't think I did a reboot after I installed that SQL now did I?
 
One sheepish grin later... I now have a fully functional Companyweb with a search box.
 
Yeah... don't forget a good reboot every now and then does the trick.

Dear Mr. Allchin and Mr. Dell:

Microsoft sharpens Longhorn for SMEs | The Register:
http://www.theregister.co.uk/2005/04/29/ms_sme_os/

He said Longhorn features such as security, backup, and peer to peer networking would deliver specific benefits for SMEs. At the same time new features in the operating system, such as its web services capabilities or its management capabilities, should throw up new SME opportunities for ISV or services providers

“There’s a lot of small businesses today who buy the wrong products,” said Goldberg.


Dear Jim Allchin and Michael Dell:

Can you do me a huge favor?  First off... Mr. Allchin?  Mr. Windows to the rest of us... can you make it real clear in the next version of Windows called Longhorn is good for doing what duty?  Down here in SBSland we're getting a bit tired of having to convince the small business owner that they bought the wrong operating system?  While one would think that it would be really clear that XP Home should only be used at home, it's amazing how many consultants come into the SBS community asking how to connect a XP Home to a SBS domain. 

Conversely, Mr. Dell, it drives me crazy how on the web, in the brochures I get from your company how many times in the category of “Small Business” you showcase XP Home machines and only in teeny tiny writing do you recommend XP Pro.  Take a look at this link to your “featured deals” on the web.  The first desktop on the left is only offered in XP Home, yet the web site is clearly marked “Small Business”.  You say at the top “Dell recommends Microsoft® Windows®  XP Professional“, but you don't say “why“ XP Pro is recommended.

You've got a good overview of a SBS network, but where's the page on what operating system needs to be attached to a true server? 

I see there's a big push to make networking better for home and business users, but please don't make the same mistake in the XP platform.  Don't make two versions, or make one that is 'cut down'.  Either that, or make it a lot more clearer than it is now because obviously the name “Home” just doesn't give enough information to buyers to buy the right operating system.  One would think that the name “Home” would be enough, but obviously it isn't.  Price speaks louder.  Not to mention the fact that it's near impossible to buy a XP Pro machine in a retail computer store that caters to offices. 

Gentlemen, make it easier for the small business owner connecting to a small business server to buy the right operating system.

There's only one ME last I checked

I was out googling today and don't ask me why I googled on my name [vanity kicking in or something] and on the right hand side I saw something that just made me flabbergasted.  On the right side of Google are 'Sponsored Links'.  And there was an ad for “Hey Susan Bradley SBS Fan”, and advertising tips and tricks for small business consulting.  Except there's one problem.... um...you see....that's not my web site. 

So to all those out there googling... know there's only one me and I don't advertise on sponsored links.  Heck... I don't advertise period, I just blog.

I've pinged Mr. Feinberg to stop advertising his site as being related to me.

I'm just an SBSer out here helping other SBSers and kinda feel a bit strange with Mr. Feinberg taking advantage of SBSers to get them to come to his site.  That's an old fashioned bait and switch tactic in my book.

For the record, I'm in the newsgroups, the blog, in Harry's Advanced book.  But I'm not on Josh's web site.

What I take for granted

I was helping my Dad and a neighbor with their computer [got them on XP sp2] and now they have a lovely red shield down in the system tray that warns when things are not as they should be.  I was there to help them with speakers that weren't working and they were thinking it was a driver issue.  Well I checked the control panel and could tell that it wasn't the driver as there was no “!” in there so I tried the next solution that normally works.... and that's merely to change out the speakers.  Yup that was the trick.

Sometimes you just know to try something like hardware.  But sometimes you know to look in software.  We had a scanner that needed an updated driver.  A pop out to the internet and all was well.

But it makes me think of all the things that I just take for granted.  Knowing that the event viewer is there, that I have www.eventid.net around.  That [and this is the really important one] I have a peer group that I can go to and say “Are you seeing this?”.

Benchline, Benchmarking, whatever you want to call it... it's all about knowing what is 'normal'.

To all those out here that help me do just that, Thank You.

So how was your Friday night?

Windows XP Service Pack 2 machines with critical patches and PC-cillin Internet Security 2005 starts to experience high CPU utilization after updating to Pattern 594

Yeah...slight understatement of the year in this KB from Trend. However the KB only talks about PC-cillin when mine was an issue with OfficeScan, and it not only affected the workstations, the server ground to a halt. 

Any workstation that was turned on at 3:35 p.m. when the 594 dat file was applied was totally pegged at 100% CPU utilization and unresponsive.  I had to sneakernet to each workstation, boot into safe mode, get the 594 off the machine and reboot to get any kind of control over the machine.  I even had to do this on my member server as it too was totally unresponsive.  Chad said that his servers and workstations fixed themselves... but mine were totally not fixing themselves as the workstations were too flatlined to get an updates.

Here at home, by the time I got home, the server had gotten up to 596 and had settled down, but the two workstations were still totally flatlined.

Krissy [that's my Dog] loved the experience though, he and my sister came to the office to keep me company since I was the only one there and he loves to run throughout the hallways at a fast clip as the carpeting allows him to have almost an interior dog run.  [BTW Krissy is a spoiled white toy poodle..yeah... I know.. girly dog all the way... even going to the poodle parlor for haircuts]

So while my Friday night wasn't exactly how I planned it to be, his turned out to be very fun for him.  As I left the office, my sister pointed out it was meant to be... it was a full moon.

...oh well... so how was your Friday night?  That's how I spent mine.

P.S.  This is why I make sure I have a way to the Internet that goes around the server.  I literally had a laptop on the wireless connection and it was nice to know [well not really THAT nice but kind nice if you know what I mean] to know that around the globe others were seeing the issue too.  To all of you out in the community that shared the 'Friday Flatline Experience” thanks for all of your help!

Getting IT

We were discussing the other day the perfect firm for SBS.  It isn't any one type or industry, rather it was the type of Boss.  The first that installs and embraces SBS [or any network actually] has to 'get IT'.  Meaning that they see the value in investing in their firm's technology as a way to grow the business.  I met with a client today and a post in the newsgroup asking about upgrading went hand in hand.  The newsgroup poster was asking about upgrading to SBS 2003 and whether or not it was worth it.  He said 'the current Windows 2000 exceeded their needs'.  The client had a Windows 98 and I was unable to plug in a USB thumbdrive without search for Win98 drivers which I didn't have.

But I'm not sure I would agree with that statement that the OS exceeded the clients needs... certainly not without sitting down and talking with the client.  They might want more out of their current system.  I would argue the killer apps of SBS 2003 have to be seen before you can say “the current OS exceeds their needs“.

Next is the whole security issue....I may not agree with Dave Aitel's disclosure policies but I do agree with one statement he makes:

Securing software is actually quite easy. Both Open Source and Microsoft compilers have special flags to protect software from common vulnerabilities. There have been dramatic changes in the security of recent operating systems. These days, there's no excuse for anyone to run Windows 2000 on a network and then complain about it getting hacked. Upgrade to Windows 2003 SP1 or XP SP2 or any modern Linux and your problems just go away.

 

You know.. I do need a new workstation here at home...

Cleaning up the desktop here at home before tomorrow's webcast and it reminded me that Chad sent me a reminder that I need a new computer here at home:

I'm tempted... really tempted  :-)

 

To all those people on my IM listing

To all of the people on my IM listing who've had to suffer through my long 'tag' lines on IM...they are no more.  I upgraded to MSN 7 so that the tag line is no longer something that wraps around in IM windows.  It's now in the “personal message“ screen area.

So like today instead of “Susan B. SBS-MVP aka “Ebitz“ - so exactly what was that on Camilla's head“ which is what my tag line on MSN 6 looked like, now it only says “Susan [SBS-MVP]“ and the rest [which still questions what exactly that was on her head], is down below so that when the IM chat session is going on, you dont' have that whole thing wrapping it's way into the conversation. 

Actually I may need to revise my tag line upon seeing what Laura Parker Bowles had on...okay so what is THAT?  I think I'm glad I'm an American where we don't even know how to spell the word millinery let alone worry about wearing it.

...so ...what's the funiest or silliest or wacko-est tag line you've seen on an IM window?

When monoculture makes sense

James blogs about the Fortune article on how Linux just hasn't caught on in the medium businesses to match the media coverage.  I agree even in the small ones.  Not in American anyway.  As a business owner here who doesn't make a decisions about whether my firm stays on SBS and Microsoft products just because I'm wacko about it, here's the reality for my sized business:

It's still a business decision that still makes sense from a Security one as well.  And even if I wasn't a wacko SBSer, it would make sense to chose Windows 2003.

I still say that it's in my best interests to stay on a monoculture platform.

Patchable.  Soon there will be a Windows Server Update services coming out... and like I say...while it won't be my perfect SBS patching platform, it will go a long way to making patching in a SBS network easier for SBSers.  [At the same time in full disclosure ... I'm staying on Shalik just because ... I'm staying on Shavlik... it's like why I stay on Microsoft.  When something works and works well.. I'm not changing].  I know the resources for Security information on this platform, the issues to watch.  I have communities of support information, knowledge on how to test and deploy patches, on how to mitigate threats on this platform.  I wouldn't have the ability, nor the energy, to keep up with multiple platforms [and trust me every platform has issues]    

Supported.  I have way more resources to understand, protect and defend the Windows platform.  My IM listing has technical resources and contacts bar none.  So why would I want to move to a platform where I don't have these resources?  I've been extremely fortunate to be involved in a platform that has close ties to the people in the product support communities. 

Sometimes it's the knowledge that makes me more secure...not necessarily the platform I'm running.

Sometimes you have to remember just 'how truly portable' you are

America West has this feature that you can go to the Internet, log in and print out the boarding pass. So the guy at the office who is in Arizona gets ready to fly back, goes online just like he did at the office, checks in, confirms his booking and goes to confirm it and realizes.......

Um...He has no printer.

Now I have seen printers that offered IP based printing in the hotel rooms [but I've never been quite confortable with that], but he didn't have any such options. 

 I guess you “could” cart around a portable photo printer, or as I was joking with him as he related the story, print it to Adobe PDF and then when he got to the Airport, turn on the laptop and say “here's my pass”, but somehow the instructions on the print out that says 'cut here' might not work on a laptop screen...you'd have to have some really sharp scissors to cut the pdf off the screen, me thinks.

Speaking of airports, someone mentioned that they lost their roller blade allen wrench going through security.... 'course... I have to wonder about someone that packs roller blades for business trips [seriously they probably just forgot it in their pocket], and my sister one time had to mail back an manicure kit that she forgot in a carryon bag.  She forgot and threw it in there at the last minute.  Fortunately she had enough time to get out of the security line and find a mailboxes etc in the airport but I guess the world is a little safer from Allen wrench and Fingernail file toting Airplane passengers.

In case you are wondering, the list is here of prohibited items and 'lighters' were just added to the list.  Now mind you, I'm not so sure that given that anything “I” can't stick in carryons I now place in checked bags that I want a butane lighter in a checked bag.... to me that doesn't sound too brilliant of an idea as well.  It's clear from the list that you aren't even suppose to check it.  So just remember folks... when traveling... check those cattle prods and brass knuckles.  It interesting that it does say that fingernail files can go in carryons.  Go figure.

Bottom line..just remember there are limits sometimes as to how truly portable you can be.

How about just working?

With my “I'm going to be patient and see if this works today” cap on I'm surfing over to Fedex.com's web site to see if I can update my credit card today.  Last night I was about to throttle some Java web site coders.

 

I can log in fine, go over to make payments online...I can go into preferences, then into update my credit card.  I've entered my credit card information... here we go about to see if they got their stupid Java site working [I think it's java anyway...if it's some other web coding let me know..it appeared to be a jsp page]

 

Ah... yes as you can see below... they haven't fixed it.

 

Now while I can understand that their web site admin folks probably don't want to work on the weekend, but it is a bit annoying that their web site isn't working.

 

For all of our 'this has more security than that platform' religious wars that seem to go on around security, the bottom line is that Fedex is getting real close to losing my business. 

 

Right now I don't care about security, I don't care what platform you are on, just FIX it so I can update my credit card and ship what I need to when I need to.  {I still owe Charlie Russel a Microsoft Bob that I have that I've been meaning to send to him and just keep forgetting to do it}

 

Man do I hate logging in to all the online places and updating credit card information.  I've got quite a few 'auto pay' things set up and it's a pain in the rear to dig up all of the places to go in and update [assuming I remember the password I used for the site in the first place]

 

So Charlie?  As soon I get my credit card updated...and Fedex gets their web site working expect a Bob on your doorstep.

 

The RFC info is cool, but guys?  How about just working?

 

 

--------------------------------------------------------------------------------

 

 

Error 500--Internal Server Error

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

 

10.5.1 500 Internal Server Error

The server encountered an unexpected condition which prevented it from fulfilling the request.

Dear Mr. Best Products:

Dear Mr. Best Products [or is it Mrs?]

Thank you for ensuring that Peachtree runs in User mode but can you answer one question for us?  Why [exactly and be specific please] don't you support ACT 2005 running on SBS 2003?  Can you tell us why, when we have WMSDE or SQL server 2000 that you specifically say that you don't support SBS?

Once upon a time GFI Faxmaker also said we had a “non standard version of Exchange' and well... that just didn't sit well with me and thanks to Mir we got the issue straightened out so that GFI does now support SBS.

I guess the answer instead is to just use Microsoft's CRM package which IS supported [heck kissing cousins actually] on the SBS 2003 platform.  So much so there's a CRM/SBS bundle going on.

Okay so maybe you don't need the sales ...but I'd like to know why exactly you don't support SBS?


System Minimum Requirements for ACT! 2005 (Standard Edition): Operating Systems:

      Microsoft® Windows® XP Home, XP Professional, 2000 Professional, 2000 Server, 2000 Advanced Server, Server 2003 Standard Edition, Server 2003 Enterprise Edition.Note: Citrix Servers, Terminal Servers, Windows Small Business Servers, and other unlisted versions of Windows are NOT supported.

How about I just put it in an envelope and put a stamp on it?

Email.  Ugh.

If we don't get spammed to death, SMTP auth attacked, attempted relaying, we can't send the stupid thing out the door.  Brian Livingston of Windows Secrets sent over a link that reminded me of something that we've been battling out here.

Just trying to get the email delivered.

First we had Verizon and their issues, now we've got about 4 or 5 ISPs that are making our lives interesting.  These appear to be causing some of the issues for us:

  • BellSouth
  • DirectWay
  • Rogers
  • Yahoo DSL smtp.sbcglobal.yahoo.com

In these four ISPs, we've found that we're having to put the ISP's IP address of the smarthost rather than the name of the smarthost itself. 

From the tech details:

When the Exchange server delivers the outgoing messages through smarthost, the server queries the MX record of the Fully Qualified Domain Name of the smarthost address.  If the MX [Mail Exchange] record of the smarthost is different from the A record [for example the FQDN is a Cname, and the Cname is pointing to an IP address that doesn't accept email] this will occcur.

Javier pointed out that he was trying to use a smarthost to mail.isp.com but if you perform a MX record lookup on the mail.isp.com you get a bunch of A records that are not that smarthost.  So, as long as a MX record exists on the smarthost and it points to a host that doesn't accept email... Exchange will have issues.

Ugh.

Brian indicated that his consultant found a slightly different variation of a fix for Exchange issues when using DNS to route email that put the ISP's DNS into the Exchange connector.

Somedays you just want to stick a postage stamp on that email and send it don't you?

1-866-PCSafety

 1-866-PCSAFETY

Your hot line.

You know when bad things happen with security patches [which isn't that often but nonetheless] that it's a free call.  If you don't call and merely just ask your neighbor, Microsoft won't know there's a problem. 

I'm amazed that people don't realize that hotfixes and issues with security patches AND viruses are free calls.  Call and give feedback folks.  Get the message directly back to the channel that can then follow up and get you the help you need. 

I cannot stress enough how important the right feedback to the right place is. 

So call.

1-866-PCSafety

One last time.....It's a free call.

Do we truly want to be secure? I don't think we truly do.

"Only this mode is available because Windows Small Business Server 2003 always runs on a domain controller, and if you run Terminal Server on a domain controller, you may risk the safety of the server and the safety of your organization's sensitive data."

The Terminal Server component is not available in the Windows Components Wizard in Windows Small Business Server 2003:   http://support.microsoft.com/default.aspx?scid=kb;en-us;828056&Product=sbserv2003


There are time I wonder if we truly do want security around here.  Oh sure we say we do, we argue that Microsoft needs to be more secure, but when it really comes down to it, do we?  I mean do we really?  Do we really and truly want to embrace security, evaluate the risks and be more secure?  SBS 2000 did a dumb stupid thing that never should have been done in the first place.  It allowed people to set it up with Terminal server in application mode on a domain controller.  When Microsoft made the Security push for SBS 2003 there were two things that the security folks at Microsoft just couldn't let it do anymore.  The first was modem sharing.  The second was TS in application mode.  So off they went.  Good riddance in my book.  The things that we thought were secure before are not secure now.

But it amazes me that I get emails from folks holding off on installing XP sp2 because they've heard it blocks attachments that 'normal' people want and it makes their email unusuable.  I get folks asking for pictures back in Outlook 2003.  I get folks asking to stop the annoying 'Outlook would like to access your address book, is this okay?“.  People say they want security...but do they?  I mean do we really and truly want it?

Take least privilege for example.  When working right you would have to give admin credentials to those times that you need something working in an admin like mode, downloading approved software for example.  But even in the latest SuSe desktop, there's a little box to 'remember the admin password' so the user isn't bothered anymore by the prompting.

And then there's the blog post on here that even to this day gets postings and followups.  The Terminal Server in application mode post.  The one where many consultants there say that they 'can' make TS secure and I'm there screeching like an emotional banshee saying “Are you insane?“

Now you could argue that the platform of SBS 2003 breaks the 'best practices' anyway so why should be we so concerned about TS anyway.  And I would say that I hope that someday natively in the program each compartment of SBS, each application would be 'sandboxed' so that they wouldn't affect the other parts.  Now I'm sure Dana would probably say that sticking applications as we do on the server [like Sharepoint and what not] opens us up for risk too.  I'll agree.  But all of you that are arguing so hard that you can do what it takes to secure a server even if it's TS in app mode have missed a few points.

Security

First and foremost, let's review what “I” had to do to my member server to set it up in TS mode. 

  • I had to take off the Michael Howard “Secure by default” Enhanced IE lock down that blocks active X and what not.  Surfing at a server in this day and age of malware is totally insane.  Robert Hensing's even talked about domain controllers being nailed by trojans with the admin surfing at the server.  What's the way to clean up a trojan?  Flatten it. Yeah, like I really want to do that to my server.
  • I had to turn on themes so the desktops would look like XP.  Okay minor thing, right?  But nonetheless it introduces another service that might introduce a vulnerability. [yeah like I also want to let people use a hacked UItheme on my DC]
  • I'm allowing users to log into the domain controller and use it as if it were a workstation.  The last thing I want is end users downloading anything willy nilly on my domain controller. 
  • Remember I live in SB1386/AB1950 country, better known as 'notification' territory out here, where if something happens to my server I'm licking stamps and sending out postcards saying “Hi there, we've had a slight problem here“.  If I have a “Hensincident” [aka Robert Hensing], you'd better have the electrical paddles out giving my heart an electronic shock because I'm having a heart attack for certain. 
  • Do I think that allowing TS in application mode should be allowed on 'normal' Windows 2003 Server if it were a domain controller?  Heck no, and if I were in charge of the universe there would be a code block on that too.  Make a server a domain controller and TS in app mode should be code blocked out.  I think it's pretty obvious that when the choice comes between business and security ...guess which one is going to win.

Scalability

  • We already have a lot of stuff going on that server box.  As you know I already had to throttle my SBSmonitoring instance and Exchange is already used to doing what it wants with memory and now you are going to hang how many folks off of that domain controller and have them use it?  The best desktop experience for that end user is on a member server doing those functions.  Read the scaling document on TS.  I don't really want to start yanking memory away from my DC functions.

 

Knowledge Workers

Data Entry Workers

Memory per user (MB)

9.5

3.5

System Memory (MB)

128

Total Memory

System + (# of Users x Memory per User)

Consultants out there?  Please listen to me.  You are guiding your customers here.  They depend and rely on your expertise and your guidance.  They trust you to recommend a solution that not only is secure but legal and supported.  Wanting to run Terminal server in application mode on a SBS box endangers your customer, your client.  It's not a good business reason to do this when you can add a second server/member server with only the cost of the Operating system [remember the cals for that box are covered by the SBS box].  Then for the TS Cals, which you will need anyway, any XP Pro you had in the office prior to 4/23/2003 have a redeemable TS cal.

Put users on a member server where they belong.  Scale this right and those owners and users will have a good computing experience.  If you need one or two remote sessions, buy a couple of desktops.  And hey, if you bought the SBS on Open licensing and/or SA, remember that even though I hate XP homes, you can buy XP homes, then get Open licenses for XP Pro and kick them up.

Scale it the right way.

Secure it the right way.

Your customers trust you.

Microsoft is stepping up to the plate.

Will you?

The laptop is alive, the glass windows in the office are intact, the OEMs are now ticking me off

Following up to my 'Right about now a laptop” post, DJ says that they have a 15, sometimes 30 minute rule... if it takes longer than that, they nuke the laptop and start fresh with a Ghost image.  'Ain't' it true.  Computer issue take 15 minutes or 4 hours. There is no inbetween.

OEM.  I'm getting a bit ticked at OEM right about now.  Turns out there was some sort of Dell virtual drive something on this sucker.  My clue was the issue I had when I even went to manually install the patch and it was failing on me.  Googling gave me the hint that there was some sort of virtual drive software on the box.  Huh?  What virtual drive software?  I don't have my PGP drive on this laptop [which reminds me.. I do need to install that on this before it's next trip]  So off I got to the add/remove program and start searching.  In there are a couple of Dell entries for software that kinda sound 'virtualish”.  Hmmmm... last used is ages ago... off they go.  Reboot.  Windows update again.  

GRRRRRRRRR  it's works.  14 patches later I have a fully patched machine.

I'm getting a bit tired of OEM and their hidden 'presents' that they give us when patching.  The other day I realize a desktop [an Optiplex] that I thought was relatively  clean had a MSDE instance on it because the OEM version of Outlook was the BCM version.  It also has a Sun Java JRE that phones home to Sun for updates [doesn't work though with my egress filtering ISA on the server], and the new HP laser printer we bought loads up a Apache web monitoring tool.  Apache?  I have Apache software on a desktop that I need to monitor for patches now?  Come on DELL and HP, you are not making this easy one bit to keep these suckers patched and protected.  Can you TELL me what you are loading up on these guys so I know what software to watch out for?  Can you NOT load up software that interferes and totally blocks software updating?

I have to fix one workstation because right now the HP print monitoring program is totally filling the log files with stop signs.

To all those buyers of Apple that say their buying and using of computer experience is more pleasurable...like duh... Apple controls the entire chain from software, hardware to distribution.  What does Microsoft control?  Right now I would argue they don't even control the patch distribution channel well enough.

Look at today's experience for me.  The average person would be cussing Microsoft right now for making an application that breaks.  But who truly was the root cause of the issue?  OEM software not software by Microsoft.

The big firms buy select and enterprise licesning and can load a clean image of what exactly they want.  Us down here in small business get software that we didn't even know we were buying.  Mr. Dell?  Can I get a OEM system, Optiplex with 'just' Microsoft XP sp2 and Office 2003.  Nothing else.  No Sun JRE, no nothin'.  I'll even pay more to get an image of exactly what I want with no other special software that I have to worry about patching.

One patched, firewalled, antivirus up to date Laptop is now ready for the road.   

Right about now a laptop is really getting on my nerves

We have these 'floater laptops' that stay in the closet and come out when folks travel.  So some of them don't get the attention they need [patches, a/v whatever] until they are needed for the road. 

I think I may need to include these suckers on my once a month patch plan.  My inattention is now costing me.

Anyone want a laptop, Dell, Inspiron 8200 nearly new, only missing 14 security patches?  If you act now you might be able to get it from me before I'm tempted to chuck it out the window.

I've tried WU, AU, heck I even joined the stupid thing to the domain to Shavlik AND attempted to manually install these 14 patches and they all fail.

So now I'm in google error code resolution mode.

The error log from 'one' of the log files gives clues, as well as the attempted manual installation.  The manual install gives me “Setup cannot copy the branches.inf“.  I AM the adminstrator, I've tried it on several profiles with admin access, I've run anti spyware, grrrrrrrr.... right now I'm running the disk cleanup to find temp files and delete them.  I'll be working through this list of errors next.

Update:  Ran through that list... still no go...now looking at permissions on the drive.  A call into PSS may be in order but I think the XP division closes on Saturday a bit earlier [what is it that I get to the 'giving up' stage and they are closed]

I'll keep you posted as to why this is doing this.  Otherwise anyone want to come over and restrain me from throwing a laptop through a window soon?  The feeling is getting much stronger now.


1.382: ===========================================================
1.382: 2005/03/19 15:35:06.189 (local)
1.382: c:\492924401b9deff5d09f\update\update.exe (version 5.5.33.0)
1.422: Service Pack started with following command line: /passive /norestart /quiet
1.853: DoInstallation: CleanPFR failed: 0x2
1.873: SetProductTypes: InfProductBuildType=BuildType.IP
1.873: SetAltOsLoaderPath: No section uses DirId 65701; done.
2.003: DoInstallation: FetchSourceURL for c:\492924401b9deff5d09f\update\update_SP2GDR.inf failed
2.003: CreateUninstall = 1,Directory = C:\WINDOWS\$NtUninstallKB890047$
2.003: LoadFileQueues: SetupGetSourceFileLocation for halacpi.dll failed: 0xe0000102
2.013: BuildCabinetManifest: update.url absent
2.013: Starting AnalyzeComponents
2.013: AnalyzePhaseZero used 0 ticks
2.013: No c:\windows\INF\updtblk.inf file.
2.013: OEM file scan used 0 ticks
2.013: AnalyzePhaseOne: used 0 ticks
2.013: AnalyzeComponents: Hotpatch analysis disabled; skipping.
2.013: AnalyzeComponents: Hotpatching is disabled.
2.013: FindFirstFile c:\windows\$hf_mig$\*.*
2.013: KB890047 Setup encountered an error:  The  update.ver file is not correct.
2.013: KB890047 Setup encountered an error:  The  update.ver file is not correct.
2.013: KB890047 Setup encountered an error:  The  update.ver file is not correct.
2.013: KB890047 Setup encountered an error:  The  update.ver file is not correct.
2.013: KB890047 Setup encountered an error:  The  update.ver file is not correct.
2.013: KB890047 Setup encountered an error:  The  update.ver file is not correct.
2.013: KB890047 Setup encountered an error:  The  update.ver file is not correct.
2.013: KB890047 Setup encountered an error:  The  update.ver file is not correct.
2.013: KB890047 Setup encountered an error:  The  update.ver file is not correct.
2.013: KB890047 Setup encountered an error:  The  update.ver file is not correct.
2.013: KB890047 Setup encountered an error:  The  update.ver file is not correct.
2.013: KB890047 Setup encountered an error:  The  update.ver file is not correct.
2.013: KB890047 Setup encountered an error:  The  update.ver file is not correct.
2.734: AnalyzeForBranching used 721 ticks.
2.734: AnalyzePhaseTwo used 0 ticks
2.734: AnalyzePhaseThree used 0 ticks
2.734: AnalyzePhaseFive used 0 ticks
2.734: AnalyzePhaseSix used 0 ticks
2.734: AnalyzeComponents used 721 ticks
2.734: Downloading 0 files
2.734: bPatchMode = FALSE
2.734: Inventory complete: ReturnStatus=0, 731 ticks
2.744: Num Ticks for invent : 741
2.744: DoInstallation: LoadOrInstallBranchesInf failed to install; error=0x00000005.
2.764: Access is denied.
2.764: KB890047 installation did not complete.
2.764: Update.exe extended error code = 0x5
2.774: Update.exe return code was masked to 0x643 for MSI custom action compliance.

Um...Guys? I'm not connecting to my computer at work?

So you probably know by now that I have a fully functional SBS 2003 at home as well as at the office and there's just a couple of things that bug me about RWW.

I'm not connecting to my Desktop at work.

Okay so this is really dumb but the page that says “connect to your desktop at work” makes perfect sense here at the office but is dumb when the desktop I'm connecting to is at home.  Picky.  I know.  But I'm not.  It's my desktop at home.  Somedays I'm brain dead enough to need a reminder of which one I am connecting to.

Next... dual screens. 

I'm a dual screener here at the office [we even have a guy who has quad monitors] and I'm always moving the programs I'm running from one monitor to the other.  Here at the office when I RDP to the server [rather than just get the exercise I need and walk to the server and do admin stuff] I can minimize the screen and move it around to which ever monitor I need to slide it to.  RWW isn't so easy.  First I tend to forget to adjust the screen size so it grabs the big 19 inch flat screen before I've had a chance to grab it.  Next, if I do remember to adjust the screen size, it's never quite the way I need it and I'm ending up scrolling and yanking the page around to get to where I need. 

Reminds me of the guy who was asking about TSing using a pocket pc back into the server.  I've done it.  It can be done.  But unless you really get your kicks out of taking a stylus and dragging that window ALL OVER the place, it's not exactly the most efficient way to remote access into your server.

I told you these were dumb things.

The moral of this story is ....use USB external harddrives instead

Event ID 133 is logged in the Event Viewer if you use the Ntbackup.exe with a Certance Travan tape drive in Windows Server 2003:
http://support.microsoft.com/?kbid=894255

RESOLUTION

Microsoft is researching this problem and will post more information in this article when the information becomes available.

 
I think the moral of this story is, if your client has a Travan drive run away from it as fast as you can and talk them into using USB external harddrives.  Since day one we have had nothing but grief from those stupid Travan drives.  During the beta in fact [and I take full responsibility for not beta bugging this properly], I had a sucky travan drive that didn't work and I put it down to old sucky hardware and never beta bugged it.
 
If you can grab your client BEFORE they buy the backup device... get a USB harddrive as your backup media rather than going this route. 
 
Trust me, you'll save a lot of loss of hair.

Patching anyone?

From the mailbag today comes the question.... how do you let workstations automatic update and still be restricted user at the same time.

Answer.....

You can't.  Not that I've found anyway.

Ah, great there Susan, you are the one advocating restricted user and now it makes me MORE insecure?  Ah, no.  There's a way around this.  Several options in fact.

You see there's this thing called SUS and soon to be WUS or MUS or whatever the marketing folks decided this week to call the current and future centralized patching tool.  As long as you set the updates to automatically install at a certain time, the machine is turned on, the patches will deploy [you'll have to check the event log files or scan the machines with MBSA to confirm the install.

Right now SUS is fully supported, WUS is in beta.  My strong guess is that sucker will be shipping before July of 2005 come h-e-double toothpick or high water.  [Spell it out, my mother taught me never to swear...not on blogs anyway they get caught by my Trend e-manager filters, I lose more Rory blog posts  and get the 'Removed by Exchange content scanning service' notifications to know that those filters cross over from my inbox into my newsgator folders ] 

Why you ask?  Because if I were in Steve Ballmer's shoes I wouldn't be going back in front of a crowd of Microsoft partners at the WorldWide Partner conference another year without something ready.  He first announced it when SBS 2003 was launched in New Orleans in October of 2003.  Now that that very vocal rant is out of the way, you are probably asking what the other method is....

Shavlik.  My FAVORITE once a month control thrill is my Shavlik Patch tool.  With it on my desktop I can insert the domain credentials and remotely patch ALL workstations in my office.  As long as those machines are merely turned on, they are patched.  I even deployed my XP sp2 in this manner and only had one 'gotcha'.  [Nvideo digital video card driver, rolled it back to the SP1 version and all was well]

With these tools you don't have to have local admin rights on the desktop, and in fact can patch remotely.

Read any good EULAs lately?

About a year ago there was a AICPA Tech Conference session that was titled “Privacy is good business

There are times when you look at a firm and scratch your head as to why they are doing business practices the way they are. 

So tonight on the blogosphere I'm seeing a few people post the terms of service of AIM and are a bit concerned about this section in particular:


From AIM Terms of Service

Content You Post

You may only post Content that you created or which the owner of the Content has given you. You may not post or distribute Content that is illegal or that violates these Terms of Service. By posting or submitting Content on any AIM Product, you represent and warrant that (i) you own all the rights to this Content or are authorized to use and distribute this Content on the AIM Product and (ii) this Content does not and will not infringe any copyright or any other third-party right nor violate any applicable law or regulation.

Although you or the owner of the Content retain ownership of all right, title and interest in Content that you post to any AIM Product, AOL owns all right, title and interest in any compilation, collective work or other derivative work created by AOL using or incorporating this Content. In addition, by posting Content on an AIM Product, you grant AOL, its parent, affiliates, subsidiaries, assigns, agents and licensees the irrevocable, perpetual, worldwide right to reproduce, display, perform, distribute, adapt and promote this Content in any medium. You waive any right to privacy. You waive any right to inspect or approve uses of the Content or to be compensated for any such uses.

 
Now granted, I'm having a hard time imagining anyone wanting to write a book using my IM conversations, but to all those corporations out there... can you not freak us out with these privacy notices and EULAs that make us not trust you?
 
Let's check out the EULA inside MSN IM 7.0 beta shall we?
 
While the full privacy statement is here, inside the EULA is this:

MSN IM 7.0
 

5. PRIVACY.

 

If you are using MSN-branded software with the Service, please see the MSN Privacy Statement 'http://privacy.msn.com' for notices about how we collect and use your information. If you are using any other software with the Service, please see the .NET Messenger Service Privacy Statement at 'http://www.microsoft.com/windows/messenger/privacypolicy.asp' for notices about how we collect and use your information.

 

We consider your use of the Service, including the content of your communications, to be private. We do not routinely monitor your communications or disclose information about your communications to anyone. However, we may monitor your communications and disclose information about you, including the content of your communications, if we consider it necessary to: (1) comply with the law or to respond to legal process; (2) ensure your compliance with this contract; or (3) protect the rights, property, or interests of Microsoft, its employees, its customers, or the public.

 

Always use caution when giving out any personally identifiable information about yourself or your family.


 

And also this section:

 

4. WHAT YOU MAY NOT DO WITH THE SERVICE.

 

The privacy, safety and security of our Service and the users of our Service are very important to us. You may not use the Service in any way that could harm the Service, other Service users, Microsoft or our affiliates. Some examples of harmful activity that we do not permit include:

 

· Trying to gain access to any account, computers or networks related to the Service without authorization.

 

· Disrupting accounts, computers or networks related to the Service.

 

· Obtaining or trying to obtain any data through any means from the Service, except if we intend to provide or make it available to you.

 

· Using access to the Service to obtain any data to design, develop or update unauthorized software that you use or provide to others to access or use the Service.

 

· Charging others to use the Service either directly or indirectly.

 

You may not use the Service in any way that is against the law. You may not use the Service to send or receive messages or materials that are inappropriate or violate the intellectual property rights of Microsoft or others. Some examples of types of material and messages that we do not permit include:

 

· Using the Service to participate in pyramid schemes or chain letters.

 

· Using the Service to send, either directly or indirectly, any unsolicited bulk e-mail or communications or unsolicited commercial e-mail or communications.

 

· Defaming, abusing, harassing, stalking, threatening or otherwise violate the legal rights (such as rights of privacy and publicity) of others.

 

· Creating a false identity for the purpose of misleading others.

 

· Sending or otherwise making available, any material protected by intellectual property laws unless you own or control the rights to such material or have received all necessary consents.

 

· Sending or otherwise making available any material that contains viruses, Trojan horses, worms, time bombs, cancelbots, corrupted files, or any other similar software that may damage the operation of another's computer or property.

 

· Downloading any material sent by another user of the Service that you know, or reasonably should know, cannot be legally distributed in such manner.

 

· Using, downloading or otherwise copying, or providing to a third party (whether or not for a fee) any (i) directory of users of the Service, (ii) information about users of the Service; or (iii) Service usage information.

 

· Falsifying or deleting any author attributions, legal or other proper notices or proprietary designations or labels of the origin of source of software or other material contained in a file that is transferred.

 

· Violating any code of conduct or other guidelines which may be applicable to the Service.

 

· Using any portion of the Service to harvest or otherwise collecting information about others, including e-mail addresses.


 

Now I'm not smart enough to know if both of those EULAs and terms of service are talking about the same thing, ensuring that if you do 'bad things' on their IM services that they have the full right to contact the FBI and Secret Service because you are doing bad things, but AOL's “You waive any right to inspect or approve uses of the Content or to be compensated for any such uses.sure doesn't sound to “good business“-y to me.

 

Bottom line folks... read those EULAs ... one firm, PitstopPc already proved that we don't read the EULAs.  They offered a financial incentive in theirs and it took someone 4 months to take them up on it.

What to do in case of.... and "The effect of the PIX"

So the menadering contents of this blog post all started when Steven Banks asked me what should a person do if their IP address was spoofed.  So I asked my security guru buddies of the various steps one should take if something happened and one of the comments that “Mr. ISA” Dr. Tom said was that there was an hypnotic effect that a Cisco PIX had on people.  You know..the glazed look in the eye and the chanting....“Oh, I must be safe, I have a PIX

It's true isn't it?  So many times I hear people want to take ISA off of our domain controller because 'oh it's not safe' but I'll bet those same folks have local administrator rights and Windows 98 machines in their offices.  You could have a firewall that is built like Fort Knox and as long as “Joey” can surf out to “Malware-R-Us” and has the rights to download and you don't have software restrictions or other limitations in place, neither that “ISA on our domain controller' or a Cisco PIX will help one bit.  For all those folks that want ISA off of our domain controller... go take those workstations in those offices, kill off Windows 98, and move to restricted user on the desktop.  Once you have THAT in place, then we'll talk about taking ISA off of our domain controller.  In fact in the upcoming book by Dr. Jesper Johansson and Steve Riley, there's a chapter and a section that talks about ISA server and it's risk on a domain controller and how it rides low in the TCP/IP stack.  When I read the sentence in the preview of the book I could have hugged them.

Stick a natting router on the outside for good measure just to thin down the ISA logs on the inbound side and this [ISA on our DC] is not the security issue that TS in application mode is.  Sorry but me wacking off the Enhanced IE lockdown and letting stupid users work and surf on my domain controller as if it were a workstation is just a lot more insecure no matter how much you think that you as a consultant know better and can lock it down.  With the nasty malware on the web today?  Get real folks.

You know what freaks out a lot of SBSers right now?  SMTP auth attack pings on our port 25.  Guess what folks, if we move from RRAS to ISA server to Cisco PIX, you will STILL have those same port pings on port 25.  The port opening is still there no matter what firewall you have.

A hole is still a hole.  And if the firewall you have [whatever brand] has the hole open, you have a risk no matter what the name of the firewall is.

Without further ado..here's what to do if something happens:

  • I have spam and I want it stopped!

Invest in a good antispam filter, but the best protection is to invest in a solution that gives you negligible or non existent false positives, easy administration, and little to no interaction on the end user side.  [Like Gavin says the IMF still needs work]

  • I'm getting port scans and I want it stopped!

Port scans will happen. Solutions range from the drastic (impractical) measure of disconnecting your systems from the internet, through investing in a Firewall solution that can detect and drop the probes. If you are a targeted victim, then your option is to trace back to the source(s) and chase them all the way to their upstream provider and get it to stop. Tedious, but there really isn’t much you can do.  Now this is going to start up a conversation from folks in SBSland I'm sure... but unless you want to have someone track down and report to each ISP an abuse report, this is life on the lnternet.  Personally I think at some point in time, Exchange will need/will get some sort of proxying something in front of it so that we don't have our port 25's quite so exposed.

  • Help!  I think I'm a mail relayer!

First off know that SBS 2003 is not a mail relayer.  Well... okay in full disclosure... if we haven't patched for the POP mail issue .... we turn ourselves into one pretty efficient mail spammer. I joked one time that the folks that think we can't handle everything on one box should realize just how efficient we are ... 3 boxes sent out 6 million pieces of email... not bad for 3 little SBS boxes... that's definitely doing more with less!  Seriously, I cannot stress enough how important ...and how all of us should just routinely think of second Tuesday as patch day.  We can suffer from NDR attacks so you may want to tarpit your box as well.

  • Help, my email address/IP address is being spoofed!

While you have open up the email and possibly track back the sender, your best solution is like the above, a good antispam solution.

  • Help, I can tell from the  speed of the attack attempts in my log files that some 'person' not a bot is attacking me!

When a 'bot' hits an open port and you see the effects in your security logs [yes, this is why we have 'em to know what is going on out there], you'll see it 'bang on the port' in a very rapid succession.  If it's a very slow methodical attack... then it's probably 'not' a bot.  That's when in SBSland you should gather up all the log files, IIS, ISA, security events and start tracking back to see who is hitting you.  Look up the attacker in the Whois database and contact the ISP's abuse department [normally in the IP record]

  • Help I think I'm really screwed, I opened up annoymous FTP and now can't delete files...or... someone downloaded Kazaa and now my internet connection is still blinking....or... I've got a really sinking feeling something is wrong with my server and I've been hacked!

First .. don't panic.  I've seen people on security listserves think they've got backdoors and rootkits because their Word documents are entering words by themselves and it turns out the voice recognition part of Word was turned on.  Most of the time in SBSland we're 'roadkill' out here.  We get nailed because of our stupidity of not setting something up right... which is WHY I love the wizards...especially in ISA server.  Unlike the Cisco PIX, SBS helps you set up the firewall correctly.  Most issues with the firewall are from misconfigurations.  Next, if you truly have done something stupid and you want it investigated, Call PSS and ask for their Security investigations.  Robert Hensing talked about it on his blog.  Again, one of the VERY important parts of the investigation is log files.  So again... those PIX fans out there... looked at your log files lately there? 


Just remember....have a plan and DON'T panic!

 

How do you sell to a small business customer?

Dave and I are lucky.  We work in offices where technology is not a line item on the budget that we nickle and dime to death, but rather one that is seen as helping our firms grow to where we are now.

A conversation started on the Microsoft Small Business community about the differences in selling technology in a break/fix setting, or technology in a 'this is a part of our firm' way. 

There's firms like mine and Dave's that 'get' technology and 'get' security and realize how it adds to the bottom line.  These are your A+ type customers.  The ones that aren't the break/fix type, the ones that want you maintaining and watching that box. 

It's funny but I've found too that there is the typical SBS consultant out there that knows he or she can handle just 'so' many SBS boxes and then they don't install anymore because they stay loyal to the customers they are supporting. 

There's a difference, a longer sales cycle and a different revenue stream from the “Oh we just want a server” to the “we need a business solution and need you to be here for us over the long haul”.  Accounting, Retail sales and CRM package installations take much longer to 'sell”.  Both from a technical setup standpoint, but because while installing/migrating/ripping out hardware and networks is bad enough, there is something out messin' with how a person has been keeping track of the accounting of widgets for 20 years just better not be messed up by that installation of that new fangled gadget.  

There's an article on the New Small business web site that I found via the RSS feeds and while it has some valid points, the author has two things in there that has me scratching my head [and yes I already pinged Eric Ligman on it saying that I wasn't too pleased with the content of the article]

Scratching my head number one - the author says that the Tech firm 'upgraded the computers from Windows 98 to Windows NT”.  Uh...note to tech firm... NT had a 'end of life' last June and the server platform just ended in December so I sure hope that they didn't 'upgrade to NT”.

The next scratching my head, is the phrase “trunk slammers”.  There's a lot of SBS consultants that could possibly be lumped into that 'trunk slamming' category.  But honestly, they are some of the best SBSers around. 

I personally think this is an old article that may have been re-used.  SBSers may work out of small shops, out of their homes and what not, but these days, working out of your home is actually part of big business too.  Heck the whole remote web workplace idea is that you don't 'have' to be in an office to get your job done.

But this does bring up the argument of exactly how DO you get a client to move from 'break/fix' to “maintenance plans'.  Sometimes it's an event...loss of data, a disaster that makes the client see why they need prevention and not a fix.  Sometimes it's regulation.  Sometimes it's multiple shops and multiple locations that make the owner need something more than the part time computer guru or neighborhood kid.

Similarly in the software assurance argument, my profession [accounting] and Dave's [legal] are used to a subscription model for software.  Thus for our professions, moving to a SA purchase plan is a no brainer.

When do you tell your client “I'm sorry, you won't buy yourself the tools you need to be a viable business, I cannot support you any longer”?  Sometimes you will spend more time monkeying around with an old piece of equipment to make an computing experience 'just like' what they had before. 

So... now it's your turn... how do you get your 'break/fix' clients to move up to A+ clients?  The ones that trust your decisions, the ones that see technology as a part of their firm's growth and thus a needed element?

A Haircut, a manicure and a computer

Tonight was the night for my own 'patch maintenance', haircut and nails.  You know us high maintenance gals.  But tonight I also picked up a bit of maintenance of another sort.  My manicurist brought in her computer for me to take with me and fix.  In chatting with her she has a family member that uses Bear Share and Kazaa to download music on the family computer.  Given that news reports have said that these peer to peer file sharing/music sharing platforms are notorious for spyware and malware, it's no wonder her machine is near impossible [if not impossible] to use. 

So it's here at home where I already plan to probably replace the harddrive [so we can retain some photos and what not on the drive], and format and start over if need be. 

I'll first isolate it from my network ensuring that it won't be anywhere near my network, and then I'll give it a quick try to clean it, but honestly, I'm totally ready to put in a new harddrive [so I can hang on to the data from the old one], flatten and start over.  I recommended that she use the Microsoft anti spyware beta, which worked for a bit, but it soon lost the war.

As I was chatting with my hairdresser and my manicurist, they both talked about the same thing...what I take for granted and understand... is confusing to them.  Something pops up in the right hand corner saying to scan something, and they really don't know if that 'thing' that is prompting them to download this, update that, scan whatever is a good thing or a bad thing.  They don't care about patch Tuesday...they just want it handled.  They don't want spam, nor popups, nor malware.  They don't want confusing interfaces, just things 'handled'.

It's hard to say where the blame best lies.... the spammers and phishers and spyware folks that entice us or Microsoft's operating system for being too open and willing to download software because even in Windows XP, it acts like Windows 98.  It amazes me that in the year 2005 we're still all paying the price for having our desktops run like Windows 98.  Yeah let's lay blame on Microsoft for painting us into this corner...but lets also blame ourselves for letting our vendors that provide us with software to not be held to the fire as well. 

Chicken and the Egg, which came first? 

Restricted user and vendors that won't support it?

How about we ask all computer vendors [and not just Microsoft] to step up to the plate and help fight this mess we're all in?

Here's to a SBSer getting a bit of html to call SBSized

I don't mean to be this way.  But I am.  I don't know why.  Haven't really stopped to analyze it.

Show me a fellow SBSer who truly 'gets' SBS and chances are, they will be the same way.  There's a fierce pride in being an SBSer.

Don't call me a person who knows Windows Server.  Or Exchange.  Or ISA Server.  Or SQL.  Or Office.  Or Outlook.  Or Windows XP.  But here's the crazy thing, I can answer questions in a lot of those categories.  But that's not what I am.  I'm an SBSer.

Call SBS 2003 a 'limited version of Windows 2003 because it doesn't have Terminal server in application mode' and I'll tell you we're the smarter more secure version of Windows 2003.  But lump SBS 2003 in with Windows 2003 in a tech forum and I'll call you crazy.

To all of you out there who hang out in forums that are traditionally not SBSized where I hang out... I have to truly give you credit for putting yourselves on the line.  One such person is fellow SBS MVP Nick Whittome, who day in and day out in the Mark Minasi forums puts up with a bit of ribbing about SBS and for a long time had to constantly defend the product.

Another is a fellow California resident like me, Jeff Kane who is over in Experts Exchange trying to get them to open up a SBSized forum.  Looks like right now they have no SBS forum so the questions are posted all over the place rather than a separate forum.  I don't mean to be mean, but if you guys over there are truly supposed to be a forum where “experts' exchange information, I must say when I've googled SBS solutions and hit the answers in that forum, I've cringed at times.  It just drives me totally insane with folks coming from the Enterprise space down to SBS do not follow the wizards, do not take the time to read the documentation, think they know what the heck they are doing and end up screwing up a SBS install.  I'm not saying that all the posts are like that but truly, I hope that the folks at Experts-Exchange do listen to Jeff.  We're getting to be a big enough marketplace that they need to have a forum for SBS.  While we “ARE“ the same, we “ARE' different and there are times that folks too used to the manual way may not set it up the SBS way.

The post that Jeff points to in fact... where someone without a SBS box is giving advice on setting up Outlook over http when the step by step information is inside the SBS box and further expanded on by M&M on the Smallbizserver.net website, is an example where people who don't understand the product are making it harder than it should be. 

I'm not saying that we SBSers always get it right in telling our fellow SBSers how to do things, in fact I was telling someone tonight in fact that I'd rather have someone nicely wack me upside the head when I screw up and get something wrong, and I certainly couldn't answer questions on Server clustering or Front end/back end Exchange and what not, so having your own 'place', your own space where you know that you'll get the appropriate answer from folks who understand where you are coming from goes a long way to end some of the frustrations out there both from the client and the customer. 

To Nick who single handedly does the SBSized forum in Minasi's web site ...attaboy.

To Jeff... I wish you luck my friend in getting your own space for SBS.  If you get it... let me know... I just might visit there.  Until then, I'll stay in my communities where we're a lot more SBSized.

Can we clear up a few misconceptions over Service packs on SBS?

Over on CRN is an article on SBS sp1 that just doesn't ''quite" get it right and I'd like to specifically comment on a couple of items listed:

  • One new feature in SBS SP1 will help partners with the client issue: The client setup feature in SBS SP1 will support Windows XP SP2, Microsoft said.

Not quite following what this sentence is referring to?  You can set up XP SP2 machines now with no sweat you just add your connectcomputer web site to the trusted zone and all works wonderfully, if that's what this sentence is all about?

  • Microsoft, Redmond, Wash., said partners should use the enhanced Configuration Wizard in SBS 2003 SP1, and not attempt to use the Security Configuration Wizard in Windows Server 2003 SP1. Doing so would remove some of the "glue" that integrates the server components in SBS 2003, causing server crashes and other headaches, Microsoft said.

...huh?  ....um... as far as I know we don't 'have' a 'enhanced configuration wizard in SBS 2003 sp1' versus the normal Windows 2003 sp1 'security configuration wizard'.  Mind you I purposely installed Windows 2003 sp1 and ran the SCW [you know the one we really shouldn't run on our box and chose the defaults] on the server that I'm now typing via this blog and as you can see... my server isn't crashing.  It didn't DO anything worth running the wizard for... it shut off IPsec services which now makes an alert email to be sent to me daily and it truly didn't harden anything, but it certainly isn't causing server crashes.  Honestly SBS 2003 is pretty darn well tweaked as it can be for running what it does.  It's my understanding that the icon for the SCW just won't be on the desktop and in the readme file ... you know the thing we never read... it will say we're pretty tweaked, hardened and secured already [well, if we kill on Windows 98s we would be anyway] and we don't need to run the SCW. 

  • Most partners are aware of the "do not install" rule for Windows Server 2003 SP1 on SBS, said Jason Harrison, president of Harrison Technology Consulting, Nashville, N.C. Harrison explained that individual Service Packs available for Exchange, SQL and ISA may not work well with SBS management tools.

Huh?  On my PRODUCTION [yes that's Production with a P] real live server a the office I've installed Exchange 2003 sp1, ISA 2000 sp2, Sharepoint SP1 and obviously during the install of SQL, SP3.  Now because 'this' install is a bundle of ISA 2004 and what not, that's why they are recommending that we wait for 'OUR' SBS 2003 sp1, but as I stated, I installed Windows 2003 sp1 RC on this testing machine at home.  My management tools are just fine. 

We are normal parts.  Let me repeat that.... SBS 2003 is made up of normal parts of Windows, Exchange, SQL, ISA, Sharepoint, etc. and normally you can install any Service pack for a 'part' to us.  Do not get the idea that individual service packs are not supported on a SBS box.  In fact if you merely Windows update, you get Sharepoint SP1.  In fact last month's patches included a patch that you HAD to be on Sharepoint SP1 before it installed. 

For this time only because of the bundle with ISA 2004 for premium, because of it being so close to being shipped out to 'normal' Windows 2003 sp1, we're saying 'wait for 'our' Service pack'. However, do not think that you cannot install the normal service packs of the 'parts' of SBS ON SBS.

The best thing to harden a SBS network is to upgrade every last one of your Windows 98 machines to Windows XP sp2.  I know that my life is truly easier being all borg.  I only have to worry about patching Windows xp sp2 and Office 2003 at my office and thus my 'radar' for watching for potential issues is very focused.  I can understand folks that use LOB apps that can't run on the new stuff, but for other folks... honestly, you'll make your out of pocket costs back in the lack of rebooting of that Win98 platform and gain of productivity.

Bottom line folks, and you are talkin' to a veteran of testing patches on SBS boxes and patchin' SBS boxes and ensuring that they are kept in working condition and kept well patched, there isn't a service pack for a 'part' of SBS that I haven't installed on my office network.  I've never waited for a 'specific' SBS service pack.  I'm only doing it this time for the Windows service pack part because 'ours' will come out in close alignment with the Windows 2003 sp1, and we're specifically getting ISA 2004 [for premium customers] with 'our' SBS 2003 sp1.

The power of Word...the REAL power of Word

Word.

Noun.

A sound or a combination of sounds, or its representation in writing or printing, that symbolizes and communicates a meaning and may consist of a single morpheme or of a combination of morphemes.

Microsoft Word

Noun.

Annoying program that when it works, it's wonderful and when it doesn't want to cooperate with you and instead number pages is some bizarre sequencing pattern, and no matter how many section breaks you insert or delete, you still can't get the last three pages of the report to be numbered 16, 17 and 18.

A word processor is a very powerful program.  Singlehandely it is making me

  • Forget how to spell
  • Forget grammer
  • and increase my blood pressure with it comes to headers and footers

Okay, here goes the rant for a Friday.....

My bug a boo....my one sticking point with Word that if it gets really bad we've got like two or three people in one person's office trying to get something fixed is ... Headers and Footers.

Click View....Header and Footer.

When they work..heaven.

When they don't...grrrrrr

Now in Excel this same sort of headers and footers is in a totally different menu drop down so if you are a beancounter that's your first thing you have to get used to is where the thing is... then... if you need the pages to count in a non-sequential manner, make sure you have a lot of Tums and aspirin on hand.

Today was one of those days when our Word Expert Extraordinaire and myself could not get the last three pages of a document to number as we wanted them.  We finally gave up and printed those three pages separately.  Even if you turn on the paragraph indicator [and there are people that leave that annoying view turned on ALL THE TIME] and we still could not see the offending 'bit' that was causing the issue.  We deleted page breaks, we inserted breaks and still we could not get the last three pages to 'skip' a number and then go on it sequential numbering.

Word Perfect even did one better and exposed almost a 'code level' view in a dos-window below.  I've been in Attorney offices and there those split screens are being typed on.

I've even had Word documents that I've put in 'placeholder' pages because it was easier to stick in 'placeholder blank pages' and have them numbered than it was trying to insert breaks and what not.  Is it any wonder that we are killing more trees for paper these days than we use to in the past?

Final Score

Susan - 0

Microsoft Word - 1

Things to do next Tuesday

So for all those within earshot of this blog...listen up.  You've got a free day next Tuesday as there is no Security patching to do.  Now you 'could' go outside and enjoy the [insert whatever weather you get in your region] or you could be a real geek and do one of three things....

  • You could be an absolute maniac and walk the streets of your city in search of SBS boxes that are unpatched for the POP connector patch that turns them into spamming machines.  Now then keep in mind that you just might be arrested for screaming at the top of your lungs “Do you have a SBS box“, so if you want to pass on this suggestion, I'll understand.  But if you happen to meet up with an SBSer, do try to mention in passing that they should visit the www.microsoft.com/sbs page, click on downloads and GET THEMSELVES PATCHED.  When someone comes to the newsgroup and says 'I'm fully patched', you'd better truly be 'fully patched.'
  • Next, you could take your day to make sure a XP sp1 machine is ready to go for XP sp2.  The press is making a big deal that come April 12th the XP sp2 patch is coming down, like it or not, but here's the scoop, you have to have automatic updates turned on and you STILL have to click through a EULA so all my beancounters that are worrying that XP sp2 will install just as they are attempting to finish tax returns have nothing to fear.  The wise thing to do is just install it now anyway [like WHAT were you waiting for anyway?]  A nice guide is located here.
  • Last but not least, you can take the day to make your computer 'genuine'.  This is a process where you go through an ActiveX page and make sure your system has a geniune license.  Yeah yeah I know that you did buy it, but in places of this world, that isn't always the case.  So can you take the time on patch Tuesday to confirm your box.  Remember you will ONLY get the MS antispyware when it comes out if you have been deemed 'genuine'.   I found that when I was on a system that had a volume license or retail box product key installed it went through without a hitch and 'found me legal'.  For OEM operating system, this wasn't the case and I had to do a bit more proving of who I was.  I clicked on the genuine page and it asked me for a Product key code.  Now, here's the problem...the code on a Dell Tower is ON THE FLOOR, upside down.  I crawled on the floor, wrote down what I thought it was and got the key wrong.  On that page there was a “alternative ways to validate“ link [trust me... right hand side..keep looking] I clicked, and entered that I had a Dell, bought from Dell, it made me enter a “captcha“ confirmation [like in the blog comments section] and voila.  I'm genuine. 

Now, here's the problem I see.... I don't think they are kicking up the communication on that last one enough.  Let me restate that.... Volume license folks and Retail box folks go through just fine, is OEMers are slowed down by a bit of an annoying entry method. 

If anyone out there is Microsoft land is listening, I'd really start a communication process on the OEM genuine process.  I think a lot of folks that buy through the OEM channel are going to be a bit miffed that they have to 'prove' that it's their machine.  I know that I wasn't too keen on crawling on the floor and will definitely use the 'alternative method' on my systems that are OEM.

On the Microsoft Genuine page it says “The validation process determines if you have activated your copy of Windows. If you have not activated Windows, you will be asked to enter the 25-character Product Key printed on the Certificate of Authenticity (COA) you received with your PC or software purchase. If you have already activated Windows, the validation process will sense that the PC has been activated, and will not request Product Key entry.”  I'm sorry but that's just dead wrong in my book in the OEM experience.  Two out of Two OEM computers that I've tested wanted the product key code.  I'm assuming because the OEM 'activated' my machine and not officially me...but none the less...

....and sorry one more rant for the evening before I go to bed... the word 'richer'.  There are over 11,500 uses of the word 'richer', and over 81,600 uses of the word 'rich' on the Microsoft.com web site.  I'm actually surprised about that number.  I thought it would be higher.  When we finally get the OS with the horns... can we find some other word to describe things other than 'richer' and 'rich'?  Just start thinking about a new descriptive word please?

Have GFI and not getting mail?

Using GFI and all your mail being Quarantined or Deleted ?

http://www.theregister.co.uk/2005/03/02/gfi_beserker/

Quote----
GFI's Mail Security anti-virus product threw a wobbler Wednesday
afternoon (2 March) when an update to BitDefender Engine Module caused
it to delete the body content of every incoming and outgoing message.


Okay Symantec had a security vulnerability and needed a patch, Trend had a security vulnerability and needed a patch [which I think should automagically come down today] and now GFI. 

Sophos and Panda folks?  Keep a look out ... at this rate you guys are next....

Excuse me.... it was my database first!

I order things from Office Depot and so does the Office Manager at my office.  I buy stuff for home.  I personally feel it's perfectly normaly to buy a whole box [10 reams] of paper.  And because I'm normally a geek I regularly use the online ordering system.  Log in before 5 and the order is delivered the next day.  Then I just have to twist someone's arm into putting in my car and I've got paper for home. 

So the other day I log into the Office Depot site to review a past order to get a reimbursement on it as it was partially business.  And I'm looking down the listings of orders going....okay....something doesn't look right here...these aren't my orders...they are the firm orders.  I check the account name and sure enough it's been fully flipped to the office address and name. 

Okay that's odd and call up Office Depot.  Well you see they track their database with a telephone number and because in my online account I have a office/business phone number of ..where else... my office and I normally don't like to put my home number in the database, especially since during the time they are delivery I am....hello....at the office..... so guess what.... you guessed it ...they mooshed the databases of my orders and got it mixed up with the firm's orders, even though the firm's account said 'no online ordering'.  So now I need to set up a new account because every time I do something in the online account it thinks that's the firm account. Nice huh?

So.... I don't have my online history anymore and my firm that didn't want any of this info online has it tied to my account. 

As we move forward databases are going to become more and more important...and proper handling of them even more so.  Someone/some program obviously consolidated databases and someone/some thing decided that since me and my firm had the same phone number, we MUST be the same database!

This happens to me and my sister a lot too.  We share a house and thus we share a phone number and thus we share a database identifier.  We've given up trying to straighen out the databases. 

If I send an email via a web interface I'm not 'Susan' I'm 'Karen'.  Other things, the account is in my name not hers.

Bottom line... if there's a database attached...just say Susan/Karen... I'll answer to both. 

Next time, Barbara, just call me

Barbara Darrow in the Unblog on the CRN site talks about the new online  “Small Business Center”.  Reading the post reminded me of a happening just this weekend.  

In her post it talks about the demo of the new site had the person putting in that he or she was a 6 computer shop and they ended up getting referred to Tectura and  Avondale.  Now I'm not 100% sure they would turn down a 6 person computer job, but I guarantee you Tectura would not do as well as my buddy Steven Banks or any one of his fellow SBS partner user group in Seattle.  AH HA after doing a bit of digging and clicking through I did find Steve down under the registered partner level.  The initial 'landing place' only offers up the Gold Certified partners [you know, the partners that at least two of which back in the SBS 2000 days of mine tried to talk me out of SBS]. 

I guess I'm always trying to swim a bit upstream or something but at a time when CRN is talking about some partners seeing Microsoft 'over recruiting new partners', I'm trying to drag more registered partners in the door.  Just this weekend in fact, someone emailed me and asked if I knew of an SBS consultant in Orange County and with our SBS user group ties, sure 'nuff I did.  Guaranteed installer of SBS networks, in fact, courtesy of our SBS Group network.

So for all you registered partners out there reading this blog... click on Products overview, Solutions Advisor, answer a few questions and make sure you are in the database.

For you SBS consultants that aren't even a registered partner... get your buns on over to www.microsoft.com/partner and register yourselves!

For you Gold Certified Partners that may get some potential SBSers calling you, make sure you treat those SBSers right.  If any one of them find their way into the SBS newsgroup and I hear you tried to talk them out of SBS.... just remember... they could end up turning into me.....that'll keep you awake at night, won't it?

I think I had a bit too much Mountain Dew too late in the evening or something....

I had this bizarre dream this morning.  You know that morning dream you get when you go back to sleep for a bit..the one in which you dream really really bizarre stuff?

I had this dream that in order to promote LUA and least privilege user mode and all that ... Bill Gates was Grand Marshall of the Pasadena Tournament of Roses Parade.

Now exactly HOW being grand marshall would promote running as restricted user ... I have no idea... but that was my crazy dream this morning.

Now given that the Grand Marshall tends to set a theme for the floats...and the theme was LUA and least privilege... I have no idea how the flower covered floats would look.  I didn't dream that far into the details and just woke up going.... okay how exactly did that idea get into my head?

Okay... I really need a life   :-)

The balance

Oh my gawd...the enemies are out there....oh no...they are in here.... The Security mentor brings up something along the lines of my password issue..... it's an issue I call “the balance”.  Every day, each one of us take our expertise and talent and try to balance the forces of needing to do our jobs, needing to secure the information we are caretakers for.  The most secure information is locked up away never shared.  But....you see.... the best solution to our problem might be to share that information.

So every day we connect and communicate and open the holes and go through the firewall and pass the syn acks and all that. 

And every day we balance the access with the abilities it brings.  Push your end users too much security restrictions and you restrict interaction and stifle creativity and business.  Enable freedom too much and you have insecurity all over the place. 

There's a balance...and that balance costs. 

One of the ways to help set the line, to help determine the right costs for that balance is analyzing and putting mental boundaries around data.  Even if your computer systems don't categorize data in a “high risk“, medium or low risk, you should.  What is the data that should never ever be let out the castle gates?  Make sure everyone in the office knows to treat that data as carefully as possible. 

When it comes right down to it a lot of this really comes down to the 'people' part of the equation.  Make compliance with 'doing the right thing' too hard and people will find ways around it.  Make the choices easier to do, and people don't mind 'doing the right thing'.

Sometimes the worst enemy of all.... is you.

The ugly truth about Passwords

For all my talk about security I'm going to bare my soul to you all.  I do something very very dumb.

I do a very stupid thing.  One that my fellow Security gurus beat me up over [and rightfully so].

Like Gavin, there are times I need to log into “THE PROFILE”.  Not the admin profile, not a generic profile, but THE profile of the person that will be logging into that system come Monday morning.  So I need their password.  Yup, not too smart is that?

So either I have to do what my Security Guru's do, like Gavin, force people into changing password every time I need to manually install something or ensure that an server deployment went as it should, or I have to figure out some other way of installing updates on a weekly basis, ensuring that the desktop experience is “perfect” and not jeopardize accountability in the process.  I'm still personally struggling with the right answer.  I mean I'm totally violating authentication here.  Yeah, I know, totally NOT smart, I'll be the first to admit it.

Steve Friedl says this is something that is done all the time in the 'Nix world.....and while many times if one OS has something the other OS has it too but this is one area that I'm not sure I can find a Windows equivalent.  Redhat does have the same ability to age passwords and force certain policies with addons and other built-ins.  So if you can login as an admin in Redhat [or similar 'Nix distro] and then go into the profile experience of a user on that system.....sooooo.....why can't we do that in Windows?  I'm the Administrator of my network .... so why can't I get into the profile of that user without jeopardizing accountability in my network?

The real problem that “I” have, is exactly what Dr. Jesper Johansson says:

“The best practice is not to make the same person responsible for both security and system administration. “

And that's exactly the problem I have.  I'm both.  I'm trying to make the desktop experience 'automagically' for my users, and at the same time, trying to keep us secure.

So I know that the folks that do consulting normally do force the user to change the password like Gavin does.  What do you do in a similar situation?

Me, I'm hoping some folks north of me will listen up and maybe in that OS that I'm tired of hearing about [pssss.... goes by the name of that cow with big horns that I'm tired of hearing about so I won't even say it's name], will do something about my problem.  Either that or maybe I need a upgrade in policies myself.

I think I'll probably end up upgrading myself to the next paranoid version.  :-)

The glass is indeed 1/2 full, not 1/2 empty

On the blog comments today comes a passionate post that I'd just like to respond to because it points to a Microsoft partner that I came across once upon a time...the glass is 1/2 empty partner....

Scott in the blog comments rants that SBS is a “bait and switch” because it's limited to 16 gigs of Exchange storage space under all versions of SBS and to go to the next level of 16 terabytes you have to fork out for the Exchange Enterprise version which is like $4,000.

First off, while I agree with Scott that there's a need out here for a “mid” sized SKU for Exchange... dude, you DO realize that SBS includes Exchange “Standard” and thus even if you buy standalone products you are stuck with the 16 gig even at the Exchange standard version.

Exactly what “are” you installing for your small business clientele if you “are” a Microsoft partner.  Hopefully not 25 user peer to peer networks?

You sir, are exactly the type of Microsoft partner that I ran into when I was looking for one back in the SBS 2000 days.  “SBS is too limiting” they said.  “You'll outgrow it”.... they said.

Guess what dude... I'm still on it. 

Yeah 16 gigs is too limiting..but blasting my blog comments isn't going to move any mountains.  Making a calm argument that we're doing will.

And Scott what are you a blog spammer tonight or something?  You've blog commented the same rant three times.  Enough.  You've said what you've had to say, and if you post one more comment I will remove it.

The glass is half full and we're asking for a refill.

P.S. Do remember that every gig of more Exchange storage is potential for liability, legal issues, and disclosures.  It increases your business risks to be that much of a email hog.  Keep in mind that all those terrabytes are discoverable.  Sometimes forcing people to keep neat and tidy mailboxes “is” a good thing.  Just ask Enron, Arthur Andersen and Martha about email and courts...they might disagree with you on mail retention policies.

Yeah...the catch is ...98 has no security

In yesterday's mailbox came the email from WindowsITPro with an article/commentary by Paul Thurrott and in it he talks about IE 7.0:

 “IE 7.0
   The biggest security hole in any Windows system is IE. Although
Microsoft made many important improvements to IE in Windows XP
Service Pack 2 (SP2), the product is still a conduit for spyware and
other malicious software (malware), phishing probes, and numerous
other electronic attacks. Microsoft is going to attack the problem at
the source: Rather than wait for the release of Longhorn in 2006,
which was the original plan, Microsoft will ship IE 7.0 in late 2005.
At least two public betas will ship around midyear. As with SP2, IE
7.0 will include sweeping security fixes and, possibly, heavily
requested features such as tabbed browsing.
   There's a catch, however. IE 7.0 will be made available only to XP
SP2 users. That's right. Customers still using earlier XP versions,
Windows 2000, or Windows 9x are out of luck. This kind of forced
upgrade in the name of security is dangerous, in my opinion. Although
I agree that XP SP2 includes low-level security features that aren't
present in other OS versions and would be difficult or time consuming
to add, forcing customers to upgrade an OS--with all the inherent
time, difficulty, and cost associated with such an effort--is
problematic.”

uh.... folks... newsflash for ya.... Windows 9x has no security so to even expect something that can protect us like we need to be protected in the year 2005 when the underlying code was probably written back in... oh... say 1996 or 1997 is a bit much.  The same goes for Windows 2000 to be honest with you.  I'd probably say that my first real awareness of Security was back on the SBS 2000 platform in the “code red” days.  Windows XP sp2 and Windows 2003 both are better built to withstand today's threats.

  • 98 has no event viewer and thus none of the benefits of the web site www.eventid.net
  • 2000 has none of the build in protections that XP has.
  • XP sp1 doesn't have the additional protections that sp2 has

Someone once said that you can't bolt security on afterwards.... you definitely can't with Windows 98.  It has no security.

I have full XP sp2 here in the office with the firewall enabled INSIDE the firm for additional protection.  Believe me, I sleep a lot better knowing that I've killed off Windows 98.

Arrggghh...the myths of SBS revisted

So Dean posted about an article in Windows IT pro and one of the commenters was pointing once again to the “Myths of SBS

Unless you're a really small business running only 1 win2k server to take care of all of your needs, SBS 2003 might be the option for you but I would steer clear of this product. You must setup SBS 2003 as a domain controller, if you don't, it's a violation of the eula and the server will power itself down after 7 days and every day afterwards. If you have other servers at your site and possibly other sites with other domain controllers, SBS 2003 won't play nicely with them. It's a domain controller of a different flavor, no other DC's are allowed in this domain, it's a like a single tree in a single forest (why do you call it a forest if there's only 1 tree?). Also, aside from it's packaging indicating that this is an easy product to install & maintain for the non-IT person, real world experience indicates that this is most definitely not the case. If you can stick with Win2K server if that's what you're currently running for as long as you can. It's a rock solid server product without all of the headaches & XP'ish eye candy that SBS2003 brings to the table. If you plan on going with SBS2003, plan on increasing the amount of time you spend at your workplace by the amount of time you'll be reducing your sleeptime by. IMHO, 2 thumbs down for SBS2003! 'nuff said.

Arrrggghhh...... will folks get out of the NT world please?  We CAN have additional domain controllers we just have to be the PRIMARY domain controller and hold all the FSMO roles.  When will everyone understand that we can add as many additional domain controllers if we want to?

Next, Windows 2003 is way more rock solid than Windows 2000... IIS 6 is ROCK solid over IIS 5...nuff said.

The SBS2003 platform shows the “lowered profile“ both in terms of services turned off as well as the Enhanced IE lockdown... nuff said.

Then the article never talks about the killer app of SBS which is Remote Web Workplace....nuff said.

Run with XP's and they use cached credentials such that the issue of a [so rarely down it's not funny] domain controller is a non issue...the workstations log into the domain profile no sweat....nuff said.

Oh well... I guess if people didn't post this kind of stuff I wouldn't have things to rant about on the blog.....nuff said.

I like what I see Mr. Clarke

"Given their record in the security area, I don't know why anybody would buy from them," the former White House cybersecurity and counterterrorism adviser said yesterday, when asked for his thoughts on Microsoft's forthcoming line of security software.

Seattle PI had that quote from Richard Clarke from the RSA Security Conference.

Interestingly enough I don't think Mr. Clarke is seeing what I'm seeing.  On the SBS 2003 sp 1 beta [that has Windows 2003 sp1 in it] I did something stupid and Windows 2003 sp1 kept me from being blonde.  You see, before I ran the Connect to internet wizard to fully enable the RRAS [or ISA 2004] firewall, I stupidly assigned the external NIC an IP address [you see I didn't have to do that as the wizard does this for me] but the point is as I first went to run the wizard on that live enabled NIC the new Windows 2003 sp1 firewall popped up and said “are you sure?” just like XP sp2 ensures that it checks.  You see it was protecting me from my stupidity of putting a live server on the Internet and was protecting me from the get-go by ensuring that inbound protection of a LIVE connection was protected.

Mr. Clarke?  You aren't seeing what I'm seeing .... yeah sure.... we need to get it so that running in user mode is “normal” around here but that's our entire industry.  In my own little way I'm trying as best as I can to make people aware that the software that REQUIRES power user or local admin don't “get security”, but in the meantime, I think you should see what I'm seeing.....

  • A basic firewall that protects that live NIC connection from the get go, from my own stupidity of putting a live server on the web
  • The COM protections that were put in place in XP sp2 now in Windows 2003

Yeah, sir, I'm buying security from Microsoft because I see their CURRENT track record and I like what I see.

Verizon.... "We do stop working for you"

 We never stop working for you.  [well unless you are a customer with a dynamic IP that is...]

Companies can either handle a policy well by communicating in a great way, or they can totally blow it.  Handle it right, you build Customer Evangelists.  Handle it wrong and you end up with blog posts like this one.

Today Verizon proved that they are totally messing up by not notifying customers that they've changed their mail policies.  Eriq posts on his blog the troubleshooting steps and resolution that he had to do to overcome his issue [and it's a great how to on checking mail issues by the way]


"AS OF JANUARY 31, 2005, VERIZON WILL NO LONGER ALLOW BUSINESS OR
RESIDENTIAL CUSTOMERS WITH DYNAMIC WAN IPS TO RELAY THROUGH THEIR SMTP
SERVERS." 


Update 2/22/2005:  Please note it appears that if you don't host your domain with Verizon even if you do have a Static IP they block your sending.  Your only alternative is to route your email through your domain mail hoster's SMTP servers or investigate the third party mail relayers like Eriq used.

All I know is I have it!

From the mailbox tonight is a question about Entourage for Macs and I'm just letting you know I am now going to stomp off and email a few folks and figure out what's up with Entourage.

It used to say we got it on this page. [see blog post]

I KNOW I have at my office a cdrom in turquoise that says SBS 2003 Premium “Entourage” that clearly is part of my SBS 2003 media.

Stay tuned to the blog for more details.

More please, sir?

 The RSA conference uploaded the webcast panel on “To regulate or not to regulate“ and Bruce Schneier [at about 45 minutes into the web cast] makes the point to demand more security from our vendors.

....to paraphrase... “If we are not getting the security we want... we need to figure out a way to demand it...“

There was this security researcher who once said “Don't lose sight of security. Security is a state of being, not a state of budget. He with the most firewalls still does not win. Put down that honeypot and keep up to date on your patches. Demand better security from vendors and hold them responsible. Use what you have, and make sure you know how to use it properly and effectively.“

The funny thing is there are a lot of postings that Microsoft needs to fix the security issues.  And don't get me wrong... I can point out a list of “sighs“ of mine that I'm still waiting for solutions and know that Microsoft needs to do way way way better than they are doing now.  But a lot of our insecurity is NOT caused by Microsoft. 

On a daily basis I use software that states in black and white that it wants me to break and violate a basic tenant of Security fundamentals... the law of least privilege.

If any of these “Windows only“ applications were ported to Linux, they'd be laughed off the face of the planet if they stated “we need to have Root access in order to properly run“.

So “what's in it for the vendors“ anyway...as Bruce Schneier said .they aren't charities are they?  We... as consumers of software need to make the need for “what's in it for the vendors“.  We and only we can start asking the hard questionsRichard Clarke made a call to ask our vendors to detail out their secure coding practices...some of the one that I would ask about would be....

  • What are your secure coding practices?
  • What encryption level/type is provided in your program?
  • Do you support user mode or do you require elevated rights on the desktop and thus increasing my insecurity?

Ask more.

Want more.

We deserve more...and only we can make these corporations realize that “what's in it for them” is our business.  Otherwise, we should take it elsewhere if we don't see them responding to our questions.

Yes! Yes! Oh Yes! Yes David!

Don't worry this isn't the scene in Harry met Sally or some X rated posting or anything, it's just me totally agreeing with David Coursey's column about how we need “The Single Update Service I want Micosoft to create

You see my friend David [who is the one that gave me the “Diva” nickname by the way], is like me.... we totally “feel the pain” of trying to keep a small network of Microsoft systems up to date.  We are just like out big server brothers ...but just have all our “parts” concentrated on one box.  We own Small Business Server 2003 boxes.  In my own network I'm monitoring the patches of Windows 2003, Windows XP sp2, Office 2003, Exchange 2003, ISA server 2000 [soon to be 2004] SQL Server 2000, and a few other things like Live Communication Server and Windows Messenger 5.x [that I had to manually patch recently]

About three years ago I became a Shavlik.com customer because I knew I needed to have just such a one stop patch solution and I didn't see anything coming from Microsoft.  Even the Microsoft Baseline Security Advisor [which is going into a new beta - see below] didn't scan for and patch ISA server 2000. 

When Small Business Server 2003 shipped in October of 2003, Steve Ballmer talked about Software Update Service 2.0.  I saw a light at the end of the tunnel for us in SBSland.  Well it's been a long time in SBSland since October of 2003 and it is indeed a bit disappointing to see another “beta' starting up.

David...oh yes, yes, yes, yes, yes, yes, yeaaasssss!

That is exactly what we need.  I just hope it's sooner and not later.  In the meantime folks... for now here are our steps:


Announcing MBSA 2.0 Beta
MBSA 2.0 is the next version of the Microsoft Baseline Security Analyzer, which utilizes the Windows Update Services infrastructure for security update scanning. Please help us improve the quality of this release. We are currently accepting nominations into the MBSA 2.0 beta program. To nominate yourself for the beta, visit
http://beta.microsoft.com, sign in to the system using your Passport ID and a guest ID of "MBSA20" and complete the survey.

There's technology and then there's..... technology

So I'm getting my “monthly” personal patching done [hairdresser and nails...hmmm....never realized it until now that it is usually a week after patch Tuesday... go figure] and me and my hairdresser start talking about how she bought a new fridge.  Not just any ol' fridge...but as she described it... the one that as you walk into Sears it has the spotlights on it and you can hear the “angel choir” singing as you walk closer to it.  Freezer on the bottom, Fridge on the top, the whole top of the line.  I told her my story about how we bought the washer and dryer and how for the first couple of days we were dragging out as many clothes as we could find just to use the appliances.  We got to talking about Microwaves and we laughed about how we loved the ones that had buttons for “Frozen entrees” ...push and push start and there you go.  No “thinking“ involved.  Just “doing“.  We were near “rapture“ in our descriptions about the technology that made these normal tasks enjoyable.

So where's this late night blog post headed?  Just made me start thinking about how all of these appliances don't bother me with a lot of confusing things.  I can preset all that I need and then they just work.  I think we need more technology in computing to give us fewer choices.

Either that or me and my hairdresser need a life....

;-)

TAZ blog makes a wonderful point

Dear small business owner.... if you are looking for advice...make sure the consultant you hire to advise you on a small business solution has done their homework.  Make sure they understand that:

  • Terminal server in application mode on a domain controller is insane, always was insane and in this day and age of malware, even more so
  • That you only need a single domain and if you buy quality hardware, the issue of redundancy is a non issue.  Multiple forests only add complexity.
  • That if you grow past 75 machines/users/whatever that there's a migration pack.  You don't “rebuy anything“.  You just grow.

It freaks me out when people who make their living providing computer and networking advice showcase as TAZ has in his blog that they haven't done their homework.

Small Businessperson out there?  Ask your consultant point blank how many SBS installs he or she has done.  Even if he or she says only “3” [one to screw up, one to take notes, one for real] that's obviously better than the folks at Tavis' T2 event.

Customers... ask the hard questions.  Find a consultant that is an SBSer.  Trust me.  They are out there.  And there are more of them every day.

.....and Consultants that aren't SBSer's out there?  This is your job.  Do your homework.  Small businesses deserve the right answer.  Become a SBSer.  I'm sorry to be “angry Susan” tonight but a consultant once tried to talk me out of SBS.  Needless to say I didn't listen to him.

How do I call PSS? What is PSS?

In the newsgroup tonight someone when from the eval to the retail version and a driver stomped on a driver that worked and now their server isn't working and he can't get into Safe mode.  And while I called in my buddy ..the king of Disaster recovery to look at the thread it was obvious that the poster had no idea how to contact PSS.....and then I was thinking that you guys out here may not know what PSS is too!


Information for DIYers and Customers of Microsoft

Microsoft Product Support Services.  If you get stuck and newsgroup support is just not going to be timely, I whip out the ol' credit card and call into Microsoft Product Support Services and 1-800-936-4900 [for International folks check here]

And regardless of what is said on the web site, if you paid the $245, even if it's an OEM, I can't imagine Microsoft not supporting the product.

So if you are reallllyyyyy in a panic, know that there are options besides that of a newsgroup for your Server support needs.


Information for Registered [or higher] Partners of Microsoft

For those that earn a living installing computers and networks, there is a difference service option for you [see why I keep HARPING on you guys to sign up for the partner program?]

You'll have more options for support to help you help your client back on their feet as fast as you can.  Sign up!

Dear Mr Gates... I need you to go buy something....

...and no I don't want you to buy a company or an island or anything like that.  I need to you take a short walk from the RSA Conference you are attending and go to ...say the CompUSA store on Market Street in San Francisco.  I want you to buy a computer.  Not a computer that someone in your corporate IT division has set up... I want you to buy an OEM [original equipment manfacturer] computer, take it back to your hotel room, and plug it in.

Now as you set it up and let it boot up, let me warn you, you'll increasingly get annoyed as it boots up.  The desktop will have a barrage of “free for 6 months offers” but as I found out this weekend, that “free” comes with a price where Earthlink obviously sold [or someone did] the email address. 

You'll then not be able to figure out whether it's McAfee's security center that is freaking out, Windows XP sp2's center or perhaps BigFix [if Gateway] or Dell's hardware and software update “reminder” that is causing your computer to constantly want to be connected to the internet when you boot up.  {I finally gave up and just made sure that the icon for “connect automatically” was unchecked}. 

You'll get annoyed because the choices are confusing and there are too many products competing for the desktop.  I don't need offers from Earthlink, Netzero AND AOL cluttering up my desktop.  But that's indeed what I got.

People are saying “there's a buzz” about Apple's products...but you see there's one huge flaw in comparing Apple to Windows.  Apple controls everything from the Hardware to the Software. 

I think if Mr. Gates bought a retail  computer, he's be having a talk with Michael Dell about the junk he was loding up on his nice operating system.  Don't get me wrong, Dell's Optiplex line was a breeze to set up compared to the Dimension as I had to uninstall about 5 things on the “D's” whereas I didn't in the Optiplex.  But I think the home OEM channel is needing some cleanup....and it's not due to the spyware or viruses too...it's just all the junk that got shipped with the computer.

The understatement of the year award goes to ....

“In contrast to the Intuit customer representative, we do not believe this is a reasonable design decision.”

The understatement of the year award for 2005 goes to Shuo Chen; John Dunagan; Yi-Min Wang; Chad Verbowski in the Microsoft Research document....A Black-Box Tracing Technique to Identify Causes of Least-Privilege Incompatibilities...Download their document that discusses “Most Windows users run all the time with Administrator privileges, equivalent to root privileges on a UNIX system. The possession of Administrator privileges by every user significantly increases the vulnerability of Windows systems. For example, simply compromising a user network service, such as an instant messaging client, provides an attacker complete control of the system. We address this problem by making it easier to develop applications that do not require Administrator privileges, thereby decreasing the inconvenience of running without Administrator privileges. To this end, we present a novel tracing technique for identifying the reasons applications require Administrator privileges (which we refer to as least-privilege incompatibilities). Our evaluation on a number of real-world applications shows that our tracing technique significantly helps developers fix least-privilege incompatibilities and can also help system administrators mitigate the impact of least-privilege incompatibilities in the near term through local system policy changes.”

Interesting read....

..btw it's TurboTax that requires admin rights ..... and Intuit's customer representatives think this is fully acceptable....

www.threatcode.com

http://nonadmin.editme.com/

We customers have to start demanding more of our vendors.... that's for sure...

So exactly what are the requirements for being a Microsoft Registered Partner?

From the mailbag today comes the question “What are the requirements of becoming a MS partner?  Do I have to setup so many networks per year?  Attend so many meetings?  Or do I just sign up?”

There seems to be a lot of confusion about the “levels” of the Microsoft partner program.  There are the Gold Certified partners, the Certified partners and then there is the heart and soul of SBSland...the “Registered” partner status.  It's the Certified and Gold Certified are the levels that they need so many MCPs...so many letters of referrals from customers.  In the Registered partner level, they just want your name to better contact you..in return..

In the “SBSLand“ Registered Partner level you get

  • Access to exclusive online content just for Registered Members: Registered Members can access premier content on the Microsoft Partners website. Get the information you need to plan your business, build and maintain your expertise, market and sell, and provide service and support.
  • Microsoft Registered Member newsletter: The latest news, promotions, and updates are delivered directly to you in email every week.
  • Single point of contact for Partner Program Support: Regional Service Centers located around the world can help answer general questions regarding the program, requirements, and benefits.
  • As a Registered member you are eligible to purchase the Microsoft Action pack which is a nice bundle of software to get started in building a SBS test network for patch testing.

Here are the requirements:

Do you use Microsoft software as the building blocks for value-added services such as integration, consulting, software customization, application development, e-commerce solution development, Web and application hosting, technical training and support, or licensing services? Do you use Microsoft software for building and distributing software and hardware solutions? The Microsoft Partner Program is a worldwide program for solutions partners in all segments, including:

  • Consulting Services Providers
  • Independent Software Vendors (ISVs)
  • Independent Hardware Vendors
  • Large Account Resellers
  • Original Equipment Manufacturers (OEMs)
  • Support Providers
  • System Integrators
  • System Builders
  • Training Providers
  • Value-added Resellers
  • Value-added Providers

It takes just a few minutes to enroll as a Registered Member. You only need to:

  • Sign the Microsoft Partner Program agreement.
  • Complete an online business profile.

So what are you waiting for?  If you've installed even a measly ol' peer to peer network based on Windows, you are eligible for being a registered partner!  Enroll! This is just one of those “oh let me just wack you upside the head if you are in any way shape or form already supporting or installing SBS networks and you are NOT a registered partner... you are soooooo missing out on benefits that you SHOULD have“ kind of events.

Go sign up RIGHT NOW!  Do it!  You need to be a Microsoft partner and I won't take no for an answer.

...so to answer your question...they don't count networks, nor meetings, they just want to have your name to better help you be a great consultant.

So I went to go set up a computer today...

...and the computer is for a church so when I signed up for the email account through Earthlink I put in the name of the church in the email address.  It's obviously a “churchy” sounding email name...so imagine my surprise when I tested the email account and 35 emails came down since when I first set it up..... “Mike, did I give you the email address already?” I asked the guy who I was setting it up for... “No”.  Funny thing was...this wasn't what I would call “normal” spam.  About 90% of it was “religious” spam.  Bill Gather was one of the organizations that obviously had bought some email list from Earthlink and was “spamming” out these messages.

You know it's days like today that I realize how “rosy colored” and “naive” I am to think that Ministerial organizations wouldn't resort to something I think it unethical...spam.  It just blows me away that such “religious spam” would even considered as a viable sales channel.  Just goes to show you when organizations that I would think would consider “ethical means” of electronic delivery and not resort to spamming, we're going to have a huge battle on our hands to tame the spam beast.

 

 

The perceptions of patches, and a little bit of OS Stew

.....where's that icon..there it is... click... favorite scans... server... run.... yup tonights the night for the server as I did all the workstations and the other server earlier in the week..... yup missing Tuesday patches..... go, advanced.... force reboot.

...and now I wait for Shavlik to 'do it's thing' and reboot the server.  No runs, no drips, no errors, no big deal.  Not since I have procedures, and a tool that makes it a piece of cake to patch the network.

Scoble pointed to the Commentary by Michael S. Malone on “Is Microsoft dying” and I'd like to take Mr. Malone to task on one point...and I'd like to take the reading community out here to task on this as well and then rant on about a few other comments he made.

Michael says “The only thing Microsoft seems busy at these days is patching and plugging holes.”. 

Dear, dear, dear Mr. Malone... earlier this week... on about Thursday I opened up my email box..the one that is signed up for “all” the security bulletin notification and dude... I had tons of vulnerability notification and Microsoft was just one of the many vendors with issues....wake up and open your eyes to the world of software today ...just about ANYTHING and even the software that was DESIGNED to help secure is needing patching and plugging holes.

This week alone we had....

  • Symantec..our very own software that is “supposed” to protect us with vulnerablities
  • F-secure as well with buffer overflows.
  • Firefox with issues with IDN spoofing
  • and other app vulnerabilites that just make you want to go back to pencil and paper some days

Michael Malone says he smells rot... but I see something else.  Scoble talks about the “blog” phenomenon and is has changed and revolutionized how Microsoft is perceived..but even folks “inside” the wall say to me that they want to be more open, have more communication, do better on acting on feedback, listen more.  They say they need to do even better still. 

In the small business world that I hang with... open source just isn't doing major hacking and carving out here.  In fact, because of the fact that we've got all the new cool parts of Microsoft, we're able to be a heck of a lot more agile than our big firm counterparts.  I think it was Steve Riley who said you had to swallow more of the blue pill to better protect and defend and he's right... our ability down here to have Active Directory from the get go means we have all the cool toys.  XP SP2 with the firewall enabled INSIDE the network is done by many a SBS consultant down here. 

Longhorn?  Call it a new name because I don't need Longhorn and I'm getting tired of hearing about Longhorn... don't get me wrong I need a few more tools and guidance and information, but I'm still sooooo scratching the surface on what I have now Michael.. I don't need a new operating system yet, I still have more toys to learn about on this one. 

Rot?  Tablet PC is hardly rot.  Small Business Server 2003 is finally getting the respect after all these years of “runt server“ is not rot.  Media Center Edition...isn't rot.  Go into a retail store Mr. Malone...even an annoying one like Best Buy..... how much Open Source do you see there?  Apple is still kinda stuck in the corner. Ipod's may be front and center but the rest is not.

And honestly.. part of the “rot” problem and annoyance of Microsoft I would argue isn't Microsoft but it's all the third party crud that gets loaded up on a system these days.  Apple does indeed have it made because they control EVERYTHING from the hardware to the software.  Microsoft doesn't even control the desktop or the Security Center on the retail system that I loaded up the other day... it demanded that I choose between Microsoft's Security Center and McAfee's Security Center.  To me it wasn't Microsoft that was annoying but all the other crud loaded up.

Oh and another thing... in fact... I won't name names...but a “blue badge“ I was talking to the other day [gasp] likes to have ISA Server on the inside of his network combined with an Open BSD firewall on the outside.  Heck even Bill Gates himself is advocating Interoperability these days.

I think it's not rot you are smelling Mr. Mallone..but a stew... a goolash... a melting pot.  I don't think we want 100% of one thing and no choices...but I'm not so sure we're wanting “nothing but open source“ either. 

I think we want it all, Mr. Mallone.

And I think that's exactly what we're getting.

A little too much security got in the way of me trying to be more secure

So I'm out on the PGP web site, bought the personal PGP drive for adding a virtual PGP drive to another workstation for a bit more paranoid security and I go to “authorize the license” and get this message:

Rats.  Okay....must be because of ISA...so let me do a quick fix to allow anything out and try again....hmmm still no go... okay let me contact customer support/tech support.

grrrrr tech support is only 24/7 for their Enterprise customers....okay so I have to send an email to ask for support....okay so I sent an email off..... and now I notice this info:

To submit your license authorization request, please go to http://www.pgpsupport.com/licenseadmin.asp. After submitting the form, you will receive instructions on authorizing your PGP Software within one business day. This excludes weekends/U.S. holidays.

Oh gee thanks...I was hoping to have this in place over the weekend because that's the best time I have with messin' with computers around here without interfering with everyone elses schedules and time.....sigh..... 

...okay so I'm in a mood tonight ...but PGP ..while I totally understand the need for you to put in a “rights management“ system to ensure that only licensed folks get to use your software.... just don't make it hard for us folks buying the software to get what we need when we need it.

... maybe I'll just use EFS instead.....


With PGP 8.0, we are introducing a new license number system. Please follow the steps below to authorize your license and begin using your software.

  • After installing the PGP software, please launch it. When you launch the software for the first time, you are presented with the License Authorization window, which has three fields that need to be completed. Enter your license number that is located next to your "Grant Number" in your confirmation email from PGP Corporation. Then enter your name and organization as you did when purchased this product.
  • Once you have entered the correct information, use the "Authorize" button in the license authorization window to complete your authorization.

In full disclosure

In honor of Church of the Customer's posting

  • Honesty of Relationship: You say who you're speaking for
  • I'd like to think I'm speaking for the SBS owners and customers of the world

  • Honesty of Opinion: You say what you believe
  • Oh yeah...sometimes too much so.. gets me in trouble sometimes....

  • Honesty of Identity: You never obscure your identity
  • Just a SBS owner and admin, if you want to see who I am.. click here

    And I'm a strong believer in word of mouth marketing because it's how I found SBS in the first place.  Also a believer in BTDT... the greatest credential in the world.. “been there, done that”.

    Warning this could be habit forming!

    Someone came into the newsgroup today and said that he wanted to show his firm the power of SBS but they weren't quite ready to “bite off” on networking software.  Well while I've never quite understood this attitude ...because to me we knew that for our firm to grow we had to stop considering floppies as a networking device.... some firms need a bit more of the “show me the power of SBS”.

    Well there's a way to do that.  You can order the Trial Software for Windows Small Business Server 2003 kit and install this 180 day evaluation version.  Before the 180 days over over, get a retail version and install it right over the top and you'll have the real thing.  I've personally tested this out and it truly does work.

    So if you have firm members that just don't get it....

    • Don't get it that they don't have to worry about manually installing virus updates because Trend just automagically updates
    • Don't get it that they don't have to figure out what floppy they saved the work on and now cannnot find
    • Don't get it that they won't lose data on floppies that stop working because they got bent
    • Don't get it that they have centralized backup so data isn't lost
    • Don't get it that they can buy [or these days lease] a really fast scanner/printer/copier and hang it off the network as a shared printer and everyone can use it
    • Don't get it that they can share calendars and contact databases
    • Don't get it that they can buy network enabled software that only has to be updated from one location rather than sneakernetting
    • Don't get it that they can centralize Internet access through one DSL connection that is properly secure and protected

    Show them.  Show them the power... the possibilities... get them hooked on the network habit.

    I cannot imagine doing business without a network ... it's just would not feasable, rational.... we just couldn't function without a network.

    It definitely is a habit I won't give up... and don't ...not even here at home  :-)

    Do you know about the WUS Wiki?

    <in full disclosure I”m a Shavlik customer and religiously use their patching tool>

    The week, the number of patches makes us realize that we need a plan to handle these.  As I've harped on, Windows update is not enough and you need to visit our download page.  There is a WUS [the next version of SUS] in the works and there's a community web page called a WUS WIKI.

    Directions on Microsoft just released their analysis of WUS... take a read on it.

    I can't stress it enough...

    Windows Update is not enough for our SBS boxes

    And Microsoft knows this.....

     

    So I'm getting these SBCore messages....

    • I want to install SBS 2003 as a member server
    • I want to install SBS 2003 as a workgroup
    • I want to install SBS 2003 without active directory
    • I want to install.....

    There is a major flaw in all of these statements... and you've missed reading the documentation that states that SBS 2003 MUST be the primary domain controller and hold the FSMO roles. 

    So the question comes up

    • How can I fix this?

    Easy.  Stop fighting it.  This is the stated requirements for this platform.  SBS 2003 HAS to be the Primary domain controller but you can add any number of member servers to our domain.

    This document lists all the “gotchas“.  Read it ahead of time.  Better yet, read the getting started guide before you begin.  Read this KB article.

     

    Okay there are times that mail isn't junk mail Mr. SBC

    I guess I should have figured it out sooner, I wasn't getting any comment emails coming into my email box from the blog.  I chalked it up to something broken on the blog and figured I'd look into it.  But today a listserve I'm on that I have a cc to another email address I have didn't get that email.  Hmmm.....that's interesting I said, and logged onto the webbased interface to see what was up.

    There, permanently stuck in the "bulk" email filter was 2,475 emails some of them NOT spam email at all.

    Dear SBC.. I turned on bulk email filter for the web only, so that I didn't blast though my mailbox limits while I'm on vacation.  I didn't want you to permenantly leave it on the web so that I would end up looking rude to people by not responding to them.  It appears that since 1/23 anything marked as “bulk“ was never pulled off the server period by my local email account and filtered by me as it used to do in the past.

    It's getting so in the world of email that my office is going back to either faxing or doing a phone call to ensure that the email has been received.  It's a sad state of affairs when we cannot depend on an electronic medium that was supposed to get us off the "paper tiger".

    You want a document to absolutely, positively get to it's destination?  Fax it.  Drive it over to the recipient, but email it?  You might not want to rely on "just" emailing without a return receipt option.

    But... oh here goes my pet peeve of emails......

    • I hate return receipt requests on people's emails when they've sent the email to a listserve.  Annoying as all get out and I hit cancel when a receipt request is received.
    • I hate out of office messages because I think they are too much of a security risk.  You want phone numbers, names of people in the help departments of many firms?  I've got them as OOF messages.  And don't set up a OOF on a listserve because you'll get OOF to death when someone is on vacation.
    • I hate any of the white list technologies.  If you've sent me an email, and I send you one back, you'd better not request me to “authenticate” anything. 
    • Oh and Mr. SBC, I hate it when all of the requests to join a listserve of which I'm a moderator ended up in this bulk mail filter that I only found today.  As the moderator of that listserve, my sincere apologies to anyone who was thinking I was ignoring you.  I wasn't, SBC was interfering.

    Okay, so obviously I have issues with email...... we don't need the Rolex and ads and junk, but I need my email.  Send it to me, okay?

    To all those who have emailed me and wondered why I was ignoring you?  I wasn't... SBC was being a bit too “helpful“.  Sorry.

    Now this is why I love technology

    Scoble pointed to the web site that is showing the SuperBowl ads so that I don't even have to live through the football to see them.

    I'm going to need a magnifying glass

    I was setting up a Dell Optiplex and a Dell Dimension computer and while the OEM product key code was already in the system, the Office product code was not and I had to enter both into the systems.  Okay I know that I'm getting older because the Secretary in the office only knows certain tv shows as being on Nick at Night, whereas I remember them when they were first on [Partridge Family comes to mind of one example], but I felt like I needed to get old people glasses because I could NOT read the product code off the cdrom jacket.  It was sooooo tiny and the “B” looked so much like an “8” that I was about to call up Dell and ask them if they sent out bogus numbers because I absolutely could not read the code number.  David Coursey brings up the point that we're going to need these OS product codes off of our systems when we do the Windows genuine, and the problem is, the number that Magical Jelly bean will show on a OEM product apparenly is not the one that is your real product key code.

    I'm with David... I don't want to crawl on the floor [especially at the office where I'm wearing a skirt, heels and pantyhose most days] and get dustbunnies.

    If there's a sudden surge of sales in magnifying glasses later on this year, you'll know why.

    Isn't that just a kewl idea Garrick has?

    From a blog post by Garrick


    An idea I just had
    Wouldn't it be wonderful if there was a product similar to MS Small Business Server 2003, but called MS Home Server 2003 (or MS Home Server 2005 or something). It would be similar to SBS, but oriented toward home networks rather than business networks. It would probably have the same kind of components as SBS, but with maybe a hard limit of 5 clients (no additional licenses possible to add) and would have features more oriented toward home apps rather than business apps. Outlook/Exchange would be there, and the SharePoint portal server would be there, but geared for a "family" website, with built in photo sharing, blogging, personal webpages, etc. MS could include either antivirus and anti-adware stuff on the server to push down to clients. And to keep it from working in corporate environments, it would only allow XP Home clients, through some secret way that MS would have of unlocking the ability to join a domain.


    Oh man ...woudn't it be though? 

    Except for the e-home of the future can I have a robot that does the dishes and hangs up my clothes automagically?  Something that will automagically hang them up as I change into the “home clothes” so I don't have to pick them up off the floor. 

    Wonder if I can mswish that one?

    I think I'd hire new analysts first.....

    From Businessweek....“But Ballmer may have a tough time persuading customers that Windows is cheaper than Linux. It often isn't. With Windows, end users pay an up-front fee that ranges from several hundred dollars for a PC to several thousand for a server, while there's no such charge for Linux. The total cost over three years for a small server used by 30 people, including licensing fees, support, and upgrade rights, would be about $3,500 for Windows, compared with $2,400 for a Red Hat subscription, say analysts.

    SBS 2003 standard with 5 cals..      $   520.00

    20 SBS cal.....................................$1,830.00

    5 SBS cals ...............................     $   459.00

    That's $2,700 in my book for a full retail [and obviously cheaper if you are upgrading from SBS 4.5... now if you want to add Software assurance...that might get you up to that $3,500....but Redhat's “upgrade rights“ are not the same as Software Assurance. 

    But for Redhat, I'm not seeing where they are getting that $2,400, as I see a base of $900 or so but OS upgrades are not the same as Software Assurance.  Oh I see now what they compare... they compared it to THIS one which I don't think is comparable at all.

    As far as support, I can find SBS support, I'd have a hard time to find Linux support locally that I'd trust [I'm a control freak] and quite frankly I love that I don't have to worry about security issues on two platforms. Patching is needed on any software, any platform and the sooner we all realize that the bad guys are going after anything that computes, the better off we are. 

    Funny thing is, the theme of this year's Bill Gates memo of interoperability is something that us SBSboxes have been doing a lot lately with attaching Macs to our servers.  [me thinks he's just catching up with what we already do out here in agile small businesses, eh'?]

    Let's go off to Dell shall we and get a server for 30 people?  In fact on this page you can get a better comparison of what the operating system prices do and playing around I get $1,756 that INCLUDES the hardware and then if you do a 5 pack of the cals, you get $2,300... which means we're about at $4,000 to drive a box off the showroom floor that INCLUDES THE HARDWARE.  What do you want to bet when those “analysts“ pushed the pencils they included hardware in those totals?

    Folks... I think the moral to this story is “don't listen to analysts” as they have no clue as to comparing or pricing products.  Pick a product that does the job that your client needs and ask in the communities what has worked for others.  I have the knowledge and know how to secure and support Microsoft products.  I'm not as comfortable on other platforms even though I use them in vmware settings on my laptop.

    Push your own pencils and make your own decision....and about that “the culture is cooperative, meritocractic” and all that?  You haven't hung around the communities of SBS, have you?

    So which SCI FI Character are YOU?

    So reading a blog I came across this site that you answer questions and figure out which SCI FI personality you are most like.

    Take a guess as to which one I came out to be.

    Yup.  You guessed it.

    An open letter to the "Bob's" of the world

     

    Sorry to pick on you Bob, but Bob left behind a comment in my post about how I'm seeing “allocated memory errors“ in my SBS2k3 and how after his first [FIRST mind you!] installation of SBS 2003 he didn't think the product was “ready to be shipped“ and too quirky.

    Bob... man I so disagree.. the issue you are seeing with ISA server is just the Lavasoft not authenticating that's egress rules issues...and if it works on the standalone ISA server it will work on SBS2k3. For the record, Microsoft antispyware works just fine.  Either adjust ISA to the all/all/all rule or pick a better behaved application, dude.  I prefer the Microsoft antispyware better [yeah running beta software in a production setting and loving it].

    This is just the monitoring a little not tweaked for those Xeons as that's the common thread on the boxes seeing this issue.  It's the Xeons.  Adjust the monitoring number or if your issue is SQL/SBSMonitoring, tweak the value as obviously they are a bit “hotter“ than normal.  Primarily it's those dual Xeons that I'm seeing with this issue.  It's Hardware based in my book.  Also remember to visit the download page for non Windows/needed SBS part patches.  Not to pick on Bob again ...and I don't mean to assume but many folks don't keep their boxes [even non SBS] as patched as they should be and so you need to make sure you keep those in mind.

    Bob... ping me with your email address because I'm sorry I sooo disagree with your assessment and I think you are doing your clients a disservice with this attitude.  I don't think you are plugged into the SmallBiz communities and you might not be plugged enough into the Partner program to use the Technical Support newsgroups for partners.  Coming to my blog and just posted “yeah it's not ready for prime time“, isn't exactly showcasing that you've ensuring you are covering your support bases properly.

    If you've only had one install of SBS2k3... dude you are a newbie.. we say the first install you are just learning, it takes to the third to be the real one.  If this is your first production install...sorry but you can't make a blanket statement like that after one install.

    And not to pick on Bob...but here goes an open letter to the Bob's of this world:

    If this is your first time installing/seeing/using SBS 2003, dude, first off we say in SBSland the first time is a test, the second you take notes, the third you do it for real. 

    You know why I'm here?  Because a Microsoft partner didn't take the time to learn this system properly and another one tried to talk me out of the platform.  I get asked these days for people who can support SBS 2003 and it totally warms my heart to know that I can give an emailer the name of a person that I KNOW is a “SBSer” who can set them up right.  I'm lovin' it that I know a network of people around the world that I can say “here's this persons email address or phone number, they'll treat you right“.

    But boy, when I hear that a consultant doesn't take the time to learn about SBS, that they give a SBS customer bad information or advice, I makes me absolutely boil.  I've literally sent SBS2003 books to Microsoft partners to wack them upside the head to better support customers.  I had to send an email to one firm to make sure they even got the books.  Hopefully someone there read them.

    So, Bobs of the world, don't have an attitude like SBS 2003 isn't worth it or too much trouble...because quite frankly... there's a lot of people in the community that would disagree with you... because you are turning your back on a marketplace that is under served and has tons of potential.

    And as I ranted on yesterday, if you install SBS 2003 boxes and are not a registered partner, sign up.  If you are a certified or gold partner, don't assume that just because “you do big servers” that you know what you are doing in “little server land”.  Start out first by following the wizards.  They are there to help you.

    And Bob?  Sorry to pick on you again, but don't judge an experience by ONE experience.  In SBSland you are a newbie.  Come and join us in the world of SBS where we see the possibilities.....not the limitations.

    The Myths of the Microsoft partner program

    Got an email today and I was urging them to sign up on the Microsoft partner program and the response came back that “because I'm a one man band, Microsoft tells me that I don't qualify for membership”.  Huh?  Hello?  Where did you get that idea from?

    Here are the “requirements IN PLAIN ENGLISH” for the Microsoft partner program for the REGISTERED LEVEL:

    • Do you install computers, networks, technology for a living that have the words “Microsoft“ somewhere involved in the process?
    • Do you breathe?
    • Can you click a button on your computer?

    If you can answer yes to those three questions, you qualify for the Microsoft partner program at the registered partner level.

    Just like the “Myths of SBS” there are these myths about the Microsoft partner program.  YOU WANT to sign up!  You get partner newsletters, you get information, you get tech support options and to merely sign up for the “yes, I'm breathing status” of Registered, it doesn't cost a single DIME.

    So right now, this VERY MOMENT... click RIGHT HERE and sign up for a registered partner status.  What in the world are you waiting for?

    It amazes me that the VERY people that install the MOST SBS boxes do not get it that THEY NEED TO BE a Microsoft Registered Partner. 

    Keep in mind that I'm not implying that you don't need to have some sort of experience or compentency in this but dude, if you are installing and supporting and consulting and delivering solutions that include Small Business Server 2003 ... YOU NEED that connection to Mothership Microsoft.  You ARE the ones they want, they NEED to be connecting with.  YOU NEED to be a registered Microsoft partner and I won't take no for an answer.

    :-)

    Big server land versus Little Server Land

    There is one thing that both Dr. Jesper Johansson and Steve Riley say in a lot of presentations...they say that “Account lockout has no value”, that it will “cause a denial of service”.  And this is ONE area that I timidly disagree and say... sirs?  I think we can handle this.

    • Big server land knows that account lockouts cost $70 a help desk call.
    • Little server land says “it doesn't happen that much and we can handle it

     

    • Big server land says “this is the number one PSS support call“
    • Little server land says... “how we set up DNS is OUR number one support issue

     

    • Big server land says that someone could do a denial of service against our website.
    • Little server land says ...”uh...we recommend you don't host a website if you want to be nice and paranoid

     

    • Big server land says it adds no additional security.
    • Little server land says ...”that may be for you, but it lets us sleep better at night


    I think we can handle account lockout.  What do you think?

    Like yeah, Dude! We do need a MCE Server!

    There are times sometimes you want to go.... yo...dude...what have I been saying?  Scoble tonight ponders about a home server.. not a mirraserver but a server based on Microsoft Media Center Edition.  Like YO DUDE...this is what I've been saying for like how many years now?  Especially I said it after touring the E-home at Microsoft.  As we toured the home of the future...well..the home of the future for GUYS as we gals still had to cook and clean and pick up the dustbunnies and what not.  But as we walked around the house I could see.. wow they need a server here.  My friends in LA already have in their closet a wiring cupboard that has the needed router, wireless access point, replay TV connectors, etc.  The house of the future will have a server.

    I will wack Scoble upside the head on one thing though, a server in my world is a dedicated box that has dedicated software on it.  The title of this software has “SERVER“ in the name.  Not Windows XP media center or Windows XP.  So many of my fellow computer geeks consider a “workstation“ that they make into the “Mothership server“ role as a server and it's not.  Servers are designed from the get go for maximum “serving“ and they are not designed as a “client“.  MCE is a “client“, not a “server“.

    In one of Scoble's link blogs they talk about the lack of a “cult” for MCEers.  Man I guess I'm just more friends with geeks but everyone that I know that have MCEs are quite “culty” about them.  Heck, when two SBSers got together for lunch did they talk about SBS?  No, they talked about MCE. 

    So folks..yo..Microsoft... wake up and realize that people are already making the product that they want to have.  A home server. And while we're in rant mode tonight, I was relaying my “computer purchase from h-e-double-toothpick story and everyone in my office says the same thing about their Best Buy Computer experience.  They hate the store.

    Build us the product people are starting to want.

    Sell it in a better way to us.

    Sam the SBS 2003 Server ....the Spammer

    We start this interview with Sam the SBS 2003 server

    Q.  Hi Sam.... uh Sam?  You okay?

    A.  Uh... well.. I'm kinda embarrassed,

    Q. Embarrassed?

    A.  Yeah, some of my fellow SBS 2003 server boxes ...well their owners and consultants haven't patched me like they should.

    Q.  Patched you?

    A.  Yes, well just like you would with a car, I need monthly maintenance and that includes patches.  And the thing is Windows Update is not enough.

    Q.  It's not?

    A.  No, it's not.  You need to visit my download page in addition to Windows Update.  And people running Popconnector and haven't visited that page....well... they kinda got into trouble the other day.

    Q.  Into trouble?

    A.  Yeah they kinda caused a mess by sending a bunch of emails.

    Q.  Oh wow that's a really big mess.

    A.  Yeah, a real big mess.

    Q.  So what's the best thing to do.

    A.  Well obviously download those patches.  And I'd also recommend folks review the password on the Administrator account.

    Q.  The admin account?

    A.  Yes, by design the admin account cannot have a lockout policy applied to it so it's really important to ensure that a VERY strong password or passphrase is selected for this account.

    Q.  That's good to know.  So Patching and Passwords is the lesson for today?

    A.  Patching and Passphrases, actually!

    Q.  Cool, Thanks Sam!

    Hardware, vendors and other rants, oh my!

    Wayne pinged me and asked if I had any Netgear PS110 print servers here and I don't.  Seems like the servers just don't want to work on Win2k3 and you either have to buy the 113s or buy some other print server.  Now we all know that hardware firewalls and print servers are just code in a box and you would think that they could just flash it or something but it acts like the vendor doesn't want to do this.  Hey Netgear, how about some better response than this?  Listening out there, Mr. Netgear?

    Speaking of vendors, when you buy software these days, do a “Howard/LeBlanc” on it.  A what you say?  A bit of “Secure coding Second Edition” sanity check on how it's set up, what it wants you to do on your system, what it's installing on your computers.  Ask for the specs BEFORE buying the product.  Ask the vendor how “securely coded” they are.  Threat Model that sucker too if you can.  We as consumers have every right to ask how things are setup.

    I once had to go up to like third tier tech support to get the right answer when a vendor said they needed an “inbound port 80” connection to our server.  I was like WHAT?  You HAVE to be kidding!  Well come to find out it was like an outbound connection [like we all do outbound connections] and the initial three guys we talked to had no clue. 

    If you don't know if the vendor specs are okay, run it by someone more paranoid than you are.  Big firms can do project requirements that lists specifications.  We can't.  But we can start in our own little way start putting the seeds of “hey are you coding right?” into the minds of all software companies that develop for small business.

    Wonder if it would be in poor taste to send Scott Cook [CEO of Intuit] a Secure coding Second Edition just to make sure he can hand it to one of his devs to make sure they've read the book.

    Migration just sucks, let's face it

    I want to revisit yesterday's blog post talking about different ways to go from point A to point B.  There's something that is glossed over in the “zeal” to showcase that SBS 2003 is just...well it's just Windows 2003 [other than we are SO much smarter than plain Windows 2003 that we dont' allow Terminal Server on our Domain Controller ...but that's another hotly contested blog post].  Nearly anything you can do with migrating from/to Windows 2003, you can do with SBS 2003.

    But, there's something to remember in all of this talk of migration.

    Let's face it.  The process sucks for the consultant.  You are ripping out a working network and hopefully not walking off a deep cliff that you can never return from again.  The Official Microsoft ADMT migration method is the one that Mothership Microsoft will support. 

    No matter whether you do it the old fashioned SBSland way of “clean install“, rejoin the domain, and then attempt to make your users are happy that you kinda put their desktops back the way they were, or any other method, migrations is just kinda sucky.  It's equivalent to choosing a “C-section“ or a “natural birth“ method.  Both have the same result. Both can have issues.  Both can have side effects.  Both involve pain and drugs [drugs in the IT migration case is in the form of caffeine].  Both have huge rewards at the end.

    Kinda like we joke about when learning SBS for the first time [install it once, screw it up, install it twice, take notes, install it a third time to check your notes], the same thing is true for a migration plan, you need to test.  Even then, stuff happens.  If you have never done even the Microsoft ADMT migration method before, your client is not the one you should be practicing on.  And for those DIYers like me, realize that I've got a support net that's second to none.  [Admittedly though when I needed to rerun the Connect to Internet wizard tonight and ISA web proxy was barfing, it was the fact that I had a laptop still able to get out to the web to find me support that helped better than the Tech Call I made to Microsoft.  [More on this lovely event in a separate blog post]

    So what's my point here?  My point is that whatever migration path you choose, be comfortable with that path.  Know why you chose it, why it's the best plan of attack for your situation and just be prepared.  It is doable.  It is possible. We do have options.

    Just remember that you can have

    • SBS and a file and print server.
    • SBS and side web server in a DMZ
    • SBS and another SQL server [with cals and what not extra]
    • SBS and a terminal server
    • SBS and multiple servers
    • As long as you stay below the magical limit of 75, you can add any number of servers.

    I am constantly amazed by the number of people think that SBS can only be the one server.  Oh and Backup Domain controller or BDC on a SBS network?  I've given up trying to correct anyone about the “BDC thing”.  It's a leftover from the NT 4 days and isn't relevant anymore...but if you ask me “Can SBS support a backup domain controller?”  I'll probably say yes because I've given up trying to correct the Universe over that misconception.  But yes, we can add additional domain controllers, and member servers, and file servers, and print servers, and......well just keep thinking of the possibilities...NOT the limitations.

    I just got the "Networking Infrastructure Solutions" for SBS 2003 from the Action Pack

    I just got the “Networking Infrastructure Solutions“ from the Action pack and the diagram for networking on the back is a single nic setup.  I just don't get it why every single time I see an official Microsoft “small biz” setup it's a single nic.  You would have to pry my cold dead fingers off my two nic ISA server setup at the office and my two nic RRAS server at home.  I don't want to rely on a hardware router firewall as my only protection and I'll tell you an excellent reason why.

    My router at home DIED tonight and was causing such excess packets that it was slowing down my network connectivity.  Now why do I want to rely on a firewall that I haven't patches or bios flashed since the day I bought the dang thing?

    I want a stupid cheap firewall on the outside and then my big beefy ISA server firewall on the inside.  [and not to mention in a few short months ISA 2004 as part of SBS 2003 sp1 which we will get as premium customers for a nominal handling and shipping fee]

    I do agree with one push in the document.  The push to migrate OFF of Windows NT.  It seems like everywhere I go people are interested in migration.  And yes for the record you can even migrate from Windows 2003 and Exchange 2003 to SBS 2003.  Now why you'd want to buy the normal stuff in the first place I have no idea.  ;-)

    The stuff we take for granted

    I'm sure people wonder what exactly is my job.  Sometimes that's a very good question.  Somedays it's just standing over the shoulder and telling someone in the office how to attach a file to an email.  Somedays it's trying to visualize what a client is looking at over the phone.  Sometimes it's trying to visualize what my partners are looking at on the screen. So many times I have to walk over and see what they are looking at and more often than not, I say “oh yeah, just click there”.  And they'll say...where?  “There, I say... right there”.  I can see the obvious “click“ but they can't.

    It's funny that just right after yesterday's post about documentation that was prompted by a newbie SBSer in the newsgroups who came looking for real basic documentation as he was helping to set SBS up in his small firm... comes an article about “the basics”.  I chaired the Top Technology survey and helped “craft” the descriptions.  And in our survey of fellow “uber geeks”, the top issue was Security [gee that's a surprise].  But when the Ohio Society put it out for ALL of the membership to revote on their idea of the top ten...what was their top issue? 

    Finding out where to click.

    Learning technology was their biggest issue.

    It's even obvious in my firm that there are those that are the “technology enablers” and those that ...well are still just dealing with the technology.  John Pocaro back on blogging again, has some great productivity tips about handling email overload that they do in Microsoft.  But they are a pretty darn consistenly agile firm. 

    The “real” SBSers are still a bit lagging behind, I think.  What are my goals this year as compared to his daily tasks? 

    • To get more people to use the shared calendaring.  I have a few but not all using it.  Some are still relying on paper calendars.  Lose the paper this year.
    • We're doing pretty good on saving in file shares but my weekend loss of a desktop reminds me to put a better, stronger emphasis on redirection of the “my documents“ and remind folks to NOT store on local hardrives.  SeanDaniel.com talks about how the My document redirection is for “backup“ purposes.. I'd add how about for physical security purposes?  I can and do physically secure the server... I can't the desktops.
    • If the item is of a personal [personnel] nature, I'll be setting up access controls for that location and deny everyone BUT the people that need to have the information
    • Install Lookout on all the desktops
    • Have more training sessions and do more “picture“ how to's.  People remember with pictures not words in my office.

    So I think this year I need to concentrate on taking the concepts that I take for granted and making them more normal for everyone else.  So that folks will just know to click “there”.

    The ethics of marketing

    Vendor:  noun:  one that sells something

    Customer:  noun:  One that buys goods or services.

    Salesperson:  noun:  A person employed to sell merchandise 

    VAR/VAP:  Value Added Reseller/Provider

    Value:   noun:  quality considered worthwhile or desirable

    Added:  verb:  To join or unite so as to increase in.... scope

    I looked up the definitions of these tonight for a reason.  On a community listserve the topic came up regarding “should vendors be allowed on a peer resource list who's charter states that it's designed to discuss issues around the marketing, sales and development of small business IT consultants for those IT consultants servicing small to medium businesses“ and it just made me think a bit.  Especially when some of these “customers“ of vendors are obviously, vendors themselves.. I would think that people who are themselves vendors would want to try to bridge the gap between customers and vendors.  The concern was that the “vendors“ on the list would turn on the “sales and marketing“ mode and the real truth would get overwhelmed by the advertisements and offers. 

    I too, am sometimes guilty of talking about “marketing” as the dark side.  But here 's the dumb thing... it's doesn't have to be.  Sometimes the best marketing is just being honest.    Jackie Huba today in the Church of the Customer [there's that word customer, again] talks about a disturbing trend in marketing. “Stealth Marketing” as they call it.  And included in the post is a very interesting discussion of “ethics in marketing”.  [Okay, I'll admit that I've never quite thought of that phrase quite like that before].

    In an email thread that I was on today, someone wrote that they didn't trust a company to have their [the customer's] best interest at heart.  I find that statement a bit odd since it would seem to me that any company would want to have their customer's best interest at heart because without that customer, they wouldn't BE a viable company.

    Jackie talks about that there's a “growing demand of transparency and credibility”. There is isn't there?  Too often I see it time and time again that when the “salesman” says “Oh we can do that” and totally overpromises what the item or software or technology can do and all that ends up happening in the long run is an unhappy customer.  If there is one thing that I could say to any company wanting to bridge the gap between vendor and customer is to just BE HONEST.  I don't expect a firm to say “oh we totally screwed up when we promised you the moon”, but I do expect more of an honest “we can't do that now, but we're working on it for the future”. 

    In reality, even though over time I've turned into this hybrid of a wacko SBS customer that is turning into a Windows Software Patching ebook author and newsletter author, I still feel a lot like just a customer around here making sure that the SBS customer gets a fair deal.   I don't like it when a SBS customer doesn't get the installation experience he or she deserves.  I don't like it when consultants don't take the time or the energy to learn the SBS platfom and install it and support it the right way. 

    It drives me crazy when people constantly hang onto the myths surrounding the platform.  I was on a security listserve where the topic of having Internet Information Services on a domain controller and here's little ol' wacko SBSer me piping up and saying that these days I wasn't worrying about my domain controller and IIS6 on there but rather freaking out about controlling my workstations.  In the ensuing back and forth threads it was very obvious that people still had stuck in their minds the steroetype of SBS.  “Limitations“ was definitely in their mindset.  Once again the myths of SBS surrounding the backup domain controller, the lack of expandability in their minds.... [hello?]  Don't people know that once you hit the 75 limit there is a transition pack that allows you to grow past 75 and split off the parts to separate boxes if that is truly your heart's desire?

    Instead I don't see limits at all... I see possibilities.  Already a couple of folks at my office are thinkin' ...hey with this remote web workplace.... I don't have to come into the office all the time to do my work... I can do it from home!   That's right.  And my boss already asked about email on the cell phone that he saw some other Attorney receiving and responding to.  As I told him, you want it?  Say the word as we can set it up!  [He declined because he said the Attorney was constantly emailing on his phone].  But the point is that seeing technology truly in action, honestly, and credibly had done far more to “sell“ my boss on technology than any glossy ad had done.  He saw it working in real life and asked me about the technology.

    The “Build your business“ ad campaign is my FAVORITE ad.  To me it so much showcases when the Vendors and the VARs and the VAPs and customers all come together and synergy is made what possibilities you can have.

    To all those VAPs and VARs out there.. be transparent and credible.  The best way to sell SBS is to fall in love with it yourself.  Show that customer how it can grow and expand their business by making it more agile by being a showcase of SBS's ability for agility yourself.

    To those vendors that support VAPs and VARs, be honest and responsive.  Admit when things in the channel don't work and be honest that you can't change things overnight but you are working on them.  And let's be honest, there are always things that need to be changed.  No one is perfect. 

    To the customers of SBS, demand this transparancy and credibility of your consultants.  The best ones are a part of your life.  The best ones are in reality a member of your firm and truly do have your best interests at heart.  The best ones are a part of your team.

    Sam the SBS Server answers the question "Can I have a backup domain controller?"

    We sit down again with Sam the SBS 2003 Server and ask a few questions:

    Q.  Hi, Sam, it's been a couple of weeks since our last Q and A and we just had to do a follow up.

    A.  Sure thing!

    Q.  We got a question via the mailbag today as to whether you could support a backup domain controller, there seems to be a bit of a misunderstanding about that, can you clarify that?

    A.  Sure thing.  I don't know how that myth got started.  I can INDEED support having a backup domain controller in my network and don't mind it in the least.  In fact you probably want to have one around when you have branch locations.  But remember that when you have XP pro machines attached they use cached credential if they can't find me around [say they are laptops or what not] so it's not quite the big issue that people think it is. 

    Q.  So you can have backup domain controllers and other servers attached to you?

    A.  Oh, absolutely I can.  Like here where I live... I actually ...well...guess I might as well disclose it here... I have a relationship with Tammy the Terminal Server. 

    Q.  Oh, really?

    A.  Yeah, we have a strong connection, she's acting as remote Terminal Server desktops for some employees at the office. 

    Q.  That's really cool.  Congratulations on the relationship. 

    A.  Thanks.  Yeah it's pretty recently that we got together.

    Q.  So are there things you can't do? 

    A.  Yup, there are some things I must have and things I can't do, but it's a short list.

    Q.  What are those?

    A.  I do not support active directory trusts and must be installed at the root of the forest. There must be only one of me in any domain.  I must hold all of the flexible single-master operation roles [FSMO], I can't be demoted.  I max out at 75 users.  I am just like normal standard Windows 2003 and have a maximum of 4 gigs of RAM.  I cannot [and wisely SO, I might add] do Terminal Services in application mode, but I can be remotely administered via TS.

    Q.  What can you do that normal Windows Server can't do?

    A.  Well for one I offer SO much more than normal server it's not funny.  I offer Exchange 2003, I offer Outlook 2003 licenses to all my licensed workstations, I have Sharepoint with special templates that offer up unique features like an help desk, I have ISA server 2000 [soon to be 2004], SQL server 2000, and Front Page 2003 in my Premium version and I have Monitoring emails and Remote Web Workplace.

    Q.  Remote Web Workplace?

    A.  Yeah, let me point you over to Tristan's blog where he called it the Ninja feature of SBS.  I was pretty proud of that.  It's a way for folks to remote back to their desktops at the office.

    Q.  Okay I think that's enough for tonight... so just to recap you DO support a backup domain controller.

    A.  Oh sure thing I do!

    Q.  Thanks!

    A.  My pleasure!

    [today's excuse is that we're out of Dew at the office]

    P.S. Sam would also like to indicate that in the AD world “backup domain controller is technically not true.. we're just “ADDING” an additional domain controller..but the phrase “backup DC” is leftover from the NT days and commonly referred to as a reason for not wanting to install SBS for those more Enterprisey.

    Save a Smart Phone from utter destruction -- Patch your POP Connector

    Today an email was sent out and it was cc'd to several SBSers.  Due to the fact that there were a couple of SBSers on the list who had not patched their systems for an issue with the POP Connector, those of us on the email blast are now receiving the email....over...and over....and over...and over.

    They obviously had not patched for Knowledge base 835734 which says “The SBS 2003 POP3 connector may incorrectly re-send certain messages to recipients who are not part of your SBS 2003 e-mail domain.”  Well everyone on that list can attest that it's not a “MAY it's more like an “IT WILL”.

    Folks I cannot stress enough HOW IMPORTANT it is to patch your systems and today's fiasco points out HOW IMPORTANT it is to visit the SBS download page and install ALL OF THOSE PATCHES in that order.  The only exception is if you are not using POP.  If however, you are using POP.. PLEASE on behalf of ISPs and email recipients throughout the world that are now being bombarded with messages... GO PATCH YOURSELF.

    • Go to windows update - update your box
    • Go to the SBS download page - update your box in the order on that page

    Patching your box is very important and the people in Mothership Redmond know this.  They will be working on making it easier...but for now, THIS IS WHAT YOU NEED TO DO.

    Let me also take this opportunity to tell you about how all my ranting on the Patch Managment listserve turned into a 'gig' on Windows Secrets for a column called Windows Patch Watch.  My column is only in the paid version, but there's a hint of what is included.  Patching is PART of life and the sooner you understand that we do have information and resources, the better off you are.

    If all you are doing is Windows Update... YOU ARE NOT FULLY PATCHED. 

    Over the New Year's holiday my firm got nailed with an email message that kept resending and now that I think about it more I'm positive it too was from a SBS box as the cc mail list included folks that I know are SBSers.

    Please...on behalf on my own email box and that of a poor SBSer who can no longer sync their mobile device for fear of getting 5 more copies of an email, patch your POP boxes.

    Like now.

    RIGHT NOW.

    PLEASE!

    We've added a bit of "intelligence testing" to the blog

    In addition to adding the search box for the blog, [see the box above Yoda to the right] we've adding something else tonight.  A bit of “intelligence testing”.  You see like every other “good thing” is this world, we were being overwhelmed in MVP blog land with blog “spam”.  Christian in particular was getting totally nailed.  Thus tonight we added a CAPTCHA to the blog.  A what you say?  A technique to ensure that only humans are posting comments to the blog.  We're using a variation of “Gimpy” to visually distort a random number or word.  At the present time, only humans can process this and convert this distorted image.  CAPTCHA stands for Completely Automated Public Turing Test to Tell Computers and Humans Apart.  Steven Toub talks about captcha in this MSDN article.  Stefano Demiliani and Brian Desmond both have to be thanked...first for Stefano for sending over the Captcha code to add to the blog and then the adjustments to postcomment.aspx and then to Brian Desmond to kindly fix this “blonde's” inability to adjust the web.config properly in the first place.  I had the extra code needed in the wrong place.  Brian also helped to identify the additional code lines that I needed to add to the other “skins” that Stefano didn't have so I could keep the LuxInteriorLight skin that I have.

    So now when you go to comment, there's a bit of a funky distorted image down there that you have to type in before you are allowed to submit.  I'm sorry about the inconvenience, and I hope you understand it's just there because bad guys and spammers are jerks.

    Why they think people will buy stuff off of blog comments ... I have no idea...but obviously someone must click and follow there stupid links otherwise they wouldn't do it.  So do your part, will you?  Tell folks that blog comment spam should be avoided.  Don't give them any more reason to do it in the future.

    SCW on SBS? DDT!

    In the world of geekdom we use many abbreviations.  Small Business Server 2003 is abbreviated to SBS.  The new Security Configuration Wizard that will be included in Windows 2003 sp1 is nicknamed SCW.  And DDT?  That's Jason's [a tech lead in Mothership Charlotte] phrase when you shouldn't do something on a SBS box:  “Don't Do That“.

    Windows 2003 sp1 will ship with something called the Security Configuration Wizard...the problem is .... we're already pretty Security Configured as it is and don't need it.  In fact, if you run in on a SBS box you are going to end up shutting off something that I think provides you with MORE security.

    Just for grins I ran the SCW included in the Windows 2003 sp1 release candidate on a SBS test box just to see what it would break.  And based on my unscientific testing it's going to hurt us more then it helps us.  In fact it was interesting that it didn't really do much on our SBS boxes that I would call of any real value. 

    The major change it made in auditing, changing the auditing of directory services from “not audited“ to success, could actually hurt us, as SeanDaniel.com pointed out that we shouldn't be auditing that.  The good news is that it appears our SBS unique auditing policy does kick in but I'd rather not mess with the stuff that the SBS team has done to make backup work.

    Next the other big thing that it hurts more than it helps is turning off the performance monitoring and alerts which will blow off our SBS monitoring email.  I don't know about you, but I check that every morning just to make sure that my server is a “happy camper”.  Again, why mess with a good thing here?

    You see, SBS is already pretty well “tuned” to begin with.  We really DON'T need the Security configuration wizard at all.  In fact, I would argue that these days, it's not my server that I'm worried about at all.  In fact, I'd much rather have a security configuration wizard for my desktops than I need one for my server.

    Reminds me of something funny, in the newsgroup the other night a poster asked “Is there a document on creating a bulletproof, high security SBS server?” and both Javier and I said “Yeah, don't have end users!”  Seriously, what is the “thing” that introduces the most risk into my network?  End users.  If I could just have a wizard for them, that would be real grand.  I have one that we joke about, but it's a bit messy in it's application.

    I would argue these days that you can't just look at protecting the server.  And in fact if that's all you are looking at you are so missing out on where most security issues are entering these days... at least in the small business world of computing anyway.  Heck this weekend's burglary showcases even more than ever that my weaknesses are my workstations, both in terms of my inability to physically protect them [even though we did have an alarm system, the machine taken was near the front of the office and quite visible from the outside, definitely a smash and grab], and to lock them down via group policy in a simple and easy manner because many of my line of business applications refuse to work without administrator rights.

    So if you start hearing in the “buzz“ from Microsoft about a Security Configuration Wizard and wonder about it's applicability to Small Business Server 2003 know two things:

    1. We are already pretty tweaked as it is and running this wizard will only hurt not help
    2. The folks in Mothership Redmond are going to come out with our OWN SBS 2003 sp1 which will include ISA 2004 [for those folks on Premium edition] and thus you'll want to pass on downloading and installing the normal Windows 2003 sp1

    So about that Security Configuration Wizard on Small Business Server 2003?  Just Don't Do That! 

    The experience of buying a computer -- ugh never again

    I had to buy a computer in a retail computer store today. 

    I hope I don't have to repeat the experience.  You see we had a bit of a problem at the office.  We had a break in and lost one desktop.  Fortunately because there is NOTHING on that desktop that has identity information on it, I had no SB1386 notifications, and because I had pulled an inventory script of the network prior to migration, guess who had a full itemized listing of what was stolen.  Came in handy!  Because all of my data is on my server, and once I got word that it was fine, I was much more relieved and just more in a “Oh bother” mood [as Pooh bear would say].

    But I needed to get a computer back in that person's desktop as soon as possible.  I normally purchase systems from Dell, specifying what I want, but decided to order the Dell and then get an inexpensive desktop at a retail store for Monday morning.

    I've come to the conclusion even more than before that the retail experience is overwhelming and confusing.  I went into Best Buy with a range of computers in mind, found what I wanted and then went in search of a salesman.  Now I can't blame Best Buy for being busy and having their salespeople needed to go in detail over all the options, but I can fault them as to the ambiance.  Blaring stereo noise coming from the video section, and just an overall “cluttered” feel.  The Windows Media player was getting a lot of attention but it was in the far back wall and the one kid that had settled down in front of it had pulled out a chair and was sitting in the middle of the aisle working the remote.  The area where the laptops were, again seemed a bit cluttered.  You can definitely tell that Laptops are hot sellers because there was more floor space for them than for desktops.  I could tell that I was not in my normal “patience” mode today because after waiting for about 15 or twenty minutes for a salesman to free up I finally left BestBuy and went to CompUsa where I bought a desktop.  Now trying to find a XP Professional machine when you want to attach to a domain was just about impossible.  Fortunately I keep a copy of XP Pro upgrade around at all times “just in case” and I have Office 2003 MOLP media that I have licenses for so I knew I didn't care what OS the machine was, as I'd put on it what I wanted to. 

    After getting the retail box home I found it had the following installed:

    • Norton antivirus suite
    • McAfee security suite
    • XP sp2
    • BigFix Consumer
    • AOL

    Ick... and I promptly removed all of those.... well obviously NOT the XP sp2  :-)

    Then because I couldn't find a desktop WITHOUT about four media slots I had to go into computer management and move all the media drive slots away from my network drives.

    There was a guy there comparing prices to Costco.  You know that makes me wonder about if there was more “small business network computers” there at Costco that had XP pro it might be better for small businesses.  I don't know how a small business would ever find a computer SBSized in a retail store these days.  No wonder all the VARs and VAPs complain about small businesses ending up with XP Home.  It's hard to find a XP Pro from a retail store.

    Did see an interesting thing at the checkout.  A plastic bubble pack for a $99 per month subscription to XDrive with a 5 user version that advertised file sharing and collaboration.  Chad was talking in the listserves that he does whiteboxes because retail computers load up with Soooooo much gunk that they spend more time uninstalling all the junk that it's just not worth it.  I definitely found that to be true today.

    To all of those folks who beleive that you can safely run TS in app mode on a SBS 2003 box:

    To anyone who truly beleives that running Terminal Server in Application mode on our SBS 2003 domain controller can be made secure and could ever be secure, I am reminded of a joke that Dr. Jesper J said and has been repeated in SBSland.... “what are you smokin' and why aren't you sharing?”

    Today, in addition to screwing up the user versus cal in Terminal server I loaded up more applications on it.  I loaded up Office application on my Terminal server [keeping in mind that normally we tell folks to NEVER install any applications like Office on a server.]  I flipped the “Themes” service to automatic and started it so that the desktops could “look” like Windows XP.  I uninstalled [but only for the users] the Enhanced IE active X blocking.  I basically lowered and totally introduced threat vectors all over the place.  All the hard work done by Michael Howard and his team to protect that server from the stupid user, I totally ripped out everything that his team did.  I still haven't even grabbed the security resource kit to apply the recommend guidance.

    How can anyone honestly and truly think that they can in turn ACL and permission themselves back to the lowered attack surface that the Microsoft server team built. 

    I enabled services, I installed software [which reminds me need to Shavlik that box again because that's “unpatched Office 2003 as it's fresh off the CDrom”, I'm letting a user “drive” that box instead of normally how my domain controller runs, left alone to do it's job, with most of the time having me remote in from my desktop and not even walk over to the console. 

    Sorry all you folks who think that they have the skill to lock down a domain controller enough so that it can be run in TS in application mode, I just so totally disagree with you folks. 

    You want to introduce too much risk, Way too much risk.  Remember, where I'm at, in California I must make reasonable Security precautions to protect my data.  If you think that running Terminal Server in application mode on our domain controller was ever reasonable.... “how about sharin' what you are smokin'“?

    I will post once again what I've ranted about in the newsgroups before:

    1. Apply the Notssid.inf security template to TS running permissions compatible with TS users.

    2. Use the AppSec tool to limit which applications can be executed.3. Do not enable remote control.

    4. Do not enable application server mode on a domain controllers.To connect to a terminal server from the network, users must have the Log On Locally user right assigned. If you implement application server mode on a domain controller, nonadministrators must be assigned the Log On Locally user right at the domain controller. Because this user right is typically assigned in Group Policy, it enables users to log on at the console of any domain controller in the domain, greatly reducing security.

    5. Implement the strongest available form of encryption between the TS client and server

    6. Choose the correct mode for your TS deployment [if you only need remote administration, the only deploy that]

    7. Install the latest service pack and security updates.

      

    Don't want to do #1, nor #2, on our SBS boxes, and we clearly are in

    violation of #4.

      

    Page 393-394 Security Resource Kit.

     

    Read this doc and see how much is done to lock down a TS server..... we can't do this stuff in SBS land. 

    At least not on our domain controllers anyway.

    WINDOWS UPDATE FOR SMALL BUSINESS SERVER 2003

    It's that time of the month when people go to Windows Update and I need to remind everyone.....big deep breath...

    IT DOESN'T PATCH EVERYTHING!!!!!!!!!!!!!!!!!!!!!

    You must visit our SBS download page after visiting Windows update.

    In my mind our biggie is still the fact that the ASP.net mitigation patch isn't more obvious to us SBSers.

    Then there's the POP connector turning into a spam monster patch.

    So if you are WUing this week don't forget to surf over to the download page!!!!

     

    It's all XP sp2's fault

    Today I fielded a call from a fellow CPA who was trying to fix an issue with his computer at home.  He started off by saying “well I installed XP sp2 and I probably shouldn't have done that”.

    Wrong.  You SHOULD do that!  AND we all should do that step.

    See his problem was that his easy no brainer way of viewing photos from the memory stick from his camera wasn't working anymore.  No matter what he did it wasn't bringing up the photo wizard anymore.  So I walked him through checking some things and just as I suspected the file extensions for .jpg got “sucked over” to be controlled by another program.  Roxio 7 was the program that he updated AFTER installing SP2 that was the problem program.

    Now did he remember that he installed Roxio 'after' SP2?  Did he blame Roxio for the issue?  Of course not, XPsp2 was initially seen as the cause of the problem and he was about ready to uninstall it.

    Sometimes it's hard being a person who likes to give ALL software the benefit of the doubt.  Too often we are quick to jump on the “Oh it's Microsoft's fault” bandwagon.  It's fun and so easy to do isn't it?  I mean, yeah, when it comes to certain things we all know they have the agility of a slug.  Right now Internet Explorer is down in that slimy slug category.  But I would argue [and there's a couple of people that I truly respect that say similar things] that we really shouldnt' be trusting ANY browser.  I'd be keeping an eye on this site and checking ANY browser you are using.

    I was reminded of this “blame it the software..or not“ on Friday when I was ranting on how badly Quickbooks was coded and a guy there who was on the Intuit's Accountant group in the past who basically said that it took several years to recode the program and that kind of gave the impression [to me anyway] that we, as an industry should cut them some slack because rewriting the application was a big process.  Cut them some slack?  They sure love to force my clients to upgrade from Quickbook 2002 to Quickbooks 2005 for payroll tax purposes.  How about coding in a Windows 2000/XP manner instead of a Windows 98?  Is it Microsoft's fault that I have to beat my head against a wall to get my workstations to run in user mode or is it that vendor who won't follow the proper guidelines for coding to make their app work properly.  Can't they just set the permissions on the keys and files they need as they load up?  I'm sorry but I dont' think this is acceptable.  If they force my clients to buy new software in 2005, they should at least have programmers that code like they are living in the year 2005.

    I mean if Best Software's Peachtree can do it.. come on Intuit.  We deserve better than this.  To my fellow CPA who was saying “well it takes time to recode”... how about giving all software that same “leeway”?

    A message from Sam the SBS 2003 server

    Hi!  I'm Sam the SBS 2003 server with today's friendly reminder:

    To the Computer installer community, just remember that when it comes to renaming me you can't run dcpromo on me and rename me.  This is the one area where I differ from my big brother counterparts.  My Motherships that support me don't support renaming the domain once it's built.  I've got a lot of glue and gunk in active directory and even with ADSLedit,  I have Exchange under the hood, so you can't [even with Exchange 2003 sp1] just rename me with no consequences.  To rename my domain the best and only way to do it is flatten me and start over.  Now remember, no matter what you name me internally, this has NO bearing whatsoever of what I need to use to pick up email.  So you can name me anything at all for my internal domain name, but when you run the connect to internet wizard, name that email domain name something else.

    In my world I don't need dcpromo as my wizard does it for you. In fact, how the normal big server world can stand running those commands, honestly, it would drive me crazy.  It's sooooooo lame how they have to manually type that stuff in.  Wizards are so important to me and they make your life easier.

    In fact, I had to snicker just a little bit when I read from one of my builders, the post from Charlie that he had to manually set up his internet connection and couldn't use the wizards.  And he even wrote it!  Made me laugh.  Made him appreciate what he did too!

    So if you ever start mucking around deleting users like the backup user, remember to let me reinstall from the integrated install so I can put the glue back.

    [again a little too much Dew and newsgroups today]

    So all those IM messages you have on a daily basis

    So you are IMing away typing up some pretty senstive info and because it's on IM and not on email the fact that you are giving away secrets to Fort Knox is fine because this is IM and not email right?

    You do know that IM traffic can be sniffed... that it's going over in plain text. 

    We were talking yesterday in a meeting how we need to take a concerted effort to “do the right thing” when it comes to computer security. 

    Encryption is a HUGE right thing and it's still WAY too hard to do.  Like MSN IM.  Why doesn't it just include encryption that you can turn on natively?  You can add it on to your IM sessions but it's not built into the box.

    Greg talks about what a pain it is to get people to understand let alone swap public keys to set up encrypted email.  WHY IS THAT?

    Why shouldn't we try to ensure that communication is safe and secure ESPECIALLY when it comes to sensitive info, but on a regular basis I about fall out of my chair as to the number of documents that are merely emailed with no regard to sensitive information.

    I mean why do I have to google to find the Verisign public key page?

    It should be easier than this.  Right now I'm recommending that we at least use Adobe Acrobat and password protect/encrypt the file for the minimum of protection.

    And pssst... Microsoft.... read this from the Verisign instructions...if AIM does it...why don't you?

    The latest release of AIM (5.2 and up) allows you to send and receive encrypted instant messages using your Digital ID.

    To use your new Digital ID with AIM, follow these directions.

     

    You don't really have too much of an excuse do you?

    During our tech meeting today, one of my fellow geeks was telling the story of how the firm that leased the space below her office moved out and they shut off the DSL.  When they did, they shut off her DSL and she realized how much she depended on high speed access.

    Disaster Recovery.  Preparing for the worst.  It's a big issue.

    And yet, even now, when we really have no excuse whatsoever, there are folks that come into the communities that don't have a backup.

    Yo... walk over to the computer screen a little closer so I can wack you upside the head.

    You have a backup wizard.

    Heck, you can even backup to a usb harddrive.

    What in the world are you thinking if you are not utilizing this?

    I mean, come on, there's a web site that goes over backup and restoring SBS 2003, for heavens sake.

    We were talking today about clients that think nothing of running their businesses on 7 year old hardware and have NO backup.  Now I'm not sure which I need to wack more.... the business owner who uses such old equipment that any day it will keel over and die.... or the small business owner who HAS A BACKUP WIZARD and still doesn't backup.

    The minute you don't backup is the time that you'll need a backup.

    Do it.

    You have no excuse not to.

    Hey you! You there! Mr. or Ms. Small Business person!

    Yes, you know I'm talking to you!

    You need a centralized place in your firm.  A meeting place the represents the meeting of the minds of the employees in your office.

    You need a place to share data.  None of this mamby pamby peer to peer stuff.  YOU need a real network.

    You need a way to share calendars ...to backup your mail database. 

    YOU NEED A SERVER.

    I use at home a mail client [Thunderbird] just because I don't want to pull into Exchange my truly gunky, icky, junk mail filled Pacbell account but I count on at least once a year that I orphan email and have to start over.  The standalone pst/pop kind of email just does not work.  Not for business.  You need Exchange.

    You are a business.  Remember that.  And as a business owner, you need to get guidance and advice from someone who understands your needs, your wants and has guided businesses just like yours into setting up THEIR first servers.

    [Okay so I know I'm preaching to the choir but I was reminded after a post to Joe Wilcox about how US small businesses still don't adopt servers as fast as other countries do, and that's a real shame.  I would guess that more technology is sold via word of mouth on golf courses than anyplace else.  Maybe it's because the computer stores don't showcase this?  Maybe there needs to be Saturday morning demos at Costco or something like there is at Lowe's?  Or maybe the USA marketplace is too filled with wacko DIYers like me?  Not sure, but I sure know that having a network means that small businesses are just way more flexible and agile because they have ALL [and then some] of the tools that their big brother businesses have]

     

    Yo, Joe? The average business owner doesn't WANT to do what I do.

    In Wednesday's Joe Wilcox's Microsoft Monitor, he says I'm dubious reseller support is necessary for every SBS 2003 installation, or even the majority.

    Yo, Joe, I have news for you, while easy to set up, this little box still needs a bit of TLC and most business owners want to pay someone to externally 'handle” this stuff.  Yo, Joe? You probably gas up your own car but do you change the oil, the brakes, and do maintenance on the engine yourself?  My guess is probably not. So while I'm a control freak, DIYer myself, I would argue that the average business owner may not want to deal with changing the oil and the breaks on their computer and may want to find a SBS consultant to handle this for him.  I mean, heck the average Joe [pun intended] needs to rely on their neighborhood geek to clean out the spyware and gunk from the average computer.  So why do you think that average SBS 2003 installations don't need reseller support?

    Most of the gang I hang around with are Microsoft registered partners.  They carefully guide the business owner in their technology business decisions.  Joe, dear?  You ever try to figure out the right SKU code for a hardware firewall on the cdw.com site?  Ever try to get your SBS 2003 Software assurance order updated by yourself and figure out the right SKU code?  I first went through another vendor, and then found a true LICENSING specialist in Softwareone.com and I must say that once “I“ outsourced THAT function, I haven't been pulling my hair out and getting frustrated like I was in the past.

    You think the average SBS owner knows what product or add-on is the best value?  To know what the best price is for Trend Micro antivirus?  To know what the best {free} spam add on to SBS 2003 is [Exchange IMF is in my opinion by the way]?  To know the proper way to apply patches?  To know that there are lots more patches besides Windows Update to be applied?  Even I as a DIYer apply patches to a test server AT HOME before I apply them to my server.  You think that business owner is going to watch the health and security of a box [or even know stupid stuff like the fact that Trend freaked us out last week with a false positive]? 

    No, Joe, it's with a community viewpoint in mind that we ALL do well.  It's because a VAR/VAP is monitoring a bunch of like minded networks that he or she can see those patterns.  They can see the “normal-ness” and build a baseline.  I do it as a DIYer by watching the “pulse” of the newsgroups.  There's no way a normal business owner would want to do this.  And trust me, it doesn't matter which operating system you pick, THEY ALL NEED OIL CHANGES.  There's not a day that goes by that there isn't a patch for this or that in any software package.  

    You have to have a VAR/VAP that sees the patterns.  It's only this “trusted consultant” the Outsourced CIO that can help the firm stay nimble.

    No, Joe, I would argue that the best thing for a business owner to do is indeed get someone who montors a whole bunch of SBS boxes.  The more the merrier.  Because then they know that system inside and out better than anyone else and probably have already figures out solutions for their own home [or office] SBS networks that they can then just customize/tweak for all of their clients that they support.

    That business owner needs someone who lives and breathes SBS, that knows what's the best for this little guy.  Yes, you can be a DIYer but when you can have instead the comfort of knowing that a person who oversees on average about 20 of these networks and knows what's the best, why wouldn't that business owner want to ensure that the outsourced CIO is the one keeping an eye on things and not him?

    Yes, SBS reseller support is not necessary.  But since the folks that I know that install and support SBS are some of the most talented computer and technology folks around because they truly see and support the big picture, why wouldn't you want to hire someone who

    I mean why wouldn't you want a Reseller that has that going for them?

    Who protects the Internet?

    Back from our New Year's trip to Disneyland.

    We survived the Tower of Terror ride [well the adults barely survived, the 10 year old we were with wanted to go again].

    While in the park we noticed two cool technology items.  Once was at the Test Pilots grill where we were able to order our food from a touch screen menu order taking system.  We also checked into the hotel using a similar technology.

    At dinner in Downtown Disney, the 10 year old asked “Who is in charge of the Internet?” and we had to explain to him that there are many organizations that provide the backbone of the Internet.  From phone companies and what not, and we explained how the Internet came into being.

    Then the 10 year old asked “Who protects the Internet?”

    Hmmm... good question from a 10 year old.

    I would argue that we all do.

    We do when we patch, when we make sure our antivirus is up to date.  When we don't open up emails automatically.  We also all protect the Internet when folks like those at www.incidents.org keep an eye on things and notify the necessary parties.

    You know they are volunteers, don't you?

    You know you can help out don't you?

    It takes all of us, yes even little SBS networks to do their part to make the Internet safe.  We're all on this highway together.

    So keep an eye out, will you? 

    And remember, WE ALL help to protect the Internet.

    Windows NT 4.0 Server 1996-2004

    Windows NT 4.0 Server, operating system, died, Friday, December 31, 2004 in Redmond, Washington.

    Born 1996 in Redmond, Washington, he was the son of Windows NT 3.1 and Dave Cutler.

    Windows NT 4.0 server worked for many years in many corporate offices and was for many years a beloved member of many firms.

    He is survived by two sons, Windows 2000 Server and Windows 2003 Server, both of Redmond, and five cousins, Windows 2000 workstation, Windows XP Professional, Windows XP Home, Windows Tablet PC edition and Windows XP Media Center edition.  He was predeceased by his nephews Windows NT workstation, and Windows 95.  Currently another close relative, Windows 98 is on life support but the Doctors indicate has a few more years left.

    Private visitation will be in Redmond.

    A Christian burial will be celebrated at midnight [your local time zone] on December 31, 2004.

    Windows NT 4.0 server had been in failing health but finally succumbed to the dreaded final “Blue Screen of Death”.

    May you rest in peace.

    Internet Explorer - what actions to take

    If you've been seeing some of the tech news, you'll know that a group overseas called Xfocus published some details of Internet Explorer vulnerabilties on the web right before Christmas.  And while the press can say [clearing their throats] “Microsoft hasn't responded”, I can say that every time I sent in an email to the Secure alias [secure - at - microsoft.com] I got a response back.  They know and are “responding“ in their own quiet way when such things occur.

    But in the meantime some general rules to keep safe until a patch is released:

    • Begin to push for running in lesser “rights“ on the desktop.  This isn't easy at all, but it's something that we all need to push our app vendors to do natively in 2005.  I don't expect you guys to do this right away, but start thinking about preparing your end users and clients to not being able to download and install just willy-nilly.
    • Ensure that you always use up to date antivirus
    • Only surf where you know you'll be safe [I know...this one is kinda dumb as there have been reports of “good sites“ that don't keep themselves up to date on patches getting turned into “bad sites“ - but just try to be AWARE]
    • Block all unnecessary email attachments.  Whether you use the native to SBS Exchange attachment blocker or Trend's blocker, PICK ONE and don't even let this stuff get in your network.
    • Consider running IE with High security turned on, and only place those web sites into “trusted“ zones that you need fully functional for business purposes.
    • While you can use alternative browsers like Firefox, Mozilla, I'd still recommend that you not “install and forget it“.  Mozilla today just released a new patch for a security issue it had.  Remember that Windows update does not patch Firefox, Mozilla, so you are on your own.  The default for Firefox is to check every 7 days [apparently as I'm guessing from the about:config that I'm looking at.  Brian Livingston has a great primer on Firefox that he had to dig up from their web site and other locations.
    • Just in general be aware.  If an email sounds too good to be true, or is trying to sound like the sky is falling, check it out on the snopes.com web site.

     

    P.S.  Next time guys, send an email to the secure alias and work with them for a patch FIRST?  Don't just disclose this stuff and then contact Microsoft?  Be part of the solution, not part of the problem.

    Running with Scissors... uh .....I mean admin rights

    When we were little kids we were told by our parents to “don't run with you have sharp objects in your hands” ... like..scissors.  So remember my rant how I don't trust any browser?  I want to revisit that a bit again tonight.  Active controls in a web browser are, I think, like “running with scissors”.  Why?  Because what I said before that they rely on me trusting too much.  While the whole concept of “active content” means great things have happened in the Internet space, it also means that the very way we have let our applications get away with being coded as horrifically as they are and haven't really noticed how bad they are is contributing to the malware/spyware and other gunk we now have to deal with. 

    While one could argue that Active X is worse than Darth Vadar, worse than ....oh I don't know.... worse than offering me fresh fish [I really hate sushi...I“m really sorry... it's chicken or beef for me], the fact is the real threat is there because Active X only plays in whatever “rights” you have on that system.  Run in user mode and Active X isn't the issue we're all running from.  Run like we're all used to with full rights to every single registry key on that box and Active X starts making us start thinking of a tall guy in a dark plastic suit that is a heavy breather.  Active X is the bad guy it is because we're running with scissors around here.  It can't be sandboxed from the user rights we have.  Thus as long as we go “la di da ing“ through life accepting that my business applications, ones that I just bought during the 4th quarter of 2004, many of them still think they live in a Win98 world are just wonderful, we're going to be stuck in the mess we're in.

    Tonight I was running some tests on one of my lovely applications that are not “Designed for Windows XP” but yet we all happily load it and run it on our XP systems.  Once in particular ...well lets just say that I knew it was coded pretty poorly and now I'm certain more than ever that Vendors really need to step up to the plate more on securely coding these applications.

    Now I'm not a coder by any means.  The last coding I did [other than a quick batch file here and there] was the misguided attempt to have beancounters learn cobol.  But it didn't take a degree in computer science or a slew of certifications to take one look at what that testing program was trying to tell me.  That application of mine, the one that I put firm's financial data in, looked to this untrained eye to probably make someone like Michael Howard  or Howard LeBlanc fall over in apoplexy.

    In the document “Designed for Windows XP“ logo certification, the documents are pretty clear.  Support user mode and you get that certification.  So why the heck are we not beating up on vendors that DO NOT get certified on it and not giving awards for those vendors that DO get certified. 

    As I'm typing this up I have an idea.  My term as Chairman of the Technology Committee of California CPA Society expires in May.  Perhaps one of my final duties can be to set up an “award” to the accounting application that meets security criteria.  Hmm.... I'll bring it up at the next meeting. Or perhaps my AICPA geek group, CITPers can also do that?

    I'll showcase some of the vendors who ARE coding for least priviledge

    Keep in mind that Peachtree 2003 is “compatible with XP“ and thus doesn't meet the guidance.  Notice there is one major application missing that isn't in the “designed for Windows XP“ logo program at all. 

    Amazing isn't it?  We run our daily business in an application that is not “designed for Windows XP“

    That in this day and age we can accept The user doesn't have sufficient permissions with the Windows user login. Users must have full Admin or Power User permissions that permit them to write to the Windows registry. “ as being acceptable from an accounting application...   shouldn't we as CPAs, as fididuciaries of our client's records demand better than this?

    Pssst you can't “intuit-itively“ figure out the app?


    The designed for Windows XP logo includes this as a criteria

    3.4     Support running as a Limited User

    Applications must not require users to have unrestricted access (for example, Administrator privileges) to make changes to system or other files and settings. In other words, the application must function properly in a secure Windows environment. Complying with the previous requirements in this section will help to ensure that the application meets this requirement.

    An application that does not install (executes without installing any components) must still support use by a Limited User.

    A secure Windows environment is defined as the environment exposed to a Limited (non-Administrator) user by default on a clean-installed NTFS system. In this environment, users can only write to these specific locations on a local computer:
    [Note 1]

    ·         Their own portions of the registry (HKEY_CURRENT_USER)
    [Note 2]

    ·         Their own user profile directories (CSIDL_PROFILE)

    ·         A Shared Documents location (CSIDL_COMMON_DOCUMENTS) [Note 3]

    ·         A folder that the user creates from the system drive root

    However, applications defaulting to use of these folders do not comply with the other requirements of this section.

     

    Users can also write to subkeys and subdirectories of these locations. For example, users can write to CSIDL_PERSONAL (My Documents) because it is a subdirectory of CSIDL_PROFILE. Users have read-only access to the rest of the system.

    NOTES

    [1] Applications can modify the default security for an application-specific subdirectory of CSIDL_COMMON_APPDATA. This may provide an additional location to which users can write for a given application.

    Any modification of the default security for an application-specific subdirectory of CSIDL_COMMON_APPDATA must be documented when submitting your application.

    [2] Users cannot write to the following subsections of HKCU:

    \Software\Policies

    \Software\Microsoft\Windows\CurrentVersion\Policies

     

    [3] By default, users cannot write to other users’ shared documents; they can only read other users’ shared documents. Applications can modify this default security on an application-specific subdirectory of CSIDL_COMMON_DOCUMENTS.

    Any modification of the default security on an application-specific subdirectory of CSIDL_COMMON_DOCUMENTS must be documented when submitting your application.

    This requirement does not apply to all features.

    WHEN DOES THIS APPLY?
    When the major features of the application can be successfully run by a non-privileged user, minor features are allowed to fail gracefully. These minor features must not be installed by any default mechanism (for example, a minimal or typical install) other than a complete install and must not be considered important for the operation of the program. Examples of such minor features include components necessary to support legacy file formats.

    Limited Users cannot perform several system administration functions such as disk defragmentation, backup/restore, changing system time, and so on. When most of the primary functionality of an application is system administration, the application must still run from a Limited User account and inform the user why none of the features can be used.

    For any feature that a limited user cannot use, when submitting your application you must document what objects need to be opened for that feature to work, such as file system, registry keys, and so on.

    When a limited user can’t use a feature, the application must degrade gracefully.

    Test Cases – 3.4

    As defined in “Designed for Microsoft Windows XP” Application Test Framework:

    TC3.4              Does application support running as User1, a Limited User?

     

     

    XP Home [s] CANNOT join a domain

    To the poster in the newsgroup who said “I wish they wouldn't keep it a secret” that XP Home [s] cannot join a domain.

    Let's blog this up a bit so it's more googlable shall we?

    XP HOME platform are for “Homes, houses, condos, apartments, shacks, shantys, leantos, outhouses, etc., etc., etc.“ but they are not for BUSINESSES.  Get it?

    The information on whether or not XP HOME can join a domain is on the XP Professional page.

    “Windows XP Professional is required to access a domain-based network. If you're not sure whether the network you will access is domain-based, talk to the person in charge of the network to make sure you choose the proper version of Windows XP.“

    I love those kind of postings don't you?  I AM in charge of the network and what if I don't know the right answer? 

    Like those messages that say “please contact your network administrator for more information“.  I AM the network admin and can't get this thing running the way it's suppose to.

    XP professional is what you need to have computer JOIN A DOMAIN. 

    I would argue that XP Professional is just plain better in general, with or without a domain, but that's just my opinion.

    Let's blog it one more time for dear old Uncle Google

    XP Home machines cannot join a domain.

    XP Professional machines can.

    XP MCE 2004 can join a domain.

    XP MCE 2005 sort of can't but I hear if you install them from stratch the bits are there and you can join them, but officially they aren't supposed to be domained.

    P.S. Changed the blog so that XP HOME would be better googlable  :-)  Thanks Sophos 

    Hey, Directions on Microsoft? Aren't you going after the party not causing the problem?

    I'm reading Directions on Microsoft's Top 10 issues that Microsoft has for challenges in 2005 and I'm pulling one paragraph out that in particular [I think] needs clarification.  In the Directions on Microsoft article they state:

    “Security has always been near the top of our Top 10 list, but despite laudable efforts by Microsoft, such as a drop-everything-else code review, security is still a problem. In fact, the bad guys seem to be winning. Before anyone gets on the Internet the first time these days they need a PC already protected by the latest service packs and security patches, an antivirus program, an antispyware program, and training on how to avoid phishing exploits. Although Microsoft arguably bears little direct responsibility for these problems, the company has the most to lose if these security issues persist. Furthermore, Microsoft is in the best position of any vendor to address the problems. Some useful next moves? Make it possible to run Windows all day without requiring administrative privileges and work with other players on standards that will make it easier to authenticate the senders of e-mail.

    "Security problems raise the cost of managing Windows clients, and make the perennial thin-client alternative more viable. This year, Microsoft has to deliver the improvements it promised for patching corporate PCs, and not let development of future product versions interfere with keeping current ones secure."
    —Michael Cherry, Lead Analyst for Windows”

    Mr. Cherry?  Office applications and Internet explorer run FINE as a user and do not need administrative privileges.  It 's my stupid APPLICATIONS that are coded stupidly that need these rights.  And even in SuSe [a Linux distribution] there are times to adjust the monitor, to apply patches, to install software that you need to Sudo [the equivalent of Administrator rights - or the Windows equivalent of RunAs].  I just recently loaded up SuSe and looked in absolute horror at this screen:

    See that box that says “Keep password“?  You and I both know that your home user/end user is going to click that box and say “sure“ save my password because it's a pain to type in that really long strong password I gave the machine when I built it.  What's the insecurity [or insanity] of saving the administrator password so the next worm du jour that blasts through a SuSe box will have admin rights?  We cannot dumb down these desktops like this and keep these boxes secure!  The bad guys are winning and the sooner we all figure out that we should be fighting “them“ and not flighting the “who has the better Operating system“, the better off we will be.

    Look at these applications in my office that REFUSE to run in user mode.  So I ask you?  Who's at fault?  Microsoft applications DO run in user mode.  It's my third party stuff that doesn't.  I say that it's not Microsoft that needs to make 'Windows' run as user, but rather that we get tools to help us identify how stupidly these applications are coded and then go and beat up THOSE vendors to make them either set the right permissions as they load on “just that registry key” or code better in the long run.  I don't need them to make Windows run as a “user” ...it does... I need Microsoft to give me tools to help me identify my vendors that are the dumb ones.

    Ask for the right solution to the real problem, I say.

    My favorite things

    It's Christmas evening and Julie Andrews is singing about her favorite things and I thought I'd take this time to talk about my “favorite things” [at least related to technology and SBS].

    • The communities of Small Business Server - more that even the technology of SBS, the “we share, we win“ attitude of all the communities out here.  If you haven't joined in one of the communities... we have lots of variety of ways to “community“ out here so if your “thing“ is newsgroups, or yahoogroups [from business to technical to beyond], or web forums, we've got lots of options.  For each one of you that takes the time to share your expertise, THANK YOU for doing that.  You are what makes the communities so strong and so valuable.  Pat yourself on the back for doing what you do every day.
    • The people of the SBS family who night and day, via email, or IM respond to anytime any day that I “say I need help, I'm stuck“ whenever I need help [or are just there when I need to rant about something].
    • The people who work at Microsoft who work on SBS.  From Mothership Redmond, to Mothership Las Colinas, to Mothership Shanghai and to our future Mothership Bangliore, the people I know that work on SBS tend to go an extra mile, walk a little farther, and certainly some of you guys and gals stay up all hours of the night. 
    • My fellow Microsoft Most Valuable Professionals who day in and day out do what they do because they want to help others make their systems just work.  You guys inspire me with your passion and knowledge.  You guys do what you do to help people and definitely believe in the concept of “pay it forward“.
    • The people who work at Microsoft that I know in “weedy” areas and security.  The attitude on the “outside” is that Microsoft doesn't care, but whenever I meet people on the other side of the wall, I see people that I know care, and in fact sometimes feel just as passionately as we do out here about getting things “fixed” in security.  I think we're constantly going to be fighting the good fight against the bad guys no matter what platform, browser, you name it.  Yeah there is still a lot to be done, a lot to be fixed, but as I've seen the patch engines move to two engines, the fact that they are willing now to 'break things' is promising.  It's only us out here, working with more folks “in there” that more changes can be made.   

    Happy Holidays everyone!

    Merry Christmas to all!

    And here's to a happy new year.  So far we haven't blown anything up for the day's events.. but the day is young.  :-)  To everyone, to all of yours, here's hoping you have a very happy holiday season.

    Stay safe, stay secure, use IE in high security and “let's be careful out there“. 

     

    Use Firefox/Mozilla for a safer system

    Eweek today has an article that says for “me” to be safer I need to use an alternative browser.  But today I'm giving myself my Christmas present early.  I'm wacking my registry via group policy to run in User mode[a].  And you know what I found?  That Mozilla/Thunderbird will not work in EITHER user mode or power user mode.  You have to run as local administrator for it to work.

    That's right, I have to run in a manner that I'm not willing to run in anymore in this firm to load a program that Steven Vaughan-Nichols says will keep me safer. [I'm 99% sure that Firefox also puts in the profile in a protected space but I'll go download it on this machine to triple check].

    See the error message I get when trying to run in User or Power user mode?

    Click here for a larger view

    Next, in order to have Mozilla to access the web here at the office I would have to adjust the firewall to allow “unauthenticated outbound connections” [in other words turn off “egress” or outbound filtering.

    Again, how is this making me more secure?

    Can someone explain how leaving myself in administrator mode, and opening up my firewall more is going to give me a “safer system” here?  I'm still scratching my head how this is going to make me more secure.

    Remember what I blogged about the other day?  I don't trust ANY browser and thing they should all be considered "untrustworthy".  All of them ask too much trust of me these days.  And especially when they want me to run as Administrator.

    [a] I'll be blogging more about this process but it's in the next Harry B. book.

    P.S. I chose the 'standard' Mozilla/Thunderbird settings.

    Nice Timing - how about trying to do THAT with XP Homes Mr. Dell!

    So last night I posted [okay, so more like ranted] that Dell shouldn't be selling to SMBs...well one always puts a bit more “heat” into a headline at 11:00 p.m than one does at noon.  What I really should have said is that Dell should be selling the RIGHT way to SMBs.  They should be ensuring that SMBs know that without XP Professionals they don't get all the toys and bells and whistles and cool stuff and Sharepoint and ...oh just EVERYTHING you get when you have a server setup.  So today I'm surfing over to the home page of SBS to pick up a link and low and behold.... there on the page.... a glowing icon... a beacon.... a light in the far yonder distance...it's a sign I tell ya....

    Very Very Nice timing guys and gals at Microsoft because you have a link today to a PDF document explaining to the business owner why a server is where you want to be.

    “Using a server to network your computers can help your small business run more smoothly and cost-efficiently, while also boosting productivity. Our free guide, Networking Basics for Small Businesses, can help answer many of your most important server questions. You'll learn what networks and servers are, whether your business is ready for a network, what type of network architecture is best for your needs, and much more.”

    And again, what is the operating system that gives us all that joy?  XP Professional. 

    The traditional 'benchmark“ for networks was more than 10 people.  Today?  With the pricing of SBS 2003 standard?  Man, if you are even a 5 user firm and don't have some sort of automated backup.... then you need to seriously be looking at SBS2003 to be your base... your launching off to more growth.

    Send that link off to someone who's “thinkin'“ about a server.  Push them over the edge.  2005 should be the year of the small business..the year of the server...the year of SBS.

    P.S.  Okay..so it was more like midnight....

    Michael Dell of Dell Computers -- would you STOP selling to SMBs?

    Joe Wilcox comes through again with another SMB post that is SO SPOT ON it isn't funny.

    Mr. Dell...would you please realize that every single time you make a “deal” for us SMB's, those of us in the Small Business Server world have to clean up your mess?  I can't tell you how many times consultants have to deal with a XP HOME machine that cannot and will not connect to a domain.  Joe Wilcox is so spot on!  We need XP Professional in SBSland and not XP Home.  You aren't doing us any favors whatsoever in calling these systems “small business” systems.  They are NOT...they are HOME machines by name and by definition [get it]?  They are called HOME for a reason and should not be sold for small businesses.  We NEED servers here.  We NEED domains.  We DON'T need workgroups.  And XP home is a crippled system for our networks.  We've complained before that retailers only sell XP Home machines in stores ...but this takes the cake...you ADVERTISE these machines as being for small businesses.  And guess what...they don't work in our networks!

    We want domains... what do workgroups give us?

    • Workgroups have no domain controllers.
    • Users are more often than not local admins of their own machines.
    • Permissions across a group cannot be set.
    • No consistent permissions or rights.

    What do domains give us?

    • Group policy which manages
      • Password policies
      • Lockout policy
      • NTFS permissions
      • User rights
      • Event logs that can be viewed across the lan
      • Registry settings
      • IPSec
      • Much more
    • The ability to use Software Update Services [and in the future WUS] to patch all our systems
    • The ability to centralize backup
    • Centralize antivirus
    • Redirect the “My documents“ for all employees to the server to be backed up
    • Enable roaming profiles
    • and much much much more.....

    Mr. Dell... you sell us XP Home's for our networks and the first thing we have to do is convince that business owner to take that brand spanking new workstation and spend more money.

    You want to sell to the SMB marketplace?  You sell us XP Professionals for our BUSINESSES.  Don't try to sell us XP Homes down here... we're running businesses...not HOMES.  Come on Mr. Dell...work with us down here and help us all enable these businesses to go farther, work better, be more empowered with a NETWORK that needs XP Professional machines.

    P.S.  What amazes me is how Joe Wilcox “gets our space” but Dell Computers does not.

    Can Browsers be trusted?

    Last night I'm reading the blogs and I like to read the Michael Howard one [he's a coder dude, but he's security so it's always kinda interesting] and he links off to Peter Torr's post on whether you can “trust Firefox” because of the fact that it's not digitally signed, that you are going off to some University web site and what not.

    While he makes some valid points, which Karl had a nice summary of in a post today that basically is as follows:

     Brief summary:
    1) The Firefox installation redirected the author to a download from some random university server or in a second trial, an IP address instead of a host name. 
    2) The downloaded setup file isn't signed. 
    3) The install generates an error message popup that is blank, no words in the message. 
    4) When downloading unsigned Firefox extensions, the default action is still "Install now." 
    5) Downloaded programs like the Flash extension aren't checked to see whether it was signed or not, and
    6) there was a "don't ask me again" checkbox on the dialog box asking whether to run the downloaded file. 
    7) There was no apparent way to disable or uninstall the Flash extension,and
    8) an unsigned third party extension had to be installed to do this.

      But I think they are both missing the bigger picture.  There are many programs like the one I just installed today that I bought and paid for that I must click through and say “sure I trust you because I think you are the program I just purchased“.  This is the exact screen I was presented today to install a “business“ application I must have in order to run my business.  So, you think I'm going to decline to install something that I just paid for?  Don't think so.  I'm clicking the “Run“ button and not really thinking this is a security issue at all and more like a software developer who didn't take the time or expense to get their code “signed“.

    In full disclosure here, my pacbell.com email address that I “have had for ages, use in the public newsgroup, how would you like Rolex ads or the lastest scam because I get them because I purposely don't filter this email account so I can get a pulse on what gunk stuff is out there and don't pull it into Exchange or Outlook“ gets dumped into a Thunderbird mail client that I downloaded the software for, and clicked through and said “sure, whatever, I'll install it, no sweat because I want to!“

    There are many times I just “trust“ in the system.  Do I verify the PGP key on the Microsoft Security bulletins to ensure they are the valid bulletins from the Microsoft Corporation?  uh...no.  Never have.  Do you?

    Do you run md5 check sums on the security patches that Shavlik downloads to ensure that what they “sucked down“ is what patches are supposed to be coming from Microsoft.  uh...no, can't say that I do that one either.  Do you?

    Look around and we have a lot of “trust“ that goes on.  The problem is really that we've [the industry, not Microsoft] have embraced the web as a platform.  But when you start peeling back the layers, I'm not so sure it's a good idea to trust ANY web browser these days ESPECIALLY if you are running in local administrator mode.

    As I was studying for my GSEC/GIAC renewal, I was re-reading the sections where it talked about what “active content“ in web browsers is all about.  The Java, Javascript, and ActiveX was designed to unload bits of code onto our desktops to share the computing power so that the web servers weren't so over loaded.

    ....wait... let's read that one again... they were “designed“ to put code on our desktops. 

    document newly released by the W3C.org group that is entitled “Architecture of the World Wide Web, Volume One“ uses the word “security“ in the document only four times.  Hey, Guys?  Can we sprinkle that word around just a tad more than that?

    In the organization's  long term goals for the Web, the follow three items are highlighted:

    1. Universal Access: To make the Web accessible to all by promoting technologies that take into account the vast differences in culture, languages, education, ability, material resources, access devices, and physical limitations of users on all continents;
    2. Semantic Web: To develop a software environment that permits each user to make the best use of the resources available on the Web;
    3. Web of Trust: To guide the Web's development with careful consideration for the novel legal, commercial, and social issues raised by this technology.

    I don't know about you but I would feel a heck of a lot better if this didn't quite sound so much like a “Woodstock convention of free love, peace, happiness and interoperability“ and a bit more emphasis on “restricting bad guys from running code on my desktop“ and a realization that we are running financial transactions and business deals on a platform that wants to take into account “social issues“. 

    Don't get me wrong, I think that the web has brought us a lot of good, but I don't think anyone, even now, is really thinking in a crystal ball kind of fashion to locking this browser down enough so that I don't feel that my thinest edge of the border of my network is right now at this Internet Explorer window typing up this rant post.  It's this thin line between this browser window and the rest of the world that freaks me out the most these days.

    Right now I don't trust ANY web browser.  On a daily basis Secunia.com and the web site of incidents.org remind me of this. 

    Pick a browser and you'll find that if it doesn't have issues today, it probably will tomorrow or it will next week.

    And the scary part about all this gunk is that more often than not it's “from remote“... out there.  The only thing that any other browser has going for it is that it's not quite so embedded as Internet Explorer is so they can make patches a bit faster as they don't have to worry about the entire world who built applications on the web freaking out if a patch isn't tested enough and goes and kills computers and applications.  But in the big picture.. I'm not any more secure because I have less patch tools, and no control over any other browser without group policy.  Sure there are guys that are trying to fill in the gap like Cider giving guidance to set the settings via group policy , but I'm just not ready to install another piece of software that I can't control, can't patch, phones home for patching when I don't know about it, and that I would have to lower the security in my egress filtering firewall just so it would work.  Right now a Firefox or Mozilla browser won't work in my AD/ISA integrated environment and I'd have to tick the check box that would say “oh don't authenticate users before allowing them out the firewall“.

    Sorry folks..just not going to happen here.

    So what I“m ranting about folks is ...should we really be trusting ANY browser these days?

    I don't think any of them are secure enough for me!

    It's just not a Bradley family holiday without some event

    [warning off topic blog post]

    It's just not a Bradley holiday season without an “event” occuring.  You know... an event.  When I was much younger one year the event occurred when I was attempting to do recreate “Chestnuts roasting on an open fire” California style and placed fresh Chestnuts in the Oven.  I opened the door to check them and somehow the open oven door with the cold air interacted with the warm chestnuts and .... well.. I had an explosion of Chestnuts all over the kitchen ceiling and chestnut meat in my hair.

    Another year my Mom roasted the turkey with the plastic giblet bag still in the neck cavity.

    Another year I caught bread dough on fire in the oven [even had firemen come to the house on that one]

    Another year we were opening up a Whipped cream canister [the cool ones from Williams Sonoma that you “re-charge“ yourself] and the leftover cream that was inside shot through the open kitchen window to the outside [it was still under pressure]

    Last year a one inch water pipe broke in our bathroom and flooded our living room.  I walked in from the garage, heard water running, thought the lavatory got stuck and realized...uh oh.. when my shoes went “squish squish”.  We had carpeting we wanted to remove anyway... we just kinda removed it a little sooner than we planned.

    So tonight my sister comes home and is talking on the phone and notices some brown sticky stuff and thinks that I've dropped maple syrup on the tile.  Little does she realize that I haven't had maple syrup in about a month... and then she realizes there is “syrup” on the front ...the front of the fridge. 

    You see my Dad was trying to get the ceiling blade fans to straighten out so he um... varnished them... and um.. then after he thought they were dry.... um... and turned on the fans and ...... oh yeah.  That brown maple syrup was actually varnish.

    One messed up manicure later as Karen [my sister] and I [we share the house together] scraped the varnish polka dots off the walls, the floors, the tile, the ... well kinda everywhere and in this really interesting arc-ing pattern.  Amazingly it came off.  [Poor Dad felt kinda bad but in hindsight it's really funny now]

    Happy Holidays everyone.. NOW it's truly the holiday season at the Bradley house... we've had our annual holiday “event”.

    P.S.  Do you kinda get the idea that you don't want to be invited over for Christmas dinner at our house without wearing some kind of body armor?

    So lets all switch to Firefox and solve all our problems, right?

    Not so fast.  Read this first.

    Rule of Susan:  If it browses, don't trust it.  If you think that switching to another browser of your choice will solve all of our problems, I have news for you.  It wont.  Heck, spammers are even using blogs for spam these days!

    As long as I can't group policy or remotely patch Firefox, I don't consider it a viable option for the business even a small business.

    They've figured out how to blast through popup blockers, they spam blogs, they hijack web page ads, obviously there's a financial incentive for all this gunk otherwise they wouldn't do this stuff.

    So meanwhile, we're driving out here on the web with all this junk along with all the normal spam email I get like Rolex ads and what not.

    I'm honestly browsing these days with IE in high security.  Yeah pages like hp.com look ridiculous, but at least I'm being super duper paranoid.  I'm just not willing to move over to another browser that I'd have to actually lessen my security for because it doesn't authenticate well to ISA, doesn't have a patch tool for like I have with Shavlik so I can remotely patch with.  I'll stick with using my tweak bar tool instead which makes it easier to add sites to the trusted zone.

    HELLO OUT THERE PEOPLE!!! WE EXIST!

    Today on a comment posting, I noticed a blog link and followed it. And there on the page I found this post:

    Tools people should be using but apparently aren't aware of.:
    http://jamesatuncw.com/blog/archive/2004/12/11/220.aspx

    "I'm getting a little confused, disappointed, and downright upset by the high number of "computer professionals" I am meeting that simply know nothing about certain tools made by Microsoft, mostly for free, that really help administrators“

    Amen James to that. I find it funny sometimes that a little SBSer tells enterprise folks about the power of Group Policy as well. And a bit down in the blog post was this phrase:

    ”The fact that Small Business Server exists"

    Yup I hear ya James. There are times when people post into the newsgroup that have entered from the Enterprise venue and i just want to box their ears when they’ll post in “well I just did a DCPromo and now need to know how to install Exchange 2003”. Yo, Dude? We don’t DCpromo in SBSland…well we do but only during gunky migrations and what not, we certainly don’t do it when the SBS wizard does it’s own install.  And Exchange gets automagically installed!  What are you doing trying to manually install it? 

    I still remember how “I” first heard about SBS 4.0. From a fellow accountant who was in the technology biz and thought it was perfect for our sized firms. I still think it is. Of course these days with the document imaging that we’re doing it’s starting to be the “SBS + some other big storage device because we can’t fit it anymore on the server”, but nonetheless I still see it as being the perfect base to many CPA firms.

    So hello world!! We’re out here!! Find us!

    Remember we do everything [and more] that a small firm needs just like the big guys. Heck Tim was asking me this morning about how to directly manipulate files in the Sharepoint/SQL database and I’m like… uh.. Tim.. my knowledge of SQL consists of Google, a step by step that Jerry wrote up so I know how to setup blogs, and enough knowledge to know that fellow SBS MVP Steve Foster is the one that people should ask questions about SQL.  Uh.. Steve?  There are so many things that we can do with our boxes and it's sad that folks don't even know we exist.


    P.S. To the party who just logged in while I'm typing this on IM with the name “JeffZi – OS&B Resurrected!!!!! …okay what’s up with that, huh? ;-)

    When last they were seen, they were on their way to the airport

    Last Friday at Lunchtime... um.. I mean in the afternoon... um... I mean in the evening... two guys flew down.... um...well drove down....in the fog no less to video tape some “sound bytes” for a Mike Nash [Mr. Blue shirt and nothin' but blue shirts] Security 360 video

    I warned them about FresNO's [David Spade commercial] reputation of puddle jumper flights but I forgot to tell them about then even worse issue of cancelled flights. So there they were in San Francisco ...getting delayed...getting delayed... and finally the flight was cancelled, they grabbed a one way rental car from San Francisco [they were coming from Seattle] and started driving....and...hit traffic....and fog....

    Poor guys.  Needless to say it was fun and hopefully I won't do at much “blinking“ eyes as the soundbyte thing I did for Trend Micro. 

    One of the questions that they asked that just floored me a bit was .

    What are some of the ramifications of not having a patch management program in place? Or, put another way, how do you make a business case for patch management?

     

    Yo, folks?  How can you NOT make a business case for patch management?  It's just good business.  Especially now with AB1950 kicking in in January

    "This bill would require a business, other than specified entities, that owns or licenses personal information about a California resident to implement and maintain reasonable security procedures and practices to protect personal information from unauthorized access, destruction, use,
    modification, or disclosure. "

    "A business that owns or licenses personal information about a California resident shall implement and maintain reasonable security procedures and practices appropriate to the nature of the information, to protect the personal information from unauthorized access, destruction, use, modification, or disclosure. "

    I argued on the Patch Management.org listserve [that I got a plug in for during the soundbyte interview I might add], that Is using an end of life, no longer patched OS "reasonable security procedures"?  Me thinks there's going to be a few Attorneys getting rich arguing over that definition.

    Mind you this is an argument over EOL for Redhat 9.0, 8.0 etc, not Windows NT.

    As I pointed out in the post, ever listened to "Death of the DMZ" by Steve Riley? As Mr. Riley points out the original RFC[a] for tcp/ip states that "security was not taken into consideration".

    We've got systems set up that were never intended to be over "untrusted" communication and now we're still using them how many years later on the Internet that these days and we shouldn't be trusting even the people "inside" the wall?

    Check this out...

     An Applications View on Security: 
    http://www.eweek.com/article2/0,1759,1738991,00.asp?kc=EWRSS03129TX1K0000614 
     
    In fact, more than 80 percent of companies have detected system penetrations of internal origin, according to data compiled by insurance brokerage and risk management company Arthur J. Gallagher & Co., in Itasca, Ill. This means that applications performing their normal function, at the behest of authorized internal users, must be viewed as dwelling in hostile territory rather than in trusted environments.

    I mean when you have employees like this... who needs enemies on the outside of your wall? [Well ya guys listen to me why audit logs and ISA logs are a good thing?]

    [a] which I think is this one

    P.S.  For the record I did not wear a blue shirt.

    MERRY CHRISTMAS (In Legalese):

    For your reading pleasure during this holiday season . . . :) MERRY CHRISTMAS (In Legalese):

    Please accept without obligation, express or implied, these best wishes for an environmentally safe, socially responsible, low stress, non-addictive, and gender-neutral celebration of the winter solstice holiday as practiced within the most enjoyable traditions of the religious persuasion of your choice (but with respect for the religious or secular persuasions and/or traditions of others, or for their choice not to practice religious or secular traditions at all) and further for a fiscally successful, personally fulfilling, and medically uncomplicated onset of the generally accepted calendar year (including, but not limited to, the Christian calendar, but not without due respect for the calendars of choice of other cultures). The preceding wishes are extended without regard to the race, creed, age, physical ability, religious faith or lack thereof, choice of computer platform, or sexual preference of the wishee(s).

    THE NIGHT BEFORE CHRISTMAS:

    Whereas, on or about the night prior to Christmas, there did occur at a certain improved piece of real property (hereinafter "the House") a general lack of stirring by all creatures therein, including, but not limited to a mouse.

    A variety of foot apparel, e.g., stocking, socks, etc., had been affixed by and around the chimney in said House in the hope and/or belief that St. Nick a/k/a/ St. Nicholas a/k/a/ Santa Claus (hereinafter "Claus") would arrive at sometime thereafter. The minor residents, i.e. the children, of the aforementioned House were located in their individual beds and were engaged in nocturnal hallucinations, i.e. dreams, wherein vision of confectionery treats, including, but not limited to, candies, nuts and/or sugar plums, did dance, cavort and otherwise appear in said dreams.

    Whereupon the party of the first part (sometimes hereinafter referred to as ("I"), being the joint-owner in fee simple of the House with the party of the second part (hereinafter "Mamma"), and said Mamma had retired for a sustained period of sleep. At such time, the parties were clad in various forms of headgear, e.g., kerchief and cap.

    Suddenly, and without prior notice or warning, there did occur upon the unimproved real property adjacent and appurtenant to said House, i.e., the lawn, a certain disruption of unknown nature, cause and/or circumstance. The party of the first part did immediately rush to a window in the House to investigate the cause of such disturbance.

    At that time, the party of the first part did observe, with some degree of wonder and/or disbelief, a miniature sleigh (hereinafter "the Vehicle") being pulled and/or drawn very rapidly through the air by approximately eight (8) reindeer. The driver of the Vehicle appeared to be and in fact was, the previously referenced Claus.

    Said Claus was providing specific direction, instruction and guidance to the approximately eight (8) reindeer and specifically identified the animal co-conspirators by name: Dasher, Dancer, Prancer, Vixen, Comet, Cupid, Donner and Blitzen (hereinafter "the Deer"). (Upon information and belief, it is further asserted that an additional co- conspirator named "Rudolph" may have been involved.)

    The party of the first part witnessed Claus, the Vehicle and the Deer intentionally and willfully trespass upon the roofs of several residences located adjacent to and in the vicinity of the House, and noted that the Vehicle was heavily laden with packages, toys and other items of unknown origin or nature. Suddenly, without prior invitation or permission, either express or implied, the Vehicle arrived at the House, and Claus entered said House via the chimney.

    Said Claus was clad in a red fur suit, which was partially covered with residue from the chimney, and he carried a large sack containing a portion of the aforementioned packages, toys, and other unknown items.

    He was smoking what appeared to be tobacco in a small pipe in blatant violation of local ordinances and health regulations.

    Claus did not speak, but immediately began to fill the stocking of the minor children, which hung adjacent to the chimney, with toys and other small gifts. (Said items did not, however, constitute "gifts" to said minor pursuant to the applicable provisions of the U.S. Tax Code.)

    Upon completion of such task, Claus touched the side of his nose and flew, rose and/or ascended up the chimney of the House to the roof where the Vehicle and Deer waited and/or served as "lookouts." Claus immediately departed for an unknown destination.

    However, prior to the departure of the Vehicle, Deer and Claus from said House, the party of the first part did hear Claus state and/or exclaim: "Merry Christmas to all and to all a good night!" Or words to that effect.

    Thanks to Ralph Ostermueller of fvginternational.com for this legalese.

     

    An open letter to the Security Community:

    Stop surfing, browsing and using any sort of Internet viewing software.

    Seriously.  Right now there are several unpatched browser vulnerabilities and one “blast through the POPup blocker”.  The sky is definitely falling.

    And why do we have these unpatched vulnerabilties that are being discussed in detail with no patches?  Because someone believes that it's more responsible to disclose it to the community of folks that then turn it into worms and what not than to responsibly disclose to the vendor and WAIT for an appropriate time for us to test and apply patches. 

    • Nicolas Waisman disclosed a paper on WINS vulnerability - patch is not yet released
    • eEye while stating on their web site that they practice “responsible disclosure“ have released technical details about an vulnerability the same day as the patch is released [approximately 12 hours last time] with usually enough technical details to begin the clock ticking.
    • http-equiv-at-excite.com has regularly disclosed before allowing for a patch.
    • Liu Die Yu, in reading his essay on the Microsoft Security Resource Center titled “Die slowly this time MSRC explained“, apparently believes that going after the MSRC with verbal abuse is the noble thing to do.

    These are just a view of the examples of businesses and individuals that make us more IN-secure out here.

    I can hear you now say if the Evil Empire  well if they'd only write better code“.  Wake up folks.  In the book Practical Cryptography the authors state that bridge builders have a finite threats to deal with.  Gravity, water, weather.  Software coders have an infinite amount of threats, including, but not limited to, all of us pesky end users still running as local administrator around here.  [And while those say that it's hard to run as user mode, I would argue that for the vast majority, that if it were not for the insecure requirements of the applications we are running, we COULD run as user mode most of the time as many of us have no need to install software on reoccuring basis]

    I'm tired of my security, my patching, being influenced by someone not even willing to use their real name. 

    I'm tired of security firms that don't sell products in the small business server space that say they holding Microsoft responsible when all they do is end up hurting my community.

    Patches hurt me in my community in two ways.

    Firstly they hurt me when I don't know about them.  When all I do is go to Windows update and that's not enough to fully protect me.  [Granted, these days on the Internet, most “gunk” traveling the wire is tuned for XP and 2k and thus even when USAToday stuck us out there with only a strong password to protect us and netbios ports exposed, we stayed up].

    Secondly, they hurt me when I apply them and they do harm.  Granted, this is happening less often, but there are still the rare times that they cause issues.  Rare is one time too many for me.

    I'm sure there are folks that will tell me I'm kidding myself that the exploit is only coded “after” the patch comes out, that is, it's already been out in the exploit community and the mere release of the patch alone gives the folks out there the opportunity to reverse engineer an exploit.

    But folks you are missing something.  Down here, my community is not specifically targeted.  We're road kill.  We get hit with the worms, the blasters, slammers.  We don't get hit with the specifically targeted attacks.  Ryan and Kevin stuck us out there to get hit by a MACK truck.  They weren't specifically hacking us.

    So to those folks that think you are being noble, that you are holding Microsoft responsible, that you are making sure they do secure coding?  You hurt me and my community more.

    Remember that we don't buy your products.

    We don't know who you are down here if you are seeking fame.

    We just get affected by what you do.

    Remember that.  You hurt us most.

    For the record, Opera is patched, Firefox has a workaround, but I'll stick stick with IE because I can group policy it and I have not heard of these actually being exploited.... yet.

    Google desktop is slightly freaking me out

    Google desktop is slightly freaking me out....and that's a bit of an understatement.  I'm trying it out here at home just to see what it does and ...well... for me... it's not.  I guess I have an active system because abut 28 hours later, it's still only indexed 17,000 items.

    Next, I don't know about you, but I find it freaky to google the Internet and get results from “my computer” as well.  I think this experiment is going to be uninstalled for now.

    While the Privacy statement says “So that you can easily search your computer, the Google Desktop Search application indexes and stores versions of your files and other computer activity, such as email, chats, and web history. These versions may also be mixed with your Web search results to produce results pages for you that integrate relevant content from your computer and information from the Web.”, and I know after attending the Encase class that index.dat file showcases how intertwined Internet Explorer is with the file structure, I just do not get a warm fuzzy feeling seeing “desktop results” on the top of an external web page.  That so does not give me the “air barrier” feeling that I want and need to be putting this anywhere near a production network.

    Yes, I know.

    • Sky is falling.
    • We're all going to be sucked into a worm hole.
    • A meteor could hit us tomorrow.

    All of these are probably way more possible that Google even caring about my data [and that's one of the reasons that I always say “yes” to Dr. Watson dumps and what not because I really do beleive that the “Evil Empire” is not getting personal data when I send them a Dr. Watson dump], but this just “feels” a bit more of a line blurred.

    If Google desktop was a “Lookout” kind of application, I think I'd feel better.

    Okay here's a sample page.  What do you think?  Me it freaks me out.

    Well, we at least have 5 more minutes now

    Dean posted in an article that quoted Orlando Ayala in an article

    “The Small Business Server is a case in point. "That product has been on the market for six, seven years," he said, "and we finally got it right. It is successful now because we simplified things, we reduced installation time to about 20 minutes -- it went from a day to almost plug-and run."

    Yo, Orlando, sweetie, dahling.  Patching?  Did we forget to patch this little guy after you plugged and run'd it?

    Gavin's post points out what we already know out here.  It's a pain in the butt to patch these guys up to where they should be.

    Shavlik “isn't enough“

    Our patch page is missing the ISA patch, and sorry some of those “recommended updates“ I would consider a bit more important.

    Heck we even have a Trend patch to track down [if using POP]

    I'll be chatting about Patch management in the future in fact [both on an upcoming webcast and in print - stay tuned for details]

    So Orlando, thanks for giving us 5 more minutes to set up a network but you are missing patching and totally misleading clientele into not realizing that there's these pesky things called workstations that also have to be delt with.

    Man I must have majorly screwed up because my network install took a bit longer than 15 or 20 minutes, that's for sure.

    P.S.  I'm sure that Mr. Ayala knows and was talking about the OEM install to the base system, but I still say that it's a bad message to put out in the marketplace for customers.  It sets the expectations that installing a network should be nothing more than “just” the server, when you still have all the workstations to connect.  My network is my server AND my workstations.  After that initial install is done, my work is “just” starting.

    Uh..Walt..nice but tell me how to run "my" business apps on that APPLE will ya?

    The Microsoft monitor blog today points to the Wall Mossberg article where he takes Microsoft to task for not making computers more secure and easy to secure.  While he has some valid points, the fact that he recommends an APPLE MAC is a bit obvious that he's a person who can work in the MAC enabled world of journalism.  Sorry Walt, MACs are not easy to use for this tired brain of mine, I think it's just what you are used to.

    The link to Walt's story will be active for a week.  Read it and see what you think.

    While I agree that computers need to be more easily secured, as I just last night had a chat with my hairdresser and when I asked “do you have a firewall, is your antivirus up to date” brought a bit of blank looks, I think the issue can also be traced back to the computer vendors.  They sold us on the idea that computers are “toasters” and they are not. They've color coded the plugs on the back but NO WHERE do they include a “how do so safe computing manual“ in any of their installation documents.  Where's the information on phishing?  On how to BUY the subscription to the -- in 90 days this will expire antivirus that's installed on the computer.  Is it because as an industry we don't read manuals?  Or is it that we consider computers like “toasters“ that shouldn't need any maintenance.

    Walt, only 5% of the worlds population run MACs.... if you are a virus writer would you want to write one for Windows with 90% of the marketplace or 5%?  Come on.  And as far as releasing patches faster?  I would hope so, MAC has had some doosies.  AND again, at only 5%, less applications, testing those patches is hardly a big thing.

    No Walt, until MACs run Lacerte, and CCH, and time and billing, and tax planning, and ..... you get the idea.... sorry but you might be able to run a newspaper on that MAC, but not an accounting office.  Not this one anyway.

    So to agree with Eriq - can you run a business on a MAC, yes you can... just not “this“ business.  Walt needs to realize that it's the applications that drive the platform, not the other way around.

     

    An open letter to Steve Ballmer:

    Mr. Ballmer: 

     

    My name is Susan Bradley and I'm a Small Business Server MVP.

     

    This is my open letter to you:

     

    A while back in the blogosphere there was a blog post that [per reports], made a lot of impact on Microsoft.  It was a post on how Microsoft lost the API wars by breaking backwards compatibility and focusing on web applications.  The infamous Joel on Software post was discussed and even nominated as one of the top essays on software for the year.  There’s another trend out there in the tech world that disturbs me even greater than APIs and web applications.

     

    In general, in my view there are three things that impact Microsoft: 

     

    Security. 

    Licensing. 

    Product Support. 

     

    I’m putting you, Mr. Ballmer on notice that I’m going to be very carefully monitoring one of those three.  I sincerely hope you are not making a grave short term mistake that will have huge long term consequences more than you realize.

     

    Security is still a big public relations nightmare.  Even though I believe that any operating system can be made secure and you have employees of your firm practically living out of a suitcase trying to get CIOs, admins and techs to realize this, that’s a long term problem still being worked out.  But for the most part, all in all, I’ve seen the changes that the Security push has made and am quite pleased.  I think we're on the right path.  Sure, we’re still fighting over features versus security, but we’ll be doing that until our dying day.

     

    Licensing and simplicity in the Microsoft world is an oxymoron.  I can’t tell you how many times myself and my fellow Most Valuable Professionals have brought up to even as high as to you at the Microsoft MVP summit last April, that licensing “sucks” and the attitude we constantly get back is that they’ve tried to make it flexible.  It’s not flexible, it’s complicated and confusing and you practically need a team of Attorneys to figure it out.  When 32 SBS MVPs have long threaded email discussions over the interpretation of what a DEVICE CAL is all about, sir, you’ve got a problem.  Small Business Server platform in particular is “supposed” to be easy, simple, and I’m sure I’ve got a few grey hairs under this hair coloring I apply every now and then that I’m sure are directly caused by me trying to track down my correct information for Software Assurance.   To top it off when we’ve had to go up the ladder to clarify licensing and then go back to local Product Managers because THEY were giving incorrect information about licensing, sorry, but you have a problem. 

     

    And now we come to the reason for this blog post in the first place. 

     

    Support.  In my mind it’s the ONE absolutely positively one thing that Microsoft has over any other platform, over any other operating system out there.  Support.  You’ve supported me.  I could be guaranteed that if I called in and specified “SBS” that there would be a person on the other end of the phone call that was an SBS expert, might even have it installed at home, and might even have been around the product longer than I have been.  As has been discussed on other blogs, the beancounters at Microsoft apparently have been looking around to cut costs and one area that is now under the block to chop is support.  

     

    I just heard that starting next year; front line support for the Small Business Server platform [the first call] will be to India.  Now before you think that this is about nationalism and loss of jobs or anything, it’s not.  I’ve heard that the folks that used to be SBS product support team members in Charlotte will just be moving around to other areas and Mothership Los Colinas will be our main escalation “home base”.  [The term of “Mothership” is an affectionate term that I use that refers to the places in the world where the technical support staff that live and breathe SBS work out of].

     

    While we will still have “Mothership Los Colinas”, “Mothership Shanghai”, but we will no longer have “Mothership Charlotte”.  It’s not about a concern of where SBS will be supported; it’s a concern of the loss of history with the product, a loss of team members, a loss of connections to the community out here.  Now to give credit where credit is due, we’ve expressed our concern and those folks in Microsoft that understand how special the SBS community is, are ensuring that there are connections and ties be put back in place.  But it still concerns me that the first call will be to a person who might not have the depth of history with this product that I do.  I’ve lived and breathed an SBS box since SBS 4.0 in 1999.  I have a network at the office and one at home.  I have a Virtual PC version on my laptop.  I know when this system sneezes and catches a cold.  I know when Security Patches hurt us and when they don’t.  I know what works and what doesn’t work on this box.

     

    Already we’ve seen erosion in the support surrounding the SBS platform.  We used to get 2 free calls on the SBS 2000 platform; now on SBS 2003 we have guaranteed newsgroup response.  Even then, some folks have indicated that they are not getting the guaranteed response that they thought they would.  Me, I’m just a volunteer in the newsgroups and it’s not my job, it’s just a hobby.  Granted an addictive hobby, as addictive as blogging, but I do it out of passion for the platform, for this community.

     

    I’m always amazed of the attitude towards product support I see elsewhere [and sometimes with large firms with premier contracts], that the attitude is that support is not good and sometimes useless.  I’ve never felt that way about the support that the Small Business Server platform has received.  SBS product support rocks.  In fact the folks that first coined the phrase SBS Rocks was Product Support Services in Charlotte [at least that’s my understanding]

     

    Funny thing, though, this is only a USA phenomenon.  In fact outsourcing of support has been going on overseas for some time and my fellow MVPs from the International arena were actually quite pleased to see that your firm is finally outsourcing US support because they hope that once we in the United States have as lousy support as they have had to suffer through that perhaps, finally, the overall quality of support will be universal… that is we will ALL have lousy support. Perhaps only then will a long term systemic plan of action to the problem of support at a level and quality that is appropriate throughout the world will be addressed.

     

    I wouldn’t call myself a Microsoft partner but your support policies impact a lot of Microsoft Partners out here.  The ones that sell your products.  Your Small Business Server boxes.  Your real sales staff members.  I will say that I’m a wacko end user who only wants what’s best for SBS and the customers of SBS.  I always have since the first day I went searching for help and guidance and found the SBS communities and used the SBS support. http://www.microsoft.com/windowsserver2003/sbs/support/default.mspx

     

    There’s a scene in the Goldie Hawn movie “Protocol” where she’s testifying in front of the Senate and she tells the Senators …the gist of it is…. that it’s her fault that the events of the movie happened… that there is no such thing as a free ride…that it was up to her to make sure that they, the Senators and others in the Government, were doing their jobs.  Her character in the movie said “I’ll be watching you.”

     

    Well Mr. Ballmer, this is a blog post to put you on notice.  I’m a SBS community member.  I’m used to a level of support that I and my community have come accustomed to.  I’ve called in the past, paid the US$245 and more than gotten my money’s worth.  I’ve been pleased with the support I’ve received.  I think my community has been too.

     

    Here and now, I’m putting you on notice that I’ll be watching out here and monitoring.  And making sure my SBS community gets a fair deal.  We deserve the support that we’re accustomed to now. We’re rolling out your new technologies faster than those big firms.  We deserve folks that care about our Community, about our platform.  We deserve long term support and not short term solutions.

     

    I hope you understand, Mr. Ballmer that I think this cost cutting binge your firm is on lately is very short sighted.  I’m a shareholder and I’m concerned that the short term decisions that your beancounters are doing now will hurt the company in the long run. 

     

    Partners can learn other operating systems and tend to choose the best solutions for their clients in the long run.  You take away support, or have it lowered to a level that makes it comparable to everything else out there, combined with the complexity of licensing, and small businesses don’t have quite the same resistance to rip out and totally change that large entrenched firms do.

     

    Bottom line, Mr. Ballmer, if I see erosion in the level or quality of support that I see now, that my community is used to now, you’ll be hearing from me again. 

     

    I’ll be watching you.

     

    Update:  12/14/2004:  Director of SBS, Eugene Ho responds:

    Dear USA Today...now the story is even better

    Follow up to our lovely USA today article about the “finagle vulnerability”...you remember they did a honeypot and "To hijack the Windows Small Business Server, the attacker finagled his way into a function of the Windows operating system that allows file sharing between computers. He then uploaded a program that gave him full control."

    Well at first I was thinking they purposely chose p-a-s-s-w-o-r-d as the password to get the system SMTP auth attacked [which, yes we ARE vulnerable for -- remember CHOOSE PASSWORDS WELL like Dr. Jesper Johansson tells us to].  But it didn't dawn on me what they really did to purposely get this box hacked.  They set it up with one network card and no firewall.  Yo, folks. READ THIS.

    • Because the Internet connection device is the default gateway to the Internet, the device must provide a firewall service or you must add a firewall device to protect your local network from unauthorized Internet access. In this topology, you cannot configure the firewall provided by Windows Small Business Server 2003 because the server is not the gateway to the Internet. If you want to use the firewall provided by Windows Small Business Server 2003, you must install a second network adapter in your server and use the topology shown in Figure 2.4. For more information, see Appendix B, “Understanding Your Network.”

    Does everyone understand how totally bogus of a honeypot test this was?  They purposely set it up such that the file sharing ports were exposed as part of their server honeypot test.

     

    We never EVER do that.  No self-respecting server does.  So for this article, the honeypot experiment was such a bogus test.  Did the article say in any place in that article how bogus of a test this was?

     

    Sorry folks.. but I”m still blown away by this article and it's content.

    No you don't always need to reinstall!!

    Folks, just a reminder but when there's issues with OWA or issues with Sharepoint.. don't knee jerk think that reinstalling is the way to fix things.

    OWA issues with images?  GZIP patch folks --

    831464 - FIX: IIS 6.0 Gzip Compression Corruption Causes Access Violations:
    http://support.microsoft.com/?id=831464

    Sharepoint problems after applying SP1?

    841216 - "0x80040E14" or "HTTP 500" error message when you connect to your Windows SharePoint Services Web site after you install a Windows SharePoint Services service pack:
    http://support.microsoft.com/?id=841216

    Before you rip out things and start to uninstall and reinstall...come out to the newsgroups and ask!  That's what we're here for!

    The BTDT credential

    We have a saying in SBS land... BTDT.  It stands for “been there, done that”.  It's the highest credential anyone can have in fact.  It means you have first hand experience of “fill in the blank”.  You read the instructions, interpreted them into your environment, and then made the project work.  It's higher than an MCSE credential, higher than an MVP award, it means you made something work

    Sometimes people come into the newsgroup and say “well I'm not a MCSE or a MCP” and you know what... that doesn't matter one twit.  Because each one of us bring our experiences, our BTDT to the table and we can share our ideas.  Remember the other night when a calm voice on the other end of the phone let me stop and think “oh yeah, I have the firewall turned on and I bet it's blocking the Windows messenger”.

    Sharing your experiences, knowing that there are others out there just like you.  On the SmallbizIT yahoogroup that I hang, Doug started a database of SBS consultants so that when he has a need for a branch office install or a remote installation or some other install issue in an area of the country he's not in, he'll have a database of fellow SBS consultants to call on.  A new consultant was asking some questions about starting out and the consensus came back that you didn't necessarily have to have employees, you could contract work out.

    This week a person I was chatting with was talking about the SBS community, that he was blown away by how we share info out here.  Pat yourselves on the back folks, because that is what we do.  We've learned long ago that when we share we all win. 

    Look around you, especially during this holiday season of the places where “sharing” of knowledge, of information means we all win. 

    • Did you know that the web site handlers at Incidents.org aren't paid for what they do?  But their daily diary keeps me informed of what is going on in the Internet.
    • Did you know that many fine folks volunteer at Broadband reports and share their experiences don't get paid for that?
    • Did you know the posters at PatchManagement and the moderators at that listserve don't get paid for that job?
    • Did you know that the communities where people share information like those at SBS2k yahoogroup [all versions of SBS], SmallbizIT [the business/marketing listserve] the CRM listserve, that we all win when we share our BTDT stories?
    • Did you know that the Microsoft communities have tons of “BTDT“ credential holders all ready to help?

    So Gordon out there my friend...you just come on over and introduce yourself to my community.  We do matter, we do care, we get results, ...and we do know it means something out here.  I think your problem on day 2 may be NIC related but you know what? Come ask in the newsgroup or listserve and will give you lots of ideas of what it might be.

    Chad talks about what being a consultant for small businesses is all about.... “there's nothing better than being able to truly help a small business by taking their percieved IT liability and make it an undeniable IT asset . . . “

    Nice going Chad!  That's what we're all here for.

    Dear USA Today - followup - what our SBS box got "hit" with

    I found out how the SBS 2003 got ”Finagled” into.... it was weak password

    That's what the “hijack the Windows Small Business Server, the attacker finagled his way into a function of the Windows operating system that allows file sharing between computers. He then uploaded a program that gave him full control."  was all about in the USA Today article.  I checked with the person who set up the honeypot experiment named in the article [he's a moderator for the Patch Management.org listserve I hang out on] and he confirmed that it was a weak Administrator password [the chosen password was password] that was broken that allowed them access.  That once a strong password was chosen, SBS 2003 was snug as a bug.

    Guys, read this post about choosing passwords.  Any questions?  No?  Good.  Roll over and go back to sleep.

    Heck I'm not a coder or scripter or hacker but I think even “I“ could have “finagled“ my way into a server using that attack.

    And I still say that SMTP auth attacks, worms and bots are not directly “targeted to us“ but like SuperG says, it's like buckshot, we get shot via the blast.  I'll repeat this again:

    • Stupidly misconfiguring my SBS box
    • Weak passwords
    • Not patching
    • No backup
    • Not paying attention to the risks of my desktops

    Now “THAT'S“ my risk factors

    The perfect gift for Christmas

    Want to give the perfect gift for Christmas?  XP sp2 that's what.  So what are you missing out on if you don't have SP2?

    While Windows 98 will have critical patches released until June of 2006, the fact that you have to lower the security in your network to accomodate them in your network is unacceptable to me.  Remember you are only as strong as your weakest link. 

    For those folks that say “I have apps who's vendors won't support XP sp2”, to that I say, let me know whom those vendors are.  Your vendors should not be the ones setting your security policy.

    And Jethro?  Dude!  Get up to SP2 as fast as you can!  The people that I'm trying to jump up and down and get on XP sp2 are probably wheezing on Windows 95 and 98.  It almost sounds like you are already on XP sp1?  If so, what in the WORLD are you waiting for?  Granted, I think that XP sp2 without a server to control the features is like driving a fast car in second gear the whole way and I would argue that if you have 6 XP computers... dear... come on up to the pleasure us control freaks can get with group policy and XP sp2s and join us with a Windows 2003 server or better yet a SBS 2003 server to control those 6 machines!  Okay so maybe I'm a major control freak, but knowing that I can remotely patch, touch and control all my workstations just makes my day.

    The only pain I had in upgrading to SP2 was two workstations that had digital video cards from nvidia.  That's Nvidia not Windows at fault.  All of my other machines had no issues.  What's cool now is that I have firewalls on my desktops that I control from my server.  I've limited the attack surfaces of both my server and my desktop.  Now once I kick my workstations down to user mode ... that's “my” Christmas present to myself...I'll be in an ever better position to protect and defend all over the place.

    Jethro... it's not painful.  Not when you've made sure your machines are clean of spybot gunk like Charlie said.  And once it's done you can rest snug as a bug knowing that your machines have the best protection around.

    If I never post back to the blog, tell my Sister I'm stuck in the attic

    We're putting up the Bradley Christmas tree and this normally includes one of us [normally me] crawling on my knees in the attic to pull out the Christmas ornaments.  The good news is this year we found the spare tiny light bulbs.. the huge bag of tiny light bulbs...that is as big as it is because every year we can't find the bag of spare tiny light bulbs until about December 26th and we buy more each year. All bulbs worked this year [we leave the light strings on the tree], so it's fitting we found the bag when we don't need it.  We'll probably forget where we're going to store it this Christmas season in case we need it so we'll probably end up with more light bulbs after we go to the store and buy more because neither one will remember where we stuck the bag.

    When I was a little girl we had a mondo kewl Christmas tree.  Aluminum tree with the color glo wheel.  Now THAT was a Christmas tree.  None of this warm, cozy Christmas tree stuff, this was George Jetson's tree embodied.  To see how much it costs now...just don't tell my Dad who probably sent it off to Salvation Army years ago how much they are selling for now.  But we didn't have a hardwood...nah ... our tree was 100% metal.  One day Mom was vacuming the living room and had to yell “timber” as she sent the tree tumbling over.

    Okay enough of a break... time to crawl back in and drag out the rest of the ornaments.

    P.S.  You don't have to call my Sister.. I made it out.  :-)

    There's always one that drives you to drink

    Well day two of the “you really don't want to do it like I'm doing it and I never want to do this again and have to “touch” the workstations like I'm having to do it” migration.

    I got the permissions needed for Lacerte working, and used the “touching the workstations” opportunity for a good spyware inventory.  There are a couple of workstations that I did a “what the heck is that!” in the add/remove directory.  Time to prepare the troops for “user mode” by Christmas.  A little too many funky programs in there that just shouldn't be there.

    And of course there's one workstation that had to make my day.  I've never seen a Window XP that wouldn't let me flip from the “cutesy” control panel to classic mode, but I did certainly today.  It also only has “restricted site zone” in Internet Explorer.  That's it, no internet, no trusted zone, nothin'.  Just “restricted”.  Like I said, I've never seen a machine do what this one is doing.  Oh, did I happen to mention that it had [notice the past tense] AOL on this workstation?  Remember the other machine [a laptop] that I had xp sp2 upgrade issues with was also a machine that had AOL on it.

    I'll let you decide about supporting AOL in a firm environment, but I know I'm putting my foot down and not installing it anymore as I've wasted too many hours with machines that have had it on and it just gives some really weird issues.  Now granted in might be coincidence, but given that two out of two computers with AOL have been my problem children, it just makes you go hmmmmm, doesn't it?

    Kevin actually recommends a different approach if the owner “has“ to have AOL:

    • Use Enetbot's utility that will send/receive AOL email into Outlook [http://www.enetbot.com]
    • Or use the AOL webmail [which in reality isn't too smart either as you are blowing past all of your Exchange based antivirus]

    Well there's a repair install of XP in the cards for tomorrow.  The worse thing about this workstation is it's one of the ones with a Nvideo Digital card.  I have two of these machines in the office and they hate the SP2 driver so I have to boot into safe mode and roll them back to the sp1 video driver.  I even tried totally building a new profile on this system and it still was an obviously not so healthy box.  Mind you.. this is one of the partner's computer [of course... it would have to be his computer, wouldn't it?] so I want to get it ... well... kinda working.. ya know?

    So I took this opportunity to

    • Update the ISA client
    • Update to the new Trend suite
    • Ensure that the antivirus was being seen by the XP sp2 security center
    • Ensured that a port was opened up for Trend to listen at 24091 [Trend's default]
    • Reviewed Windows update to see if “it thought“ I needed any additional patches [for example one machine “thought“ it needed XP sp2 even though I had previously applied it.  Under the theory that just let it do it's thing and don't argue... I let it reapply SP2.  The other machines wanted to load the GDI+ tool
    • The annoying thing is I have to launch the time and billing program for each workstation and make it build a local calc space and reattach to the right billing database
    • Some programs don't bat an eye when you've ripped out their UNC name and some do

    Funny thing.  I was contacted on Wednesday to give feedback on patching.  It's very fitting that I “just“ finished “patching“ a new server up to snuff and then had to take inventory of all these machines.  It's still not easy to patch.  Even with my Shavlik patch tool, it's still NOT “blonde“ enough for a do it yourselfer or even a consultant that isn't the wacko for patches that I am.  The impact of the ISA patch the other day points out that many folks did not realize that ISA Server sp2 had come out as far back as last May.  I still want an RSS feed that keeps track of all Service packs.  I think I'll ask Santa for that for Christmas  ;-)

    Note to self, don't forget the little things

    So the robocopy finished and I have copied over the data files and was checking to make sure that the data had copied and noticed the drive space on the newly build server was slowly decreasing.

    Huh?

    Then it hit me.  It was 11:00 p.m. and I had set up a test backup the night before of the little bit of data that was on the server at that time to backup to the drive since I hadn't yet moved over the tape drive.

    Duh.  Nothing like backing up what you are backing up.  You've seen those circular errors in Excel haven't you? [Okay so maybe it's a beancounter thing] anyway I stopped the backup and cleaned up the log files and all is well. 

    Tomorrow is clean up day... all the little things.  Okay off to bed and Happy Thanksgiving to those in the US as it's already Thursday for me. 

    For those that aren't in the USA to celebrate to know what the day is about... well it's a day we give thanks for our blessings.

    Mind a little indulgence while I say “thanks“?

    Thank you to all the SBSers that pitch in and help each other out day in and day out.

    Thank you to my friends, my extended family around the globe.  I'm not going to embarrass anyone by naming names but you guys know who you are.  You keep me in line, threaten to put duct tape on the email port when I go overboard, you keep me grounded and humble.  Some of you are in this photo.

    Thank you to the folks that I know through ...well for lack of a better term.. geek relationships that go beyond way that.  You guys work so hard, are so talented, that it just makes me want to learn more, to do more.  You guys inspire me.  Who knows... I keep joking that one of these days I just might get comfortable with command line and scripting. 

    Thanks to the SBS family members/Motherships from around the globe.  I don't think SBSers realize the passion and dedication of these folks.  From Dev to Support to Sales... the passion, the caring is beyond belief.

    On this Thanksgiving day, thank you to the folks that touch SBS, affect SBSers.  You know who you are.

    Thank you.

    Okay if you know a sort of geeky beancounter... send them this post

    If you got forwarded this, it's because your friend considered you a geeky beencounter.  Wear this badge with pride my friend because I think that geeky beancounters will be more and more the drivers of technology in the future [but that's just my opinion].

    So what's this post all about?  To ask if you are a member of the IT section of the AICPA, that's what!  If you are, you'd get the AICPA 2004 Top Technology Guide for free for downloading via a email link.  But because you aren't ... you are missing out on some really valuable information and insight.  Better yet become a Certified Information Technology Professional and show to the world what your friend always knows.  That you ARE a geeky beancounter and proud of it!

    An open letter to "the Dark Side"

    To the marketing department of Companies in Technology:

    Two things came across my desk this week to inspire this post.  The first was a study to help “develop a share CIO/TMT understanding” and the other was this blog post.

    First off, there's a fundamental flaw in how you market computers to decision makers.  You make it seem so easy to install networks and computers and technology in your message to decision makers and quite honestly, it's not, nor should it be. 

    The study that I refer to above says “the CIO must consistently work to provide the TMT with realistic expectations of the capabilities of IS. If the CIO allows the TMT to understand how IS can realistically be used within their firm to meet specific objectives, the CIO and TMT will be better able to reach a mutual understanding regarding the role IS will play within their organization.” 

    Let's translate for the SBS world, shall we?

    The consultant must constantly fight against marketing materials that indicate that installing and migrating to a new system is so easy that all it takes is putting a cdrom in a drive and following clicks.  The consultant must try, as best as possible, to manage the expectations of the customer that have been improperly set by brochures and information that state that the network installation is so easy, will only take minutes, computers are a piece of cake, and 2 year olds can handle this. 

    Gordonian was blindsided by the expectations that you gave his customer that upgrading was easy. Even on those “15 minute” preloaded machines, you do realize that it took me way longer than 15 minutes to find all the tweaks in Trend I needed to do, to add patches, to adjust some group policies.   Now granted, I was slowed down a bit by capturing what I did and blogging about it, but still, the process I've done took longer than you, the marketing department, has set as expectations. 

    Yes, I'm sorry to call you guys the “dark side”.  I know you don't mean to.  It's hard to run a business that needs to “cheerlead” out new products at the same time you properly set expectations. 

    But understand, that to set up a network, securely, safely takes time.  Computers aren't easy. There's a reason that the geek squad division of Best Buy is making a name for itself or that geeks are going home at Thanksgiving fixing computers..  [thanks to Anne for that blog link]

    Have you seen the other message that marketing puts out?  It's an ad by Cisco advertising their Network protection feature.  You've seen it, Dad is at the office and there's a massive worm attack underway and they can't figure out how it got in and then “Sally” skips by and tells Dad “Oh, I just downloaded a game on your computer, Daddy!”. 

    Well folks, first and foremost, there's a flaw in that commercial.   First, “Daddy” should never allow kids on corporate assets and this should be a written policy that technology isn't needed for.  Secondly, “Daddy” shouldn't have the rights to download everything and anything on his computer.  He should be protected from himself.  Jeff Middleton wrote a section of Harry Brelsford's next book on the concept of “least privilege”, but honestly that's not an easy thing to do.  Security takes time.   

    We” need to change our view.  We need to change the idea that all of the packets on the inside of our networks are good packets.  That we can trust explicitly all traffic that is on the inside of our networks.  That we don't need outbound filtering because only “good stuff” can be traveling outside, right?  That workstations are protected enough as long as there's a firewall on the outside.  Steve Riley talked about this at Tech Ed this year and it was captured on some of the blogs and articles around that time [and for the record XP sp2 is out Windows 2003 sp1 is still in beta]. 

    But let's start first by changing... managing...the expectations of the decision makers.  Putting in network infrastruture isn't easy.  It's hard work.  And quite honestly even if it WAS possible to install a network in 15 minutes.... it wouldn't be secure.  You can't get fast and secure at the same time. Decisions are involved here and the word alone implies thought, consideration, review... certainly longer than 15 minutes anyway.

    So to all those folks that market.. make sure your message is clear and truthful.  Security is a process, it takes time.  Help the consultant manage those expectations by managing the message from the get-go. 

    To all those customers out there ....hire competent folks that make the right decisions.  Understand that they are making decisions in your best interests and don't rush them.

    To you consultants ....communicate to your customer of your process and why this isn't a 15 minute thing.

    Let's all manage those expectations, shall we?

    Last patch - thank you SBS 2000

     Getting ready to fire up the Shavlik Hfnethck pro to patch my network [yes even though my brand new baby..um..my new SBS 2003 server is coming in next weekend I don't want to slip from my designated patch schedule] and it's the last time I'll be patching this server.  It got me to thinking of how far “I've“ come in my own journey over the last three years.

    Since this will be the last time I patch this server [it's going to be reincarnated as a 2k3 member server], can I wax a little poetic about how far we've come since I put that box into production in July of 2001. 

    This box was put into production right before a time when worms were still pretty much those red crawly things.  We thought pretty much that our little boxes could stay under the radar of the big guys and their issues.  We weren't hacked, we weren't targeted.  We sat here on the sidelines while our big brothers had issues.  Our biggest issues back then were pretty much viruses or the fact that the boss couldn't get his AOL email through the ISA firewall.  I still would like to know why so many of my male geek friends who got ILOVEYOU from another guy opened the dang things up.  Ya have to wonder on that one.

    July 19, 2001 changed all our notions of security in SBSland.  I still remember Jeff Middleton reviewing the security bulletin that came out in May or June [I forget now] and said this one was going to be bad.  So we screamed and yelled and jumped up and down in the newsgroup as best as we could and still the Code Red worm came and we were “Road Kill“ out here.  Remember too that was in the day and age that if you were a smart admin you waited until the Service pack and then you waited some more after that.  I still remember Mal Osborne posting into the newsgroup saying “what rock did you out from under“ when the 33,647th person posted in the newsgroup that there IIS service wasn't running and there was some weird message about “Hacked by Chinese“ up there instead.  Remember too, back in those days too Microsoft patches came out at any old time and day of the week.  Tuesday at 4:30 a.m., sure release a patch, someone is up somewhere wanting to download it first. 

    Look how far we have come in three years.  SBS 2000 and Windows 2000 was “kitchen sink and all on by default“  We ran everything including Terminal Server in applicaton mode on that box.  Look at SBS 2003.  Heck we have folks beating up on it because Terminal server in app mode was taken off.  Remember what I harp on all the time... we cannot, could not then, cannot now, lock down Terminal services on a domain controller.  Go grab [please do] the Security Resource kit and the 6 steps for securing TS on a server cannot be done on a domain controller.  Go knock yourself out if you think you can.

    We now have a regular patch schedule.  Now those in my space can argue that they want patches any ol day or night, but let's be reasonable, the fact that I can count on second Tuesday as Patch day helps even little me.  I've only been away from the fleet two times on Second Tuesday.

    We now are starting to see the movement of two patch engines.  Update.exe and .MSI.  Gawd, do you know you are a geek when you get excited that the last IE patch was built on the update.exe platform.

    We see less and less of uninstallable patches.  Exchange 2003 sp1 was a one way trip.  It used to be that a lot of the security patches were that way too.  The other day I talled which ones of the 2004 patches were not uninstallable [trust me, just don't ask why I did this, I had a good reason]

    04-033 Excel
    04-027 WordPerfect
    04-017 Crystal reports
    is a "it depends on the product"
    Visual Studio yes uninstallable
    Outlook with BCM NO
    Not sure about CRM
    04-010 MSN
    04-009 Outlook
    04-005 Virtual PC for MAC
    04-003 MDAC

    It would be better if all the patches were uninstallable, but to me it tells me that it's the applications that still need to move a bit more in compliance with the goals for patching.  Heck even CRM just released a “patch schema“ KB.  The bottom line patching is getting better and is going to get even more better.

    Today it warmed my heart that Jake in the newsgroup  asked if the “Reported vulnerability in Microsoft ASP.Net affected Sharepoint services?  Sure 'nuff, Jake as well as potentially to our remote web workplace.  But it isn't a Code Red/Nimda kind of event to blow through our Remote Web Workplaces, but it is a recommended patch for our boxes.  In fact it's listed on the place that we should also visit once a month to ensure we have the latest and greatest.  The fact that we have in three short years gone from where all we are worrying about is how to setup AOL through ISA to being concerned about security issues is a big deal in my book.  And I'm sure some of you will say that “oh, if you were running “fill in the blank OS“ you wouldn't have to worry about patches, to that I say, dream on dudes.  Go over to the Secunia.com web site and pick ANYTHING that runs code and it probably has a known vulnerability and probably a couple more that are unknown.

    W2KNews had a great paragraph today on the “holy wars of OS's“ and I hope they don't mind if I copy a section of their email here:

    The controversy about Operating Systems was very well put in perspective by subscriber Mike Boutelle and I could not agree more. He said: "Regarding the holy wars, I think that the debates back and forth show that it is people and processes that make the difference, not the raw technology. You can install a good OS badly or a bad OS well. The security of the system will always come back to the people and the processes behind. Maybe a few CIO's should consider that before that outsource their operation."

    The sooner we “get over“ that US versus THEM isn't about Windows versus the Penguin, but rather the good guys trying to just do their JOB and the bad guys trying to stop us, the better off we are.  Steve Friedl today on a listserve I'm on gave a heads up of some potential stuff happening on the web. 

    So what can WE do to help in the fight?  For one, we can do our part in putting pressure on vendors to code more securely, to support patches faster, to not require local administrator  rights on our workstations to run applications.  I also heard that some vendors are still not supporting XP sp2.  A major vendor in the accounting space just announced a new product upgrade for Tax Season and it includes installing .NET and MSDE on each workstation for full optimisation.  So what did I do?  Sent an email and asked if the vendor would either send out patches for MSDE [since it's not patchable by Windows Update at this time] or support third party patch tools like Shavlik.

    For the SBS 2000 network, one of the reasons I got Shavlik [and still recommend it] is how blonde it is to set up.  I'll be honest with you.  I'm on the WUS beta and I've got the server synchronized, but I've yet to get the clients “talking” with that server.  I'll probably revisit it this weekend. In the meantime, while the WUS is still in beta we do have a download page that helps us keep our boxes all patched [and contrary to newsgroupser, patches come out once a month on a predictable schedule [remember Second Tuesday of the month].

    So how should you patch? 

    • Well for one.. test the patch first.  I can hear you say now... “Easy to say, Susan when you have a server at home that you use for that purpose.”  Okay, you guys got me there, but in SBSland we also “test the patches” by letting others in our community test them.  For all of you in our communities that test patches and report back your experiences, a big thank you.  Report back your experience and just like with the ISA patch [which I'm putting on tonight] if things don't go right, CALL Product Support.  Any issue is a free call.  The quality of patches is EXTREMELY important to Microsoft and this feedback loop is critical to making patches be painfree.
    • If you don't have a spare box, you can also VMWare or VServer or VPC a copy.
    • Ensure you have a good backup, just in case.  But honestly, over the long haul, I've had less problems with security updates than service packs.

    So patches can come down via Windows update for the Windows patches, but for everything else visit here for the other patches needed. And yes, as you can see the ASP.net mitigation patch is included there.

    So what else can you do?  Check out security guidance here for a start.  It's a nice Small biz guidance from Microsoft Australia.  Then go bore your friends, neighbors and relatives at events you attend.  Everyone is aware of the 'gunk' out here but may not know how to handle it.  SANS.org has a new newsletter called OUCH. A blog for Ma and Pa and the Corporate Clueless is a great starter.  Always use Protection is another great place.  Be your own Security evangelist to your communities.  Urge folks to have a firewall, antivirus, visit windows update and add anti-spyware.

    Next week is Thanksgiving in the United States.  If Norman Rockwell was alive today, I'd want him to add to his Roosevelt Four Freedom series and add to the Freedom from Want “Thanksgiving' image and perhaps add to his “Freedom from Fear“ picture.  Okay so it's a cheesy idea, but consider these days the uncertainty and fear people have with their computers.  I'd have a picture of everyone crowded around the Personal computer while a person is there teaching people about the basics of Computer Security.

    So as you prepare for traveling home, burn in a couple of copies of XP sp2 will ya?  Check out the status of the antivirus.  Go to grc.com's Shields Up and do a quick scan to make sure the firewall is in place.  Run a spybot/adaware clean up and DONATE or BUY their products.  They can't keep fighting the good fight for free you know. Talk to the parents the importance of knowing who is on their childrens' IM listing.

    It takes all of us good guys to keep it safer out here.  We joked at the Security Summit that the day that we know everyone will “get“ security, will be the day that Oprah calls and wants Rich Kaplan on her show to talk about computer security.  [Trust me, he doesn't look that geeky in person - he looks more normal]

    And with that... it's time for me to patch for the last time... thank you again SBS 2000 ...you served me well.

    Don't mess with my firewall

    When I read this the other day, I don't remember if I blogged it.  When Windows 2003 sp1 ships, the lovely community of people that talk to Microsoft [read Enterprise folks] have asked Microsoft to disable the XP sp2 firewall “by default”. 

    It's so nice and refreshing to know that Enterprise folks have our best interests at heart, isn't it?  This is one of the reasons why I think holding up big business/enterprise as a pillar of best practices is a crock.  We're out here in the small space installing XP sp2 with our firewall ON, thank you very much, and meanwhile they are wanting it turned off.   Don't mess with our firewall in SBS 2003.  Remember we have a QFE that enables it and then we the consultant can adjust it as WE want.  It's cool to know that we're being more proactive out here for security than the big guys and yet we get the bad “rep” for being all on one box.  Honestly though, our risks are more internal and in misconfiguration of that firewall than it is of having ISA on our domain controller.   And as we've said before, stick a natting firewall on the outside and rollover and go back to sleep.

    Had an interesting set of conversations tonight over dinner and pool while I'm up here in Redmond.  I'm here for a couple of days of meetings with a bunch of my fellow newsgroup/online/book author/MVP buddies and the focus is all on Security.  

    Talking tonight with folks the most frustrating issue that Microsoft has to deal with is vendors who 

    • Require that applications run as local admin
    • Still are coding/supporting for a Windows 95/98 Code base

    Newsflash for you folks, if you think, that in any way shape or form that a operating system built in 1995 is going to in any way shape or form be somehow magically made secure, you need to wake up.   For one thing, I would argue that with California's new AB1950, it would be hard for me to argue that that product made a reasonable effort to be secure.  Windows 95 and 98 have no security. 

    Mr. Vendor, stop making my security decisions for me.  You aren't helping me.  We're all in this fight together and if your business model is such that you don't think keeping your software on a operating system reasonably up to date... I'll cut you guys some slack and let you get away with Windows 2000, then you obviously don't care about my business, nor care about security.

    Honestly, if you have a line of business application that will not run on anything other than Win9X, ask yourself if that vendor is truly showcasing to you that they care about YOUR business, YOUR data and doing the best they can to help you be secure. 

    Firms that say “we can't afford to migrate off of 9x“ are kidding themselves.  Lack of blue screen, group policy, remote patch management, event logs telling you more about that system, You are kidding yourself if you think not migrating and updating is a cost free decision.  Your inaction to move from 9x costs. 

    Risk analysis time folks.  If your vendor isn't stepping up to the place and helping you in security, you really need to question if they care about your business. 

    Quite honestly, Microsoft can't push these vendors.  Only we can.  Complain.  Post the vendor to my web site that I've set up to “shame“ these vendors.  Only the community out here can push vendors to step up to the plate.

    My kingdom for a download link

    Okay I'm sitting on the ground at the Fresno Air Terminal [yes, the letters spell FAT] next to the wall so I can plug in and get power because when they built the new terminal they didn't put power in the places where the seats are.  Brilliant isn't it? 

    So here I am on wireless trying to find the Download button on the ATT wireless site so I can install the cellular phone/internet dialer that connects to my cell phone but I can't find the stupid place on the web site.  Really really annoying when I know it's there somewhere but they hide it. 

    This is the first geek trip where the Tablet is “solo-ing” and I never got around to putting that ATT communications manager on this system.  Oh that makes sense.  I found the link.  I have to go into customer support forums before I can find it.  No wonder AT&T is being bought out by Cingular.  Folks, make this stuff easier to find.  Geeze.  I'm downloading it even though I'm obviously on wireless because it gives me connection flexibility. 

    Being a geek on the road means you still need to either be flexible or know where all the Starbucks are located.

    So I'm off for a VERY quick trip to Orlando, Florida just for a meeting tomorrow and I'm taking the red-eye to Florida tonight from Los Angeles.  Then on Sunday popping right back to Fresno. 

    I may live to regret this. Already I'm figuring that I'll have been wearing the same makeup for about 36 hours by the time I'm done.  I may need a spatula to spackle my face back up in the airport before Saturday's meeting.  Looks like it's a clear night for flying though.  My Dad who dropped me off said, “you aren't taking a computer are you?”.... uh...well... Dad...I have to admit that I'm totally addicted that if I don't have a computer when I travel I feel really disconnected and certainly without entertainment for certain.

    I'm definitely a high maintenance gal for sure, already I've gotten a SMS message on my cell phone from United telling me that my flight was on time, my connecting gate info and what not.  I'm obviously sitting on the floor like a pretzel while I wait for the AT&T communications manager downloads [by the way, this is a slow download].  Whenever I travel like this I know that if I forgot any last minute “anythings”, with a cell phone and a computer I can remote back to the office, get the email or information I need.

    Plus, there's something to be said for the warm comfy feeling you feel when your geek friends sign in.  You feel connected no matter where you go.  It's a social network thing.  Except, oh, Mr. Stu Applegate, [who just logged in] thanks but did you HAVE to remind me that it's not long until Christmas?  [His tag line advertised that the days are getting closer]  I haven't even started Christmas shopping yet!

    Next week I'll have the fun experience of meeting some folks that I've emailed and IM'd with for awhile up in Redmond, Washington.  I've never met some of these folks in person, but we've been communicating for a long time so that I feel they are friends.   That's always really cool to me when I meet up with people who I've communicated with via electronic means and finally meet in person.  There's a level of communication that goes on once you meet face to face that is different than if you just met.  It's a notch above.  It's a weird but cool feeling whenever I've experienced it.  I do find that I tend to not know a person my his or her real name, but rather his email address.  I still remember the first time I met Chad Gross in person.  We knew him as the guy who wrote the OWA over SSL paper for the Smallbizserver site.  The entire weekend that first SMBnation we would say “this is Chad Gross” and people would go...okay...we'd then say “he did the OWA over SSL paper” and faces would light up like Christmas trees and they'd say “YOU'RE OWA over SSL?”  It was funny to see.  They knew him for his white paper and not his name. 

    The world is a small place.  To everyone out there, have a great weekend, and cut me some slack over the next day or so if the posts don't sound too coherent. 

    And to answer the question of my friends who know I have an annual pass to Disneyland.  Yes.  I'm flying across the country to the site of Walt Disney World and NOT going there.  Can you imagine?  Definitely need my head examined on that one. 

    I think "Best practices" is a crock

    I'm in a mood.  No, not one of those female moods where you guys go “Yes, dear”, more like a ... okay if big businesses who have budgets can't do this stuff.... kind of mood.

    Today my email box is another red banner day of bagel viruses/worms whatever you want to call it. AND a huge red letter day for getting “you sent a virus notification” from all these firms that have their A/V email notification turned on,  AND I got a ping from a guy who said “do you realize you just sent a virus to a listserve?”

    No, sir, I did not.  For one thing this virus “spoofs“ the from address, for another, I don't click on email attachments on clearly obvious virus laden messages.  And here's the thing that I don't get.  In order to launch this virus, some do-do brain firm has to do something really dumb.  They have to allow end users to click on a .exe, a .scr, .com or a .cpl.  Inside my firm, I totally block all of these types of attachments.  There is NO REASON whatsoever to have your firm employees have access to these types of email attachments.

    So here's the other thing that set me off, you know that AB1950 bill that I talked about yesterday?  I can predict right off the bat what's going to happen.  You, the SBS consultant will come into the proposal meeting and your competitor across the table is going to say “Oh but SBS is not AB1950 compliant because it doesn't do best practices, because your firewall is on your domain controller”. 

    Fiddlesticks and Poppycock.  At home where I have the RRAS firewall, NO ports open, another hardware firewall on the outside, also with NO ports open, I've had to un-hijack my sister's search engine three times.  Would it have helped if my firewall was off of my domain controller on a separate device?  Absolutely, positively NOT.  It would not have helped one bit.  Would running an alternative browser like Firefox help? No, because it too is subject to vulnerabilties these days.

    As long as I allow my end users full rights to everything on the desktop, as long as those do-do brain administrators somewhere don't block what is clearly virus attachments, as long as end user blindly open what is obviously a virus laden attachment, I'm doing way way more best practices down here on my little SBS box that “breaks” all the so-called security rules than the big guys do.

    So many times in SBSland people get sold on the idea that if they only buy a hardware firewall they will be safe, or if they only buy this or that, they'll be safe.  It doesn't work like that.  Even Gartner in their analysis of the new law says “However, your overall security practices — not a specific solution — will ensure compliance.”  You have to look at the entire network and not just one part to ensure your system stays safe. 

    You are only as good as your weakest link.  And in my case, it's NOT the Small Business Server box.

    Assembly Bill 1950 - new California Law

    I'm putting together a Top Technology powerpoint tonight and was looking at the Gartner web site and they have a headline that says “Prepare for California's new Data Security Law“. 

    Okay I'm familiar with SB 1386, the “you get intruded, you must inform those affected parties that may be affected by identity theft”, but what new Data Security Law?  In digging, it's a new law, called AB 1950 that expands on SB 1386.  As Gartner puts it, this expands our duties to not just report, but to follow best practices to “protect“.

    • Take "reasonable precautions" (the law provides no definition of this term) to protect personal information from modification, deletion, disclosure and misuse.

    • Require partners with which information holders share information to meet the same standards.

    • Protect personal healthcare information.

    As Gartner puts it, California will need to provide more guidance on how this law will affect data security.  Until then, follow best practices and pay special attention to protecting data types specified in the law, such as Social Security numbers and medical information.

    I would LOVE to pay special attention to protecting the Social Security numbers in my Tax Preparation programs, but you see NOT A SINGLE ONE OF THE APPLICATION VENDORS will support my use of Encryption of those data fields. 

    It's a little hard to do “best practices” when my vendors won't help.

    Dear IT Company:

    Sorry about the rant, folks but a customer posted in the public newsgroup that got me in this mood.

    So here's a letter to an IT Company somewhere:

    A customer of yours posted into the public newsgroup today.  They said that you are a supposedly reputable IT company and you said that you'd have SBS 2003 installed in one day, no problem.  You quoted them SBS 2003 Premium.  But you ended up installing SBS 2003 Standard.  And then you told the customer you'd arrange for “bolt on“ software products so that it would have SQL and ISA capabilities but that an upgrade to SBS 2003 Premium was “impossible” as it would have to be a complete re-install of SBS as “it can't be upgraded”.  You've ended up spending 4 days on this install instead of what you said it would take the one.

    Thank goodness this customer of yours did a 2 minute Google search and found that all you have to do is install Disk 5.  There's no need for a reinstall AT ALL.

    Dear IT Company:  When will you realize that you affected not only “this“ install, but the expectation for upgrades in the future.  You think that customer of yours is going to want to upgrade in the future after this mess you've put them through? 

    You know, it's okay if you don't know everything, but it's not okay when you mislead a client.  If that customer can find out the right answer in two minutes of Google searching, why can't you?  You now look really stupid as a whole bunch of people in the newsgroup are telling your customer that you are full of it.

    As the Small Business Server platform gets more interest, I'm cringing at the folks just coming into this space and not doing their homework and learning about SBS. 

    http://www.microsoft.com/sbs see that?  Start there.  Go to a SMBnation conference.  Grab a book.  We've got several in the marketplace these days. 

    Next time, take the time to learn more about this product and be HONEST with your client.

    SBSers deserve to be treated better than you just treated your client. 

    And remember.  Word of mouth is big in this space.  You just blew the chance of that client of yours being your Customer Evangelist, your volunteer sales force.

    About that "Windows Validation"

    I see folks on the web talk about how you MUST validate your Windows before downloading some things like the Microsoft Time zone tool.

    That's actually incorrect.  You can say “no” to validation and still get to the download page.  Personally, while I understand that any corporation needs to worry about piracy and what not, what I don't like is how it penalizes those of us who are trying to do the right thing. 

    At this point in time you “can“ say no.

    In our MVP community several people have noted that even on OEM installs it has failed to validate the operating system and they've had to either “opt out” or dig up the product key code to make it validate properly. 

    Before you penalize those of us that ARE trying to do the right thing, make sure this is bulletproof... especially for those OEMs, okay? 

    And another thing.  While I'm in rant mode here tonight, can we do a little bit better job of communication when you bring out new initiatives like this and the new KB search and Microsoft support pages? 

    I don't know if it's that Microsoft sends too many emails or not enough, or not the right kind, but I must have missed the memo about the changes to the Microsoft support web site and to the Validation initiative. 

    A little less on some stuff and more on stuff that truly touches me, okay?

    Hey the hotel has wireless!

    While the advertisement of the hotel only said “dataport” the nice surprise was that it had Wireless Access in the rooms.   Right now I”m not my “baby laptop”, my Acer Tablet PC just about ready for bed.  Tomorrow will be day one of a four day geek fest.  At the hotel I”m on a 172.16.x.x network here and one thing I forgot to do to this laptop just to do a smidge more security by obsecurity....not that I don't already have Windows Firewall enabled and Trend micro's turned on ...and no matter what Trend Micro's installer says, the two cohabitate just fine..... is change the Workgroup name to “not” be workgroup.  I try to make laptops that I use for the road to be “just for the road” and I don't have them as domain units.  If I'm hanging out in wireless all over the place, taking the laptops to security venues and loading gawd knows what tools on here, I don't like them anywhere near my production domain.

    I consider this the ulimate “air gap”.  I will use a USB pen drive and what not, but my machines that are my “test beds” I like to stay separate from the real network. 

    I also make sure my laptop is up to date on patches and anti virus def files if it's going out on the "highway".

    What about you?  Do you take extra precauctions in your role as consultant to ensure that you don't get infected when connecting to others?

     

     

     

    To whom it may concern:

    I don't want Rolex watches.  I don't need V_agra.  I don't need P_nus enlargement.  I don't want an IBM laptop.

    When I go to the HP web site and look at the 3d version of the zd7000 notebook, I didn't give you the right to suddenly load something called Viewpoint.

    If I load up AOL's IM client, I also didn't allow you to load this up or whatever else you allow to tag along.  You have this ad campaign on that says you care about stopping malware.

    To whatever software....I didn't give you the right to install Wild Tangent.

    I didn't give you the right to install WexTech Answerworks either.

    And ZDnet, after I specifically opted out of newsletters and email, I still ended up with junk mail from you guys.

    Apparently you as vendors think that we're stupid enough just to put up with this?  Maybe we are because we aren't putting up the fuss we really should be doing.

    And the sad part is how much effort we put into cleaning these boxes up.  We can't trust them anymore.  Yet we spend so much time and energy in malware tools when we should be flattening them and rebuilding the systems.

    I was just chatting online with a guy who just rebuilt a system yesterday, loaded up AOL IM [for friends and family] and ended up with Viewpoint.  So I'm recommending that he loads up Trillian instead that plugs into multiple IM clients.  Mind you he's re-flattening a system he just built because he's in an industry were security is important and having programs “do thing” that he didn't authorize is just not his way. 

    Maybe that's the thing to do.  “Vote” with our feet and walk away from vendors that do this.  Or email them.  Or talk to their representatives.  Or.... well you get the idea.... start speaking out against this.  If we don't, we won't “own” our systems anymore.

    Okay I'm in a mood....

    Fredly posted in the newsgroup asking a question about Watchgard versus ISA and where ever he crossposted to responded back that he had gotten another response that said this:

    “The best thing you can do is to get a firewall as Watchguard or another box
    and remove the ISA. Its never any good ide to run a firewall on the same as
    your production server. I cant think off any explanation why MS dont removed
    the ISA when they removed the TS on SBS2003, its a bad ide to have firewall
    on your production server, very bad. But if you have the Watchguard you will
    be safe, and then you only need one network card. But if you only are runing
    ISA, DHCP and DNS and not excahnge or other stuff, then you can use your SBS
    as a stand alone firewall and thats ok, but maybe a litle overkill to have a
    SBS box for that and not only a standard server with  ISA.”

    To whom it may concern that posted that:  The best thing you can do is to understand that right now my vulnerabilties, my threats, my weaknesses are not my ISA on my domain controller but the fact that many of my line of business apps want local administrator.  Having a firewall on our little boxes is not where my security threats are coming in from, dude.  It's my blasted desktops that cause me my grief.  A firewall is a speed bump.  A Watchgard firewall is also just “software on a box“.  And right now with my Shavlik, I have a patch tool for my firewall.  Watchgard needs patching just like anything else. 

    As long as you are running Windows 98 or XP's in local administrator mode, the number of NICs, the position and make/brand etc of your firewall is irrelevant. 

    My threats are not attacking my domain controller.  They are attacking my desktops

    As long as we don't understand where our true vulnerabilities are.... we will be arguing while the house burns down in flames behind us.

    UPDATE:  Bruce Schneider has a blog post on this subject:

    http://www.schneier.com/blog/archives/2004/10/security_inform.html

    “Again and again, it tells customers that they must buy a certain product to be secure. Again and again, they buy the products -- and are still insecure.

    Firewalls didn’t keep out network attackers -- in fact, the notion of "perimeter" is severely flawed. Intrusion detection systems (IDSs) didn't keep networks safe, and worms and viruses do considerably damage despite the prevalence of antivirus products.

    The key to network security is people, not products.”

    I'm just going to stop using the Internet...maybe that's the proper answer?

    So I'm reading that Internet Explorer, XP sp2 is screwed, Firefox and Mozilla have vulnerabilties and as the Incidents.org web page so aply puts it, “If you are reading this diary with any web browser other then 'lynx' or 'wget', you are likely vulnerable to one of the issues released today.”

    Okay... so that's nice to know.  And how long before Lynx and Wget get vulnerabilties?  I know a lot of geek buddies have switched to firefox but I don't like any browser that can't authenticate in with ISA and active directory.

    When push comes to shove it's all about risk.  A new blog on Security guides opened up recently and Brian Johnson pointed to a Security Risk document that was released. 

    Me, I'm making to movement to User Mode and least privilege here in the office and making sure I have other processes in place.  I'm not willing to move from a browser that I can remotely patch.  Sometimes you have to stand back and realize that we will never ever have absolute security.

    Just is not going to happen folks. 

     

    The client is not "ALWAYS" right

    On the same day that SeanDaniel.com talks about how to host two domains on one SBS, I get an email from someone asking if they can take a SBS 2000, connect a Win 2003 member server and install Exchange 2003 on that member server.

    Well.. you can do a lot of things..but the question is ....why? 

    The answer came back that the SBS 2000 was serving two companies and now they want one domain but two servers one for each company.  Can they use the SBS 2000 active directory and Exchange 2000?

    Sometimes while the customer is always right is the standard saying, the customer isn't always “bright“.  Call me a bit wacko, especially after I bought the “monster“ server that some question my sanity about, but I just can't see that this will add a great deal of anything other than complexity to a situation. 

    Two Exchange servers to lock down, two entry points into that network, and not to mention since they obviously can't purchase SBS 2003 for that second box, a lot of costs for not a lot of bang in my opinion. 

    Some folks ask this question for redundancy and I can see that more logically [but then I can point to the services like tzo.com that do backup MX records for mail and what not]

    I mean we can do a LOT of things in SBSland but we don't have to do EVERYTHING.  Sometimes the client doesn't always know best and it's up to you as the consultant to guide them.

    So.  Am I the wacko one?  Do you see a good reason for this setup and why it would make sense?  I think I'd rather find out from the client why they see this as a need.  I'm going to use a word I heard at SMBNation  “pain point“.  What is their pain point here and what is this going to solve?  I just see this as more complexity and not solving a problem, but maybe that's just me?

    What do you think?  What would you recommend?

    I'd rather they spend their money and upgrade the SBS 2000 to SBS 2003.

    Privacy and Good Business

    Lisa Traina gave a talk at the last AICPA Tech conf, the jist of it was 'privacy is good business'Steve Friedl posted this morning this lovely story about a research project that, while authorized, didn't handle their data in the best way possible.

    Ouch.  Big time ouch.  Man, what in the world that researcher doing with that detailed of information?

    My favorite is this section in the version on CNN: “The data, which included home addresses, telephone numbers and dates of birth, was being used at the state's authorization but without the consent of the individuals whose information was being used in the study.“ 

    Ouch.  And then SB1386 notifications big time.  This is why my laptop has a mounted virtual pgp.com drive that all my potentially senstitive data goes into.  Should anything happen to my laptop [which is my biggest risk areas] I will protect my client's data.

    So today I get asked if there is anything in HIPAA....

    So I'm on the phone today and get asked if there is anything in HIPAA that says that ISA server/SBS 2003 is not HIPAA compliant because it has two Network cards.

    Huh?  Say...whaaattt?  First off a bit of background,  HIPAA stands for the Health Insurance Portability and Accountabilty act which was signed into law in 1996 and part of that law includes protecton of ePHI ... electronic Protected Health Information.  Stuff you want to secure, you know?

    As part of the final rules that were released, it is purposely technology neutral. 

    As is discussed in this GIAC practical by Dan Aiken-- “Network Design – The Rule makes no explicit mention of network security principles such as resource separation, firewall placement and protection, and limiting visibility of traffic between systems.”

    The National Insititute of Standards and Technology has also produced a introductory resource guide for implementing the HIPAA Security rule.  At 96 pages I would argue it's probably a bit more than an introduction, but nonetheless, it too is silent as to the exact type of protection i.e. one network card or two.

    So we continue on the conversation and the gentlemen on the phone says that he recently lost out on an installation of SBS 2003 with ISA server because he thinks that another firm came in with a dash of FUD [fear...etc] and sold them how that they had to have a CISCO protecting their firm.  Meanwhile CISCO's source code has been stolen and it has a few vulnerabilities here and there per Secunia.  Meanwhile ISA Server 2004 has none in the same database, and ISA Server 2000, just a few.  Now, granted you can be totally freaked out by the number of services on our boxes, but the point is, it's not how many nics you have, what firewalls are in place, it's the entire network you have to look at. 

    Where's your weak spots?  That's where you need to be focusing your time and budget on.

    Counting network cards is not the way to more security.

    Just a heads up folks... There's no silver bullet that is going to make the bad guys all go away.  Staying on an up to date and patched platform is the best way to stay safe.  And with that... I'm firing up the Shavlik folks and getting my control thrill in for the evening!

    About that open source....

    So yesterday I ranted that I couldn't send out email to a couple of listserves and places and I thought it was because I was blacklisted because of my ISP.  Well, I was only half right.  I still am partially blacklisted, but that's not the reason why I couldn't send out email as I had been used to.  You see, I keep my office firm email separated from my outside email account that I've used on the web because I really don't want to pull in all the gunk that goes into that account. I've had my pacbell account so long that my V__gra emails get V__gra emails.....So I purposely use a different mail client to separate out the firm email from the “public email“.  Then, because I hang out in newsgroups and am not a fan of Outlook Express for newsgroups, I've always used some Netscape/Mozilla/Thunderbird derivative for newsgroup reading/posting. 

    So when my Thunderbird at home AND my Thunderbird at the office both started experiencing the annoying error that "supposedly" was fixed two or three versions ago per the Thunderbird support page, it sort of doesn't leave you too many options.

    <click here to see the error>

    Gartner's Talking Technology talks about when you make the decision to go with open source solutions to make sure you lock in the support.  In my case I just orphaned my old emails and left them behind in Thunderbird and moved over to Mozilla and using it just for email.  Not exactly the greatest answer, but when I attempted to build a new account for my pacbell and left the old one behind to keep my emails, I found that yesterday I couldn't email anything to anywhere.  I couldn't get Thunderbird fixed and had no “Mothership” to call for support.  I tried their web site but they indicated it was fixed a couple of builds ago.  I even tried totally removed the program and folders and then copied the folders back in.  No go.

    So I fixed it. Sort of.  I'm now on Mozilla and if I need to find an old email, I have to open up Thunderbird and go searching.  'Course I don't have my address book from the old Thunderbird so I'll now go in search of that... and while this is not the best solution, I don't have a phone number or product support personnel to call.

    My Dad called me at work last night and I had to help him send an email.  Technology is still just a bit too much for the geeky I think.  It needs to be more self monitoring and alerting of when something isn't right. 

    So far I have done this “fix“ before when I used Netscape and the mail client broke on me.  Happened with Thunderbird.  Hopefully Mozilla will hang in there for awhile.  Meanwhile my office email is on the Exchange server, backed up nightly.  I've added Lookout to Outlook to make searching easier because the native search was cumbersome and slow as compared to Thunderbird.  Now the Search is nice and speedy.  Outlook is also where my RSS feeds reside....everything over THERE just works....

    hmmm....go figure..... 

    Now if Outlook could just handle newsgroups....   [1]

     

    [1] even with the NNTP ability of Newsgator.. it's not the same...

    I am NOT a spammer!

    Let me just get this off my chest...

    • I'm not a spammer
    • I pay for a static IP at my office
    • It's the only DSL in town
    • Can I help it if Pacbell is SBC that joint ventures with Yahoo?

    I noticed it a couple of days ago when a business email that I was sending out bounced back as undeliverable saying that I was a “spammer”.  Today, I could not post messages to various listserves and locations from my Pacbell account through the office but I can here at home.  I think I know the reason why. 

    The good news I'm in good company with Dana, whom I was helping out the other day relaying email with his issue and it looks like my ISP's smtp server that the office system goes through has been SPEW'd, Dana was SORB'd but it's still a case of mistaken identity.  What's weird is the originating IP is 209.132.240.249?

    I'm going to have to do more digging to figure out if I'm reading and investigating this correctly, but it's just plain annoying these days when it's getting harder and harder to stop spam at the same time it's getting harder and harder to send email. 

    Message labs sent out a Monthly report that said:

    MessageLabs currently scans over 70 million emails per day on behalf of its clients.

    In September, MessageLabs scanned more than 1.45 billion emails worldwide for spam, of which over 1.05 billion or 72.14% (1 in 1.39), were stopped as spam (404.68 per second).

    During the same period, we also scanned over 1.78billion emails for viruses, Trojans and other malicious content, and more than 86 million or 4.83% (or 1 in 20.69) were intercepted (33.27 per second).*

    That's pretty bad when almost 3/4's of email traveling around the Internet is Spam.  I've been in a hotel room where I had to remote back to my office to send email because the mail server the hotel used was blacklisted.  I'll have to investigate more tomorrow.

    Bottom line to you folks that run Blacklists, Whitelists and what not... they are not working.

    If I had a dime for every time I told someone that hotfixes are a free call

    I think I've posted this again, but I'll say it again.....

    When you have a Knowledgebase article that indicates that there is a file to be obtained from Microsoft IT'S A FREE CALL. 

    Nada, zilch, zippo, zero cost.

    You call in the US 1-800-936-4900 or UK 0870 60 10 100 or the other phone numbers found at Microsoft Help and Support and it's a FREE CALL.  I think it's option 3 if I remember right.

    Call, state that you need a hotfix, they see if they can bundle it up and send it...and then they email a link to a place on on their servers to you with a password to unlock it.

    P.S.  To answer the question at the top... I think I'd at least have enough to buy a good dinner.

    Whoa Scoble.. you cut to the chase don't you?

    Scoble has an interesting posting today about a conversation he had on a plane where the passenger told him that Microsoft products “suck!”  So he invites folks to:

    So, I'm looking for more people who think our products or processes or services suck. Tell us why. Either here, or on your own blog. Just link here and I'll see it show up in PubSub or Feedster or on my referer log.

    Okay dude.  You asked for it.

    • SUS sucks.  It's been a year since Steve Ballmer stood at the Worldwide partner conference and told people that he'd be back in a year to ask them if they were running SUS 2.0.  They aren't.  It's not out.  A year since SBS was first released there is still not a automatic patch tool built into the SBS platform to help the consultant/owner keep their boxes patched.  Microsoft... just buy Shavlik or license them or something because you just shoved out 10 patches yesterday and several of them do not come down via Windows Update.  Fortunately the SBS team has built a page for downloads...but our latest ones that we need are not listed yet.
    • Licensing sucks.  In SBS land I don't NEED the same licensing that works for the big firms.  I don't NEED user versus device cals.  All that it does is make things more complicated.  My Software Assurance vendor even screwed up my SA renewal quote and I had to get the kindness of the folks from SoftwareOne to guide me through the process.  You are going to lose out to open source NOT on the basis of security, but on the complexity of licensing.  I as a customer should not have to track down the SKU code for Live Communication Server that I'm allowed to get as a SBS 2000 SA customer.  We shouldn't hear first that we are not licensed for Entourage for MAC and then I get in the mail from SA fulfillment a Entourage disk.  There's not a day goes by that someone doesn't complain about the complexities of licensing [heck even Directions on Microsoft say this and even Dan Appleman ] and yet you guys seem to be stuck in a quagmire.  I don't get it.  You got the Security stuff folks... fix the licensing now.  Kudos to Eric and the gang for getting us the SBS 2003 standard to premium/SA upgrade SKU because initially we only had a retail upgrade package. 
    • End of life sucks.  Okay there will be probably people that disagree with me on this but when you say end of life for Windows NT 4.0 server is December of this year.  Mean it.  Don't even think about extending that.  I'm getting tired of hearing “we're phasing this out“ and then right before it's the drop dead date, you decide that you have too many people still on that platform and you can't drop it.  Decide that up front or something because too many of us decide what we do based on what WagEd says you are going to do.

    So... Scoble asked.. answer him.  What do YOU think sucks?

    P.S.  Every person that I've shown my Acer Tablet Travelmate C110 to also goes ooooh... get those suckers out in the store where they CAN be seen!

    No, Thank You!

    On the Microsoft web site is a flash movie that says “Join us in celebrating the one year anniversary of SBS“ and it says at the end “Thank you for making SBS 2003 a continued success“

    No, Thank you.  Thank you, the people of Microsoft.  The ones that I personally know at Mothership Redmond.  Thanks to you, this Server was built with security and features that any business needs to thrive.  It's now safely in the hands of Motherships Charlotte, Las Colinas and Shanghai for the excellent support you give to Microsoft partners and owners.  Thanks to the folks I know there that even work during national holidays, weekends and late nights to provide support.

    Thank you to the Microsoft partners that have installed and supported this platform. It's not easy being in your shoes.  You are the Outsourced Chief Information Officer of that small company.  You help guide the technology decisions in the small firms you consult with.  You have a trusted relationship with that small business and you never forget that.  Sometimes your clientele come to you and say “whatever you say is best” and sometimes you have clientele that keep you on a budget. 

    Through it all you guide that small business.  You analyze their systems, guide them on what is best and recommend the technology that keeps them in business.

    Thank you to the Small Business Server 2003 customers.  You bought 262% more of SBS 2003 than SBS 2000. You are the one most to gain because you now have everything you need to be agile, productive, a global presence. What?  You think I”m joking? Read this.  You now have the power to compete globally.

    Oh and I'll say this again, if you install Small Business Server 2003 and are one of those Outsourced Chief Information Officers and are not signed up at least as a registered partner on the Microsoft partners web site, why not?

    Dana was on the ball wasn't he?

    Remember when Dana was looking to make SBS2003 into a “virtual office”?  I just spotted this article on that new RSS feed of mine about “Virtual Workplace Trend Changes Business”.  Interesting  I think Dana was spot on don't you?  I was blogging the other day that small businesses are way more agile than big business counterparts and Amy followed up on that thought.  What other industry can you make a decision and make an immediate change.  We're kind of like little tug boats down here.  Tiny and little but without us, big business couldn't get into the harbor.  My boss used to be part of a large national accounting firm and he purposely left it never wanting to go back to that model again.

    Hmmmm interesting links as well off of this site -- see what you think --

    http://www.radiantmarketing.biz/

    http://www.danavan.net/weblog/index.html

    http://www.sbblog.com/sbbloghome/

    http://www.wonderbranding.com/  I found this one interesting as they say that Women do a lot of the decision making

    http://www.ducttapemarketing.com/weblog.php

    http://www.entrepreneur.com/blog/0,6834,,00.html

    http://www.business-opportunities.biz/

    <sorry screwed up the link...fixed.

    Patch management tool comparisons

    http://www.winnetmag.com/Windows/Article/ArticleID/43870/43870.html

    In this month's IT pro there is a patch program comparison... now I can't talk about other products....but I can talk about the one I personally own and the chart says that Shavlik doesn't support uninstalls and rolling back patches but I've got 4.3.0.1 [Which according to my machine is the latest version] and there's patches that I can roll back....not that I want to go ripping patches off my production server mind you on a Friday night just to prove the author wrong... [I do have a BIT more of a life than that] but I do have the option to do it.  I have tested it at home though.  Also, I know that they patch ISA server and Linux as well.  So if those items are wrong, the best thing to do is do your own homework.

    Might want to do your own due diligence regarding this table.   But, it is a nice chart though of all the vendors in this space to get you started.

    Exchange Best Practices tool - what does is say about SBS?

    The Exchange Best practices tool and the corresponding update has been making the rounds in the SBS2k3 newsgroup and I wanted to showcase a couple of things.  First off the folks over on the EHLO blog have been VERY responsive to us SBSers and I'd like to thank them for what adjustments that they've already made to the tool.

    I just ran the tool, with the recent update on my XP workstation that then scanned my SBS 2003 box.  [now this does have the sp2 firewall on it so I might need to temp disable it and try this for grins again just to see if there is any change but it appears to work just fine]  You don't have to scan from your server, since the tool hooks into the active directory, it will find the server [and in the case of SBS, it doesn't have too far to look anyway].

    I did the test on mine and it only reported three issues that can be found here.  Here at home I'm “pop”in not SMTPing.

    From my XP workstation, looking at the server, I get no relay reports as some have reported.  Remember the conversations that have gone on in the newsgroups in the past that I will revisit.  SBS PM Charlie Anthe graciously allow Karen Christian to repost his response here.  A default SBS 2003 does not relay. LET ME SHOUT ...er say that again.  WE DON'T RELAY.

    We can get password cracked and be a SMTP auth attack victim.

    We can be an NDR relay attack victim.

    We can get stupid and enable the guest account and be relayed off of.

    But we are not, and never have been a relayer.

    Shut off those NDRs and all Virus notifications.  They are worthless.

    It's time to get involved World!

    Above this post is one of my favorite pictures of earth.  It's a picture done by NASA [time elasped of course] of the lights on all over the Earth.  You can see that on Jeff M and Anne's side of the East Coast of the USA that they are pretty well lit up.  But over there in Australia where Dean, Wayne, Mal and Henry are it's less populated.  But it's still a pretty amazing photo of how there are people all over the world.  Even now here at home when I'm just about to go to bed, my IM window is popping with fellow geeks on Instant Messenger waking up and starting their business days.

    So I“m sure you are wondering what sent me into this “waxing poetic“ blog post?  Well I went to a political fund raiser for a school board member in my city today and one of the things he said at the end was to get on our computers and send emails to get people involved in voting.  To tell people to get more involved in their communities. 

    Well, you know me.  I don't consider my community to be just the one in my home town, my community spans the world. My community is all of those lights down there in that photo.  And, in fact, I'll do one better than that.  I'll blog on the issue.  You there.  Yes YOU.  I'm talking to you world... I can see your lights on.  YOU need to be a better community member.  You need to look out for your fellow man [or woman].  You see that picture of US down there?  That's all we have of an inhabitable space.  For all of our technology, for all of our education, if we screw up what we have down here, we don't get a second chance.  So if you haven't voted, haven't joined in with your community whereever it is, haven't joined up with your neighbors in some event, haven't done SOMETHING to get involved, you are overdue.  Vote.  Volunteer.  Donate.  Reach out.  Mentor someone.  Move a little mountain in the way that only YOU can. 

    Nuel Brown was the gentlemen running for Fresno School board who challenged those in attendance to “Fix what was broken“.  That he needed the help of the community to build a bridge between the administration and teachers union to fulfil his wishes for the children.... you know me.... I'm seeing “community“ as the answer to a lot of things that ails us.  I was pinging a Security guy just today that “we“ the “community“ had to take the message of security to the masses.  Conversely, “we“ the community need to give better feedback to vendors. 

    See those lights down there in that photo?  That's us.  That's all of us.  That's people.  Think of the power we have if we just stop and realize that we are a community that CAN fix things together.  And we CAN.

    The picture also reminds me of the Pale Blue dot post by Carl Sagan.  You remember it don't you?  I've pointed to it in the newsgroups a couple of times.  My favorite part is the very end..... “There is perhaps no better demonstration of the folly of human conceits than this distant image of our tiny world. To me, it underscores our responsibility to deal more kindly with one another, and to preserve and cherish the pale blue dot, the only home we've ever known.

    Enough for tonight.  Thanks for the indulgence in the really off topic post.

    Just remember:

    Participate.  Be part of the community.

    I'm really bummed

    It just dawned on me that I did exactly what I didn't want to do.  First of October will be the anniversary of the official launch of SBS 2003.  And I still remember posting in the newsgroup when someone posted last year that they were thinking about waiting a year to roll out SBS 2003.  I said at that time ... no way, that I couldn't install it immediately last year in my office but that I wasn't going to wait a year.  It just hit me today that that's exactly what I've done due to a busy summer with traveling and other scheduling. So now it's definitely gotta go in because I want Windows 2003 at the office, I want the security feature of Enhanced IE lockdown.  The fact that when you give “everyone” rights to a folder that it's not like Windows 2000 and gives anonymous user rights.  And then I'm bummed because my workstations don't have the new Trend CSM suite that has the spyware protection.

    I just told a guy in the SBS newsgroup who was looking for SBS 4.5 cals to save his money and budget for an upgrade.  It just bugged me tonight that I was spending time upgrading two programs that I really want to get rid of so I can be on the SMB suite.  By the way, everyone is aware of the Trend competitive upgrade, right?

    I mean I love antiques and historical stuff, but not in technology, you know?

    Dear SBS OEM install

    There is one thing we hate about your install.  You put everything on one harddrive when best practices say to separate the OS from the Exchange to the SQL.  So what do my fellow SBS MVPs consultants do with that lovely 15 minute install?

    They take the information in the following whitepaper and move everything where it should be.

    Download details: Moving Data Folders for Windows Small Business Server 2003:
    http://www.microsoft.com/downloads/details.aspx?FamilyID=A1D0AF69-1287-4225-BD8B-59C89F44984B&displaylang=en

    Which basically takes that 15 minute install out of being a 15 minute install and makes it a much longer and much more annoying install.  They tend to take a RAID 1 or RAID5 and slam down the entire SBS install in the 12 gig partition.  As was said on a listserve  “Spend more time moving Exchange databases and user folders than is saved on the stupid thing.”  Too bad the vendors can't step up to the plate on that.  Seems like HP or IBM or Dell could poll and get a consensus, I mean like everyone knows to stick Exchange on another spindle along with SQL.  You certainly would never ever install the entire SBS 2003 on that initial partition.  That's just dumb.  And if they are selling this with and without partners installing it, you are going to get those DIY'ers into trouble real fast.  I also hear a lot of consultants flattening them and starting over so they can set it up their way.

    How is everyone else handling the “OEM setups”? 

    Tilting and Windmills and Ants and Rubbertrees

    I said to someone the other day that it's a good day when I can do a little “tilting at windmills”.  You know... an impossible dream that becomes a bit more possible.  In SBSland we get little windmills toppled over all the time... getting more respect for the platform... getting people to use the wizards....In Nick's SBS forum [you know the Naked MVP], there's a newbie SBSer who is looking at it for the first time since the 4.x days and is impressed.

    Like Yeah dude!

    Then there's the old time Bing Crosby song about “Ants and rubber trees and high hopes

    For anyone reading this blog I challenge you to do a bit of tilting and moving of Rubber Trees.  Contact a vendor about something that bothers you about their product.  [hint local admin rights come to mind]  Pick a small battle and send an email.

    Perhaps you might just want to send an email to a vendor that has responded or has stepped up to the bar to be aware and responding to small businesses.  Lately anyone asking any Software Assurance questions I've been sending over to Chris Miller at SoftwareOne because even though I didn't buy a single piece of software from their company, when I was struggling through my purchasing of Software assurance [and getting madder by the moment] the guys at SoftwareOne actually took the time to explain stuff to me even though I wasn't ever their customer.  [not to mention knowing what the right SKU code number for SBS is from the get-go is a major plus in my eyes].  So I challenge you to send a thank you email to a vendor who has supported your small biz space.

    For the record, they aren't putting me up to posting that.. this is a commercial free blog.... but when someone has embraced the SBS space in a big way, I'd just like to say “thank you to Chris“ and people like him.

    Hey ...what is this Vendor who likes SBS night?  Just got a post SMBnation email from Veritas about their SBS info.

    So what prompted this blog post?  You'll see.  I got a email today... a very interesting email that I forwarded on to Dana as well.  Stay tuned.  I think I might see a rubber tree scooting across the floor....

     

    Once upon a time....

    Once upon a time I had a SBS 4.0 box.  A consultant came in and installed this box and screwed it up.  Didn't know about the wizards, didn't understand the “tao of SBS” and I was a reasonable inquisitive person that went looking for answers.  Somehow I found the “family of SBS”.  The gentleman [and I do mean Gentle Man] who set the tone for the group was a Southern man who in time became a good friend.  I'd get all hot and bothered about a poster and he'd kindly say that we don't do things like that in SBS land.  He'd always make sure that we welcomed any question, any poster.  There was NO flaming in Grey's groups.  It just didn't happen.  And if you did [as I was apt to do a time or two] you went back in and apologized.  That's what you do when you are a SBSer.  You welcome people in.  You give them a hug.  We give SBS hugs out here. Every hug I gave out in Seattle at SMBnation came from what Grey taught me in SBS land.

    Wayne Small blogged about Grey as well in his blog today.  He said it made him feel better.  In my case, it's not.  I just had to go get some kleenix. 

    To Grey Lancaster.  ROCK of the SBS MVPs.  I want to give you another hug.  I think I missed a few in Seattle.  You will always be the head of this group.  The head of the table.  I hope that during this transition of the loss of you from being an integral part to leader in absentia I can do you proud.  Right now I'm losing mascara down my face.

    Right now I'm going to powder my nose as because right now its a bit red.  Grey wouldn't want me looking like that.

    [one more thing]  I thought I'd share the comment that Grey posted to the rest of us....

    It is a lot like raisng children, you just give them all the love and guidence that you can and hope they make you proud. I love you all, now go and make me proud.

    Happy SBS'ing
    Grey
    PS:
    If there is ever anything I can do for you, do not hesitate to call or write.
     
    From now on I'm going to try to do my best to make Grey proud.

    Alternative to SBS

    So Anthony sent me a link of an article about “alternative to SBS“.  I guess when they start writing about “alternatives“ that means the platform is successful?  There's a couple of things in the article that I question though..  First off the statement about IIS:

    “IIS is such a hack magnet that I refuse to install it unless an application absolutely requires it. From industry-standard Web server Apache to lightweights such as Abyss X1, there are many good alternatives. “

    Apparently the author subscribes to the Russ Cooper method of calculating IIS6 vulnerabilities or something?  II6 is hardly a hack magnet as it's barely had any vulnerabilities [unlike IIS 5] .  So unless the author is talking about SBS 2000, SBS 2003's IIS 6 is “very“ robust and has not had the issues of even Apache these days.

    Next, his “Exchange is overkill for my clients who just need reliable e-mail.“  Apparently his clients don't want to have sharing calendars and integration into Sharepoint?  Anyone who says Exchange is overkill hasn't set up a SBS 2003 Exchange box with the wizards.  It works.  How hard is that?

    Next “Only twice in three years I have had to touch a library's NetWare server“, guess that means that server is sitting there unpatched?  Do I need to point people in the direction of Rain Forest Puppy's BlackHat presentation on hacking into a Novell network and all the vulnerabilties?  Sorry but patching an operating system is good risk management.

    And  "The almost total lack of malicious code on non-Microsoft desktops is a powerful incentive to switch. Swapping out the whole operating system is traumatic for users but not much worse than the upheaval of transitioning older Windows clients to XP. I've managed to switch some clients to Mac OS X, which is easy to learn and supports native versions of familiar applications: PhotoShop, QuickBooks, FileMaker, Mozilla and Microsoft Office.“  I've been around OS X and sorry ... it's not as easy as everyone says it is.  Now maybe I'm an old tired, jaded geek, but it's just not.  It's eyecandy and all that but it's not as easy to move over applications to people that have been using Excel.  We migrated from Lotus to Excel and it took about 6 months before we really got back up to speed again.  As far as “the total lack of malicious code?“  Gee, what are all those vulnerability emails in my inbox.  And Mozilla and Opera and Firefox are just as targeted these days with browser scripting issues.

    Sorry but my SBS is not cluttered and as long as users control the desktops and you are not using group policy to control your users and we are doomed to repeat this.  And for the record I have too many business apps that won't run on Apple.

    As long as users have the rights to install “anything“ on their systems, we will always be insecure.

    Patching, Firewall and antivirus and we do just fine out here.   As I've said before, it's not my server, it's my desktops and end users that are my security issues and I can't get rid of them.

    Dear Mr. Schnell:

    Dear Scott Schnell:

    My name is Susan Bradley and I'm a Small Business Server owner.  I'm also very interested in security and protection of my clients' data on my system.  I have friends who work in industries that also need to protect data and have seen your RSA security keyfobs and am very interested in deploying them in my firm for two factor authentication.  There's one problem.  I don't need 25 of them.  As Dana Epp points out in his blog entry, you are forgetting that there's a marketplace down here for us little guys. 

    We have data just as critical as the big guys, just as sensitive.  Just because my firm likes to be a “boutique” sized firm, likes to stay small doesn't mean that I don't have security needs too.

    I want the added feature of a secondary authentication means as we know that Passwords are getting nailed and it's sometimes hard to get people to use passPHRASES.  So when you have your next quarterly sales forecast meeting, can I have you think about us small firms too?

    We're just as paranoid, just as needing security, just as protective.  Don't forget us down here.  And that goes for any vendor.  Belarc's inventory tool need to package themselves in a manner that they would allow consultants to legally use it.  My fellow SBS consultants have contacted Belarc and they blew them off. 

    I'm interested in Postini's mail spam filtering as they don't use RBLs and what not but instead use “reputational“ filtering.  That smtp connection starts suddenly flooding their servers with email messages and they know somethings up.  But they too only offer it via ISPs and larger companies.  So I have to find an ISV that will bundle this in rather than letting small firms sign up.  

    I understand economies of scale and all that, but call me blonde, I just think that firms that don't at least investigate ways to come into the Small business space are not fully investigating the growth potential down here.

    Guys, look around, there's a small business marketplace down here served by consultants and outsourced technical support folks.  Scale your products down and you can “play“ in this market. 

    Top things you CAN'T do with a SBS box

    While you can do a lot of things with a SBS box, there's some things you CAN'T DO with a SBS box... this post is going to be unusual for the “cup is half full” person that I am.....

    1.  You can't make the mail come in via the pop connector to be picked up any faster than 15 minutes.  First off, if I had a dime for every time I've answered that question, I'd have a piggy bank full of dimes.  I'm not saying I'd be rich enough to retire to the Cayman islands or anything like that, but I'd certainly have a LOT of dimes.  Why is this you ask?  Because of the email coming into the system.  If you could set it to pull in faster than 15 minutes you run the risk of overrunning the email still coming in and corrupting the mail.  While gfi.com and popbeamer.com can do it, I will tell you that any pop connector programs do get gunked up with malformed email every now and then and you have to go it an clear out the junk mail.

    2.  You can't do Terminial Server in application mode.  I'm hearing that there are vendors out there that are pushing SBS 2003 and not realizing that the system has been specifically tuned to realize that TS in app mode on a domain controller is just plain dumb and insecure.  Let me repeat that.  SBS 2003 does not do Terminal Server in application mode.  We do remote administration mode but NOT application mode.  You might as well let someone sit at your server and use it as a workstation and consider that a sane thing to do.  And for anyone who says “they can make it secure“, you are kidding yourself.  You “might“ have made it secure a few years ago when we didn't have the stupid cool web search and all those other IE hi-jackers and gunk we are chasing around now, but to take off that Enhanced IE lockdown [which is what you have to do to let anyone use Terminal Server in application mode on a “normal“ Windows 2003 server] means you are seriously lowering the security on your one, your main, your domain controller.  In the SBS FAQ page [and yes, we have a FAQ page that apparently NO ONE reads], they have the following statement:

    This is a change from Small Business Server 2000. Running Terminal Services in Application Server mode on a domain controller may present a security risk to your network.

    That's kinda like saying “driving down the road at 150 miles an hour may be unwise“.  Too bad the security folks couldn't write that paragraph versus the marketing folks.  The Security folks would be saying you “may“ be insane.

    Take for example, the recommended steps to lock down Terminal services on a server:

    1.  Apply the Notssid.inf security template to TS running permissions compatible with TS users.

    2.  Use the AppSec tool to limit which applications can be executed.

    3.  Do not enable remote control.

    4.  Do not enable application server mode on a domain controllers.   To connect to a terminal server from the network, users must have the Log On Locally user right assigned.  If you implement application server mode on a domain controller, nonadministrators must be assigned the Log On Locally user right at the domain controller.  Because this user right is typically assigned in Group Policy, it enables users to log on at the console of any domain controller in the domain, greatly reducing security.

    5.  Implement the strongest available form of encryption between the TS client and server

    6.  Choose the correct mode for your TS deployment [if you only needremote administration, the only deploy that]

    7.  Install the latest service pack and security updates.

     

    Don't want to do #1, nor #2, we want to keep #3 on our SBS boxes, and we clearly are in violation of #4.

     

    Page 393-394 of the Microsoft Security Resource Kit.

     

    Read this doc from the NSA and see how much is done to lock down a TS server..... we can't do this stuff in SBS land.

     

    3.  You can't argue with a vendor that won't support their application on your SBS box.  While my SBS buddies usually make snorting noises at such statements, there are times when a vendor just won't take the time or the energy to “validate” themselves on a SBS box.  And while many times you can put just about anything on a SBS box [I've yet to try my copy of Microsoft Bob on it yet, though] the consultant has to realize that it seriously jeopardizes technical support from that vendor.  Be aware of this and if a vendor won't go on record of supporting the application on a SBS box, make sure that you don't make your client a guinea pig.  Test first or don't recommend.  I'd much rather hear someone say “I don't know, let me research that” and then go off to the new Microsoft Small Business Community to check with their peers than say to a customer “Oh, yes it can do that!”

     

    4.  You can't do clustering on a SBS network.  One of the things that “big server land” does is redundant fallover like clustering and all that.  And while we can't do server clustering we should count ourselves lucky.  For one, every server dude that “does” do clustering swears “at” it and not “by” it.  It makes things complicated.  If there is one thing I've found with small business is the principle of KISS.  Keep It Simple Stupid.  And trust me, if we had clustering or fallover or any sort of level of redundancy that the big guys have, we wouldn't have KISS.  But you know one way that I ensure that I have I have a warm comfy feeling regarding my centrally stored data?  First off I make sure I buy reasonable hardware stuff.  Don't think that a desktop is truly server quality.  Have RAID [redundant array of inexpensive drives] set up so that if one dies, the other[s] keep going.  Have a tape or usb harddrive backup.  And if you want to be really paranoid, I have in my Dell workstation, a maxtor controller card with a second harddrive that at 12:45 p.m. does a robocopy as a scheduled task and pulls over the changed versions of the Excel and Word files, and anything else that has changed.  Yes it won't capture databases properly, but this is my “poor man's” shadow file copy. 

     

    5.  You can't reasonably backup ANY server to a dvd drive.  Another item that I'd love to get a dime for is the times that people ask “can I do a backup using the built in backup to a dvddrive?”.  I don't know about you but I've got WAY more than 4 gigs of data and gunk.  And given that I don't think you want to be at the office at say 11  p.m. at night changing blank dvd drives, thinking of this as an option is not wise.  Get a usb connected harddrive.

     

    6.  You wouldn't want to use the built in backup to do multi tape loader.  Personally I've found that when you get to the multi tape loaders you probably need a third party solution.  Veritas, Ultrabac....  For my SBS 2000 platform I even had to purchase a additional license to handle the multi-tape loader from Ultrabac.  Bottom line, if you can afford a multi tape loader, you can probably afford the third party backup software to go with it.

     

    7.  You wouldn't want to use the built in backup to backup the main server and a second server.  Like number 6 above, you are starting to cross the line of needing a third party backup.  Not to mention as Jeff Middleton pointed out, you start backing up that much data and you start having issues of doing a full backup each night and therefore you need a much more flexible backup program that can do multiple scheduling and what not.

     

    8.  You can't take the SQL or ISA off the main box and put them on a separate server.  No.  Our EULA specifically excludes us from taking either part of the Premium install of the SBS box and putting it on a separate server.  The other day I was finishing up spec'ing out our replacement server and knowing that I'd want SQL server and I like it to be a bit “overqualified for the job“, I was making sure that it was nice and beefy and Jeff said to me, “you know you don't have to stay with SBS if it won't fit you anymore and you need to put SQL on a separate box for your Line of Business Applications“.  But that's the thing.  My line of business applications don't use SQL server.  Down here in the size of firm that I am, we don't use SQL for the backend of our databases.  Thus, all I need SQL is for the Sharepoint installation.  So for me and my firm SBS still makes absolutely perfect sense.

     

    9.  You can't use SBS to be like an ISP and host web sites for clients.  No.  Again our EULA specifically excludes this.  Look in our specific SBS2k3 EULA:

    TITLE-> END-USER LICENSE AGREEMENT FOR MICROSOFT SOFTWARE
    SECTION 4-> Description of Other Rights and Limitations
    SUBSECTION k-> Reservation of Rigths

    “Renting, leasing, or lending the Software (including providing commercial hosting services) is also prohibited.“

    So what about your experiences?  When SBS “fits” its a really good fit.  And when it doesn't.  It doesn't.  But that's okay.

     

    I guess I should try to do an number 10 to finish this blog post out.... so what's the 10 things you “can't“ do with SBS?

     

    10.  You can't say something factually wrong about SBS without getting an email from me to that author wanting correction or clarification.  I have this wacko personality that I kinda consider this box and platform a bit of a “runt” that needs to be protected.  I've emailed Predator Watch that they were wrong in their analysis of security issues of SBS as they are scanning from inside the network, and then I blasted this poor author [actually sending them a SBS 2003 book because I feel bad about the mood I was in that day].  Bottom line, beat SBS up on the facts.  Yeah the platform has it's warts.  It's not perfect.  I wish that the ISA integration was better.  I wish that sometimes the answers to the issues were more readily apparent....I wish licensing was easier [just give me cals instead of device versus user and all that] and yeah, I wish we'd read the FAQs

    So what's the CEICW anyway?

    825763 - How to configure Internet access in Windows Small Business Server 2003:
    http://support.microsoft.com/default.aspx?kbid=825763

    CEICW... the wizard formerly known as ICW

    It stands for “Configure Email and Internet Connection wizard“.  It's your friend.  It helps you set up your email, your firewall, stuff to make your server nice and secure.  Andy has a great tutorial on this page  http://www.12c4pc.com/sbs2k3/sbs2k3-n2.htm  and I'd advise everyone who has a SBS box to run that wizard.  Always.  Absolutely.  Without fail.

    Remember how I said earlier that everything leaves behind an audit trail?  They are located at c:\program files\microsoft windows small business server\support\icw.txt

    Don't forget, they do the heavy lifting for you.

     

     


     

     

    I can so relate to this daily diary post.....

    I have as my home page the web site for Incidents.org as it normally gives me a heads up on issues that are occuring on the Internet.  Today's posting was about hardware issues.  I can SO relate to this posting.  Yesterday I had to “zap” my drives off my Adaptec RAID controller card and get them to be “refound” because I had to replace a hard drive.  I usually joke that if a woman built computers it wouldn't come with jumpers so tiny that you cuss when you drop them on the floor.  “We” would have put on/off switches or something really easy to find on the drives. 

    There are times I hate hardware.  When it works it's wonderful.  When it doesn't it's a pain in the you know what.  But all during the process of “zapping” off the harddrives I knew that I had backups.  That no matter what, even though it might be a pain, that I could get back to where I was before the issues started occuring.  In fact the guy at Adaptec first asked me “do you have a good backup that you know you can restore from”.  If the answer is yes, then you can confidently do ANYTHING to your hardware knowing that you can get your data back.

    FOLLOW THE WIZARDS! PLEASE!

    Okay I'm still in “recovery mode” from my run in with an ADAPTEC raid 5 and zapping drives [blog post on that next] so when Norman emailed me a link this this article it just really shot me over the edge.

    An article about Small Business Server.  Oh Cool. 

    http://searchwin2000.techtarget.com/tip/0,289483,sid1_gci1003317,00.html?track=NL-120&ad=490186

     Windows Small Business Server 2003 (or WSBS2K3 for short) is a version of Windows 2003 Server designed to run in small network environments where there are no other domains and no domain trusts. Only one WSBS2K3 server can exist in a domain, and it must be the domain controller and Active Directory repository. However, when SBS is installed, it isn't automatically promoted to the status of a domain controller and doesn't have Active Directory installed; the administrator has to do this manually. Learn how in this tip.

    NOT so Cool.  The instructions in the article tell you that you need to do to DCPROMO a SBS box.  Oh gawd. 

    And then he writes about it as “this is the way to install SBS” and this article can tell you how to dcpromo....

    NO NO NO.  We have an integrated install routine!

    555087 - Windows 2003 Small Business Server Shuts Down Unexpectedly; Events 1001, 1013 and 1014 are Logged:
    http://support.microsoft.com/default.aspx?scid=kb;en-us;555087

    Yo, dude.  Please!  Finish the integrated install.  Otherwise tell Charlie and the rest of the Microsoft team that work so hard on the wizards that we just don't need them anymore and send them home for a permanent vacation.

    I HATE articles like this that aren't clear that this isn't a fix, that the install was screwed up in the first place.  That whomever installed the SBS totally hasn't taken the time to understand what makes SBS so great.  IT'S THE WIZARDS.  They do all that gunk for you.  And like how could they have missed the integrated install anyway?  You leave the cdrom in there as it reboots and the SBS part starts up?

    We don't ever dcpromo in SBSland.  We let the box do all of that for us.  I've emailed this author to ask him to please take this article down and he's nicely going to adjust it to indicate that you need to finish the integrated install.

    Anyone just coming into the SBS space.  PLEASE.  Grab Harry's book or Jason's book.  LEARN what this little box can do and stop mucking it up.  FOLLOW THE WIZARDS.

    Last but not least, dude, we're SBS around here, not WSBS2k3.  Please folks, the wizards are there to HELP you.  Don't go around them, they are your friends, your helpers, your guides.

    I've been swapping a few emails with Serdar as a result and will be sending him a SBS 2003 book and he says that he meant it as a guide to help those who “don't” properly install the system.  He's already planning to change the article to let people know that the BEST way to recover from not installing the box the RIGHT way is to put disk one back in and let it do an integrated install as it was meant to do.

    You know how I said Dana was not the "normal" SBSer?

    So I'm reading Dana's blog and he's ranting that SBS doesn't allow ISA server to “work” unless there are two network cards on the server.  If you only have one server, as you run the wizard it won't set up ISA [or RRAS on the Standard SBS] to be a firewall and you must be dependent on an external hardware firewall.  I'll be the first to admit that I run at the office with two firewalls, my outside little non beefy, no where near like ISA Server, hardware firewall and THEN I run ISA server.  Why?  For one thing I like to have two walls, one to thin out the log files and then I want ISA server.  A firewall integrated with active directory, so much logging that it gives my auditor background happy, and on a platform that with a push button I can patch.  I can't do that with my hardware firewall.  And these days with the Secunia web site throwing out as many firewall vulnerabilities as operating system, the idea that the software on a hardware box is more secure is silly unless it's like as someone said the base of OpenBSD right after boot up when you have a command line prompt and nothing else.  We add on the cutesy wutsey GUI to make people like me happy and you start introducing vulnerabilities.

    The knowledge base article that talks about two network cards is here:

    825763 - How to configure Internet access in Windows Small Business Server 2003:    A two-network-adapter configuration connects one adapter to the local area network and connects the other to the Internet. A one-network adapter configuration connects a single network adapter to the local area network.

    Then in this KB it clearly states

    323387 - How To Connect Your Company to the Internet by Using an ISA Firewall with Windows Server 2003:
    Install the ISA Server

    To install an ISA firewall, you need a computer with two network adapters. You must connect one of these adapters to your internal network and the other adapter to your Internet service provider (ISP). Your ISP can help you make this connection. A firewall acts as a security barrier between your internal network (or intranet) and the Internet by preventing outside users on the Internet from gaining access to the confidential information on your intranet or your computer.

    Thus you need two network cards to enable the ISA firewall.  Dana responds to my comments that any firm that is doing a virtual firm would want this setup.  He may have a point, but I'll refer back to the first time Dana posted into the community newsgroup and was like “Dana Epp, THE security blogger Dana Epp? You aren't the normal “SBS“ customer“.  And beleive me, I mean that in the MOST complementary way.  Dana is not the normal SBSer and the wizards are built for the rest of the 99.99999999% of the marketplace.  SBS is flexible, but this is where the Enterprise folks say they don't like the wizards... because they force the “best“ practice or the “best“ balance.  As I've blogged before, the wizards leave behind an audit trail.  They do the heavy lifting for you.  They want to help you make the best choices.... like.... two network cards.

    Hmmmm... a virtual organization SBS network.  Interesting.... we are certainly doing more and more things “virtually“ rather than physically these days.  I know I've been collaborating with other folks from around the world and we certainly get a lot done without physically being in the same room.  I think I'll email Dana's blog post to some folks that just might be interested in that.

    ~Susan

    Dear Mr. Ellison: I think you forgot something?

    CRN is reporting that Oracle will be coming out with a competitor to the Microsoft Small Business Server platform.  Except that in their description of the program I think they forgot about email?  They just talk about the server, a web app server and a portal server?

    [update note] And it's not just that mail needs to be inside or outside the server, it's the whole integration package with the mail client on the desktop.  What mail client will Larry recommend?  Outlook Express?  [just kidding]

    Also Larry, if you don't also have the wizards of SBS, the “tao”, the “Yoda” of the box, you don't have what this market needs.  Wayne Small was attending the Australian Partner conference and reported that many partners there didn't know about the wizards.

    Jeff Middleton once again put it the best...

    “The IT Pro needs to be assured that the wizards are not there to dumb down the product as much as to get you into the game, at a documented and known point of installation where the true skill tasks are needed.

    Nobody takes a Windows CD and copies the files individually, then uses a remote machine to edit a clean registry to add the services and devices manually. We don't do that because there's no point.

     

    With SBS, bringing all those applications to a point of ready to use is only the start of the challenge that still requires significant skills.“

    FUD Factor part 3

    Microsoft has the following KB article out about XP sp2

    884130 - Programs that may behave differently in Windows XP Service Pack 2:
    http://support.microsoft.com/default.aspx?kbid=884130&product=windowsxpsp2

    And it says “The programs that are listed in this article may experience issues after you upgrade to Windows XP SP2. You may not notice some of these issues. Additionally, software vendors may have resolved some of these issues. Contact the software manufacturer or vendor for more specific details. ”

    Oh thanks, that's real descriptive.  Talk about FUD from Microsoft itself!  A couple of folks have pointed to the fact that includes Microsoft's own products in the list.  The only time I had “changes” to office products post sp2 was when I was on a web site and they prompted me to download Excel or Word differently where appropriate.  Otherwise let me state this again, that I've not noticed any of my applications working any differently.

    So stop listening to the newsreports, heck, stop listening to Microsoft themselves and YOU load it up and try it out.

    The Myths of SBS - "You can't do a second domain controller"

    Nick Whittome SBS MVP over on the Mark Minasi's web forum pointed out a Windows/Net magazine article where Michael Otey had followed up on his SBS article.  In it he says he's an SBSer himself.  But what caught my eye was the comment section where the first poster said that SBS could not have a second domain controller and thus it was bad from a redundancy, disaster recovery, issue.

    First off.... let's get one thing clear.  We CAN have a second domain controller and have since SBS 2000.  So that's our first myth.  Secondly... Exchange clustering?  Why the heck do I need Exchange clustering when I can just do a tzo.com mail MX backup record should anything occur.

    But guess what folks.... if you buy good stuff from the get go, monitor the health of it, plan on retiring it in an appropriate manner.... your risks are low.

    And uptime?  You must patch.  If you don't plan on some sort of “downtime“ for patching, you are running with more risk than I am.

    Ah I see Nick posted on there as well... let me copy it here:  Way to go Nick!

    SBS Supports more than one DC, but more to the point, its reliability is fantastic as long as the setup is done correctly. What I hear on a daily basis, is engineers who have been "moulded" to thinking enterprise and not small business who refuse to use the extremely powerful wizards that SBS uses. By ignoring these wizards, they kill the box.

    So, to put it bluntly, if you REALLY want to have a secondary server (which should not be necessary) then use Doubletake. It works well.

    This comment annoys me "SBS is both too capable and too complex". What a load of rubbish. I challenge you to visit any one of the SBS2003 implementations and ask our clients if they find it too complex, or to capable. I mean, how can something be too capable??? Our clients range from Garages (you know, those guys with grease on their hands), small primary schools & sites that did not even have a computer before. ALL of them can manage backups, add users, add printers, design their own sharepoint sites, run SUS, maintain antivirus... jeeze... the list goes on.

    It is about education. Teach the users how to run a SBS network, they can. Simple! This product IS ideal for small business.

    Them there are fightin' words there....

    On the EHLO blog today Nino says “is one of reasons why we do not necessarily encourage putting SQL and Exchange on the same server, as they will be fighting over whatever RAM is in the server.”  Uh oh... them there are fightin' words in SBSland.  See, in SBSland if you spec out your server [used to be 2 gig of RAM, now it's probably more like 2 or 4 gig of RAM] you can put Exchange and SQL and for that matter even ISA Server on the same server.  Yeah we make big servers folks go white as a sheet just thinking about what we do.  But you know what?  While everyone else is jumping on the bandwagon of Server Consolidation, we've been doing it for ages. 

    Off Topic -- Definition of "blog"

    Blog - as defined by Dictionary.com:

    Main Entry: weblog
    Function: noun
    Definition: a personal Web site that provides updated headlines and news articles of other sites that are of interest to the user, also may include journal entries, commentaries and recommendations compiled by the user; also written web log, Weblog; also called blog
    Usage: computing

    Blog as defined by me:

    Main Entry: weblog

    Definition:  a transparancy and accountability that occurs within an organization as they allow employees to talk with their own voice and not a corporate PR machine.  The platform can be on Radio Userland, Movable type, .Text based on .NET, but no matter what the platform, the corporation allows for human communication and connections to occur.

    So what brought about my definition of Blog?  My firm's CCH Tax Preparation program which has been “promising” the new worksheet version of their software since February.  Think Microsoft is the only one that promises and then slips dates?  Guess again, I was promised the new version in February, then in May, then in June, then in Mid July, then in late July, now it mid August. 

    And you know what really gets me?  Is that I've had to call to find out the slipping date each time.  Not once have they emailed me on the status of the software.  Not once have they proactively emailed or notified that the date of the shipment is being pushed back.  Not once have they done what I would call “basic” communication to keep me, their customer, in a sense “their employer” informed.

    It's called communication folks.  I think someone at CCH should start a blog and Vendors should stop taking us for granted.

    So if I don't have enough time to make the plane... how come my luggage did?

    Flying back from LAX and it reminds me that I need to get a small laptop for the “puddle jumper” planes.  I was working on a paper and you should have seen how I had to practically have the laptop in like a “V“ position in my lap to type without it being hit by the back of the seats in front of me. 

    I do find that I'm getting pretty good at finding power supply locations in airports.  This time I ensured that I had “full juice“ while sitting in the food court area in the corner.

    I was coming back from a quick weekend trip [went to visit friends and a baby shower] and had my friends drop me off at LAX hoping to fly standby for an earlier flight.  This is a trick us Fresno-ites do.  Show up at the airport a bit early and the chances are good you can catch an earlier flight.  Well tonight in front of me in the line I had the folks that locked their luggage and now were having a hard time getting it unlocked, the folks that were having a hard time taking the strap off, and by the time I got up to the counter, I was too late to make the earlier flight.  No biggie, I just hung out and used the cell phone for Internet access [geeze LAX ....even Fresno has wireless access throughout the terminal.. better get with it LAX.. right now it's only in certain areas].  So once I arrived in Fresno with the flight being on time, I went to pick up my luggage and about the fifth time watching the luggage carrousel, I thought to myself...hmmmm .... I bet my luggage made the earlier flight.

    Sure enough, it had indeed arrived on the earlier flight.  Now knowing that it didn't get checked in any earlier than I did, I find it fascinating that luggage can get sorted, searched and scanned faster than I can. 

    Hmmmmm .... wonder if we need a bit more technology in the human side of the airport.  ;-)

    ...and yeah... I know... I'm a geek...I travel with my laptop just about everywhere I go.  My two bags that I carry onboard are a backpack with hairdryer, makeup and my purse mooshed in there and my laptopbag with my laptop, wireless card, cell phone cable, and plastic keys leftover from hotels that I forget to turn them back in.  They also end up in my coat pockets as well.

    On the way down, my sister and I went by train, which is actually one of my favorite ways to travel to Los Angeles or San Francisco.  With 110 power connections next to the wall, plenty of room to spread out and do work while traveling, it's a very relaxing way to travel.  Not to mention great warm melted cheese filled soft pretzels hot out of the microwave to snack on the way... ooh.. shouldn't have typed that... getting hungry now.  ;-)

    So this post really didn't have anything to do with SBS other than to let you know that with either a Sierra aircard or, like I have, a cell phone, a data cable and a phone that can handle a data connection, there's very few times I can't be connected to my office.  Some may consider that a bad thing.. me.. I consider it a good thing.

    THIS HAS NOTHING TO DO WITH SBS

    I saw that they announced the name of the next Star Wars movie “Revenge of the Sith”.  Just putting everyone on notice now.  I will be in Newport Beach at the Big Newport movie theater with a bunch of my friends next May.  Oh and I should also warn you that I'm known for making folks that go with our group wear matching shirts.  This photo of me was taken in line at the Big Newport before Star Wars I and beleive it or not, someone else there brought that Yoda.  For the record I wasn't the only one who took my picture with him.  ;-)

    If you know me, you'll know that I quote Yoda when talking about the Small Business Server platform. 

    "Size matters not. Look at me. Judge me by my size, do you?"

    "Try not. Do. Or do not. There is no try."

    Personally, I think there's a little green guy inside every SBS box.

    [now back to your regularly scheduled SBS blog]
    P.S.  Click on the link for Multimedia on the Big Newport link to see some photos of the “tent city” that crops up before each Star Wars showing.  I'd also recommend that you try to watch it on an IMAX screen but NOT the domed one in San Jose... find a flat IMAX instead like the one in Las Vegas in the Luxor Hotel

    Everyone wanted to make sure I wasn't hyperventilating.....

    ...with Google being affected by the Mydoom virus.  Must have Google... can't live without google.... can't newsgroup without google.... can't GOOGLE without google!!

    While last weeks bagel was a real “stupid computer user” virus [like a normal paranoid computer user couldn't look at the bagel emails that had no body message, a stupid subject line and an attachment that SCREAMED “I'm a virus!  Stupid Computer User click here” and STILL click that attachment and get themselves infected, today's MyDoom was way more believable of an email.

    This Mydoom one of today was a lot more into social engineering.  I got an email this morning from my ISP that said my account had been sending out a lot of spam this weekend and that I'd better check my system with the attached file... yeah... right...I said... fat chance.  But it was still enough to trick possibly most not so paranoid folk.

    This is why proactively BLOCKING these attachments is key.  The virus companies were scrambling to get the dat files out.  Don't even let these files into your network, either using the SBS file attachment blocking wizard or using Trend [or your Antivirus] to block these.

    Also on a paranoid note...I was in Macy's tonight [a department store in my city] and I honestly do much of my shopping online and have not been in the store in a long time.  So it was pretty obvious that they were updating their database when they swiped in my Macy's card, asked to see my Driver's License [swiped it in], wanted my address, phone number.. and get this... asked me to enter my Social Security number on the sign-on-the-screen thingamabob.  As I entered in the Social Security number, the numbers were in plain view on the screen of the device that normally you just sign your name on. 

    Okay ... I think I'm getting paranoid because entering in the Social Security number freaked me out especially the fact that it was not even blocked on the screen while I was entering it.....I mean HIPAA rules are there to protect my privacy and electronic health information but what about my rights on my personal data.  I just gave Macy's and their IT department, my credit card number, my signature image, my address, my phone number AND my Social Security number.  I have no idea if their network system is patched, scanned, and if that transmission of my Social Security number is encrypted while in transmission...I assume it is... but I really don't know, do I?   Okay so maybe being a little too geeky and a little too paranoid is not a good thing?  ;-)  

    Upgrading to XP sp2 is going to be sooooo horrific....

    ...or so it seems to most of the Tech writers out there.  Well I know that I'm planning to have a traning session at the office once it releases to show people how to use the pop up windows stopper, add web sites to it, show how to web sites to trusted zones, but I'm sorry, these folks who consider things “difficult” should wake up and realize how “easy” it is these days for any browser to be gunked up with this stuff.

    Difficulties are in the eye of the beholder.  Is it difficult to put on a seatbelt? Was the first time we did it, now it's second nature.  In fact our cars remind us when we haven't put it on.

    I don't consider it "difficult" to do what I can to ensure that my client's personal and confidential data stays that way inside my firm.

    At home, I've got account numbers and other personal info on that system.  Again, call me stupid for wanting to ensure that browser hijacks don't occur anymore.  It's MY system, it's MY computer and I didn't give them the right to make THEIR search engine take the place of MY choice.

    Those spybots are breaking and entering into MY property.  XP sp2 is the bulldog that I just bought, the alarms for the door and the security lighting on the side.

    If folks only understood what was happening to their systems they be DEMANDING it, not considering it "difficult".

    The Power of Feedback

    SBS Release Manager Charles Anthe posts in his blog to “ feel free to post comments/questions if you like” and that “I'd like to think of this as an opportunity for dialogue with people who are interested in SBS “  The ability to add comments to the blog postings really do make it more of a tool for feedback than people may think. So I'd strongly recommend to folks that are SBSers to post on over to his blog and let him know what you like, what you don't like, what you'd like to see changed.

    You can also visit the Public newsgroups or the Yahoogroup groups to give feedback as well.  I have a really funky, funny story about feedback.  I had to do a quick trip over to Las Vegas Thursday night and flew through Phoenix on my way to Vegas.  My plane was a bit late getting there from Fresno so by the time I landed in Phoenix in the farthest gate on the B-terminal, I had to catch my next flight in the farthest gate in the A-terminal.  I didn't pack any luggage so I was carting along my laptop bag with my purse and a backpack with makeup and the bare minimum of change of clothes.  As I walked to the gate as fast as I could, I swear the laptop bag got heavier along the way.  Long story short I finally arrived just in the nick of time at the gate, they took my ticket and I was the last one to board the plane.  I'm strongly breathing [more like huffing and puffing] and walk to the back of the plane where my seat is.  Well of course, someone was sitting there so the stewardess directed me towards an empty seat in the back.  The stewardess helped me to find a empty upper bin to stash my backpack [and these bags are carryon sized people?  These are HUGE] and I stashed my laptop under my seat and sat down.  I sighed “I need to start exercising, I made it“ and the guy next said “Just relax now.”  Then the steward came to our row and said “Sir, may I talk to you back here?”.  Me and my sick sense of humor ... I jokingly said to him “Troublemaker, eh?”.  As he passed by me the fragrance of a little too much liquor made it a bit obvious that my joke was a bit in poor taste.

    The steward took him around the corner in the back of the plane and it was very obvious that he was very drunk.  He was asked what his final destination was and he said “Baltimore” [the final destination of the flight].  Fortunately he made no fuss when he was asked to leave the plane.

    So the point of this story?  Feedback.  The family in front of me alerted the cabin crew that the gentlemen was intoxicated and was swearing quietly.  The stewardess later came back and thanked the family and said that they sometimes don't “catch“ these types of issues until it's too late.  FAA regulations allow the airlines to remove problem passengers.  She thanked them for the feedback that they gave that made the flight safer.

    The power of feedback.  All of us have the power to do something similar out here.  Tell what we like, what we don't like, feedback. 

    It's a powerful thing.

     

    NEWSGROUPS

    http://www.microsoft.com/WindowsServer2003/sbs/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.windows.server.sbs

    LISTSERVES

    sbs2k-subscribe[at]yahoogroups.com - This listserve is for technical issues with SBS 2k3

    smallbizit-subscribe[at]yahoogroups.com - This listserve is for more marketing and business matters with SBS 2k3

    mscrm_smb[at]yahoogroups.com - This listserve is for the combo of CRM+SBS [Scott Colson ROCKS!]

    If I were in charge of the Universe.... part two:

    Yesterday I blogged about RSS and Exchange and at the end of the post I talked about how the 16 gig limit on Exchange should be lifted.  Today I'm adding on to my “in charge of the Universe” wish list.....

    One stop patch page for SBS.  A Super Windows Update that would let me know of every single patch both Security and non Security [QFEs] needed for my system.  Last October, Steve Ballmer talked about the new version of Software Update Service at the Worldwide Partner Conference and much to my dismay it's still not out yet.  Right now both SUS and MBSA aren't good enough, in my opinion.

    But even SUS and MBSA only do security patches.  How does the “average“ SBSer keep aware of the “rest“ of the SBS specific patches?

    Yes, I know that SBS has a page that tracks the QFEs, but that's not good enough in my opinion. That page should AT LEAST have RSS feeds on that to let me know when new stuff has come out.  I want RSS feeds of the Knowledge base articles that affect SBS 2003 [and while kbalertz.com does have this... honestly... it's not that good in tracking SBS KBs.  It will include stuff that I don't see how it's SBS related at all].  Yeah it's better than it was, but like the movie “Oliver“, I'm standing here with my empty bowl saying “I want more“.

    So I'll ask you... how do you stay up to date on Small Business Server?  Include your resources in the comments!

     

    Things I notice about Beancounters versus Geeks....

    Went to Continuing Education class today and the class was excellent.  It was a CPE course on auditing and I threw out some comments about fraud and Benford's Analysis which is a process whereby you can do data analysis on a series of numbers and you can spot fraud by numbers that fall “outside” the patterns.  Gosh, we beancounters need to work smarter and not harder and we soooo do not use technology like we should. Like how about automatic Benford law tests in accounting applications that would alert you to possible fraudulent activities?

    Anyway, I noticed something interesting at lunch.  Get a bunch of geeks together at lunch and gosh we practically can't shut up about the latest technology, geek toy, technology issue, bottom line geeks talk shop.  Get a bunch of beancounters together at lunch and the topics were... Baseball.  Pacbell Park.  San Diego.  We didn't “talk shop” at all.

    Just kinda an interesting observation......

    Microsoft isn't focused on Security.

    http://news.com.com/Ballmer%3A+Microsoft+needs+better+sales+pitch/2100-7343_3-5259001.html?tag=nefd.top 

    "We must also work to change a number of customer perceptions, including the views that older versions of Office and Windows are good enough, and that Microsoft is not sufficiently focused on security," Ballmer wrote in a wide-ranging memo to employees, a missive that has become something of an annual tradition as Microsoft starts its new fiscal year.

    Today in my blog comments Allen is complaining about how we can't do Terminal Server in application mode on our Domain Controllers wrote “ If anyone is using microsoft products they are not concerned about security anyway.“ 

    Oh, Allen.  Look at the changes that have been made in Windows 2003, in XP sp2.  Look at what we can do with EXISTING settings to harden a server or workstation.  Check out the guidance at www.cisecurity.org.  We have all the ways to secure ourselves now and we don't do it.  I love to use the movie “A Few Good Men” with Tom Cruise and Jack Nicholson as an analogy.  Imagine Jack growling to Tom “You can't handle security!”.  Well we can't handle security.

    Stop blaming our issues on Microsoft when WE have the power already to be secure.  No operating system in the world as long as they allow human interaction with it will be secure. 

    We're living in the “hood” in the Internet and we're not taking the necessary steps that we would do in real life. 

    Office 2003 has been wonderful for saving files when I've accidentally blasted off the program.  It's been wonderful for saving backups for me.  The redesigned Outlook is easier to track projects.  And yet folks still say “I can't see any compelling reason to upgrade”. 

    I think we aren't looking hard enough.  Granted, Microsoft needs to do a better job of telling me [besides the stupid Great Moments in Office ads], but there are many advantages I have on the versions that I didn't have before. 

    And better security is just one of the advantages. 

    So Thomas is trying to find documentation about adding a second server in the KBs.....

    ...and he's not finding anything......

    ....because it's not in a KB.  It's in a whitepaper! 

    SBS 2000 ~

    Microsoft TechNet: Adding a Server to Your Existing Small Business Server 2000 Network:
    http://www.microsoft.com/technet/prodtechnol/sbs/2000/maintain/addsrvrs.mspx

    SBS2k3 ~

    Download details: Deploying Windows Server 2003 Terminal Server to Host User Desktops in a Windows Small Business Server 2003 Environment:
    http://www.microsoft.com/downloads/details.aspx?FamilyID=0A06E845-57EF-43EB-802F-F274FD937400&displaylang=en

    The moral of this story is YES you can add a second server, a member server, a backup domain controller [remind me to blog on the “Myths of SBS by the way”] and here is the exact instructions on how to do it.

    The myth belief in the public is that SBS can only have one domain controller and thus it's a platform “prone to failure”.  Poppycock! Rubbish! Steve Foster [SBS bud] would say.  First off, knock wood, I've never had an issue only having one Primary domain controller, and two, if you want a backup domain controller, stick one on there dude!  There's nothing stopping you!

    Just remember that while you can log in, your email is still down.  Also remember that unless you have disabled cached credentials, you can get on that profile even if the network is offline.  It will find the network once it finally comes back.

    Don't panic when you read that the SBS platform only has one domain controller.  That SHOULD read one “PRIMARY“ domain controller.

     

    Gee Mom? Do I have to use the wizards?

    You can always tell when an Enterprise person comes into SBSland.  The first thing they want to know “Do you have to use the wizards in Small Business Server?”  Well.  No.  If you really want to to do it manually... you could... but why in the world would you?

    So I “could“ manually set up the firewall settings, and I “could“ setup the Exchange domain name, and I “could“ set up the SMTP virtual server settings and I could do the necessary settings for socket pooling and I could ....... but why?  When all I have to do is utilize the wizards inside of SBS?

    Les [poet of the SBS group tonight] gave a great analogy...

    It's like being offered a ride to the place you want to go, but not knowing
    what that place is or how to get there, saying "Oh no, I'll wander around
    and hope I find it instead."

    Accepting that ride requires you trust the driver. We're giving the driver a
    good recommendation, you can trust him/her/it.

    Take the ride. Learn the route in the process, and then should you decide to
    instead take the walk sometime, you'll be able to do it.

    If you are an Enterprise kind of person just picking up the Small Business Server platform, leave your Enterprise learning at the door.  Welcome.  You are in SBS Land now.  We do things with a little bit of trust and pixie dust around here.  Oh and a whole lot of scripts and wizards too  :-)

    Threat Modeling in the SBS World

    So Michael Howard is posting about “Threat Modeling”, and while I'm not a coder or a scripter [heck I can barely run SQL queries worth a darn], I must say that I enjoyed the first part of the Howard/LeBlanc book “Writing Secure Code, Second Edition”.  The concepts threat modeling and DREAD and STRIDE and threat modeling can be applied in a weird wacko way also to “setting up a network” as well as writing code.

    I've even ordered the book “Threat Modeling” and I'm not a coder.  So why am I so into “threat modeling” from a SBS network admin standpoint?  Because I totally think we are looking in the wrong directions at our threats in SBSLand.  We spend so much time worrying about what our boxes look like from the “outside” from a Penetration Testing point of view, in the meantime our staff are downloading smily faces for their email and getting spybots and ad gunk trojans in their machines.  Right now our biggest threat of “Tampering with data” is due to “Elevation of Privilege” issues.  But here's the rub... it's not really “elevation” of privileges... we give our end users too much rights and privileges to their own machines all the time. 

    Think about our little networks shall we, in terms of “entry points“? 

    Entry points.... in my network, that's email, remote connections and the like.  I don't open up port 80 or port 443 for web site hosting, but every day I accept gladly all sorts of fun stuff via email.  I've purposely opened the port.  Time and time again we get asked in the newsgroup, I want to run a port scan on my server, and while that is a valid thing to do, I don't think “pen” testing a SBS box is a valid exercise if I can walk by the Secretary's desk and her password is on a sticky note [it's really not in my office, I'm just making a point].

    Your network security is not only your server.  Your threat model needs to encompass the workstations as well.  Your weakest link is not your Server.  Your weakest link it out there surfing the Internet looking for emoticons to download.

     

    Once upon a time.... in a galaxy far far away...

    ...many years ago when I was in college, the powers that be thought that Accounting graduates needed to learn computers [which we did] so they had us take COBOL and BASIC courses.  Our first COBOL project was even on IBM punchcards just to torture us as you had to ensure that you typed each card perfectly.  After than we moved to dumb terminals and used Xedit to write the code.  While I cannot remember a THING from COBOL, other than leftover IBM punchcards make great grocery list notepads, the use of Xedit led into Edlin that I used extensively during those early IBM 8088 DOS days at the office. 

    These days, other than running a vbs or bat file every now and then, most of my “coding“ experience is stricly GUI with a MSI installer.  So the procedure of upgrading the .TEXT blog from .94 to .95 took me back to those days gone by of COBOL and BASIC.  We're still working through a couple of items [like I broke the main RSS feed somehow], but it's shaping up.  I've used the SQL enterprise manager before to add new bloggers to the database, but this is the first time I used the SQL query tool.  You guys that are scripters/coders would be rolling over on the floor laughing your heads off as to what I did.  Scott W in his instructions said to do one part of the upgrade “line by line“.  Well I took him quite literally.  So there I was last night, cutting and pasting one line at a time into the SQL query and running the script to extend the database for the new “parts“.  I got to this one section and the script was failing, so I googled and realized that Scott meant for us “blondes“, not “line by line“ but section by section or script part by script part.  Yup, I upgraded the style sheet section... one...line.....at....a....time.  When I could have just taken the script section and put the whole thing into the SQL query and ran that.

    Bottom line, this experience reminds me that I'm very lucky to live in SBSland.  Most of the “nasty“ scripting is done for me.  Heck, even the installation routine is automatic.  Which means I can get to the fun stuff that much faster.  To the dev folk up in Richmond... a big thank you.

    Well I'm off to post comments to Scott's WIKI on the .TEXT blog upgrade experience... mainly to let them know that “line by line“ means something totally different to us folks out here who having coded or scripted since .... well lets just say it's been a long time  :-)

     

     

    ... I couldn't agree more Robert....

    Robert named dropped “SBS” in his discussion on marketing at Microsoft and how they need to do a better job.  He says [and I agree] that there's no good marketing done of a tablet PC.  Heck, David Cieslak of ITGUSA.com has probably single handedly sold more Tablet PCs because he has one and uses it when he goes around California giving Technology courses.  Robert talks about naming two products that are marketing successes and he names One Note and SBS.    I think [I hope?]  he means that SBS has been a success, but I too believe that the marketing of it could be better.  I don't think the power of SBS is showcased enough to the very partners that are selling it.  Wayne talked about this the other day.  The power of mobility isn't being showcased.  Sharepoint isn't showcased.  Heck, I don't know Sharepoint well enough [it's my goal this summer to know it better]

    Then, I personally don't like the ads that are “canned” and ready to go for the Microsoft partners.  I call it the “angry boss, female secretary” images because that's to me, what it shows.  A woman in a sweater, an angry man.  An orange juice can as a pencil holder?  Tacky.  If you are not a partner, you can click here to see a little bit of what I mean.  See the first picture in that “guide for small business security“?  Even in that photo on the front page the owner is more friendly looking.  The advertisement that I just LOVE... is the “Build your Business” ad.  This ad, I think would be a killer SBS ad.  I love this ad.  I swear I have to get the kleenix box out each time I watch that ad.  To me it totally showcases exactly what the Small Business Server is all about... it's a business in a box.  Add the human parts and stand back and watch that business grow.  But businesses won't know of the power unless they see it.

    Boy this is SBS nite on Robert's blog or what?  SBS runs the business side of the church that he visited in Dallas.  19,000 congregation church run by a SBS box.  Excuse me... I need another kleenix...   ;-)

     

    Okay this has nothing to do with SBS.....

    Today we had Ice Cream [old family recipe], which means this is the start of Summertime in California.....and I just looked at Weather.com and yup, we're definitely going to get hot next week.

    6 eggs [I now use eggbeaters since this is a non cooked ice cream recipe]

    2 cans of evaporated milk

    2 cans of sweetened condensed milk

    2 tablespoons of Vanilla along with scrapings of vanilla beans

    1 teaspoon of orange extract [can also be lemon extract or even better Grand Marnier liqueor

    Mix and pour into a 4 or 5 quart ice cream container, fill remaining space with whole milk, half and half, and some cream in whatever proportions to your taste

    Load up in the electric or hand crank ice cream maker, cover with ice, enough rock salt to melt the ice and about 45 minutes later... voila.  So good, you don't even need chocolate syrup

    Now back to our regularly scheduled SBS blog....  ;-)

    Terminal Server in Application mode - why can't SBS 2003 do it?

    In the newsgroups today, a person updated his SBS 2000 and was prompted that the TS in application mode would be removed during the upgrade.  He went through the upgrade and then posted back in the newsgroups asking how to turn on Application mode again.......

    Well... it can't be turned back on again..... and we should not have been allowed to do it in the first place. 

    Let's determine why shall we?

    Okay first and foremost, would you agree that allowing your employees to sit at your server and use it as a workstation is a good idea?  Probably not right?  Well that's what you are doing when you do TS in application mode.  You are allowing people to log onto that server, use possibly “leaky“ applications that may require you to reboot the server, and in general, expanding greatly the threat vectors on that server.

    Take for example - Internet Explorer.  You have to remove the Enhanced IE security [go into add/remove programs to remove this on a normal server].  Michael Howard [MS Security dude] talks about the threat modeling that they did on Windows 2003 server.  Near the end of the project they did a “threat model“ brainstorm and asked themselves what was a potential issue....and the threat that came back was surfing on that domain controller.  So the Security folks pushed through that Enhanced IE [you know that box that prompts you the web site you are wanting to go to is not in a trusted zone?].  Andrew Duthie talks about the settings on his blog.

    Right now my security issues are the spybots and gunk that are going after Internet Explorer.  Just last night in talking “geek“ with my friends from LA that were up for a visit, Pierre talked about having to track down a browser hijack program [He wanted  to do it manually, but he could have used the CWshredder tool].  Now ask yourself, do you want to do that on your one and only domain controller?  Think of what you do to clean up your separate desktops. 

    So the next time someone says “But it's dumb, I want my TS in application mode back!“ remember that we can't do things the way we used to.  That was then, this is now. 

    Now, there is one way that this can be better.  Documentation and information. 

    In one of the listserves I'm on we were chatting about the lack of documentation on this issue [and I'd add the lack of documentation of WHY we shouldn't do it]  Now granted, we women would argue that guys don't read, but I do agree with my fellow listmates that the information about the lack of TS in application mode should be WAY more obvious.  The information of how it is no longer supported or included and why it's not safe and secure to have it there in the first place needs to be way way more obvious.  In fact it should be part of the sales and marketing stuff because to me, it shows better than anything else that Microsoft is indeed “walking the walk, talking the talk“.  We asked them to make the products more secure.  They responded.  This should be a selling point that they are making it more secure, not a “What happened to TS?“ question in the newsgroup.

    Documents that discuss TS in application mode removed .....

    This KB   and read Page 44 in this document

    Anne Stanton of the Norwich Group talks about the "little things"

    http://thenorwichgroup.blogs.com/fieldnotes/#a0001397448 and her post reminds me of the number of times that I have to clean up my Sister's customized Disney desktop when I'm doing my beta testing and beta builds.  Mess with her desktop icons and she's not a happy camper.

    Anne's post should remind us that sometimes it is the little things that do make an installation and consulting project 'special'. 

    Which reminds me...she sent me a cool card the other day thanking “me” for presenting with her on the topic of Collaboration at the AICPA Tech 2004 Conference [for which we used Wayne Small's SBS 2003 site in Sydney Australia to really show how there we were collaborating with the information being on a server 1/2 way around the world].  I need to thank HER because I had a blast presenting with her.

    Did I ever tell you the story of Jeff Middleton and his SBS server?  Jeff and his wife take a much needed vacation from the Panama Canal area to New Orleans by cruise ship.  On board, satellite connection, vpn ports blocked, yadda yadda and needs to do maintenance on his Exchange server... dials up, remote web workplace using Wayne's SBS 2003 site [which goes over port 443], then opens up a VPN to his server back in New Orleans and does what he needs to do.  Ship to satellite to Sydney Australia back to New Orleans.

    Lufthansa just started offering Wi-fi on their airplanes.  Big things.  But big things start with the little things... and little touches.  Like Anne's thank you note to me. 

    Note to self... ping Anne and say thanks for that note!  :-)

    It's hard sometimes being a person who likes Microsoft products.....

    I just got back from the AICPA [the American Institute of Certified Public Accountants] Technology Conference [don't laugh - us beancounters are geeks too] and on the last day, the keynoter who's the Industry guru said that Microsoft was up to it's old tricks again.

    The keynoter referred to 2 issues that demonstrated that Microsoft was back to being big bad Microsoft.

    The first issue that he referred to was the Real Networks lawsuit against Microsoft.  What I find interesting about this comparison is the fact that Click and Clack from Car Talk dropped Real Networks because of the actions they've done to dupe listeners into buying the premium service.  So exactly who doesn't do business in a straightforward manner?  Microsoft or Real Networks?

    Next the keynoter referred to Microsoft's actions at the PDC and other venues to build the buzz around Longhorn. Arguing that the way in which Microsoft is handling Longhorn and the buzz around it proves that Microsoft has not changed it's spots.

    I agree with Joe Wilcox that the hype over Longhorn was a bit much, but I'm not a developer or coder, so I'm not sure I'm the right person to judge.  I saw some presentations on it and I'm always more interested in the product I've got now, the tangible product, not the product in the future.  Conversely though, I know that to get the security embedded into a product, into a world where we've traditionally featured functions over security, we need to ensure that developers know of foundational changes early on.  I think Scoble said in his blog something like Microsoft wouldn't be where it is today without developers.  Especially now with interoperability of applications, developers need to know early on what changes to come down the pipe.  Joe Wilcox in the Microsoft monitor has a two part article about the product roadmap talked about by Jim Allchin and WinHEC.  In part one, he says that Microsoft has to build credibility, and in part two he talks about how features are whittled down by Dev while Marketing hypes those very same features.  I tend to agree with his arguments.  Sometimes I describe marketing as “the dark side“.  That's one cool thing about blogs.  It's human voices not press releases.  A bit more honesty and accountability rather than “spin“.

    But here's the sad part about this conference.  While the Keynoter is beating up on Microsoft, the application vendors represented at the conference are the ones he should have been beating up on as well as the attendees.  In a room full of attendees where I was presenting I asked people who represented CPA firms if they had patch managment programs in place to ensure that all the computers in their office were patched at a moments notice.  Very [and I do mean very] few hands went up.  Next, many of my line of business applications say in black and white that they need either local administrator rights or power user rights in order to operate properly.  Bottom line that's elevated rights and permissions inside a program that probably hasn't been updated since Windows 95 era.  It's not my operating system making me insecure, it's my applications.  That's not right.   

    So here's this keynoter saying that Microsoft is up to it's old tricks and I'm in the audience wondering if I'm the one who is wearing “rosy colored glasses“ or if it's just easy to take pot shots at a big company?

    So let's review at least one way that Microsoft is not “up to it's old tricks“ in my view:  Let's see first up we have something that floored a lot of people... On the Ehlo blog they pointed to the generating the custom mailbox limit message in Exchange and released the source code.  Oh heavens.... Microsoft releasing source code?  World coming to an end, for sure!

    I also see the Microsoft folks that I've come in contact with that work hard.  Trustworthy as individuals to use an overused word.  And before you throw out the argument that Microsoft is a corporation with shareholders who want profits, need I remind you that most business enterprises are not exactly not-for-profits?  Furthermore, show me a not-for-profit company and chances are the director of that not-for-profit isn't doing that job without pay. 

    Like I said.  It's hard being a person who likes monoculture.  Nice, controllable, patchable, monoculture.  Sorry, but I'll take controllable monoculture for now and keep my machines nice and patched.

    Just a reminder, next Tuesday is patch day when the Security bulletins are slated to be released.  A lot of people didn't know that fact either.

    So why are vendors not responding....

    So I'm here at the AICPA Tech 2004 Conference and mingling with folk tonight and in discussions we talk about how it's our applications that are making us insecure and not Microsoft.

    When people around the room all agree that it's dumb for CCH's Epace software to require local administrator access... why are we accepting this?

    First rule of thumb is to reduce the privilege, the rights, the access.  Why are we accepting this as the right thing for our applications to need?

    Collaboration thoughts .... and other stuff

    “The best leaders are very often the best listeners.  They have an open mind.  They are not interested in having their own way but in finding the best way“ - Wilfred Peterson

    I saw this on an email and like the saying.  It reminds me of the true story my Sister told me the other day.  She was in a leadership class and two groups were organized to perform a task.  One was a group with traditional leadership style.... Managers at the top with clear definition of authority,  and the person at the top was a traditonal manager.  The other group was made up of a non-traditional leadership style and the person in charge normally was the public relations person for a department.  One the Chief, One a People person.  One group very obviously the “traditional” pyramid style, the other the “non-traditional” collaboration style.

    Their job?  To put together two matching lego toys.  The instructor gave this lego toy to each group and timed how long it took for each group to put together the toy.  My sister was in the collaboration group and she said that the Leader in her group put the box on the middle of the table and instructed the group that they had to put the toy together and they were being timed on it.  Her group immediately started opening the box, one person looking at the instructions, another sorting the blocks.  One person said “My kids do this all the time and you just follow the pictures”.  Every now and then her group's leader would pipe up and provide a bit of guidance or  advice.  They soon put the Lego toy together and announced to the Instructor that they were done.

    They looked across to the “traditional leadership” group.  And there across the room, their Lego box was barely opened, the leader still reading the instructions.  The toy was a long way from being complete.

    My Sister's leader “empowered” her members to take an active role and to collaborate on the project.  They identified the areas that they were able to excel in and quickly and without issues divided up duties.  The traditional leader controlled the project.  Duties were not divided.  Individuals did not identify their strengths and take part in the project.  They were waiting for their leader to hand them a role and nothing happened.

    The moral to this story?  Empower people.  You might be surprised what can happen!

    Accurate Accounting

    I really enjoy following the blog of Joe Wilcox of Jupermedia.  Today's post was about the credibility of the number of security patches as reported by Microsoft.  In his blog entry, Joe went into a bit more detail as to what methodology he used to count his number of patches and when I got to this part..... “The list of security alerts is here, for anyone that would like to do a count. I count 15 alerts, including one for Small Business Server 2003, which is at the core is Windows Server 2003. “ When I read that part, I knew he had counted at least one security bulletin wrong.

    Security bulletin 04-001 caught my eye as well when it first came out because it specifically DOES list Small Business Server 2003 and anytime SBS and security bulletin are in the same sentence my alarm bells go off. 

    Now maybe it's just an indication of how sick I am, but I know for a fact without even checking the website that 04-001 is actually an ISA server patch.  If they ever come out with a Security bulletin version of Trivial Pursuit, I am going to kick some ...... well you know.  03-026 - msblast.  03-029 caused RRAS issues in SBS 4.5 the first time out.  04-002 - first Exchange 2k3.  04-001 may mention SBS but that one's ISA. 

    But I don't think the ISA server folks would label 04-001 as a Windows server patch, nor would I think that the Server folks would label it as one as well.  Futhermore, if you knew SBS 2003, you would know that 04-001 only truly affects SBS 2k3 Premium [not standard] and even on the Premium platform, since most of us SBSers never used the H323 stuff in the first place, they turned it off until we do need it.  Thus if you wanted to get technical about it, we aren't really vulnerable for 04-001 in the first place. 

    So if I were Joe, I wouldn't be including 04-001 in any count of a Windows Server patch.  In fact, Joe might be wise to use instead an external third party site that is an industry trusted site for information on security bulletins be used to put this arguement once an for all to rest.  Why doesn't both Jupiter Media and Microsoft have Eric Schultze declare the true count?  And then both of them can stop with the “spinning” and get back to Microsoft making it easier to patch. 

    Me being...well me... I emailed Joe and pointed this out. 

    In the meantime, we have come a long way, but we have a long way to go.  Not too long ago you couldn't put Software Update Services on a domain controller.  Now we've got a specific SBS “how to“ whitepaper. 

    As for straight talk on patches, I'll go with Eric Schultze/Shavlik's database of Windows Server 2003 patches.

    I count 12.

    Description Date
    MS04-007 :  ASN.1 Vulnerability Could Allow Code Execution (828028) 2004/02/10
    MS04-006 :  Vulnerability in the Windows Internet Naming Service (WINS) Could Allow Code Execution (830352) 2004/02/10
    MS03-045 :  Buffer Overrun in the ListBox and in the ComboBox Control Could Allow Code Execution (824141) 2003/10/15
    MS03-044 :  Buffer Overrun in Windows Help and Support Center Could Lead to System Compromise (825119) 2003/10/15
    MS03-043 :  Buffer Overrun in Messenger Service Could Allow Code Execution (828035) 2003/10/15
    MS03-041 :  Vulnerability in Authenticode Verification Could Allow Remote Code Execution (823182) 2003/10/15
    MS03-039 :  Buffer Overrun In RPCSS Service Could Allow Code Execution (824146) 2003/09/10
    MS03-037 :  Flaw in Visual Basic for Applications Could Allow Arbitrary Code execution (822715) 2003/09/03
    MS03-034 :  Flaw in NetBIOS Could Lead to Information Disclosure (824105) 2003/09/03
    MS03-030 :  MS03-030 : Unchecked Buffer in DirectX Could Enable System Compromise (819696) 2003/07/23
    MS03-026 :  Buffer Overrun In RPC Interface Could Allow Code Execution (823980) 2003/07/16
    MS03-023 :  Buffer Overrun In HTML Converter Could Allow Code Execution (823559) 2003/07/09

    Dear Mr. Bill Landefeld:

    Based on my googling, you are the person in charge of Software Assurance at Microsoft.  I've been seeing the newsstories today that people are upset about paying for SA on SQL server and then due to slip dates of Yukon and Whidbey, their Software Assurance deals they signed may not be the great deals they thought they would be

    I have another problem. I'm a Small Business Server 2000 Software Assurance customer who doesn't exactly know what I get as a software assurance customer.  I have the upgrade to SBS2000, the SBS2003 software, but there are conflicting reports whether I also have rights to get the Live Communication Server product.  You see, Exchange 2000 SA customers do get the replacement upgrade to the internal instant messenging component that used to be included in Exchange 2000.  But I'm not an Exchange SA customer, I'm a SBS customer that has inside of it Exchange 2000.  If I call US SA licensing , they say I am, if you call UK SA licensing, they tell my fellow SBSers over there they are not.  But SA is “supposed“ to be universal and I've yet to hear back which is right.

    Now we hear that Exchange 2003 SA customers look like they are on track to get additional spam filters when they are released for the Exchange platform later on.  I've asked MS folks whether or not SBS 2k3 [which has Exchange 2k3 underneath] whether or not we are eligible.  I've yet to hear back on that either.

    Today in the newsgroup where I hang, someone asked about SA.  I got news for you Mr. Landefeld. I'm normally a great customer evangelist [shhhhh don't say the “E“ word around my fellow MVPs] but I tell ya, your best word of mouth marketing falls flat when I can't even tell someone answers to basic questions like that.

    Get me answers Mr. Landefeld.  Otherwise I can't recommend SA when “I“ as a customer don't even know what I get.

    [can you tell I'm in a mood..... again....]

    I just changed the title of the blog.....

    And if that screws up your Newsgator sorry about that... but David Coursey called me “SBS Diva” in his review of SBS 2003.  It sounds so pompous doesn't it?  I'll see if I leave it up there....

    http://reviews-zdnet.com.com/AnchorDesk/4520-7297_16-5120748.html

    Nice review though

     

     

    We're all in the same Security zone!

     I recently sent this letter off to several folks at Microsoft.... we will see what happens....
    Recently Microsoft changed it's support policy for the Windows 98 and
    Windows ME operating systems, extending support for these platforms
    until the year 2006.  The indications in the press was that this was to
    assist the emerging countries and other marketplaces.  This also assists
    my marketspace, the Small Business environment.  I'm a Microsoft Small
    Business Server MVP and in our marketspace we still support a great deal
    of Windows 98 and ME computers.
    
    I was dismayed to find that there is a Security patch needed for Windows
    98 and ME computers [Security bulletin 04-007, KB 828028] but there is
    no information whatsoever on any Microsoft web site to let me and my
    community know that these patches are needed and must be called for.
    
    I have no Premier support service, no contract, no TAMS contact.  I have
    no way to know that I and my community is at risk.
    
    You and other Microsoft executives have touted the SDcubed+C.  "secure
    by design, default, and deployment, plus communications"  
    Communications.  That's the minimum that I need., that I'm asking from
    you today.
    
    Yes, I know that it would be wise to get people on the XP platform.  I'm
    very much looking forward to SP2 on XP.  I indeed advocate that.  But in
    the time being, help me, give me the tools to help my community patch
    what they have.
    
    At a minimum put the information about 98 and ME in the security
    bulletins.  Let me and my community know that patches are needed for
    these operating systems.
    
    Preferably continue to provide these to Windows Update channels.
    
    Steve Ballmer says on the Trustworthy computing page "We know it's not
    enough to just do the right things; we have to do them in the right way"
    http://www.microsoft.com/mscorp/legal/buscond/
    
    Continue to produce tools to help me protect my community in the future,
    but give me the information that I need today to protect my community
    now.
    
    Put information about Windows 98 and ME Security patches on the related
    Security bulletin pages.
    
    Sincerely,
    Susan Bradley
    CPA, CITP, GSEC, MCP
    Member, Center for Internet Security
    Microsoft Most Valuable Professional
    Small Business Server/Security
    
    
    ------------------------------------------------------------------------
    http://isc.incidents.org/diary.html?date=2004-02-22
    
    "Windows 98 ASN.1 Patch
    Readers reported to our handlers team that Microsoft is distributing a
    patch for the ASN.1 issue to Windows 98 users per request. If you are
    running Windows 98, contact your Microsoft representative for the
    location of the patch.
    
    As reported earlier, the ASN.1 advisory MS04-007 only covers newer
    versions of Windows. Windows 98 is however still vulnerable.
    
    Workaround: you may want to consider renaming or removing msasn1.dll. 
    However, please test this fix carefully as it may break some software.
    
    Careful! Do not trust any patches sent via e-mail. "
    
    --------------------
    I can confirm that if you call MS PSS, option 3 for hotfixes and ask for
    hotfix for Windows 98 and Windows ME for KB 828028 you can easily get
    them FOR FREE.
    
    US (800) 936-4900 or UK (0870) 60 10 100 other numbers through
    http://support.microsoft.com/common/international.aspx?gssnb=1
    
    If you have Windows 98/Me machines, either call that number or contact
    your support/TAM account representative.