[windows2000] Re: Windows 2000 domain upgrade
- From: "Leitman, Ken" <ken.leitman@xxxxxxxx>
- To: <windows2000@xxxxxxxxxxxxx>
- Date: Thu, 10 Nov 2005 10:15:00 -0500
Yes.
How you do this is based on your skill set and comfort level. I have
staff who are experienced in upgrade in place, and a lab where we can
run through this. I also work with a separate Exchange and DBA group on
the upgrade path for their products. We also development servers for our
major applications. Not having these makes this a much more difficult
decision. For file servers we remove a mirror drive, put in a new drive,
wait for re mirror to complete, then do the upgrade (backups done the
night before upgrade to verify completeness). On a few hundred GB file
server this saves us a lot of time, but practice and test make any of
this possible.
As usual, some applications will not work through in place upgrades. And
trying to do an upgrade with AV etc. still installed could be
devastating,
kl
_____
From: windows2000-bounce@xxxxxxxxxxxxx
[mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Dogers
Sent: Thursday, November 10, 2005 10:09 AM
To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] Re: Windows 2000 domain upgrade
Is it best to do in place upgrades, or to create new machines (or reuse
previous member machines, I guess!), join them and seize roles?
Andrew
On 09/11/05, Leitman, Ken <ken.leitman@xxxxxxxx> wrote:
1) you must go to Windows 2003 SP1 for your DCs.
2) If you have remote offices with DCs check rpc settings for
timeouts, we did have some issues with this setting being changed with
SP1
3) Verify all hardware drivers with SP1 before you roll it out,
some video and other drivers MUST be upgraded, this was our biggest
issue and we had issues with SCSI, video and network cards
4) Start simple with local FSMO servers and make sure you have a
plan in place to move roles around
We did all of our 54 DCs in about three weeks. Without SP1 we ran into
all sorts of crazy issues, even with all of our testing.
We use HP servers, but we have seen the same driver problems on eval IBM
and Dell servers when applying SP1
Remove any third party software you can before any server upgrades, by
removing the monitoring, AV and backup software, we were able to script
an in place upgrade from W2K to W2K3.
Plan, test, plan some more and good luck, thankfully this is less
complex than Nt4 --> W2K, or initial AD design/implementation,
kl
_____
From: windows2000-bounce@xxxxxxxxxxxxx
[mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Joanne Determann
Sent: Wednesday, November 09, 2005 12:00 PM
To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] Re: Windows 2000 domain upgrade
First thing I did was determine the compatibly of all my apps and
programs.
(Although my Websense DC agent doesn't work now even though their
support insisted it was 2003 compatible.)
Then I made a spread sheet 'server plan' . what server does what and
how it was gonna move things around during the upgrade.
Now it's in MS project timeline.
My DC's are done, Terminal Servers ( licensing is a biggy),backup and
one webserver are complete
Doing Exchange next week.
_____
From: Dave stevens [mailto:london31uk@xxxxxxxxx]
Sent: Wednesday, November 09, 2005 11:53 AM
To: windows2000@xxxxxxxxxxxxx
Subject: [windows2000] Windows 2000 domain upgrade
Hi Guys,
I have just been tasked with comming up with a detailed plan for our
2000 domain upgrade to 2003.
Does anyone have any tips / whitepapers that would help.
Currently it is a single domain, multiple sites setup we have. Any
suggestions would be helpful.
Thanks
Dave
_____
Yahoo! FareChase - Search multiple travel sites in one click.
<http://us.lrd.yahoo.com/_ylc=X3oDMTFqODRtdXQ4BF9TAzMyOTc1MDIEX3MDOTY2OD
gxNjkEcG9zAzEEc2VjA21haWwtZm9vdGVyBHNsawNmYw--/SIG=110oav78o/**http%3a/f
arechase.yahoo.com/>
-----------------------------------------
The information contained in this transmission may be privileged and
confidential and is intended only for the use of the person(s) named
above. If you are not the intended recipient, or an employee or agent
responsible
for delivering this message to the intended recipient, any review,
dissemination,
distribution or duplication of this communication is strictly
prohibited. If you are
not the intended recipient, please contact the sender immediately by
reply e-mail
and destroy all copies of the original message. Please note that we do
not accept
account orders and/or instructions by e-mail, and therefore will not be
responsible
for carrying out such orders and/or instructions. If you, as the
intended recipient
of this message, the purpose of which is to inform and update our
clients, prospects
and consultants of developments relating to our services and products,
would not
like to receive further e-mail correspondence from the sender, please
"reply" to the
sender indicating your wishes. In the U.S.: 1345 Avenue of the Americas,
New York,
NY 10105.
-----------------------------------------
The information contained in this transmission may be privileged and
confidential and is intended only for the use of the person(s) named
above. If you are not the intended recipient, or an employee or agent
responsible
for delivering this message to the intended recipient, any review,
dissemination,
distribution or duplication of this communication is strictly prohibited. If
you are
not the intended recipient, please contact the sender immediately by reply
e-mail
and destroy all copies of the original message. Please note that we do not
accept
account orders and/or instructions by e-mail, and therefore will not be
responsible
for carrying out such orders and/or instructions. If you, as the intended
recipient
of this message, the purpose of which is to inform and update our clients,
prospects
and consultants of developments relating to our services and products, would not
like to receive further e-mail correspondence from the sender, please "reply"
to the
sender indicating your wishes. In the U.S.: 1345 Avenue of the Americas, New
York,
NY 10105.
Other related posts:
