in-place upgrade question

  • Thread starter Thread starter Ziek
  • Start date Start date
Z

Ziek

If the company is running a single domain with 10,000 users and only has 4
BDC's in total, a located within the same location, do you think an in-place
upgrade would be inappropriate simply due to the large user-base, or
wouldn't it be appropriate since this is not a very complicated domain model
and the company is happy with its current domain name..

Ideas?
 
Ziek said:
If the company is running a single domain with 10,000 users and only has 4
BDC's in total, a located within the same location, do you think an in-place
upgrade would be inappropriate simply due to the large user-base,

Other way around, best choice due TO the large user
population. Who wants to mess with migrating 10,000
users, and likely a similar number of computers, when
they don't have too.
or
wouldn't it be appropriate since this is not a very complicated domain model
and the company is happy with its current domain name..

I think an in-place UPGRADE is the obvious path
for such networks.

In fact, it would be very difficult to make a case
otherwise -- and any such case would have to be
strongly supported in my judgment (tie goes to
the upgrade.)

Only 5 Domain controllers? (4 BDCs and 1 PDCs)???

Be over in an afternoon.

(And most of that would be making backups and testing. <grin>)

Seriously, the most important issue is inventorying anything
running on the servers that might not be supported after the
upgrade but you get that problem any way you go.
 
awesome.

Now, if I spice this situation up a bit and state that there are a total of
2 other trust relationships within this domain, due to acquitions that
occured , but that the main 10,000 users reside within the one domain, don't
you still think that an in-place of the main domain, followed by a
restructure of the other two , would be the best route?
 
Ziek said:
awesome.

Now, if I spice this situation up a bit and state that there are a total of
2 other trust relationships within this domain, due to acquitions that
occured , but that the main 10,000 users reside within the one domain, don't
you still think that an in-place of the main domain,

It would not alter my recommendation -- except PERHAPS
to strengthen it.

Dealing with those trusts if the users accounts are change
might be even worse.
...followed by a restructure of the other two ,
would be the best route?

If you mean, restructure the other two INTO the single
(upgraded) domain that would be a likely good choice,
but more info would be needed to be as certain.
 
Ziek said:
Thanks Herb. Totally appreciate the words of wisdom..

Sure. You're welcome, but...

Why do I get the feeling that I am helping you
win a bet or an argument?

<grin>
 
Actually, the bet is with *myself*..

It seems that many people in the industry think that an in-place upgrade is
simply out of the question for "large" companies.. that this type of
migration is only suitable for "small/mid-sized" companies, and I happen to
disagree with that way of thinking.. I have always felt that in-place is
the first option to consider, and unless there are enough reasons that rule
it out as an option, there is no reason not to use the method..

So, that's why I posed the question. Just to see if I had any support out
there with my line of thinking..
 
Ziek said:
Actually, the bet is with *myself*..

It seems that many people in the industry think that an in-place upgrade
is

Where are you hearing this?
simply out of the question for "large" companies.. that this type of
migration is only suitable for "small/mid-sized" companies, and I happen to
disagree with that way of thinking..

These systems were designed to be upgraded.

And for large companies the reason are MORE
compelling in most cases.

Many people think they must upgrade when there
is really NO reason (for them) to do so.

Even hardware problems can be overcome in almost
all cases.
I have always felt that in-place is the first option to
consider, and unless there are enough reasons that rule
it out as an option, there is no reason not to use the method..

Yes. It should be the default option.

And there is seldom a good reason for migration
unless you are consolidating -- then those domains
that will be discarded must of course be migrated.
So, that's why I posed the question. Just to see if I had any support out
there with my line of thinking..

Glad to help.
 
Back
Top