When using ADMT and ADClean, exactly what process changes the NT Primary
Account on the 5.5 mailbox to the new AD account from the old NT4 account?
And where does the ADMT Exchange Directory Wizard fit?

I think I missed a step or something. When I migrated a test user with ADMT
(keeping the source account intact) then merged the user's new AD account
with his ADC disabled account using ADClean, the 5.5 mailbox never updated
the Primary NT Account with the new AD account. No errors on ADMT or
ADClean. I tried ADC "Replicate Now" on the connection agreement, and then
even tried stopping/restarting the 5.5 directory service. The mailbox still
shows the old NT account. The user cannot log in to his 5.5 mailbox using
the new AD account. (He can still use his old NT4 account but that defeats
the purpose)

Looking for some help on this, I just found an article that says you can use
the ADMT Exchange Directory Wizard to change the Primary NT Account after
migrating all users (apparently there's no abillity to run on a per-user
basis?). But nothing I read on using ADMT and ADClean mentions the ADMT
Exchange Wizard, and I was under impression ADClean followed by next ADC
replication cycle changed NT Primary Account info on 5.5 mailbox in NT
domain.

Can I manually change the setting (using 5.5 Admin program on 5.5 server) to
new AD account, so the users can access their 5.5 mailbox using their new AD
account? The mailboxes are slated to be moved to a new Ex2003 server to be
introduced into the 5.5 site. The 5.5 server will be decommissioned.

Thanks.

RE: ADMT ADClean by v-leeli

v-leeli
Wed Jul 20 04:47:51 CDT 2005

Hi Customer,

I appreciate you taking time to write to us. However, I am afraid I am not
quite clear about your concern. Let me explain as below.

First of all, if your original intention is to migrate Exchange Server 5.5
from one domain to Exchange Server 2000/2003 in another domain, the correct
steps are as below.

1. Run ADMT to create active user accounts in your Active Directory.
2. Run Exchange Server Migration Wizard to move mailbox content from
original Exchange Server to this new-created Exchange Server.

Let me provide further explanation regarding this procedure.

1. First, actually, it is not necessary to run AD Cleanup Wizard (ADClean),
which is used in the following scenario.

If the ADC does not find matching User objects when it replicates the
Exchange mailboxes to AD, it creates new disabled User accounts, and
populates those with the mailbox attributes.

Using ADMT Feature to Avoid Twin Accounts
If you use the ADMT tool to migrate the NT4 accounts into the same domain
where the ADC-created disabled accounts reside, you can instruct ADMT to
merge the NT4 accounts directly into the existing accounts. This option in
ADMT is called Replace conflicting accounts.

Creating Twin Accounts
Otherwise, if you upgrade the NT4 domain or use ADMT to migrate the NT4
accounts to a different domain from the ADC-created disabled accounts, then
you will be left with two User accounts in the Forest for each person you
have migrated. The ADC disabled account contains the correct email
attributes, while the other account contains the correct SID and is the one
that should be used for log on.
The solution is to copy the email attributes from the disabled account to
the enabled account, and then delete the disabled account. The AD Cleanup
Wizard performs this function.

From the information above, you can see AD Cleanup Wizard is only used when
you run Active Directory Cleanup before running ADMT. For inter-org
migration, it is not necessary to run ADC first. And the recommended way is
to run ADMT to migrate account as first step.

2. Even if you have followed Exchange Migration Wizard to move Exchange
Information Store from Exchange Server 5.5 to Exchange Server 2000/2003,
the Primary NT Account attribute for Exchange Server 5.5 mailbox will never
change as new user account. Please understand if you perform inter-org
migration, Exchange Server 5.5 and Exchange Server 2003 are located in
totally different Active directory; Exchange Migration Wizard just let you
copy Exchange Server 5.5 Information Store to Exchange Server 2003.
Exchange Server 5.5 still has its own Primary NT Account. And the new
mailbox in Exchange Server 2003 is associated to new user account in new
domain.

3. The behavior that only old NT 4.0 user account can login new mailbox is
caused by all of the permissions that are necessary for mailbox access were
not migrated successfully during ADMT Migration.

