Re: Upgrade w2k
- From: "Miha Pihler [MVP]" <mihap-news@xxxxxxxxxxx>
- Date: Tue, 15 Nov 2005 21:26:42 +0100
I am not familiar with this imaging software (or is it backup software?)...
In general it is not recommended (and often not supported) if you deploy
servers by imaging them (it is a bit different if you restore them, but not
much different...)...
The problem with these is that imaging software (in general -- e.g. Ghost)
will make new server with same SIDs, GUIDs, server names, IP addresses
etc... This can cause conflicts on the network...
Another scenario would be you have now two servers named DC1. One if the
image of the other (and has same SID, GUID, name, IP, ...)... Now user or
computer changes its password and DC changes password for its account on
DC1. Now you take it offline and bring on the network another clone of this
DC -- clients and users that changed their password in the meantime will not
be able to logon and talk to DC...
Here is my alternative to imaging... Install Windows 2000 server. Patch it
up and run dcpromo on it. Make it a domain controller with new name, IP
etc... Transfer FSMO roles to it and make it Global Catalog ... Now you can
take it away from user's network and upgrade it. If the upgrade works out
for you take it back to user's network and it will replicate new information
to other domain controllers...
I did a lot of domain upgrades in last few years and never had major
problems with it. In larger environments we do extended testing where we
take one of domain controllers to another segment and test the upgrade there
(how we take DC off the network is explained above)....
--
Mike
Microsoft MVP - Windows Security
"manoa" <manoa@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4F590A1E-9ACA-4377-A054-900FCA13DB7E@xxxxxxxxxxxxxxxx
> We have two servers that we have clone using Symantec LiveState which is a
> backup image of the server. The image was restored to a duplicate
> hardware
> as the production. We put the clone on the production enviroment for a
> week
> and tested connectivity and network functions and it passed. Now we want
> to
> take the clone and run the upgrade and place it back onto the production
> network again. It is a backup image not meant for clone roll-out.
>
> "Miha Pihler [MVP]" wrote:
>
>> Well I guess you could take one of your DCs off the network and do the
>> upgrade if you really want to make it difficult on yourself :-)
>>
>> In this case, you would have to take off the network server holding
>> schema
>> master FSMO role and upgrade it... Once you connect it back it will send
>> new
>> information to the other domain controller...
>>
>> I am not sure how did you create your clones (can you explain a bit
>> more?) -- but I am not sure if using them is a smart idea... There are
>> few
>> things that could go wrong once you bring clone on the network... (e.g.
>> clients might not be able to talk to DC and would get access denied)...
>>
>> --
>> Mike
>> Microsoft MVP - Windows Security
>>
>> "manoa" <manoa@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:8F268A56-F2EE-4DC3-BF2B-0168D2A90807@xxxxxxxxxxxxxxxx
>> > Can I disconnect it from the network to do this? What impact will it
>> > have
>> > if
>> > it is taken offline to perform the upgrade? Does it need to send any
>> > upgrade
>> > information to the other DC or E2K3? I have an exact clone of this DC
>> > that
>> > I would want to run the upgrade on. After the upgrade is completed, I
>> > would
>> > swap it out. We have swapped the clone in its w2k form and tested it
>> > on
>> > production and everything is fine. I do not know if I can upgrade the
>> > clone
>> > to w2k3 without it being able to see the entire domain during upgrade.
>> >
>> > "Miha Pihler [MVP]" wrote:
>> >
>> >> My recommendation would be in off-hours. Server will not be available
>> >> for
>> >> the time of its upgrade and there are few reboots involved.
>> >>
>> >> Make sure that you have all drivers and 3rd party software (e.g.
>> >> antivirus)
>> >> compatible with Windows 2003 operating system.
>> >>
>> >> --
>> >> Mike
>> >> Microsoft MVP - Windows Security
>> >>
>> >> "manoa" <manoa@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> news:9CA2038E-E5F0-4C1E-8CEF-7F0184634123@xxxxxxxxxxxxxxxx
>> >> > We want to upgrade our DC which hold all the major role in the
>> >> > domain
>> >> > from
>> >> > w2k to w2k3. All the prep work has been done (forestprep,
>> >> > domainprep
>> >> > and
>> >> > mangled attributes, etc.) We have two DC in a single domain running
>> >> > W2K
>> >> > with
>> >> > all the proper SP and patches. My question is, can the in-place
>> >> > upgrade
>> >> > be
>> >> > done during normal working hours or does it need to be done when no
>> >> > one
>> >> > is
>> >> > logged on?
>> >>
>> >>
>> >>
>>
>>
>>
.
- Follow-Ups:
- Re: Upgrade w2k
- From: manoa
- Re: Upgrade w2k
- References:
- Re: Upgrade w2k
- From: Miha Pihler [MVP]
- Re: Upgrade w2k
- Prev by Date: Re: Install 2003 on new hard drive
- Next by Date: Cannot remotly connect to my windows 2003 standard
- Previous by thread: Re: Upgrade w2k
- Next by thread: Re: Upgrade w2k
- Index(es):
Relevant Pages
|
|
