cached addresses olk03 durring exchange consolidation

[Topher]

We are running into an issue with our pilot users for our Exchange
consolidation project. The issue is this, as we roll pilot users off of
their remote Exch 5.5 servers and onto a centralized Exch 2003 server,
Outlook 2003 is holding onto their cached X400 address in the .nk2 file.
Since we have over 20 sites and 6000 users that we will be consolidating,
this becomes a large problem for anyone that has the person cached in
outlook anywhere in the company. As this is a massive undertaking, we can't
keep deleting everyone's .nk2 files after every site we consolidate to make
sure that they don't get bounced messages.

Any thoughts on how to get around this? Can we somehow convert the caching
to SMTP addresses rather than X400?

Cheers,
Topher

 

[Roady [MVP]]

This depends on your migration process. If you do a move mailbox people will
still be able to find them with the old X400 address. Note that your issue
isn't limited to the nk2-file but also replying to messages they've send
before the migration.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Properly back-up and restore your Outlook data
-Creating a Permanent New Mail Desktop Alert in Outlook 2003

 

[Topher]

Hey Roady, thanks for the response.

We will be using the mailbox move in the migration process. Unfortunately,
all to aware of people replying to messages from before migration, ugh.

It's my understanding that when you use the mailbox move utility, it rewrote
the X400 address of the mailbox (more to the point the RUS stamps the
account when it lands on the new server in the new site). Thus the old X400
gets over written in both Exch 5.5 and via the ADC to AD, so there is no
record of the old X400 address in either directory. The way to keep it from
bouncing is to create an X500 address pointing back to the original server
(site) of the account that would allow for the original server to correct
delivery. The rub comes by way of the fact that we are decomissioning the
old servers after the migration.

Do you know of any utilities that can manipulate the .nk2 cache on the
client since that is where the addressing problem resides?

Cheers.

This depends on your migration process. If you do a move mailbox people will
still be able to find them with the old X400 address. Note that your issue
isn't limited to the nk2-file but also replying to messages they've send
before the migration.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Properly back-up and restore your Outlook data
-Creating a Permanent New Mail Desktop Alert in Outlook 2003

-----

We are running into an issue with our pilot users for our Exchange
consolidation project. The issue is this, as we roll pilot users off of
their remote Exch 5.5 servers and onto a centralized Exch 2003 server,
Outlook 2003 is holding onto their cached X400 address in the .nk2 file.
Since we have over 20 sites and 6000 users that we will be consolidating,
this becomes a large problem for anyone that has the person cached in
outlook anywhere in the company. As this is a massive undertaking, we
can't
keep deleting everyone's .nk2 files after every site we consolidate to
make
sure that they don't get bounced messages.

Any thoughts on how to get around this? Can we somehow convert the
caching
to SMTP addresses rather than X400?

Cheers,
Topher

 

[Roady [MVP]]

No, manipulating the nk2 cache is not the answer here. By adding an X500
e-mail address policy to your Recipient Policy you will solve all your
issues including replying to old messages. The X500 addresses on the new
server are independent from the old server so there is no issue when
decommissioning it.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Properly back-up and restore your Outlook data
-Creating a Permanent New Mail Desktop Alert in Outlook 2003

-----

Hey Roady, thanks for the response.

We will be using the mailbox move in the migration process.
Unfortunately,
all to aware of people replying to messages from before migration, ugh.

It's my understanding that when you use the mailbox move utility, it
rewrote
the X400 address of the mailbox (more to the point the RUS stamps the
account when it lands on the new server in the new site). Thus the old
X400
gets over written in both Exch 5.5 and via the ADC to AD, so there is no
record of the old X400 address in either directory. The way to keep it
from
bouncing is to create an X500 address pointing back to the original server
(site) of the account that would allow for the original server to correct
delivery. The rub comes by way of the fact that we are decomissioning the
old servers after the migration.

Do you know of any utilities that can manipulate the .nk2 cache on the
client since that is where the addressing problem resides?

Cheers.

in
message news:[email protected]...

This depends on your migration process. If you do a move mailbox people will
still be able to find them with the old X400 address. Note that your
issue
isn't limited to the nk2-file but also replying to messages they've send
before the migration.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-Properly back-up and restore your Outlook data
-Creating a Permanent New Mail Desktop Alert in Outlook 2003

-----

We are running into an issue with our pilot users for our Exchange
consolidation project. The issue is this, as we roll pilot users off
of
their remote Exch 5.5 servers and onto a centralized Exch 2003 server,
Outlook 2003 is holding onto their cached X400 address in the .nk2
file.
Since we have over 20 sites and 6000 users that we will be consolidating,
this becomes a large problem for anyone that has the person cached in
outlook anywhere in the company. As this is a massive undertaking, we
can't
keep deleting everyone's .nk2 files after every site we consolidate to
make
sure that they don't get bounced messages.

Any thoughts on how to get around this? Can we somehow convert the
caching
to SMTP addresses rather than X400?

Cheers,
Topher