Re: Windows 2003 SP1
- From: "Kerry Brown" <kerry@xxxxxxxxxxxxxxxxxx*o*m>
- Date: Tue, 5 Apr 2005 10:08:50 -0700
"RobertM" <RobertM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7CCC8176-BDE1-4C3F-BA11-691DC0A01BF5@xxxxxxxxxxxxxxxx
> Of the servers one was a Dell Poweredge 2600 which completed Ok.
> The other three were all Dell Poweredge 1750 with exact same spec.
> The other strange thing was when 2003 was reinstalled it did not appear to
> detect the original 2003 installation on the C: partition and reinstalled
> it
> on the D: partition.
> I assume it did this because it did'nt recognise a C: partition.
> The servers ended up well and truely creamed!!
> Any more thoughts.. and thanks for your response anyway.
>
Hard to say what caused it without seeing the other errors that came up in
the logs. Were you using RAID? The embedded SCSI controller? etc. It's got
to be something different on the two that failed. Figuring out the
difference can be time consuming :-)
Before a major change like SP1 I make sure I have at least two backups, one
from immediately before the upgrade. If anything goes wrong it's easier and
quicker to just restore the backup and then try and figure out what caused
the problem later. If it's a critical server it also makes sense to have a
backup server on standby in case something goes wrong that can't be fixed
quickly. I usually install a second DC on the site a week or so before.
Transfer all the FSMO roles to it and make sure it's working OK. Then
upgrade the original server and take back the roles once it has been fully
tested. A lot more work but almost no chance for network down time and no
all night sessions. If you have four DC's at different sites the investment
in a spare server would be money well spent. How many people would be down
if one of the DC's quit unexpectedly?
> "Kerry Brown" wrote:
>
>> "RobertM" <RobertM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:E1E4D51F-B187-4712-BEB9-E924BB4353FC@xxxxxxxxxxxxxxxx
>> > This post maybe helpful to others re. SP1
>> > We have 4 Dell servers in a single domain acting as DCs
>> > We updated two of the DCs to SP1 without a problem.
>> > The other two got trashed when we installed SP1.
>> > Installation completed successfully but on reboot the registry was
>> > corrupted
>> > with a STOP message and Registry_Error and error code 0x00000051.
>> > Reboot in Safe mode and last known good config gave same result.
>> > Both DCs are in different geographic sites on different subnets but the
>> > error was the same in both cases.
>> > This neccessitated a complete reinstall of Windows 2003 server.
>> > Then had to seize the FMSO roles, remove DC objects from AD using
>> > NTDSUTILS
>> > and run metadata cleanup, before recreating the DCs.(DCPROMO)
>> >
>> > I certainly did'nt want to spend all of last night and early morning
>> > doing
>> > this, so thanks alot Bill.
>> > Any MS pros out there who can throw some light on this?
>> >
>> > Moral - really check SP1 out and watch it like a hawk.
>>
>> The moral really is: deploy major changes in stages. Why would you
>> upgrade
>> four servers at different geographic sites at the same time? It would
>> make a
>> lot more sense to deploy SP1 on one server. Wait until you are sure that
>> site is OK (possibly a week or two) then do each of the others in turn.
>> 0x51
>> can also indicate hardware incompatibility, low disk space, or file
>> corruption. Do all the servers have the same hardware?
>>
>> Kerry
>>
>>
>>
.
- References:
- Windows 2003 SP1
- From: RobertM
- Re: Windows 2003 SP1
- From: Kerry Brown
- Re: Windows 2003 SP1
- From: RobertM
- Windows 2003 SP1
- Prev by Date: Re: Alias a UNC Host Name in Server 2003
- Next by Date: Re: Enable Ethernet Adapter
- Previous by thread: Re: Windows 2003 SP1
- Next by thread: Re: Windows 2003 SP1
- Index(es):
Relevant Pages
|
