Re: Renaming NetBIOS name



4. When migrating the Exchange servers, we have the same Exchange
Organization name.

Does any one has any suggestions or know about any white papers that may
help me with any of these problems?

I suggest you take a look at the migration documents at
http://www.microsoft.com/exchange/library Take a look for the multi-forest
scenarios as that tends to fit into what you want to accomplish. Likely the
most complex part of your coexistence portion of the strategy is going to be
how to overcome hooking up Exchange organizations that all have the same
names. That can be a real challenge since it's not a common scenario and
because it would be problematic for many of the available tools.

We don't really know what your coexistence strategy is, but we can infer
that you intend to live with it for longer than a short period. From that, I
have to ask: 1) what is your coexistence requirements (vs. inferred
strategy?) and 2) why do you want to have free/busy sync when you don't have
that now? Do you have an option to move faster on a per-forest/organization
basis?

There are lots of questions that come up when you are at this point of the
process. If it helps, feel free to drop a note off-line if you're
interested in other ideas about how to get to your end state. FWIW, I do
recommend migration vs. rename; as Jorge alluded to, it's not a simple thing
to rename. Effort expeneded might be better served if focused on migration
and deconstruction of the existing.

Al

"Gladys Rodriguez" <GladysRodriguez@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:867C0AF0-5C02-4B78-9909-C60ECFFC0A70@xxxxxxxxxxxxxxxx

Thanks Herb for your answer.

To explain better the problem, this is what I have:

I have domains named as:
- DOMAIN.COM with a bunch of child sites
- YYY.com with NetBIOS name YYY.

I am looking at the best way to migrate from YYY.COM to become
YYY.DOMAIN.COM(in a new forest)

To do this, I am creating new domain controllers for YYY.DOMAIN.COM and
hoping to perform the migration using the new ADMT (although I do not see
how
the new ADMT will help me with Exchange free-busy info between forests).

I want for YYY.DOMAIN.COM to use the YYY NetBIOS name at the end of the
migration. However, in order to create the trust relationship between
YYY.com and YYY.DOMAIN.COM, I cannot have the same NetBIOS name. So, if I
decide to name the new YYY.DOMAIN.COM with YYY1 NetBIOS name so the trust
relationship can be accomplished, would it be possible for me to later
rename
that NetBIOS name from YYY1 to YYY.

Thanks for your help

--
Gladys I. Rodriguez
http://www.globalstrata.com


"Herb Martin" wrote:

"Gladys Rodriguez" <GladysRodriguez@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:CA7CF8E6-764E-4671-9BBD-23FF8EF62CCD@xxxxxxxxxxxxxxxx

Hello Guys,

I am involved in a migration project that requires consolidating
several
domains into one forest. So I wanted to see what suggestions I could
get.
My
forest is 2003 and I will be bringing other 2003 domains as well as
2000
and
NT.

1. For 2003, we have thought about maybe renaming the domain but I have
only
been able to find domain rename examples within a forest. In my case,
it
would be bringing a domain from outside the forest to become a child of
my
final forest.

Renaming means what it says. Merely changing the name,
which is hard enough with AD.

There is NO Prune or Graft for domains in AD.

In addition, it seem that the rename process may not be that
reliable due to the amount of servers involved and wan connectivity
issues,
which could cause the changes not to sync.

It should be 'reliable' but it will be very tedious with
a lot of DCs.

2. For 2003, we have thought about inter-forest migration, but I am not
able
to find a lot of information about this.

What have you found or searched? ADMT (version 3 these
days) will do much/most of the work for you.

3. We would love to stay at the end with the same NetBIOS name, but I
am
unable to find a way to just rename the NetBIOS name (I cannot have the
same
NetBIOS name during the trust relationship of both forests.

If you really only want to change the NetBIOS
name then what is your REAL goal? (Don't tell
initially how you think you might do that, but
rather literally what you must accomplish....)

It might be that something trivial like a (new)
UPN (universal principal name) is all you need,
or you may have a different problem entirely.

4. When migrating the Exchange servers, we have the same Exchange
Organization name.

Does any one has any suggestions or know about any white papers that
may
help me with any of these problems?

There are tons of white papers both at Microsoft and elsewhere.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


Thanks,

--
Gladys I. Rodriguez
http://www.globalstrata.com





.



Relevant Pages

  • Re: Renaming NetBIOS name
    ... can change the way the migration will take place. ... recommend migration vs. rename; as Jorge alluded to, ... YYY.com with NetBIOS name YYY. ... YYY.DOMAIN.COM(in a new forest) ...
    (microsoft.public.windows.server.active_directory)
  • Re: Renaming NetBIOS name
    ... Gladys, it doesn't really provide enough information about the issues. ... I do understand people's expectations regarding migration of f/b and public ... YYY.com with NetBIOS name YYY. ... YYY.DOMAIN.COM(in a new forest) ...
    (microsoft.public.windows.server.active_directory)
  • Re: Renaming NetBIOS name
    ... We have considered the rename of the domain. ... In addition, the amount of fixing required afterwards, ... rename EVERY domain in the forest ... ADMTv3 Migration Tool ...
    (microsoft.public.windows.server.active_directory)
  • Re: Renaming NetBIOS name
    ... We have considered the rename of the domain. ... In addition, the amount of fixing required afterwards, ... rename EVERY domain in the forest ... ADMTv3 Migration Tool ...
    (microsoft.public.windows.server.active_directory)
  • RE: Can i change my NT 4 domain name during upgrade to W2K3 AD?
    ... give Windows 2003 NetBIOS name called "ad" or you want to create a child ... promote Windows 2003 to DC. ... If you want to rename a domain name from OLDDOMAINNAME to NEWDOMAINNAME, ... The Windows 2003 forest functionality level must be raised to Windows ...
    (microsoft.public.windows.server.migration)

Loading