The solution for this scenario is just as you mentioned to modify
permissions for the Active Directory users to include SELF rights. More
info here:

Active Directory Users Cannot Obtain Access to Mailbox After Upgrade from
Exchange 5.5
http://support.microsoft.com/?id=326018

Meanwhile, I am afraid I have not heard about ADMT Exchange Directory
Wizard. If you have further concern about ADMT Migration tool, since it is
pure Active Directory Migration tool, if you have any further concern, it
is better for you to submit your question in the newsgroup below, where a
dedicated engineer will help you explain the usage of ADMT.

microsoft.private.directaccess.win2003.activedirectory (for Windows 2000
Server)

microsoft.private.directaccess.win2000.activedirectory (For Windows Server
2003)

Thanks for your understanding regarding this. Should there is anything we
can help in the future, feel free to let me know. Thanks and have a nice
day!

Lee Li

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 your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


Re: ADMT ADClean by jremmc

jremmc
Wed Jul 20 09:49:45 CDT 2005

Hi Lee,

Every MS Doc I have read says use ADClean to merge the two accounts (new
enabled AD and ADC-created disabled) in scenarios when you have installed
Exchange 2003 before migrating user accounts to WS2K3 from NT. That is our
scenario. We upgraded HQ to WS2K3 and Ex2003. We left the branch offices at
NT4 (each office is separate NT4 domain) and Ex5.5 (each office is single
5.5 server in separate Site same Ex Org). We have ADC-created disabled
accounts for each branch user as a result. Now we are ready to migrate one
of the branch offices to HQ WS2K3 domain. We intend to migrate the user
accounts, *then* move their mailboxes to Ex2003, not the other was around,
so that their NT accounts do not need to access their Ex2003 mailboxes. We
did this in HQ (AD accounts accessing 5.5, then moving mailboxes to 2003)
with good success.

MS instructions are to use ADMT to migrate the accounts to AD, then use
ADClean to merge the enabled with the disabled. This worked in my test,
except Primary NT Account on 5.5 mailbox did not change. Yet, according to
an MS employee blog (can't remember who but think ADMT team member) about
why ADC-created disabled account has the weird random characters, after
ADClean then next ADC replication cycle the Primary NT Account on 5.5
mailbox should change. If I can find the blog again, I will post link.



"Lee Li [MSFT]" <v-leeli@online.microsoft.com> wrote in message
news:1azbbARjFHA.3472@TK2MSFTNGXA01.phx.gbl...
> Hi Customer,
>
> I appreciate you taking time to write to us. However, I am afraid I am not
> quite clear about your concern. Let me explain as below.
>
> First of all, if your original intention is to migrate Exchange Server 5.5
> from one domain to Exchange Server 2000/2003 in another domain, the
> correct
> steps are as below.
>
> 1. Run ADMT to create active user accounts in your Active Directory.
> 2. Run Exchange Server Migration Wizard to move mailbox content from
> original Exchange Server to this new-created Exchange Server.
>
> Let me provide further explanation regarding this procedure.
>
> 1. First, actually, it is not necessary to run AD Cleanup Wizard
> (ADClean),
> which is used in the following scenario.
>
> If the ADC does not find matching User objects when it replicates the
> Exchange mailboxes to AD, it creates new disabled User accounts, and
> populates those with the mailbox attributes.
>
> Using ADMT Feature to Avoid Twin Accounts
> If you use the ADMT tool to migrate the NT4 accounts into the same domain
> where the ADC-created disabled accounts reside, you can instruct ADMT to
> merge the NT4 accounts directly into the existing accounts. This option in
> ADMT is called Replace conflicting accounts.
>
> Creating Twin Accounts
> Otherwise, if you upgrade the NT4 domain or use ADMT to migrate the NT4
> accounts to a different domain from the ADC-created disabled accounts,
> then
> you will be left with two User accounts in the Forest for each person you
> have migrated. The ADC disabled account contains the correct email
> attributes, while the other account contains the correct SID and is the
> one
> that should be used for log on.
> The solution is to copy the email attributes from the disabled account to
> the enabled account, and then delete the disabled account. The AD Cleanup
> Wizard performs this function.
>
> From the information above, you can see AD Cleanup Wizard is only used
> when
> you run Active Directory Cleanup before running ADMT. For inter-org
> migration, it is not necessary to run ADC first. And the recommended way
> is
> to run ADMT to migrate account as first step.
>
> 2. Even if you have followed Exchange Migration Wizard to move Exchange
> Information Store from Exchange Server 5.5 to Exchange Server 2000/2003,
> the Primary NT Account attribute for Exchange Server 5.5 mailbox will
> never
> change as new user account. Please understand if you perform inter-org
> migration, Exchange Server 5.5 and Exchange Server 2003 are located in
> totally different Active directory; Exchange Migration Wizard just let you
> copy Exchange Server 5.5 Information Store to Exchange Server 2003.
> Exchange Server 5.5 still has its own Primary NT Account. And the new
> mailbox in Exchange Server 2003 is associated to new user account in new
> domain.
>
> 3. The behavior that only old NT 4.0 user account can login new mailbox is
> caused by all of the permissions that are necessary for mailbox access
> were
> not migrated successfully during ADMT Migration.
>
> The solution for this scenario is just as you mentioned to modify
> permissions for the Active Directory users to include SELF rights. More
> info here:
>
> Active Directory Users Cannot Obtain Access to Mailbox After Upgrade from
> Exchange 5.5
> http://support.microsoft.com/?id=326018
>
> Meanwhile, I am afraid I have not heard about ADMT Exchange Directory
> Wizard. If you have further concern about ADMT Migration tool, since it is
> pure Active Directory Migration tool, if you have any further concern, it
> is better for you to submit your question in the newsgroup below, where a
> dedicated engineer will help you explain the usage of ADMT.
>
> microsoft.private.directaccess.win2003.activedirectory (for Windows 2000
> Server)
>
> microsoft.private.directaccess.win2000.activedirectory (For Windows Server
> 2003)
>
> Thanks for your understanding regarding this. Should there is anything we
> can help in the future, feel free to let me know. Thanks and have a nice
> day!
>
> Lee Li
>
> 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 your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>



Re: ADMT ADClean by jremmc

jremmc
Wed Jul 20 12:20:30 CDT 2005

Hi Lee,

Here is the link to the blog that I mentioned in my previously posted
response.

http://blogs.technet.com/exchange/archive/2005/01/21/358240.aspx


"Lee Li [MSFT]" <v-leeli@online.microsoft.com> wrote in message
news:1azbbARjFHA.3472@TK2MSFTNGXA01.phx.gbl...
> Hi Customer,
>
> I appreciate you taking time to write to us. However, I am afraid I am not
> quite clear about your concern. Let me explain as below.
>
> First of all, if your original intention is to migrate Exchange Server 5.5
> from one domain to Exchange Server 2000/2003 in another domain, the
> correct
> steps are as below.
>
> 1. Run ADMT to create active user accounts in your Active Directory.
> 2. Run Exchange Server Migration Wizard to move mailbox content from
> original Exchange Server to this new-created Exchange Server.
>
> Let me provide further explanation regarding this procedure.
>
> 1. First, actually, it is not necessary to run AD Cleanup Wizard
> (ADClean),
> which is used in the following scenario.
>
> If the ADC does not find matching User objects when it replicates the
> Exchange mailboxes to AD, it creates new disabled User accounts, and
> populates those with the mailbox attributes.
>
> Using ADMT Feature to Avoid Twin Accounts
> If you use the ADMT tool to migrate the NT4 accounts into the same domain
> where the ADC-created disabled accounts reside, you can instruct ADMT to
> merge the NT4 accounts directly into the existing accounts. This option in
> ADMT is called Replace conflicting accounts.
>
> Creating Twin Accounts
> Otherwise, if you upgrade the NT4 domain or use ADMT to migrate the NT4
> accounts to a different domain from the ADC-created disabled accounts,
> then
> you will be left with two User accounts in the Forest for each person you
> have migrated. The ADC disabled account contains the correct email
> attributes, while the other account contains the correct SID and is the
> one
> that should be used for log on.
> The solution is to copy the email attributes from the disabled account to
> the enabled account, and then delete the disabled account. The AD Cleanup
> Wizard performs this function.
>
> From the information above, you can see AD Cleanup Wizard is only used
> when
> you run Active Directory Cleanup before running ADMT. For inter-org
> migration, it is not necessary to run ADC first. And the recommended way
> is
> to run ADMT to migrate account as first step.
>
> 2. Even if you have followed Exchange Migration Wizard to move Exchange
> Information Store from Exchange Server 5.5 to Exchange Server 2000/2003,
> the Primary NT Account attribute for Exchange Server 5.5 mailbox will
> never
> change as new user account. Please understand if you perform inter-org
> migration, Exchange Server 5.5 and Exchange Server 2003 are located in
> totally different Active directory; Exchange Migration Wizard just let you
> copy Exchange Server 5.5 Information Store to Exchange Server 2003.
> Exchange Server 5.5 still has its own Primary NT Account. And the new
> mailbox in Exchange Server 2003 is associated to new user account in new
> domain.
>
> 3. The behavior that only old NT 4.0 user account can login new mailbox is
> caused by all of the permissions that are necessary for mailbox access
> were
> not migrated successfully during ADMT Migration.
>
> The solution for this scenario is just as you mentioned to modify
> permissions for the Active Directory users to include SELF rights. More
> info here:
>
> Active Directory Users Cannot Obtain Access to Mailbox After Upgrade from
> Exchange 5.5
> http://support.microsoft.com/?id=326018
>
> Meanwhile, I am afraid I have not heard about ADMT Exchange Directory
> Wizard. If you have further concern about ADMT Migration tool, since it is
> pure Active Directory Migration tool, if you have any further concern, it
> is better for you to submit your question in the newsgroup below, where a
> dedicated engineer will help you explain the usage of ADMT.
>
> microsoft.private.directaccess.win2003.activedirectory (for Windows 2000
> Server)
>
> microsoft.private.directaccess.win2000.activedirectory (For Windows Server
> 2003)
>
> Thanks for your understanding regarding this. Should there is anything we
> can help in the future, feel free to let me know. Thanks and have a nice
> day!
>
> Lee Li
>
> 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 your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>



Re: ADMT ADClean by v-leeli

v-leeli
Thu Jul 21 04:33:46 CDT 2005

Hi Customer,

Thanks to take time to respond and clarification. Now I can understand you
implement an Exchange intra-org migration. Per your request, we have built
up the same environment; and after further research and discussion with our
senior engineers, we are afraid you may misunderstand some points. Before
moving mailbox to Exchange Server 2003, the Primary NT Account associated
with Exchange Server 5.5 mailbox will never change as new AD account. Our
tests confirm the result. Let me explain it as below.

According to your description, I can understand that you run Active
Directory Connector (ADC) first which creates disabled mailboxes in the
Active directory in Windows 2003 domain since no SIDHistroy for these user
accounts can be found in new domain by ADC. After that, you use ADMT to
migrate user accounts from branch Windows NT 4.0 domain to HQ Windows 2003
domain so that new enabled user accounts are created which are duplicated
with the disabled accounts created by ADC. It is correct now to run ADClean
to merge duplicated accounts.

However, please understand the mailbox is still stored in Exchange Server
5.5 and has not been moved to Exchange Server 2003. If it is the case,
please understand it is still associated with user account in Windows NT
domain. I think you may have a little confusion here. Please understand
ADMT is designed to create a duplicated user account in Windows 2003 domain
instead of moving user account to there. It is only after moving mailbox to
Exchange Server 2003 in new domain that SIDHistroy of duplicated account in
new domain will match the mailbox. And then the mailbox owner will become
new Windows 2003 user account. The mailbox in Exchange Server 5.5
associated with user account in Windows NT 4.0 domain will disappear.

To move mailbox across site, Exchange Server 2003 Service Pack 1 below must
be installed.
http://www.microsoft.com/downloads/details.aspx?FamilyID=42656083-784d-4e7e-
b032-2cb6433bec00&displaylang=en

The Exchange 2003 SP1 version of the Move Mailbox Wizard gives you the
option to move mailboxes across administrative groups in mixed Mode.

If your Exchange organization is in mixed mode, Exchange 2003 maps each
Exchange 5.5 site to one administrative group and one routing group in
Exchange 2000/2003. Prior to Exchange 2003 SP1, if your organization
contained Exchange 5.5 servers, you could move only mailboxes within the
same administrative group so there was no easy way to consolidate remote
Exchange 5.5 sites into a central Exchange 2003 administrative group.

In Exchange 2003 SP1, you can move mailboxes across administrative groups
by using either the Move Mailbox Wizard in Exchange System Manager or
Active Directory Users and Computers.

Hope I clarify this. If there is anything unclear, feel free to let me
know. Thanks and have a nice day!

Lee Li

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 your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


Re: ADMT ADClean by jremmc

jremmc
Thu Jul 21 12:13:04 CDT 2005

Hi Lee,

Thank you, I appreciate all the effort. I was able to manually change the
account info to the new AD account and the test user was able to log into
the 5.5 mailbox using his AD account. I will just do it that way.

Still, there is a but :-)...

Since I don't know whether I am allowed in the newsgroups to specifically
quote an article, please look again (and have your senior engineers look
too) at the blog article in the link I provided previously, near bottom
right above last table, at the sentence that *specifically says after
ADClean and the next ADC rep cycle, the 5.5 directory *is* updated with the
AD account info. That table that follows illustrates this very point. The
blog is by an MS Exchange Team member posted at their team blog site.

Given that the purpose of ADC and SRS existence is to maintain changes
between AD and 5.5 directory it makes sense that with ADC/SRS combo, the
Primary NT account change *should replicate back to the 5.5 directory. Every
other change to an Exchange attribute has (both from AD to 5.5 and 5.5 to
AD), why would that not? After all, the Primary NT account attribute resides
in the 5.5 directory, not in the NT SAM.

Also, SIDHistory is maintained with ADMT so that the new AD account can
access the resources of the source domain. I could see this is true with my
test user. For all intent and purpose, I interpret this as that the new AD
account appears as the old NT account to the NT SAM.



"Lee Li [MSFT]" <v-leeli@online.microsoft.com> wrote in message
news:QkmNNddjFHA.588@TK2MSFTNGXA01.phx.gbl...
> Hi Customer,
>
> Thanks to take time to respond and clarification. Now I can understand you
> implement an Exchange intra-org migration. Per your request, we have built
> up the same environment; and after further research and discussion with
> our
> senior engineers, we are afraid you may misunderstand some points. Before
> moving mailbox to Exchange Server 2003, the Primary NT Account associated
> with Exchange Server 5.5 mailbox will never change as new AD account. Our
> tests confirm the result. Let me explain it as below.
>
> According to your description, I can understand that you run Active
> Directory Connector (ADC) first which creates disabled mailboxes in the
> Active directory in Windows 2003 domain since no SIDHistroy for these user
> accounts can be found in new domain by ADC. After that, you use ADMT to
> migrate user accounts from branch Windows NT 4.0 domain to HQ Windows 2003
> domain so that new enabled user accounts are created which are duplicated
> with the disabled accounts created by ADC. It is correct now to run
> ADClean
> to merge duplicated accounts.
>
> However, please understand the mailbox is still stored in Exchange Server
> 5.5 and has not been moved to Exchange Server 2003. If it is the case,
> please understand it is still associated with user account in Windows NT
> domain. I think you may have a little confusion here. Please understand
> ADMT is designed to create a duplicated user account in Windows 2003
> domain
> instead of moving user account to there. It is only after moving mailbox
> to
> Exchange Server 2003 in new domain that SIDHistroy of duplicated account
> in
> new domain will match the mailbox. And then the mailbox owner will become
> new Windows 2003 user account. The mailbox in Exchange Server 5.5
> associated with user account in Windows NT 4.0 domain will disappear.
>
> To move mailbox across site, Exchange Server 2003 Service Pack 1 below
> must
> be installed.
> http://www.microsoft.com/downloads/details.aspx?FamilyID=42656083-784d-4e7e-
> b032-2cb6433bec00&displaylang=en
>
> The Exchange 2003 SP1 version of the Move Mailbox Wizard gives you the
> option to move mailboxes across administrative groups in mixed Mode.
>
> If your Exchange organization is in mixed mode, Exchange 2003 maps each
> Exchange 5.5 site to one administrative group and one routing group in
> Exchange 2000/2003. Prior to Exchange 2003 SP1, if your organization
> contained Exchange 5.5 servers, you could move only mailboxes within the
> same administrative group so there was no easy way to consolidate remote
> Exchange 5.5 sites into a central Exchange 2003 administrative group.
>
> In Exchange 2003 SP1, you can move mailboxes across administrative groups
> by using either the Move Mailbox Wizard in Exchange System Manager or
> Active Directory Users and Computers.
>
> Hope I clarify this. If there is anything unclear, feel free to let me
> know. Thanks and have a nice day!
>
> Lee Li
>
> 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 your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>



Re: ADMT ADClean by v-leeli

v-leeli
Fri Jul 22 02:44:16 CDT 2005

Hi Customer,

Thanks to take time to respond. I am glad you have successfully verified
the steps to perform the migration.

Regarding the article in Blog, I and our senior engineers have a deep
reviewing on the article. We would like to provide the following
suggestions.

1. We are not clear whether the sentence "The last ADC replication cycle
will update the 5.5 object's assoc-NT account field using the AD account's
objectSID value" does really mean that the Primary NT Account will change
to new AD account after run ADClean utility. Since we and Vicente Yim the
owner of the article are in the different team, I will write a mail to
confirm the original intention of this article.

2. No matter what Vincent mentioned in is his personal blog, it cannot
represent the official view of Microsoft.

FIRST, I think we should follow the correct migration steps from official
article from Microsoft. For your reference, I provide some official
articles about migration from Exchange Server 5.5 to Exchange Server
2000/2003.

316886 How to migrate from Exchange Server 5.5 to Exchange 2000 Server
http://support.microsoft.com/?id=316886

Note the article also applies to Exchange Server 2003.

From the article, you can see although you can first run ADC first and ADMT
second, the preferred method recommended by Microsoft is to run ADMT first
and ADC second so that it is not necessary to run ADClean. I quote the
content as below.

