Re: SBS Sp 1 Installation steps

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



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.


--
kris@xxxxxxxxx<Remove This Before Emailing>

Network & Software Integration
www.n-sv.com

"Helping put the pieces of your IT puzzle together"


"Susan Bradley, CPA aka Ebitz - SBS Rocks" wrote:

> 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 wrote:
>
> >Having just done this here's my .02.
> >
> >The sharepoint stuff (step 2) appears to be done by step1. Why the hell
> >should you have to download the XP SP2 stuff when they explicitly indicate
> >its optional. All our WS have long time had XP SP2 installed and we have no
> >need for SP deployment to the clients. Step 5 won't run unless step four is
> >done! What a croc
> >
> >
> >"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@xxxxxxxxxxx>
> >wrote in message news:%23GLXBp2IGHA.984@xxxxxxxxxxxxxxxxxxxxxxx
> >
> >
> >>...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?
> >>
> >>kfrost wrote:
> >>
> >>
> >>
> >>>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.
> >>>
> >>>Thanks.
> >>>
> >>>
> >>>
> >>>
> >>>
> >
> >
> >
> >
>
.



Relevant Pages

  • RE: unable to install anything on Server 2003 SBS SP2 (windows ins
    ... Verify the SBS 2003 sp1 is installed on SBS: ... To successfully install SBS 2003 SP1, ... Downloading and Installing Windows Small Business Server 2003 Service Pack 1 ...
    (microsoft.public.windows.server.sbs)
  • RE: Corrupted Recycle Bin
    ... I think this issue caused by you did not install SBS ... Downloading and Installing Windows Small Business Server 2003 Service Pack 1 ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Monitoring reinstall fails
    ... ""You must have the Windows SBS 2003 Administration ... Manually install the Monitoring instance. ... Reboot the SBS Server. ...
    (microsoft.public.windows.server.sbs)
  • RE: Service pack version
    ... I understand that the SBS 2003 BPA suggests ... Now, you had installed Windows Server 2003 sp2 on your SBS, and the SBS ... It is recommended to install the Windows Server 2003 sp2 after install the ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 Standard - Update to SP 1 fails
    ... order to prepare SBS server to deploy Windows XP SP2 to client computers ... that are running Windows XP Professional. ... The SBS SP1 launcher need copy ... please install it and then ...
    (microsoft.public.windows.server.sbs)