Re: Migrate Ex 5.5 (on NT4) in AD 2003 mixed AD domain to Ex 2003

From: Steven Halsey [MSFT] (Stevhal_at_Online.Microsoft.com)
Date: 08/02/04


Date: Mon, 2 Aug 2004 11:51:19 -0700

I think the dot in the netbios name may be problematic for you. I was not
able to find anything specifically saying it would be but given the general
behavior of Windows and Exchange surrounding "special" characters like a dot
it may not be wise to try and put an exchange Server in the domain. I'd
suggest bringing up a new Domain in a new Forest without a netbios name with
a dot. You could host a resource forest of Exchange here and migrate your
windows Accounts using Windows Active Directory Migration Tool to the new
forest.

-- 
Steven Halsey
Stevhal@online.microsoft.com
Microsoft Exchange
Please do not send email directly to this alias.  This alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"numbatfouram" <numbatfouram@discussions.microsoft.com> wrote in message 
news:EC44135F-DF87-438B-AEC2-64BB56D933F6@microsoft.com...
> Thanks again Steven
>
> the problem is the Netbios name is as you guess "companyname.com" the AD 
> name is "location.companyname.com"
>
> i just saw an article somewhere that i might have added to favorites that 
> says ensure your domain name has no . in it before the upgrade process to 
> AD 2003 native and Ex 2003. i'm not 100% sure what issues it refers to 
> though.
>
> I'm intendending on replacing my one other DC with a Win2k3 and then 
> raising the forest level to 2k3 native then building the Ex 2003 server 
> into the existing site as the Ex 5.5 server.
>
> i got hold of a decent book on the migration process so that with the docs 
> you referenced should help lots.
>
> any other tips would be great.
>
> Thanks for the time.
> Mark
>
> "Steven Halsey [MSFT]" wrote:
>
>> You don't have to have a native mode Windows Domain, but it is 
>> recommended.
>> The Deployment Guide explains about the security groups for public 
>> folders
>> and its relationship to native mode domains.
>>
>> I don't understand what you mean about the domain name.  Are you saying 
>> your
>> Windows domain is called something like "My.Domain" as a netbios name?
>> What then is the Fully Qualified Domain Name of your Windows Domain?
>> My.Domain.Com?   I'm not really sure what the behavior would be like in 
>> this
>> case.  It might be OK or the Exchange Server might become completely
>> confused.
>>
>> -- 
>> Steven Halsey
>> Stevhal@online.microsoft.com
>> Microsoft Exchange
>>
>> Please do not send email directly to this alias.  This alias is for
>> newsgroup purposes only.
>>
>> This posting is provided "AS IS" with no warranties, and confers no 
>> rights.
>>
>>
>>
>> "numbatfouram" <numbatfouram@discussions.microsoft.com> wrote in message
>> news:20EC4F49-9152-47B9-A31D-4A95400CB242@microsoft.com...
>> > Thanks Steven
>> >
>> > i will re-post if i have any more questions after reading the link info
>> you sent.
>> > one question, am i right in thinking that my Ad (2003) has to be Native
>> before Ex 2003 can be installed? also i saw somewhere that your existing
>> domain should not have a DOT in it, ours has (netbios name)!
>> >
>> > Thanks
>> > Macca
>> >
>> > "Steven Halsey [MSFT]" wrote:
>> >
>> > > Yes it is possible.   I'd recommend looking into the Deployment Guide
>> > > (Chapter 4:Migrating from Exchange 5.5 Server)and using the 
>> > > Deployment
>> > > tools.
>> > >
>> > > Deployment Guide:
>> > >
>> http://www.microsoft.com/downloads/details.aspx?familyid=77b6d819-c7b3-42d1-8fbb-fe6339ffa1ed&displaylang=en
>> > >
>> > >
>> > > Deployment Tools:
>> > >
>> http://www.microsoft.com/downloads/details.aspx?FamilyId=271E51FD-FE7D-42AD-B621-45F974ED34C0&displaylang=en
>> > >
>> > >
>> > > -- 
>> > > Steven Halsey
>> > > Stevhal@online.microsoft.com
>> > > Microsoft Exchange
>> > >
>> > > Please do not send email directly to this alias.  This alias is for
>> > > newsgroup purposes only.
>> > >
>> > > This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> > >
>> > >
>> > >
>> > > "numbatfouram" <numbatfouram@discussions.microsoft.com> wrote in 
>> > > message
>> > > news:ADDF84D4-6EB6-4373-A307-633ADE8FBD2F@microsoft.com...
>> > > > HI
>> > > >
>> > > > i have searched but couldn't find the appropriate information. My
>> office
>> > > > has as an already existing AD 2003 \ domain in place. all FSMO 
>> > > > roles
>> and
>> > > > GC aspects seem stable. I have exchange 5.5 sp4 running on an NT4
>> server
>> > > > which is part of the AD 2003 domain. I want to add an exchange 2003
>> server
>> > > > to this site (its a single server site, no replication).
>> > > >
>> > > > What i would like to do is build the server into the same site, 
>> > > > start
>> to
>> > > > migrate users and mailboxes and then make the final changes to the 
>> > > > IMC
>> \
>> > > > routing when im happy everything is stable. I have done this before 
>> > > > on
>> a
>> > > > site while adding a second Exch 5.5 server but not a 2003. Is it
>> possible,
>> > > > anything i need to be cautious about?
>> > > >
>> > > > Would appreciate any assistance on this greatly. Im currently in 
>> > > > the
>> > > > process of reading the Ex 2003 deployment guide and the 
>> > > > exdeploy.chm
>> on
>> > > > the 2003 cd.
>> > > >
>> > > > Thanks in advance
>> > > > Macca
>> > >
>> > >
>> > >
>>
>>
>> 


Relevant Pages

  • Re: Exchange findet sekundaeren Domaenencontroller nicht
    ... For example, Exchange 2003 and Exchange 2000 were not tested without NetBIOS, but they may work without NetBIOS in ... *keiner*, dass Wins/Netbios eine notwendige Bedingung ist, sondern lediglich, dass der Herstellerselber zu Protokoll gibt, dass eine W2K/Exchange 2Kohne funktionierende Netbios Namensauflösung nicht getestet ist. ...
    (microsoft.public.de.german.exchange2000.general)
  • RE: outlook 2003 and exchange 5.5 strange connectivity problem
    ... Outlook 2003 by default will resolve the Exchange 5.5 server's NetBIOS name ... to its FQDN. ...
    (microsoft.public.exchange.connectivity)
  • RE: Cant log in with NT stand alone
    ... the company.corp.com as the netbios name during the dcpromo so a new domain ... What should i do with the last stand alone server acting as a Exchange 5.0 ... domain as the FQDN is not possible to type in as FQDN that is the netbios ...
    (microsoft.public.windows.server.migration)
  • NT to 2K3 migration - Problem with existing NetBios NT domain Name
    ... Problem with existing NetBios NT domain Name ... I am now planning to upgrade mgtamer.com from NT to Server 2003. ... will not accept the "dot" in the NetBios name. ... work perfectly (including installing DNS and AD) except that DNS will not ...
    (microsoft.public.windows.server.migration)
  • Re: NT4 NetBIOS Domain name with a dot ("."), problems upgrading to 2003 ?
    ... >I have never seen a NT4 domain with a dot. ... can be part of a NetBIOS names but the COMPUTER ... >> I was wondering if there could be a problem in migrating a NT4 Domain ...
    (microsoft.public.win2000.active_directory)