Re: Thanks to those who help me...

From: Les Connor [SBS MVP] (les.connor_at_DEL.cfive.ca)
Date: 05/14/04


Date: Fri, 14 May 2004 10:02:55 -0500

Scamps,

If you are determined, you will learn SBS.

My bet is the first Access or SQL app you built wasn't the best one you ever
did. My first SBS server wasn't the best I ever built either. There are some
people I know that may be considered expert in SBS, SQL, and Access arenas.
But they are not common, and I'm not among them.

I'm not trying to be condescending - in fact I know little about Access, and
a lot less about SQL. I recognize that they have specialized skills. I use
some custom Access apps, but I didn't develop them, I hired an expert. I
always try to partner with an expert when SQL is involved. But hey, I can
sure make SBS play nice :-).

As it turns out, the application vendors that specialize in SQL apps, and
when SBS is the platform, prefer to partner with an SBS expert.

My point was that, marketing SBS as a 15 minute install - no related IT
experience required - is a guarantee of dissapointment.

Above marketing claim aside, SBS 2003 is quite simply the best platform
there has ever been for small business.

-- 
Les Connor [SBS MVP]
-------------------------------------
SBS Rocks !
"Scamps" <anonymous@discussions.microsoft.com> wrote in message
news:d1c301c439c1$099bbfd0$a101280a@phx.gbl...
> thanks for your comments Frank.
> I think that infact SBS does meet my needs. One only has
> to read the set book to see it is clearly aimed at the
> small business. We do OK but I think overall SBS needs a
> complete overhaul of the user interface. i thihnk I am
> suffering from a possible bad install because most of my
> problems stem from things not working that should have
> worked from day 1.
> I must admit that moving from internal SQl development
> and Access client development I have come to absolute
> deadstop trying to connect to sharepoint services from
> FrontPage in order to move the SQL server development
> online. Any help here would be much appreciated.
> >-----Original Message-----
> >Hi Scamps,
> >
> >It is unfortunate that SBS does not meet your
> expectations, but quite
> >frankly this is not a completely uncommon situation.
> >
> >The fact is, SBS can almost certainly do a superb job of
> meeting the needs
> >of your business. That is an expectation that you have,
> and one that can be
> >met. But it's not necessarily a do it yourself project.
> If it has been
> >marketed in that light, then it has been marketed in
> error.
> >
> >Where the problem lies, is that you have been led to
> believe that this is a
> >simple product that can be successfully and completely
> implemented and
> >maintained by a person with a limited set of IT skills.
> Unfortunately, that
> >is not an expectation that can be consistently met,
> because the skill set
> >that any one given person has is not known or consistent
> across all persons.
> >
> >You are not at fault. The developers of the product are
> not at fault. You
> >are simply in a situation where you need someone with
> the right skill set to
> >get this product set up for your business.
> >
> >-- 
> >Les Connor [SBS MVP]
> >-------------------------------------
> >SBS Rocks !
> >
> >
> >
> >"Scamps" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:cbb301c438ff$bea1d7b0$a301280a@phx.gbl...
> >> ...with a difficult and demanding product.
> >> I appreciate this newsgroup and the good folk who take
> >> time to help others.
> >> I have been using SBS2003 since Jan2004 and I have to
> say
> >> if it wasnt for the help from here and my "reasonable"
> >> skills from 12 years experience with windows O/S as a
> >> user I wouldnt stand a chance with this supposed small
> >> business product. I am a business person first and a
> >> frustrated IT manager second.
> >> Since I installed it:
> >> Back Up has never worked satisfactorally. It fails if
> the
> >> full SBS back up is run and you have SQL server and
> >> Exchange Installed. If you try and work around creating
> >> separate ntbackup schedules that backup various
> >> components separately (to Overcome the above issue)
> then
> >> it appears a random event that they actually run to
> >> schedule.
> >> Exchange. Now that Ive set up about 10 people as users,
> >> Exchange no longer is set up as part the user set up.
> If
> >> a mailbox is created then the user cannot be seen from
> >> the client, And now I dont even get a user mailbox in
> the
> >> user set up process. Thankfully the web client still
> >> allows me to connect to the mail box whilse outlook2003
> >> cant see the mailbox.
> >> IIS is a complete myth for a user like me. I want to
> use
> >> Front page to develop the "CompanyWeb" but I am met by
> >> security messages which prevent me editing the site. I
> >> try to read the help notes but sink rapidly in to a
> pool
> >> of technobabble which does nothing but create
> depression.
> >> ISA is even worse. I want to access my sequel server
> >> database from remote but darent even contemplate it.
> >> When I first installed the server I had some kind of
> >> replication service running which kept user data
> >> synchronised between the server and the clients but
> this
> >> (possibly because I was running mcafee antivirus)
> caused
> >> huge problems until I turned the synch feature off.
> >> CompanyWeb I think is meant to be some wizzy
> implemention
> >> of something called sharepoint but every time I try and
> >> use the "Create" menu tool I get messages that tell me
> >> that what I am trying to do failed for some obscure
> >> reason.
> >> In the Server Manager Utility evry time I look at the
> >> backup section the webpage part fails on a 403 message.
> >> Try as I might (back to IIS and ISA again) I have not
> got
> >> a clue what bit if the security stuff I need to fix.
> >> The Back up utility is buggy. clicking on certain parts
> >> of the interface makes it go mad.
> >> Thank goodness SQL server keeps plodding on and has its
> >> own backup process. Most of my effort goes into
> >> developing our SQL server solution with Access and
> thats
> >> a solid plus point.
> >> Whoever designed this product has absolutley no idea
> what
> >> a small business is. I have to keep plodding on with
> this
> >> product because as an data led growing business
> because I
> >> cant afford failure. Your help in this community
> >> compensates for a poor interface on this supposidly
> entry
> >> level product.
> >> Scamps
> >
> >
> >.
> >


Relevant Pages

  • Re: Redundancy design in SBS Domain
    ... But virtualization was not on my radar, and Exchange and SQL need more with each iteration. ... I originally went the SBS route because it was by far the cheapest was to get a server up and running with SQL Server at the time. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Std - SQL Eval expired...will un-installing break SBS fun
    ... I agree with Claus that you're able to remove SQL 2005 instances if you did ... you can get SBS R2 which already contains SQL Server 2005 ... Workgroup Edition, and upgrade Sharepoint instance, and install other ...
    (microsoft.public.windows.server.sbs)
  • Re: sharepoint error
    ... If you are using SBS 2003 Premium Edition the easiest way is to follow ... to upgrade the SharePoint named instance. ... and search on "Migrating from WMSDE to SQL Server" ... Microsoft Small Business Server Support ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS
    ... Les Connor [SBS MVP] ... Is your server exhibiting significant performance problems, and if so, how ... SQL Server: ... >No wonder SBS brings servers with 4GB of RAM to their knees. ...
    (microsoft.public.windows.server.sbs)
  • Re: using same workstation with SBS2000 and SBS2003 domains
    ... Thanks for using the SBS newsgroup! ... To make two SBS domains running in one physical network, ... to the following articles to setup VPN server and configure VPN client. ... Turn On and Configure Inbound VPN Access in Small Business ...
    (microsoft.public.windows.server.sbs)

Loading