2K DC Hardware upgrade
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
2K DC Hardware upgrade

 
Post new topic   Reply to topic    Windows Server Forum Index -> Migration
Author Message
Guest
Posted: Thu Sep 29, 2005 8:50 pm    Post subject: 2K DC Hardware upgrade Reply with quote
run a small network with 2 DC's. I am upgrading the hardware on the
main DC this weekend and was planning to use the procedure in KB 249694

which I have used several times before with good success. However I
just saw in there that it was not recommended for DC's. My question is

this, if I shut down the secondary DC first, then backed up the main dc

using NTBACKUP and followed the procedures in 24964 to restore to new
hardware, bring up the new hardware and not bring up the secondary DC
until the main dc is totally up on new hardware, would this work?


My thinking is if the secondary is down the entire time, there are no
AD changes taking place so if I bring it up after the main box comes
back up it should chug along just fine?


I would appreciate it if someone could chime in on this.
Back to top
Vincent Xu [MSFT]
Guest
Posted: Fri Sep 30, 2005 7:18 am    Post subject: RE: 2K DC Hardware upgrade Reply with quote
Hi,

I have reviewed the KB article 249694 and I found it says :"This procedure
is not recommended for domain controllers". So I also strongly recommend
you not to do it to DC

If you still want to do it, necessary backup is needed. As you said take
the secondary Dc offlien during the process.

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security


--------------------
Quote:
From: duf@duf.net
Newsgroups: microsoft.public.windows.server.migration
Subject: 2K DC Hardware upgrade
Date: 29 Sep 2005 10:52:43 -0700
Organization: http://groups.google.com
Lines: 20
Message-ID: <1128016363.635137.54670@g44g2000cwa.googlegroups.com
NNTP-Posting-Host: 70.88.32.102
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1128016369 31538 127.0.0.1 (29 Sep 2005
17:52:49 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 29 Sep 2005 17:52:49 +0000 (UTC)
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1;
..NET CLR 1.1.4322),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: g44g2000cwa.googlegroups.com; posting-host=70.88.32.102;
posting-account=U5FEdA0AAABbkn-smGP5AnhT9iAtrNyo
Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli

ne.de!border2.nntp.dca.giganews.com!nntp.giganews.com!postnews.google.com!g4
4g2000cwa.googlegroups.com!not-for-mail
Quote:
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:12170
X-Tomcat-NG: microsoft.public.windows.server.migration

run a small network with 2 DC's. I am upgrading the hardware on the
main DC this weekend and was planning to use the procedure in KB 249694

which I have used several times before with good success. However I
just saw in there that it was not recommended for DC's. My question is

this, if I shut down the secondary DC first, then backed up the main dc

using NTBACKUP and followed the procedures in 24964 to restore to new
hardware, bring up the new hardware and not bring up the secondary DC
until the main dc is totally up on new hardware, would this work?


My thinking is if the secondary is down the entire time, there are no
AD changes taking place so if I bring it up after the main box comes
back up it should chug along just fine?


I would appreciate it if someone could chime in on this.

Back to top
Duf
Guest
Posted: Fri Sep 30, 2005 12:50 pm    Post subject: Re: 2K DC Hardware upgrade Reply with quote
If it doesn't work for some reason I always have the option of just
firing the old DC back up so it is worth a shot, I'll report my
results.

I am guessing MSFT's recommendation is with the assumption that most
situations would not allow you to bring down all DC's when doing an
upgrade.
Back to top
Duf
Guest
Posted: Fri Sep 30, 2005 12:50 pm    Post subject: Re: 2K DC Hardware upgrade Reply with quote
I find it odd that the articles says not recommended for DC's yet it
specifically mentions NTDS and SYSVOL volumes and restarting servers in
Directory Services restore mode.......
Back to top
Duf
Guest
Posted: Mon Oct 03, 2005 12:50 pm    Post subject: Re: 2K DC Hardware upgrade Reply with quote
Just as a followup I did as I outlined above this weekend and was able
to successfully upgrade our primary DC using this method. If you have
a DC that is just performing AD duties I would not recommend it but in
my case, this DC had Exchange as well as some other apps on it which
made the backup and restore route much more feasible in our case.

I brought down the other DC while I was doing the backup but when I did
the restore I had the secondary DC online.
Back to top
Vincent Xu [MSFT]
Guest
Posted: Tue Oct 04, 2005 8:51 am    Post subject: Re: 2K DC Hardware upgrade Reply with quote
Hi Duff,

Thank you for your reply and telling us the method you found yourself to
resolve the problem.

I think your experience will benefit lots of users in this Newsgroup and we
really value having you as a Microsoft customer.

Have a good day!

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security


--------------------
Quote:
From: "Duf" <duf@duf.net
Newsgroups: microsoft.public.windows.server.migration
Subject: Re: 2K DC Hardware upgrade
Date: 3 Oct 2005 05:36:34 -0700
Organization: http://groups.google.com
Lines: 9
Message-ID: <1128342994.478169.160560@f14g2000cwb.googlegroups.com
References: <1128016363.635137.54670@g44g2000cwa.googlegroups.com
sogyTVWxFHA.628@TK2MSFTNGXA01.phx.gbl
1128080100.501635.156040@g49g2000cwa.googlegroups.com
1128083681.093016.238190@g49g2000cwa.googlegroups.com
NNTP-Posting-Host: 70.88.32.102
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1128342999 5106 127.0.0.1 (3 Oct 2005
12:36:39 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 3 Oct 2005 12:36:39 +0000 (UTC)
In-Reply-To: <1128083681.093016.238190@g49g2000cwa.googlegroups.com
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1;
..NET CLR 1.1.4322),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: f14g2000cwb.googlegroups.com; posting-host=70.88.32.102;
posting-account=U5FEdA0AAABbkn-smGP5AnhT9iAtrNyo
Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli

ne.de!border2.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.gigan
ews.com!postnews.google.com!f14g2000cwb.googlegroups.com!not-for-mail
Quote:
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:12213
X-Tomcat-NG: microsoft.public.windows.server.migration

Just as a followup I did as I outlined above this weekend and was able
to successfully upgrade our primary DC using this method. If you have
a DC that is just performing AD duties I would not recommend it but in
my case, this DC had Exchange as well as some other apps on it which
made the backup and restore route much more feasible in our case.

I brought down the other DC while I was doing the backup but when I did
the restore I had the secondary DC online.

Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> Migration All times are GMT
Page 1 of 1

 
 You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB