RE: Migration from Nt4.0 to Windows 2003 AD

Hi

Quote:One more infomration is that the Exchange 5.5 server is on the NT
domain PDC

We don't recommend our customer install Exchange 5.5 on PDC. This will
cause potential issue. For more information about this, I suggest you post
at exchange queue for assistance.

I have following questions:

1. Have you migrated the user account before you use Exchange migration
wizard?
2. Is target domain is native mode?
3. Please logon as source domain admin on target domain to migrate.


Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------
Thread-Topic: Migration from Nt4.0 to Windows 2003 AD
thread-index: AcZXMvZa9hA10AK6TBqCT7G5KA9E6w==
X-WBNR-Posting-Host: 205.210.159.50
From: =?Utf-8?B?UmljaGFyZCBQb29u?= <RichardPoon@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <C21B7312-B532-4CC0-AE3E-E1BBE90E16C6@xxxxxxxxxxxxx>
<$lJReJHVGHA.1376@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: Migration from Nt4.0 to Windows 2003 AD
Date: Mon, 3 Apr 2006 08:26:21 -0700
Lines: 117
Message-ID: <E1CD7D41-015D-4F4D-9480-F0D295A41A03@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windows.server.migration
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:23172
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.migration

Vincent,

Thank you for your suggestions. My test environment is in a flat IP
subnet
and not firewall is involved. I have sent you the complete log and see
if
you have any further idea. One more infomration is that the Exchange 5.5
server is on the NT domain PDC, which is the same in the production
environment. I don't know if that will cause any problem on it.

Thanks
Richard

"Vincent Xu [MSFT]" wrote:

Hi,

I have following suggestions:

1. Disable Firewall on both side.

2. If the problem still occurs, please send me the whole log.

My email is: v-xuwen@xxxxxxxxxxxxx


Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader
so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no
rights.
======================================================



--------------------
Thread-Topic: Migration from Nt4.0 to Windows 2003 AD
thread-index: AcZUOmWLHlwWFgV1TcK6zc/AaL0jEg==
X-WBNR-Posting-Host: 205.210.159.33
From: =?Utf-8?B?UmljaGFyZCBQb29u?=
<RichardPoon@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Migration from Nt4.0 to Windows 2003 AD
Date: Thu, 30 Mar 2006 12:42:01 -0800
Lines: 36
Message-ID: <C21B7312-B532-4CC0-AE3E-E1BBE90E16C6@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windows.server.migration
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:23146
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.migration

Hi there,

I am not sure if it is the right discussion group to post this
question,
since we need to migrate both Windows domain and Exchange 5.5
accounts.
We
currently have Windows 2003 AD domain in Mixed Mode and Exchange
5.5/2003
in the domain. We also have a subsidiary company with an independent
NT4.0
domain and Exchange 5.5.

We are planning to eliminate the NT4.0 domain and migrate all users
to
the
AD domain. When using ADMT in a test environment, I got some error
in
Exchange Directory Migration Wizard as follows:

2006-03-30 14:18:40 WRN1:7622 Unable to read the key
'ExchangeLDAPPort'
under 'Software\Microsoft\ADMT'. Using the default exchange LDAP
port
'389'.
2006-03-30 14:18:40 WRN1:7623 Unable to read the key
'ExchangeSSLPort'
under
'Software\Microsoft\ADMT'. Using the default exchange SSL port '636'.
2006-03-30 14:18:40 WRN1:7603 Unable to establish SSL connection with
the
exchange server 'SourceServer' at port 636.
2006-03-30 14:18:40 Using the regular port 389 to connect with the
exchange
server 'SourceServer'.
2006-03-30 14:18:45 ERR2:7313 Unable to change Associated Windows NT
Account
property, hr=5 Access is denied.
2006-03-30 14:18:45 ERR2:7315 Unable to update security descriptor
for
cn=TestUser,cn=Recipients,ou=SourceDomain,o=Organization, hr=5
Access is
denied.

I have followed the ADMT Help manual for preparation, and I can't
find
any
related KB from Microsoft for the errors. Moreover, I failed in
migrating
user passwords as well with the error "Unable to establish a seesion
with
the
password export server. Access is denied. Does it really require a
BDC
to
be the Password Export Server? I only have one PDC in my test
environment in
Virtual Server. Please help.

Thanks
Richard Poon






.

Relevant Pages

  • Re: Effect on users when rebooting a DC
    ... This posting is provided "AS IS" with no warranties, ... Exchange will use one DC for authentication, ... for an server fault), my manager asks me what effect it will have ...
    (microsoft.public.windows.server.active_directory)
  • RE: Queue Delay
    ... This posting is provided "AS IS" with no warranties, ... expand to Queues under your Exchange Server and then click to high-light ... the "Messages pending submission" queue, ... the hardware of your problematic Exchange 2003 Server is overloaded. ...
    (microsoft.public.exchange.setup)
  • RE: Queue Delay
    ... This posting is provided "AS IS" with no warranties, ... expand to Queues under your Exchange Server and then click to high-light ... the "Messages pending submission" queue, ... the hardware of your problematic Exchange 2003 Server is overloaded. ...
    (microsoft.public.exchange.admin)
  • RE: MessagePending Submission
    ... This posting is provided "AS IS" with no warranties, ... expand to Queues under your Exchange Server and then click to high-light ... the "Messages pending submission" queue, ... the hardware of your problematic Exchange 2003 Server is overloaded. ...
    (microsoft.public.exchange.misc)
  • RE: Queue Delay
    ... This posting is provided "AS IS" with no warranties, ... expand to Queues under your Exchange Server and then click to high-light ... the "Messages pending submission" queue, ... the hardware of your problematic Exchange 2003 Server is overloaded. ...
    (microsoft.public.exchange.misc)
Loading