Re: Domain Change on SBS2003 R2 w/exchange 2003

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance




Hi David,

Thanks for your update.

I am glad to know the CEICW wizard works fine and things going forward
smoothly as expected. Your time and efforts are appreciated.

1. Regarding the client Connect to SBS VPN issue, since after running
CEICW, you have not performed the "Configure Remote Access" wizard to
update the domain name for VPN server, even if you have reinstalled the
connection on client, the information is still wrong, that is normal. So
what we need to do is to rerun the "Configure Remote Access" wizard first
on the SBS server to configure/update the server as VPN server to use the
new domain name, then rerun the Connection Manager(sbspackage.exe) on the
client computer to recreate a new VPN shortcut which should point to the
new domain name.

2. Regarding the "old url email address" which will be automatically added
into the user's AD properties, I suspect the related "Recipient Policies"
settings are still incorrect on the Exchange server which always configure
the clients with wrong email addresses. So please try the steps below:

a. Go to Exchange System Manager and then locate to "Recipient Policies",
b. Please check if there is any invalid recipient policy listed in right
panel. Please also open each policy and delete the "old url email address"
if any there.
c. Then go to "Recipient Update Service", To update all objects, in
Exchange System Manager right-click the two Recipient Update Services(both
Enterprise and SBS), and then click Rebuild to rebuild them all.
c. Open user's AD properties and remove the "old url email address" again
and close AD Users and Computers.
e. After that, restart the Exchange Attendant service and test if the issue
persists.

Here is an article which may help to understand how Recipient Policy
control e-mail addresses:

How to use recipient policies to control e-mail addresses in Exchange 2003
http://support.microsoft.com/kb/319201/en-us


From your description, I understand you are also willing to configure POP3
Connector later when everything is done with your Exchange server. For your
additional reference, here are some POP3 Connector related KB articles:

KB885685 How to troubleshoot the POP3 Connector in Windows Small Business
Server 2003
http://support.microsoft.com/kb/885685/en-us

KB300681 E-mail to external recipients with the same e-mail domain causes
NDR messages when using the POP3 Connector
http://support.microsoft.com/kb/300681/en-us

Hope this helps. Also, if you have any questions or concerns, please do not
hesitate to let me know.

Thank you for your time and cooperation.

Sincerely,
Robbin Meng
Microsoft Online Newsgroup Support


.



Relevant Pages

  • Re: Exchange not receiving email from Internet
    ... Recieved email for that domain from internet. ... I understand that your exchange unable to ... permission to send to this recipient". ... The Exchange server Directory Access tab error may not related to ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange Name
    ... When Exchange is responsible for an e-mail domain, ... If a local recipient with that e-mail address does not exist, ... Configure the SMTP virtual server in Exchange to send mail with unresolved ... recipients to the Internet service provider's mail server. ...
    (microsoft.public.windows.server.sbs)
  • Re: exchange basics
    ... If you find users switching between client ... often pull the mail to a different store (as in POP3) and then wonder why it ... Exchange can inform and enforce quotas on mail storage. ... Server side rules? ...
    (microsoft.public.exchange.design)
  • Re: exchange basics
    ... If you find users switching between client ... > store, so you're right, it wouldn't be a big deal. ... >> -If messages can be stored on server instead of downloading, ... > Exchange can inform and enforce quotas on mail storage. ...
    (microsoft.public.exchange.design)
  • Re: WM5, VPN via PPTP/MPPE, and direct connection to Exchange
    ... non-Microsoft VPN server, in order to access an Exchange Server on a private ... clients to Exchange via the VPN server, I have to select the the Outlook ... NOT synchronising with a client laptop. ...
    (microsoft.public.pocketpc.phone_edition)