SBS Sp 1 Installation steps

Microsoft Windows

Hello,

I'm just curious, I've read through the docs which tell you to install the
to XP hotfixes first, and then W2k3 SP 1, then SPS SP 1, then Exchange 2003
SP 1, then run the SBS SP 1 install.

I've read multiple threads where people claim that SBS SP 1 installs SP 1
for both SPS and E2k3. If that's the case, I'm curious as to why the SP 1
read me from the MS Website states to manually install SPS and E2k3 SP's.

Then I've talked to other consultants and they don't even run the W2k3 SP 1
install and just run the SBS SP1 install. My concern there is that W2k3 SP 1
is 364 mb and SBS SP 1 is 210mb.

The doce I'm reading again is off the SBS page:
http://www.microsoft.com/downloads/details.aspx?FamilyId=B6F8A4C0-B707-4161-ADEB-44F1B756119F&displaylang=en

It's labled ToDownLoadFilesandReadInstructions.htm

Down the page it even reads as follows:

Downloading the service pack. The download for Windows SBS SP1 includes the
service packs necessary for the Standard Edition of Windows SBS 2003. As a
part of this process, you must download five separate files, which could take
a considerable amount of time depending upon the speed of your Internet
connection. If any of service packs 1-4 are already installed, it is not
necessary to do so again.

1. Service Pack 1 for the Windows Server® 2003 operating system
2. Windows SharePoint® Services 2.0 Service Pack 1
3. Exchange Server 2003 Service Pack 1
4. Windows XP SP2 for Client Deployment
5. Windows Small Business Server 2003 SP1

Currently I'm testing with using SPS & E23k SP 2 instead of one in the steps
mentioned.

Hope that's clear and if anybody has any documentation that I'm missing
pertain to the recommended SP 1 upgrade path, I would appreciate it.
...whoa... how many consultants say that they don't install Windows 2003
sp1?

HELLO TECHNOLOGY CONSULTANTS OF THE WORLD... WOULD YOU PLEASE READ
DOCMENTATION AND README FILES

There are 5 parts to the SBS service pack

Windows 2003 sp1
Sharepoint [can use sp2]
Exchange [can use sp2]
XP sp2
and then the SBS specific service pack

YOU DO THEM ALL

Tell all those consultants to read the documentation please?
The Sharepoint service pack is not done by step one...but if you've been
keeping up with Windows update or Microsoft update it's already done and
can be skipped.

The point is... you should either ensure each part is there or have been
done by MU or WU.
Jan,

One thing to keep in mind, SBS is a "dummied" up version of Windows 2003 and
other products combined together at lower prices for obviously small
businesses. By "dummied" up I mean they've added all these wizards,
trincates to allow more people without much IT experience to use it.

The flip side for IT consultant's is the features which are meant to make
the product easier to use mean more things for us to figure out when
something doesn't work the way it's supposed to. Or in these situations,
have to do things that we would tackle a different way. Sure you are
responsible and have patch management avenues setup for your clients, but not
everybody using Small Business Server is that saavy.

In that note, you don't have to run the client Deploy, if you downloaded and
installed XP SP 2 then you should have it in the environment and you can just
expand it into a directory under client apps, run the two hotfixes mentioned
in the install docs and your done.

In closing, for the users this product is designed for I'm sure they want to
force this to make sure it's on these small businesses' networks and by
forcing them to have it available on the server, they are making light of it
to users who would never otherwise give SP 2 a thought.
haha, definitely not trying to hurt anybody's feelings or insult anyone, I
used "dummies" because of the success of all the "for dummies" books. I've
bought them before so I'm a dummy as well in some areas. :)

MS uses double talk because they want to sell the product to small business
owners who can't or won't pay consultants like us to come in and set this up
for them. But at the same time they have to be careful in how far the
portray that because they do sell a lot of products through people such as us.

Plus the term has nothing to do with us. Yeah it might mean that a few more
IT consultant wanna be's might get in the business but the flip side of all
these wizards and stuff as you mentioned means it takes a sharp IT consultant
to come in and clean up a mess or figure out a gap these wizards don't fill.
All these wizards are good for the making it easier on people when they work,
but make it harder on us when things don't go so well.

So to be a setup admin who just inserts a CD and follows the prompts, it's
let's say "easied up". But when you get a 403 http error when IE comes up,
or even better yet you want to try and get SBA or something that doesn't mess
well because of this wizard config stuff, the people who don't spend the time
learning what these wizards do behind the scenes find themselves in trouble.
You are right as well, that some make matters worse by letting their egos get
the best of them and start doing things they shouldn't.

Point I was trying to make to the other lady is explain what it is by the
fact you have to XP Sp 2 in place in the client apps to proceed with the
patching. As hard as they try, they aren't going to come up with any wizard
or product that is just perfect for every person in every situation. There
are always going to be trade offs.

BTW, were you at the SBS meeting in CLT? You're name rings a bell.
Sorry, clt = Charlotte, I just thought I heard your name the other week in a
meeting. Hmm, I worked for MS for 8 years, I didn't even know they broke
down support different for SBS. When I was in PSS when 4.0 came out, they
dumped support on the existing groups such as Protocols, setup, domains etc.

I supported SBS RRas, dial up, DNS, wins and networking issues in clt until
I transferred to Alliance. I didn't care much for the product back in the
4.x days but have started playing with 2003 and it seems to have progressed
nicely.
Susan, I did but was just curious because they aren't having any problems.
Plus I would have thought the automatic update services would complain or
warn that W2k3 SP 1 wasn't installed.

But hey, I wanted to check just to make sure they didn't know something I
didn't because if you didn't have to install W2k3 SP 1 then that would save
quite a bit of time.

Interesting Les, thank you for the link. It would be interesting to update
this article with findings on using SP 2 of E2k3 and SPS Sp 2.

Another thing say you have problems with DNS, wins or something that you
need to uninstall and reinstall because of problems. Are you saying you must
reapply W2k3 SP 1 and SBS sp1? That's not good.

Also, my final question, from what I understand is W2k3 SP 1 initially broke
functionality in SBS. I'm assumming Exch Sp1 and SPS SP 1 did the same. Now
SBS Sp 1 contains all the fixes to those problems. I've read the list and
it's not that many. Or not so many that you would think it would lead to the
size of 210mb? So the final question, what exactly does SBS install?
Anybody from MS internal care to answer?
Where are these conversations taking place?

MU does not bring down Windows 2003 sp1 because we asked them not to
bring that down on our SBS boxes.

Who has problems with DNS that you need to uninstall and reinstall?

MSDE sp4 is in there for one... I forget the other parts....
Susan,

These conversations have taken place over the past 14 years of my consulting
career. Most noteably the 8 I worked in Microsoft support. You'd be
surprised the situations that come up in customer environments when you deal
with enough.