Re: SP1 finished successfully... or did it?
- From: "Jeff Middleton [SBS-MVP]" <jeff@xxxxxxxxxxxxxxxx>
- Date: Wed, 20 Jul 2005 11:46:47 -0500
Ryan,
Regarding the SP updates to an SBS 2003 Server:
- If you have SP1 slipstreamed media, this is preferred.
- If you have a source server with SPs installed, the target server should
be matched to those before attempting a Forklift of Exchange or other
application data.
- If you don't have slipstream media, and if you don't have SPs above Gold
on the source server, keeping with the same SP levels on the target server
is fine, and adding the SPs for all of SBS 2003 SP1 after the fact would
likely encounter the same success and issues as an existing SBS 2003 Server
does without a Swing involved.
- The only Swing specific concern about SBS 2003 SP1 I'm aware of is that if
you are doing a Swing from SBS 2003 to SBS 2003, if you Forklift the
Information Store, you must follow the Swing Migration documentation steps
to completion regarding the Exchange Forklift follow-up. That includes
reparing the proxyAddress information on the public folders, but in
particular it is critical that you ensure that the two public folders SBS
itself creates are repair before later running the SBS 2003 SP1 specific
update to ensure that the proxyAddress degradation doesn't become a
condition of an untrapped error by the SBS SP1 Setup utility. This is
information that is described on my website and in the Swing It!! Kit
documentation, and though the broken proxyAddress is a relatively harmless
condition in operations (unless you want the folder to send or receive
email), it causes a fatal abort of the SP1 installer which is not noted in
the SP1 Setup logs or alerted to the operator. This condition is not unique
to Swing, rather the conditions involved are related to a condition that can
be created in disaster recovery of a server in general even without Swing
involved.
In addition, the reason that the current Swing It!! Kit documentation
doesn't really contain a significant statement on SP installations is that
prior to release of SBS 2003 SP1, there had been no significant SPs released
on the various products on which to base a recommendation. At this point in
time, it's becoming clear that the SP1 issues that are being most frequently
observed are both complex and widespread, without any particular
relationship to Swing Migration methodology, rather it's just common to the
entire population of SBS 2003 servers out there. Like many people, I'm still
trying to get enough data and observations about what works and what doesn't
at this point in order to make an informed recommendation. The information I
started this post with is the most current view I have. Let's keep in mind
that SBS 2003 SP1 has been release just barely 60 days ago.
Finally, I anticipate announcing a semi-official statement by the end of
August which will identify my recommendations and support policy on SP1 with
regard to Swing Migration. I hope that by that time I will have firm
recommendation, with the thought in mind that SBS 2003 SP1 slipstream media
should be pretty readily available, and a reasonable degree of public
experience with SP1 installation will have become known.
I'm anticipating that my supported/recommended practice will be as follows:
1. For any SBS 2003 server being moved by Swing to a clean install:
- If SP1 is on the current (source server), slipstream media must be
used for the target server.
- If SP1 is not yet on the current (source server), either Gold or SP1
Slipstream media will be supported, but subject to the next
caveat/recommendation.
2. If the target server is being constructed using SBS 2003 Gold media, the
terms of support provided by the Swing It!! Kit will be that a reasonable
effort will be made to support of deploying SP1 on top of the finished
server, but this may not be part of the free support I provide for the
simple reason that it's really being handled as a post-Swing upgrade
project, not a Swing Migration incorporating SP1.
3. If the target server is being constructed use SBS 2003 SP1 slipstream
media, the terms of support provided by the Swing It!! Kit will include
completion of the Swing Migration with that server in accordance with the
terms and documentation one receives with the Kit.
I may decide to revisit this approach, but right now, this looks to me to be
the only sane way to have everyone involved understand the difference
between a best practice in following a documented construction path vs.
making a project more complicated than it needs to be. Keep in mind, the
post-construction addition of SP1 to an SBS 2003 Server constructed with
Gold media will add something like 3-4 hrs to the construction process. I
don't see this as being a productive approach for the person doing the
installation, or for me to try to embrace as it really isn't the cleanest or
most predictable installation option available. That's what Swing Migration
should be, the cleanest and fastes approach to migrating a server with a
predictable outcome.
- Jeff Middleton
YCST@xxxxxxxxxxxxxxxx
- Jeff
"Ryan" <Ryan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A79DF340-DFF3-454B-B538-3DDE8E0F2EB3@xxxxxxxxxxxxxxxx
> After clearing temp files, all the logs, and rebooting I started the SP1
> setup again. This is what happens:
> 1 Installing files
> Details - Installing Windows Small Business Server 2003 Service Pack 1
> 2 A popup comes up saying maybe a 1/4 through the copy process "Windows
> small business server service pack 1 setup has encountered an error"
> It asks if I want to view the error log now so I click yes
> 3 The sp1 wizard now says "finishing installation"
> Details - performing cleanup
> 4 You have successfully completed the KB885918 setup wizard
>
> Also, whenever I reboot since SP1 has first failed I get "setup.exe
> encoutnered a problem and needed to close" after I log in. I may get a
few
> of these messages, depending on how many times I ran SP1 before the
reboot.
>
> Jerry,
>
> Q1 From your description, I understand that you can mount the exchange
> database and your issue now is that you cannot install the SBS SP1. If I'm
> off base, please let me know.
> A1 Yep, thats basically my scenario.
>
> Q2 First of all, I would like to confirm that you have installed the
window
> server 2003 SP1, sharepoint SP1 and exchange SP1 without any problem.
> A2 Here are the steps I followed so far:
> 1 Windows 2003 Service Pack 1.
> 2 Windows SharePoint Services 2.0 Service Pack 1.
> 3 Windows Small Business Server 2003 Update KB891193 for Windows XP
Service
> Pack 2.
> 4 Exchange Service Pack 1.
>
> Here is what I find in the event viewer:
>
> Event 1023
> Source MsiInstaller
> Product: Microsoft Office Outlook 2003 - Update
> '{291832CE-338E-4F0C-9950-23BD77894741}' could not be installed. Error
code
> 1642. Additional information is available in the log file C:\Program
> Files\Microsoft Integration\Windows Small Business Server
> 2003\Logs\OutlookSP1Upgrade.log.
>
> Event 1000
> Source Microsoft Exchange Serv
> Faulting application exsetdata.dll, version 6.5.6944.4, stamp 3edc4f1a,
> faulting module suitehelp.dll, version 5.2.2893.0, stamp 4272cfb5, debug?
0,
> fault address 0x0004ae45.
>
> Event 1000
> Source Application Error
> Faulting application setup.exe, version 5.2.2893.0, faulting module
> suitehelp.dll, version 5.2.2893.0, fault address 0x0004ae45.
>
> Event 318
> Source SQLAgent$SBSMONITO
> Unable to read local eventlog (reason: The data area passed to a system
call
> is too small).
>
> Event 4377
> Source SBSServicePack
> Windows Small Business Server 2003 Hotfix KB885918 was installed.
>
> The dell fix doesn't seem to apply to me since I get an error "during" the
> install, not after. besides... I don't get a stop error #
>
> As for the setup log files... check your email
>
>
> Frank,
>
> Q1 Did you do a fresh install from CD1 boot or a Dell Server Boot CD
> Assistant start?
> A1 I performed the fresh install from SBS CD1. At first I used ran the
Dell
> CD but I didn't put in the SBS CD when it asked. I just shut the server
> down, and when I was ready to install I began the SBS setup right from SBS
> CD1.
>
> You mentioned "it is important in Swings that the OS be at the same SP
level
> during the migration portion from Production to Temp DC to final box but I
am
> uncertain about
> that point at all phases. "
>
> I skimmed through the swing it kit again and can't seem to find any
> references to when the final server should be updated. Basically, the
only
> thing I did between running the SBS, sql and isa setup and installing the
> service packs, was forklifting my exchange store, and running a few items
on
> the to do list in attempt to get SP1 to not fail on me again.
.
- References:
- SP1 finished successfully... or did it?
- From: Ryan
- Re: SP1 finished successfully... or did it?
- From: Frank McCallister SBS MVP
- Re: SP1 finished successfully... or did it?
- From: Ryan
- SP1 finished successfully... or did it?
- Prev by Date: Re: Silly DNS
- Next by Date: Re: Netwrok Browsing Error after adding 2nd NIC
- Previous by thread: Re: SP1 finished successfully... or did it?
- Next by thread: Re: SP1 finished successfully... or did it?
- Index(es):
Relevant Pages
|
