Re: Windows 2003 Service Pack 2 Active Directory Upgrade

Hi

The problem with LAB environments in this case is that you "Generally" can
reproduce the exact scenario that you have, and the big issue is the
hardware used on these machines that isn't equal.

In my opinion you should document yourself with your hardware vendor/support
and check if do you need to anything extra before implementing SP2 on the
servers (drivers/firmware/software - updates).

I already installed a couple of hundreds of SP2 updates, in my experience
the hardest are the cluster servers depending of the SAN that you're using
FibreChanel connectors etc... But there's also other problems in some well
known hardware vendors, generally a firmaware update or driver update solves
the issue.

In conclusion check with your hardware vendors if you're ready to apply the
SP2, do the tests of course, but sometimes a simple driver update may get
you out of a big blue screen.



--

===================================
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services
===================================

"Brillmike" <brillmike@xxxxxxxxx> wrote in message
news:FA9B9D0E-6B61-4765-B9B1-6A31CA17F1F1@xxxxxxxxxxxxxxxx
YEs, this is an after hours install. I have tested it in the lab, but as
you
all have mentioned, the lab is almost never identical to the production
env.
I feel I can proceed but I like to check with you all for this great
feedback. I can always unistall SP 2 incase something goes horribly wrong.

"Austin Osuide" wrote:

Hi Brillmike,
As well as the comments made by the others, the first thing you should do
is
TEST your process on DCs that are similar to your production DCs.
This way, you have a better assessment the risks associated and an
objective
assessment of the time it'll take for the process to run.
No two environments are exactly alike and "stuff" does happen, even when
carrying out seemingly trivial processes so it is imperative to the
success
of your task that you test.

Regards,

Austin

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb666747c8c9eb41257fe670@xxxxxxxxxxxxxxxxxxxxxxx
Hello Henrik,

You are totally right with that. I also do these bigger things after
normal working hours.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

I assume that you gonna do the SP 2 installation during a maintenance
window
so that you don't install the SP2 during office hours if something
would go
wrong=)?
Any way, good luck meight there shouldn't be any problems.
"Meinolf Weber" wrote:

Hello Brillmike,

see inline

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
We are not using ADAM so I have a pretty straight forward upgrade
from Windows 2003 (no service pack) to Windows 2003 Service Pack 2
on our domain controllers. I just a few questions on the
installation of the service pack.

1. Does it matter what order I update the servers (DC1, DC2)?

No

2. Will any logon services or DNS services be interupted while the
service
pack is installing? (it takes a while for the service pack to
inventory,
unpack and install and i am wondering how user will be impacted)
Check before starting the update, that both DC's are Global catalog
servers and if not done make the second also DNS server. I would
prefer Active directory integrated zones. Then during the reboot no
user should have problems, except the server stores some files from
the users (shared folders). They will ofcourse be not accessible
during the reboot.

3. Do both primary and secondary DC need to be on the same service
pack.

No, they will work together even if they are different.

I plan on doing them together but maybe I should do one, wait to see
if
we have
any issues, then do the second server.
Good idea, i would do it also this way.

Thanks, Mike






.

Relevant Pages

  • Service Pack 2 (sp2) woes.
    ... I aborted the install by choosing not to continue so I ... mostly with crashes and detection of new hardware that didn't exist. ... before I started applying service pack 2. ... into Control Panel and then device manager, ...
    (microsoft.public.windowsxp.general)
  • Re: Two Versions of SQL Server 2000, Service Pack 3
    ... beta versions installed on your servers. ... > that they had SQL Server 2000 Service Pack 3 installed. ... > are telling our entire enterprise NOT to install service ... > releaseing a service pack with the same number is going to ...
    (microsoft.public.sqlserver.security)
  • Windows 2000 Service Pack 4
    ... Service Pack 4 updates a LOT of core drivers and such... ... Hardware drivers without one of their premium Dear to Your ... >Install for End Users" twice and received the following ...
    (microsoft.public.win2000.windows_update)
  • Re: help! lost network connection after installing service pack 1
    ... working fine-had internet and email through a network with linksys ... un-install service pack 1-it works fine again but then cannot run ... Why did you install Windows XP afresh? ... Did you install the proper hardware drivers for each piece of hardware in ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: [SLE] Hardware recommendation please for MULTIPLE machines.
    ... I currently have many servers from Appro ... They warranty their hardware and pre-test the ... >> I want to install this on multiple machines. ... Since I assume the drives will be the same size and you will be ...
    (SuSE)