Re: Win2k DC upgrade to Win2k3 at remote sites
- From: "Shaun Pillay" <shaunk@xxxxxxxxxxx>
- Date: Wed, 12 Oct 2005 11:49:25 +0100
Hi Olaf,
Many thanks for your response. I totally forgot to mention that these
servers are GC's and are running AD integrated DNS. From a hardware point of
view, the server that I will be using to build the DC at my local site is a
replica of what we have at our remote sites ie HP Proliant DL380 G4 etc -
exactly the same.
Thanks
Shaun
"Olaf Engelke [MVP Windows Server]" <oenews01@xxxxxxxx> wrote in message
news:%23%23aBPHxzFHA.820@xxxxxxxxxxxxxxxxxxxxxxx
> Hi Shaun,
> Shaun Pillay wrote:
>> I just wanted to get a few opinions re my situation. In a nutshell,
>> I'm looking at upgrading our Win2k DC's to Win2k3 at all our remote
>> sites across the world without making a trip to these sites.
>
> this could work, but there are far to much possible issues (like hardware
> / driver incompatibilities causing the server to fail on startup) which
> make a onsite represence more than recommendable.
>
>> No server hardware will be replaced during this upgrade.
>
> Which doesn't mean, that really each current hardware component is also
> supported by Windows Server 2003 OS.
>
>> The IT knowledge of staff at these sites are very limited and I would
>> prefer not asking them to assist with major issues.
>
> So go and travel.
>
>> These DC's do not hold any FSMO roles and would be a straight forward
>> upgrade.
>
> None? At least I recommend to assign the Global Catalog to them (and may
> be make them a AD integrated DNS server as well) to speed up the logon
> process for your remote users.
>
>> What I thought of doing was building a fully replicated DC at our
>> local site, on completion, amend the IP address to an address at the
>> site that it will be shipped out to, number and remove the hard disks
>> from the server, ship them out to the remote site and asking a member
>> of staff at the remote site to insert the disks in the specified
>> order. Then boot up the server, connect to it and set/check
>> replication partners etc.
> This will more likely fail, starting with the different MAC of the NIC,
> maybe also be the harddisks will not properly assigned to the HW RAID or
> drive letters are swapped and leave the system in a unbootable condition
> and so on. Much more risk than necessary that something goes wrong.
>
> Best greetings from Germany
> Olaf
.
- References:
- Win2k DC upgrade to Win2k3 at remote sites
- From: Shaun Pillay
- Win2k DC upgrade to Win2k3 at remote sites
- Prev by Date: ntdsutil cleanup problem
- Next by Date: Re: Extend AD schema & Security
- Previous by thread: Win2k DC upgrade to Win2k3 at remote sites
- Next by thread: ntdsutil cleanup problem
- Index(es):
Relevant Pages
|