"Method 2:

If you are migrating user accounts and mailboxes to a new Windows 2000
domain, you can use the ADMT (Active Directory Migration Tool) to migrate
User Accounts by using security identifier (SID) history to retain
permissions. You can then use an ADC (Active Directory Connector) RCA
(Recipient Connection Agreement) to replicate mailbox attributes and
associate the new account created using ADMT with the existing Exchange 5.5
mailbox.

Important You must migrate user accounts with SID history first, using
ADMT, and then configure an ADC RCA. Failure to do this in the proper order
will result in the negative consequences associated with method 3 later in
this article. To download the ADMT utility, visit the following Microsoft
Web site:
http://www.microsoft.com/windows2000/downloads/tools/admt/default.asp"


SECOND, even though Vincent's meaning is that the Primary NT Account will
change to new AD account after run ADClean utility, I cannot agree with
him. All that I believe is based on test myself. Regarding your question, I
and my colleagues spend several hours to build up multiple test
environments, our tests results confirm that the Primary NT Account will
never change to new AD account after run ADClean utility.

I hope I clarify my meaning. If you have anything unclear, feel free to let
me know. Thanks and have a nice day!

Lee Li

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 your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


Re: ADMT ADClean by jremmc

jremmc
Sun Jul 24 09:42:51 CDT 2005

Hi Lee,

Thank you for the detailed explanation, it clarifies, and I certainly
appreciate the time and effort you made. My results matched your results. I
ended up changing the primary NT account to the AD account manually.


"Lee Li [MSFT]" <v-leeli@online.microsoft.com> wrote in message
news:xMFGrEpjFHA.944@TK2MSFTNGXA01.phx.gbl...
> Hi Customer,
>
> Thanks to take time to respond. I am glad you have successfully verified
> the steps to perform the migration.
>
> Regarding the article in Blog, I and our senior engineers have a deep
> reviewing on the article. We would like to provide the following
> suggestions.
>
> 1. We are not clear whether the sentence "The last ADC replication cycle
> will update the 5.5 object's assoc-NT account field using the AD account's
> objectSID value" does really mean that the Primary NT Account will change
> to new AD account after run ADClean utility. Since we and Vicente Yim the
> owner of the article are in the different team, I will write a mail to
> confirm the original intention of this article.
>
> 2. No matter what Vincent mentioned in is his personal blog, it cannot
> represent the official view of Microsoft.
>
> FIRST, I think we should follow the correct migration steps from official
> article from Microsoft. For your reference, I provide some official
> articles about migration from Exchange Server 5.5 to Exchange Server
> 2000/2003.
>
> 316886 How to migrate from Exchange Server 5.5 to Exchange 2000 Server
> http://support.microsoft.com/?id=316886
>
> Note the article also applies to Exchange Server 2003.
>
> From the article, you can see although you can first run ADC first and
> ADMT
> second, the preferred method recommended by Microsoft is to run ADMT first
> and ADC second so that it is not necessary to run ADClean. I quote the
> content as below.
>
> "Method 2:
>
> If you are migrating user accounts and mailboxes to a new Windows 2000
> domain, you can use the ADMT (Active Directory Migration Tool) to migrate
> User Accounts by using security identifier (SID) history to retain
> permissions. You can then use an ADC (Active Directory Connector) RCA
> (Recipient Connection Agreement) to replicate mailbox attributes and
> associate the new account created using ADMT with the existing Exchange
> 5.5
> mailbox.
>
> Important You must migrate user accounts with SID history first, using
> ADMT, and then configure an ADC RCA. Failure to do this in the proper
> order
> will result in the negative consequences associated with method 3 later in
> this article. To download the ADMT utility, visit the following Microsoft
> Web site:
> http://www.microsoft.com/windows2000/downloads/tools/admt/default.asp"
>
>
> SECOND, even though Vincent's meaning is that the Primary NT Account will
> change to new AD account after run ADClean utility, I cannot agree with
> him. All that I believe is based on test myself. Regarding your question,
> I
> and my colleagues spend several hours to build up multiple test
> environments, our tests results confirm that the Primary NT Account will
> never change to new AD account after run ADClean utility.
>
> I hope I clarify my meaning. If you have anything unclear, feel free to
> let
> me know. Thanks and have a nice day!
>
> Lee Li
>
> 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 your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>



Re: ADMT ADClean by v-leeli

v-leeli
Mon Jul 25 05:04:37 CDT 2005

Hi Customer,

Thanks for your update. I am glad my information clarifies. For your
information, I would like to provide the following additional resources by
which you can look for more Exchange support provided by Microsoft.

1. Exchange Server Technical Documentation Library: Include all Microsoft
release whitepapers about each version of Exchange Server.
http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/default.m
spx

2. Downloads for Exchange Server: Get the latest updates, service packs,
add-ins, tools, and trial software that you can download or order from
Microsoft.
http://www.microsoft.com/technet/prodtechnol/exchange/downloads/default.mspx


3. Exchange Server Developer Documentation on MSDN: Provided here are
documentation, tools, and samples for easier and faster application
development.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnanchor/ht
ml/exchangesvr.asp

4. Events and Errors for Exchange Server 2003: Search for all Exchange
related Event here.
http://www.microsoft.com/technet/support/ee/search.aspx?LCID=1033&DisplayNam
e=Exchange%20Server%202003&ProdName=Microsoft%20Exchange&MajorMinor=6.5

5. Searching the Knowledge Base: Review tips on how to receive the best
search results.
http://support.microsoft.com/default.aspx?id=fh;%5bln%5d;kbinfo

Should there is anything we can help in the future, feel free to let me
know. Thanks and have a nice day!

Lee Li

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 your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.